Work procedure creation system, work procedure creation method, and program for maintenance of production machinery

Abstract

To enable even a creator having little business experience to easily create a work procedure for maintenance work of a production goods machine.SOLUTION: Disclosed is a work procedure creation system for maintenance work of a production goods machine, which includes: an acquisition part for acquiring a plurality of work items constituting the maintenance work of the production goods machine; and a determination part for determining so that, among multiple work items, the work items to be performed on each scheduled work day of multiple scheduled work days satisfy a predetermined condition and work items to be executed on each work scheduled date falls within the work time of each work scheduled date.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] The present invention relates to a work procedure creation system, a work procedure creation method, and a program for the maintenance of production machinery.

Background Art

[0002] Patent Document 1 discloses a construction machinery sales support system that provides support information based on customer information of sales targets to information recipients. A server extracts and displays, on a sales personal computer, information that matches search conditions from customer information pre-stored in a database based on search conditions related to a customer input via the sales personal computer, and outputs an extraction display signal. The server also analyzes and evaluates the extracted customer information based on at least two combinations of evaluation items used for visualization display input via the sales personal computer, and outputs an evaluation display signal for displaying the information on an information terminal on the information recipient side.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] It has been difficult for a creator with little business experience to create a work procedure for the maintenance work of production machinery.

[0005] An object of the present invention is to enable a creator with little business experience to easily create a work procedure for the maintenance work of production machinery.

Means for Solving the Problems

[0006] For this purpose, the present invention provides a work procedure creation system for the maintenance of production equipment, comprising: an acquisition unit that acquires a plurality of work items constituting the maintenance work of the production equipment; and a determination unit that determines, among the plurality of work items, work items to be performed on each work scheduled date of a plurality of work scheduled dates, such that the execution order of the plurality of work items satisfies a predetermined condition and the work items to be performed on each work scheduled date fit within the work time of each work scheduled date. The predetermined condition may be a condition that at least two of the plurality of work items are performed in a predetermined precedence relationship. The predetermined condition may also be a condition that at least two of the plurality of work items are performed together. The acquisition unit may acquire a plurality of unfinished work items. In that case, the determination unit may determine the work items to be performed on each work scheduled date based on the remaining work time of the work items in progress. The determination unit may determine the work items to be performed on each work scheduled date based on the work required time for performing each work item. In that case, the determination unit may change the work required time according to the experience level of the worker.

[0007] Furthermore, the present invention provides a work procedure creation method for the maintenance of production equipment, including: a step in which an acquisition unit of a computer acquires a plurality of work items constituting the maintenance work of the production equipment; and a step in which a determination unit of the computer determines, among the plurality of work items, work items to be performed on each work scheduled date of a plurality of work scheduled dates, such that the execution order of the plurality of work items satisfies a predetermined condition and the work items to be performed on each work scheduled date fit within the work time of each work scheduled date.

[0008] Furthermore, the present invention provides a program for causing a computer to realize a function of acquiring a plurality of work items constituting the maintenance work of production equipment, and a function of determining, among the plurality of work items, work items to be performed on each work scheduled date of a plurality of work scheduled dates, such that the execution order of the plurality of work items satisfies a predetermined condition and the work items to be performed on each work scheduled date fit within the work time of each work scheduled date.

Advantages of the Invention

[0009] According to the present invention, a work procedure for the maintenance work of production equipment can be easily created even by a creator with little work experience.

Brief Description of the Drawings

[0010]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19A

Figure 19B

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Figure 27

Figure 28

Figure 29

Figure 30A

Figure 30B

Mode for Carrying Out the Invention

[0011] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

[0012] [Background of the Present Embodiment] For example, there are industrial machine products that are generally non-standard, one-of-a-kind, and therefore expensive, such as process gas compressors as energy power sources in production activities of manufacturers, etc., and manufacturing or production equipment such as chemical plants. The maintenance work of production equipment such as production machinery targeted in this embodiment is to periodically stop the plant, disassemble or dismantle the machinery product to check its functions, or perform repair work to restore its functions in order to maintain the performance of such machinery products for a long time.

[0013] Such maintenance work needs to be carried out systematically, and for this purpose, it is necessary to create work procedures. However, in the work procedure creation work, knowledge of the functional specifications of the production equipment group constituting the plant, as well as experience and know-how regarding maintenance plans, maintenance work, and work execution are required. Therefore, there is a problem that it is difficult for only veteran creators with a certain number of years of practical experience to carry out the work procedure creation work.

[0014] Hereinafter, such maintenance work will be described as an overhaul work in this embodiment. Also, the work procedure may be in any form, but it will be described by taking a work process table (hereinafter simply referred to as a "process table") as an example.

[0015] [Configuration of the Process Table Creation System] FIG. 1 is a diagram showing an overall configuration example of a process table creation system 1 in this embodiment. As shown in the figure, the process table creation system 1 includes a process table creation device 100, a database 200, and a terminal device 300. The process table creation device 100 and the terminal device 300 are connected to a communication network such as the Internet (wide area network), and can perform data communication with each other.

[0016] The work process sheet creation device 100 is a computer such as a server-type computer. The terminal device 300 is a computer such as a laptop computer or a desktop computer. The terminal device 300 is used by a creator who creates a work process sheet for an overhaul work or a worker who performs the overhaul work. The number of terminal devices 300 is not limited to one, and may be two or more.

[0017] The work process sheet creation device 100 can access the database 200. The database 200 may be provided inside the work process sheet creation device 100, or may be provided outside the work process sheet creation device 100 and accessed through a communication network.

[0018] For example, the work process sheet creation device 100 has started an HTTP daemon. When it receives a processing request (HTTP request) sent from the terminal device 300 via a browser, it returns a processing result (HTTP response) corresponding to the processing request to the terminal device 300.

[0019] For example, the work process sheet creation device 100 transmits page data described in a web page description language to the terminal device 300 as a processing result, and the terminal device 300 outputs a page image representing the page data received from the work process sheet creation device 100 to the display unit of its own device.

[0020] [Hardware Configuration of Work Process Sheet Creation Device] FIG. 2 is a diagram showing an example of the hardware configuration of the work process sheet creation device 100 in the present embodiment.

[0021] As shown in the figure, the process sheet creation device 100 is realized by, for example, a general-purpose PC (Personal Computer) or the like, and includes a CPU 11 which is an arithmetic means, a main memory 12 which is a storage means, and a magnetic disk device (HDD: Hard Disk Drive) 13. Here, the CPU 11 executes various programs such as an OS (Operating System) and application software, and realizes each function of the process sheet creation device 100. Further, the main memory 12 is a storage area for storing various programs and data used for their execution. And the HDD 13 is a storage area for storing input data for various programs and output data from various programs and the like.

[0022] In addition, the process sheet creation device 100 includes a communication I / F 14 for communicating with the outside, a display mechanism 15 including a video memory and a display, an input device 16 such as a keyboard and a mouse, and a driver 17 for reading and writing data to and from a storage medium. Note that FIG. 2 only illustrates the hardware configuration when the process sheet creation device 100 is realized by a computer system, and the process sheet creation device 100 is not limited to the illustrated configuration.

[0023] [Configuration of Process Sheet Creation Device] FIG. 3 is a block diagram showing a functional configuration example of the process sheet creation device 100 in the present embodiment. As shown in the figure, the process sheet creation device 100 includes a reception unit 101, a work information acquisition unit 102, a process sheet creation unit 103, a screen creation unit 104, and a transmission unit 105.

[0024] The reception unit 101 receives the information input on the screen displayed on the terminal device 300.

[0025] Based on the information received by the reception unit 101, the work information acquisition unit 102 acquires the work information regarding the overhaul work stored in the database 200. Specifically, the work information acquisition unit 102 acquires the information of the overhaul work plan as the work information. In addition, the construction information acquisition unit 102 acquires, as construction information, information on a plurality of business items associated with the overhaul construction plan information and information on a plurality of sub-items constituting each business item. The plurality of business items or the plurality of sub-items are an example of a plurality of work items constituting the maintenance work of the production equipment machine, and the construction information acquisition unit 102 is an example of an acquisition unit that acquires a plurality of work items. At this time, the construction information acquisition unit 102 may extract information on items with unfinished work from the information on the plurality of business items or the plurality of sub-items. In this case, the construction information acquisition unit 102 is an example of an acquisition unit that acquires a plurality of unfinished work items.

[0026] Based on the information received by the reception unit 101, the information on the planned work date stored in the database 200, and the information acquired by the construction information acquisition unit 102, the process schedule creation unit 103 creates a process schedule for the overhaul construction and outputs the information on the process schedule to the screen creation unit 104. Specifically, the process schedule creation unit 103 arranges the plurality of business items or the plurality of sub-items acquired by the construction information acquisition unit 102 so that their execution order satisfies a predetermined condition. Here, the predetermined conditions include a first condition that a business item with a higher priority is executed first, a second condition that another sub-item is executed before or after a certain sub-item, and a third condition that a certain sub-item and another sub-item are executed simultaneously. The process schedule creation unit 103 is an example of a determination unit that determines, among the plurality of work items, the work items to be executed on each of the plurality of planned work dates so that the execution order of the plurality of work items satisfies a predetermined condition. The second condition is an example of a condition that at least two of the plurality of work items are executed in a predetermined order, and the third condition is an example of a condition that at least two of the plurality of work items are executed together. In addition, the process schedule creation unit 103 distributes a plurality of sorted business items or a plurality of sub-items to each scheduled work date stored in the database 200. At this time, the process schedule creation unit 103 performs this distribution using the work required time necessary to perform the plurality of business items or the plurality of sub-items. In particular, for the business items or sub-items during work, the process schedule creation unit 103 performs this distribution using the remaining work time required to perform the remaining part of the business item or sub-item. Also, the process schedule creation unit 103 may change the work required time based on the degree of work experience of the worker. For example, if the number of years of work experience of the worker is long, the process schedule creation unit 103 may shorten the work required time. The process schedule creation unit 103 is an example of a determination unit that determines, among a plurality of work items, the work items to be implemented on each scheduled work date of the plurality of scheduled work dates so that the work items to be implemented on each scheduled work date fit within the work time of each scheduled work date. The process schedule creation unit 103 is also an example of a determination unit that determines the work items to be implemented on each scheduled work date based on the work required time required to implement each work item. The process schedule creation unit 103 is also an example of a determination unit that determines the work items to be implemented on each scheduled work date based on the remaining work time of the work items during work. The process schedule creation unit 103 is also an example of a determination unit that changes the work required time according to the degree of experience of the worker.

[0027] The screen creation unit 104 creates a screen including the process schedule created by the process schedule creation unit 103.

[0028] The transmission unit 105 transmits the screen created by the screen creation unit 104 to the terminal device 300.

[0029] [Configuration of Database] First, the structure of the basic data stored in the database 200 will be described. Specifically, the structure of the data related to the formulation of the overhaul work plan and the structure of the data related to the creation of the process schedule for the overhaul work will be described.

[0030] FIG. 4 is a diagram showing an example of the structure of data related to the formulation of an overhaul work plan for each production facility machine constituting a plant. In the figure, data representing the production equipment machine is associated with data representing unit (A1), unit (A2), and unit (A3). Here, a unit refers to a process gas supply system, an XX manufacturing device, etc. Also, data representing unit (A1) is associated with data representing main parts (A1-B1), main parts (A1-B2), and main parts (A1-B3). Here, a main part refers to a compressor main body, an auxiliary system, etc. Note that data representing main parts is similarly associated with data representing unit (A2) and unit (A3), but the illustration thereof is omitted. Also, data representing main part (A1-B1) is associated with data representing inspection points (A1-B1-C1), inspection points (A1-B1-C2), and inspection points (A1-B1-C3). Here, an inspection point refers to a gas-related unit, an oil-related unit, etc. Note that data representing main parts is similarly associated with data representing main part (A1-B2) and main part (A1-B3), but the illustration thereof is omitted. Also, data representing inspection point (A1-B1-C1) is associated with data representing inspection contents (A1-B1-C1-D1), inspection contents (A1-B1-C1-D2), and inspection contents (A1-B1-C1-D3). Here, inspection contents refer to appearance inspection, disassembly inspection, replacement with a new one, repair, etc. Note that data representing inspection contents is similarly associated with data representing inspection point (A1-B1-C2) and inspection point (A1-B1-C3), but the illustration thereof is omitted. Also, data representing inspection content (A1-B1-C1-D1) is associated with data representing treatment contents (E1), treatment contents (E2), and treatment contents (E3). Here, treatment contents refer to recovery by normal treatment, recovery by implementing operation adjustment, etc., recovery by emergency repair, recovery by repair equivalent to replacement, recovery by replacement, etc. Note that data representing treatment contents is similarly associated with data representing inspection content (A1-B1-C1-D2) and inspection content (A1-B1-C1-D3), but the illustration thereof is omitted.

[0031] FIG. 5 is a diagram showing an example of the structure of data for creating a process table for overhaul work for each production machine. In the figure, data representing inspection items (A1 - B1 - C1 - D1), inspection items (A1 - B1 - C1 - D2), and inspection items (A1 - B1 - C1 - D3) are associated with the data representing the production machine. Here, as described above, the inspection items are visual inspection, disassembly inspection, replacement with new parts, repair, etc. Also, data representing business items (X001), business items (X002), and business items (X003) are associated with the data representing the inspection item (A1 - B1 - C1 - D1). Here, the business items are visual inspection work, disassembly inspection work, replacement with new parts work, repair work, etc. Note that data representing business items are similarly associated with the data representing the inspection items (A1 - B1 - C1 - D2) and (A1 - B1 - C1 - D3), but the illustration thereof is omitted. Also, data representing sub - items (X001 - 001), sub - items (X001 - 002), and sub - items (X001 - 003) are associated with the data representing the business item (X001). Here, the sub - items are pre - inspection safety measures work, inspection work, post - inspection operation confirmation and adjustment work, safety measure restoration work, etc. in the visual inspection work. Note that data representing sub - items are similarly associated with the data representing the business items (X002) and (X003), but the illustration thereof is omitted.

[0032] FIG. 6 is a diagram showing a configuration example of the database 200 in the present embodiment. As shown in the figure, the database 200 includes a construction plan management DB209, a business item management DB210, a sub - item management DB211, a work plan management DB212, a work performance management DB213, a work scheduled date management DB214, and a worker management DB215. Note that the illustration of the DB for realizing the data structure shown in FIG. 4 is omitted.

[0033] The construction plan management DB209 is a database that manages the planned content of overhaul work for each unit of production equipment machines. Fig. 7 is a diagram showing a configuration example of the construction plan management DB209. As shown in the figure, the construction plan management DB209 includes a construction ID, a construction execution time, a machine ID, a unit ID, a main part ID, an inspection point ID, and an inspection content ID.

[0034] The construction ID is an ID that identifies the overhaul work and is assigned for each opportunity of regular inspection or repair work of the plant. The construction execution time is the time when the overhaul work was carried out. The construction execution time may be set, for example, by the year and month of construction execution. The machine ID is an ID that identifies the production equipment machine for which the overhaul work is carried out. The unit ID is an ID that identifies the unit of the production equipment machine for which the overhaul work is carried out. The main part ID is an ID that identifies the main part of the production equipment machine for which the overhaul work is carried out. The inspection point ID is an ID that identifies the inspection point of the production equipment machine for which the overhaul work is carried out. The inspection content ID is an ID that identifies the inspection content of the production equipment machine for which the overhaul work is carried out.

[0035] The business item management DB210 is a database that manages the business items that make up the overhaul work. Fig. 8 is a diagram showing a configuration example of the business item management DB210. As shown in the figure, the business item management DB210 includes a business item ID, a business item name, an inspection point ID, an inspection content ID, and a priority. In the business item management DB210, the business item ID is the primary key.

[0036] The business item ID is an ID that identifies a business item, which is a higher-level work item that summarizes the tasks of the sub-items described later. The business item name is the name of this business item. The inspection point ID is an ID that identifies the inspection points included in the work of this business item, and the inspection content ID is an ID that identifies the inspection content included in the work of this business item. The priority is the priority of the entire overhaul work for this business item. For example, it may be set in three levels: high, medium, and low. The priority is, for example, the priority of the setup of the inspection work determined from the constraint conditions in the design specifications of the unit of the production equipment, etc.

[0037] The sub-item management DB211 is a database that manages the sub-items that make up the business items of the overhaul work. FIG. 9 is a diagram showing a configuration example of the sub-item management DB211. As shown in the figure, the sub-item management DB211 includes a sub-item ID, a sub-item name, an inspection point ID, an inspection content ID, a standard working time, a difficulty level, a weather influence degree, a contractor cooperation degree, a previous implemented sub-item group, a subsequent implemented sub-item group, a simultaneously implemented sub-item group, and a business item ID. In the sub-item management DB211, the sub-item ID serves as the primary key.

[0038] The sub-item ID is an ID that identifies the smallest unit of work items for performing the inspection content for each inspection location of the overhaul work. The sub-item name is the name of this sub-item. The inspection location ID is an ID that identifies the inspection location included in the work of this sub-item. The inspection content ID is an ID that identifies the inspection content included in the work of this sub-item. The standard working time is the required time for the standard work when one operator performs the work of the sub-item. For example, it may be set in units of time. The difficulty level is the difficulty level of the work of this sub-item. For example, it may be set in a five-level evaluation from low to high as 1, 2, 3, 4, 5. The weather influence degree is the degree to which the work of this sub-item is affected by the weather. For example, it may be set in a three-level evaluation from low to high as 1, 2, 3. The degree of cooperation with contractors is the degree to which the work of this sub-item is coordinated with external contractors. It may be set in a five-level evaluation from low to high as 1 (none), 2, 3, 4, 5 (100% work entrusted). The previous implementation sub-item group is another sub-item group that must be implemented before the work of this sub-item is carried out. The subsequent implementation sub-item group is another sub-item group that is preferably implemented promptly after the work of this sub-item is carried out. The simultaneous implementation sub-item group is another sub-item group for which it is effective to carry out the work simultaneously with the work of this sub-item. The business item ID is an ID that identifies the business item, which is the higher-level work item that aggregates the work of this sub-item.

[0039] The work plan management DB212 is a database that manages the work plan by work date. Figure 10 is a diagram showing a configuration example of the work plan management DB212. As shown in the figure, the work plan management DB212 includes a construction ID, a planned work date, a business item ID, a sub-item ID, a work order, and an operator ID. In the work plan management DB212, the combination of the planned work date, the business item ID, and the sub-item ID serves as the primary key.

[0040] The construction ID is an ID assigned to the plant for each opportunity of regular inspection and repair work. The planned work date is the date on which the work is scheduled to be carried out, and it is preferably set in the format of YYYYMMDD. The business item ID is an ID that identifies the business item. The sub-item ID is an ID that identifies the sub-item of the business item. The work order is the order of work within the work execution date, and it is preferably set by an integer value of 1 or more. The worker ID is an ID that identifies the worker who performs the work. In this embodiment, it is assumed that the worker ID is set when the worker is input in the "Special Notes" column 491 on the system screen 490 (see Fig. 26).

[0041] The work performance management DB213 is a database that manages work performance by work date. Fig. 11 is a diagram showing a configuration example of the work performance management DB213. As shown in the figure, the work performance management DB213 includes a construction ID, a work execution date, a business item ID, a sub-item ID, a worker ID, a work result, and an estimated work time. In the work performance management DB213, the combination of the work execution date, the business item ID, and the sub-item ID is the primary key.

[0042] The construction ID is an ID assigned to the plant for each opportunity of regular inspection and repair work. The work execution date is the date on which the work was carried out, and it is preferably set in the format of YYYYMMDD. The business item ID is an ID that identifies the business item, and the sub-item ID is an ID that identifies the sub-item of the business item. The worker ID is an ID that identifies the worker who performed the work of the sub-item of the business item. The work result is the work result on the work execution date of the work of the sub-item of the business item, and it is preferably set to any one of work completed, in progress, and not started. The estimated work time is the estimated work time on the work execution date of the work of the sub-item of the business item.

[0043] In this embodiment, based on the construction ID, the planned work date, and the business item ID as keys, the work plan management DB212 is searched, and the system screen 440 (see Fig. 21) is configured based on the search result. Then, when the work performance is registered, it is assumed that the values are stored in the work performance management DB213 in the above data format.

[0044] The work schedule date management DB214 is a database that manages work schedule dates. FIG. 12 is a diagram showing a configuration example of the work schedule date management DB214. As shown in the figure, the work schedule date management DB214 includes a construction ID, a work schedule date, the number of workers, work progress, weather prediction, and work hours. In the work schedule date management DB214, the work schedule date is the primary key.

[0045] The construction ID is an ID assigned to each opportunity for regular inspection and repair work in the plant. The work schedule date is the date on which the work is scheduled to be carried out, and it is preferably set in the format of YYYYMMDD. The number of workers is the number of workers who will perform the work on the work schedule date. The work progress is any one of the states of not started (the state immediately after registering the work schedule date), work started, plan made, and work completed. The weather prediction is any one of the weather prediction information of sunny, cloudy, light rain, and rain. The weather prediction may be obtained and set based on the work schedule date from the weather prediction information publicly available on the Internet for that work schedule date. The work hours are the work hours on the work schedule date. In this embodiment, the work hours are set to a fixed value (for example, 7 hours), but a means for setting the work hours in units of work schedule dates may be provided and set by this means.

[0046] In this embodiment, the system screen 420 (see FIG. 16) is configured with the construction ID and the work schedule date as keys. Then, when a work date is additionally registered, it is assumed that values are stored in the work schedule date management DB214 in the above data format. However, the work progress is set to "not started" immediately after a work date is additionally registered on the system screen 420, "work started" immediately after the process table is automatically generated, and "work completed" immediately after all sub-items of the work schedule date are registered on the system screen 440 (see FIG. 21). In addition, when the work progress is changed on the system screen 470 (see FIG. 24), the changed value is set for the work progress.

[0047] The operator management DB215 is a database for managing operators. FIG. 13 is a diagram showing a configuration example of the operator management DB215. As shown in the figure, the operator management DB215 includes an operator ID, an operator name, and a degree of business experience. In the operator management DB215, the operator ID serves as the primary key.

[0048] The operator ID is an ID for identifying an operator, and the operator name is the name of the operator. The degree of business experience is the degree of business experience in the overhaul work during operation, and may be set as a decimal value greater than 0 and less than 1. The degree of business experience approaches 0 as the operator has more years of business experience.

[0049] [Operation of the process schedule creation device] FIG. 14 is a diagram showing the system screen 310. The system screen 310 is the top screen of the process schedule creation system 1 displayed on the terminal device 300 in the simplest embodiment. Immediately after this screen is launched, a list of plants is displayed in the "Customer" column 311 based on the correspondence information (not shown) between the production equipment machines and units for each plant stored in the database 200. Then, the content and scope of the overhaul work plan for each plant and each production equipment machine are displayed and can be confirmed. Here, although the system screen 310 including a list of units constituting the production equipment machine is displayed, it is not limited to this. For example, a system screen including a list of main parts constituting the unit or a system screen including measures for inspection points of the inspection content constituting the main parts may be displayed.

[0050] When the "Process Schedule Start" button 312 is pressed on the system screen 310, the screen transitions to the system screen 410 for each classification table for the plant and production equipment machine that is currently selected and displayed in the "Customer" column 311 of the system screen 310. The classification table is the unit for creating the content and scope of the overhaul work plan. FIG. 15 is a diagram showing the system screen 410. This system screen 410 is the top screen for creating a process schedule for each classification table. However, the system screen 410 is an example of a screen when a process schedule for the classification table "OH in 21st year" has already been created. When the system screen 410 is launched immediately after the creation of the classification table, since the process schedule has not been created yet, the work schedule by business item and work date in units of "Main Part - Inspection Point" on the system screen 410 will be blank. Specifically, the state will be such that not a single "●", which means there is a work schedule, is displayed. Also, the construction period of the classification table currently selected and displayed in the "Classification Table" column 411 of the system screen 410 is preferably calculated from the correspondence information (not shown) between the overhaul work for each plant, the overhaul work start date, and the number of days the plant can be stopped, which is stored in the database 200. And in this embodiment, the construction period is displayed in units of weeks.

[0051] On the system screen 410, when the "Add Working Day" button 412 is clicked as preprocessing for automatically creating a process schedule, the system screen 420 is displayed on the terminal device 300. FIG. 16 is a diagram showing the system screen 420. After the work date and the number of workers are selected or input on the system screen 420, when the "Add" button 421 is pressed, the dates on which work is to be carried out within the construction period are registered in the work schedule management DB 214. Assuming that the "Automatic Generation of Process Schedule" button 413 is pressed on the system screen 410 with all working days during the construction period thus registered in advance, the process schedule creation device 100 automatically generates a process schedule by the first process schedule creation logic based on the information regarding the current overhaul construction plan, the information regarding work items, and the information regarding work schedule dates. Here, the information regarding the current overhaul construction plan is the construction plan management DB 209, the information regarding work items is the business item management DB 210 and the sub-item management DB 211, and the information regarding work schedule dates is the work schedule management DB 214.

[0052] FIG. 17 is a flowchart showing the flow of the first process schedule creation logic.

[0053] As shown in the figure, in the process schedule creation device 100, first, the construction information acquisition unit 102 extracts an information group regarding the current overhaul construction plan (step 601). Specifically, the construction information acquisition unit 102 searches the construction plan management DB 209 using the machine ID for specifying the overhaul construction target and the construction ID for specifying the overhaul construction as keys. Then, the construction information acquisition unit 102 extracts an information group regarding the work target unit, main part, inspection point, and inspection content in the current overhaul construction plan.

[0054] Next, the construction information acquisition unit 102 extracts an information group regarding the business items to be included in the process schedule (step 602). Specifically, the construction information acquisition unit 102 searches the business item management DB 210 using the inspection points and the inspection content group in the current overhaul construction plan as keys, and extracts an information group regarding the business items to be included in the process schedule.

[0055] Next, the construction information acquisition unit 102 extracts an information group related to sub-items of the business items for which the process table is to be created (step 603). Specifically, the construction information acquisition unit 102 searches the sub-item management DB 211 using the information group related to the business items in the current overhaul construction plan as a key, and extracts the information group related to the sub-items of the business items for which the process table is to be created.

[0056] Then, in the process table creation device 100, the process table creation unit 103 performs an alignment process for aligning the sub-item group of the business items (step 604). Specifically, the process table creation unit 103 performs the alignment process based on the information group related to the sub-items of the business items in the current overhaul construction plan extracted in step 603.

[0057] Next, the process table creation unit 103 performs a first allocation process for allocating the aligned sub-item group of the business items to working days (step 605). Specifically, the process table creation unit 103 performs the first allocation process based on the alignment result of the sub-item group of the business items in the current overhaul construction plan in step 604.

[0058] Thereafter, the screen creation unit 104 creates the system screen 410 and the system screen 430 based on the allocation result (step 606). Specifically, the screen creation unit 104 creates the system screen 410 and the system screen 430 based on the allocation result of the sub-item group of the business items in the current overhaul construction plan to the working days in step 605.

[0059] FIG. 18 is a flowchart showing the flow of the alignment process in step 604 of FIG. 17.

[0060] As shown in the figure, first, the process table creation unit 103 performs a first sorting process on the small item groups of business items (step 641). Specifically, the process table creation unit 103 extracts the priority levels of the business item management DB 210 using the business item ID of each small item as the key from the information group regarding the small items of the business items in the current overhaul work plan. Then, the process table creation unit 103 sorts the small item groups with the first sorting condition being in descending order of this priority level and the second sorting condition being in ascending order of the small item ID.

[0061] Then, the process table creation unit 103 sets the small items in the current overhaul work plan as the processing targets in the order sorted by the first sorting process in step 641 (step 642).

[0062] Next, the process table creation unit 103 extracts the pre-implementation small item group and the post-implementation small item group for the current processing target small item (step 643).

[0063] Next, the process table creation unit 103 performs a second sorting process on these small item groups (step 644). Specifically, when a pre-implementation small item group is set for the current processing target small item, the process table creation unit 103 sorts that small item group in ascending order of the small item ID in front of the current processing target small item. If the small item to be sorted in front of the current processing target small item has already been sorted in front of the current processing target small item, this already sorted small item is excluded from the second sorting process. Also, when a post-implementation small item group is set for the current processing target small item, the process table creation unit 103 sorts that small item group in ascending order of the small item ID behind the current processing target small item. If the small item to be sorted behind the current processing target small item has already been sorted behind the current processing target small item, this already sorted small item is excluded from the second sorting process.

[0064] Next, the process schedule creation unit 103 determines whether all sub-items have been set as processing targets (step 645). If not all sub-items have been set as processing targets, that is, if there are sub-items that have not been set as processing targets, the process schedule creation unit 103 returns the process to step 642 and sets the next sub-item as the processing target. If all sub-items have been set as processing targets, the process schedule creation unit 103 advances the process to step 646.

[0065] Thereafter, the process schedule creation unit 103 sets the sub-items in the current overhaul work plan as processing targets in the order sorted by the second sorting process in step 644 (step 646).

[0066] Next, the process schedule creation unit 103 extracts a group of co-performable sub-items for the currently targeted sub-item (step 647).

[0067] Next, the process schedule creation unit 103 performs a third sorting process on the group of sub-items including this group of sub-items and the currently targeted sub-item (step 648). Specifically, when a group of co-performable sub-items is set for the currently targeted sub-item, the process schedule creation unit 103 sorts the group of sub-items and the currently targeted group of sub-items according to the first to third sorting conditions. Here, the first sorting condition may be in descending order of the degree of weather influence, the second sorting condition may be in descending order of the degree of contractor cooperation, and the third sorting condition may be in descending order of difficulty. However, the correspondence between the first to third sorting conditions and the degree of weather influence, the degree of contractor cooperation, and the difficulty is not limited to the above and may be interchanged. In addition, when the group of co-performable sub-items has already been sorted before and after the currently targeted sub-item, this already sorted sub-item is excluded from the target of the third sorting process.

[0068] Next, the process schedule creation unit 103 determines whether all sub-items have been set as processing targets (step 649). If not all sub-items have been set as processing targets, that is, if there are sub-items that have not been set as processing targets, the process schedule creation unit 103 returns the process to step 646 and sets the next sub-item as the processing target. If all sub-items have been set as processing targets, the process schedule creation unit 103 returns the process to FIG. 17.

[0069] FIG. 19A and FIG. 19B are flowcharts showing the flow of the first sorting process in step 605 of FIG. 17.

[0070] As shown in FIG. 19A, first, the process schedule creation unit 103 extracts an information group regarding the scheduled work dates in the current overhaul work (step 661). Specifically, the process schedule creation unit 103 searches the work schedule management DB 214 using the work ID that identifies the overhaul work as a key, and extracts the information group regarding the scheduled work dates after the day following the process schedule creation date.

[0071] Next, the process schedule creation unit 103 processes the scheduled work dates extracted in step 661 in ascending order (step 662).

[0072] Next, the process schedule creation unit 103 calculates the allocable working hours for the current scheduled work date to be processed (step 663). Specifically, the process schedule creation unit 103 extracts the number of workers and the working hours for the current scheduled work date to be processed from the work schedule management DB 214, and calculates the allocable working hours by calculating "allocable working hours = number of workers × working hours". Note that, initially, the allocable working hours calculated in this way are used, but afterwards, those calculated in step 682 or step 685 described later are used.

[0073] Next, the process schedule creation unit 103 determines whether the weather forecast is rain or not (step 664). Specifically, the process schedule creation unit 103 extracts the weather forecast for the current scheduled work date to be processed from the work schedule management DB 214, and based on this, determines whether the weather forecast is rain or not. If the weather forecast is rain, the process schedule creation unit 103 returns the process to step 662 and sets the next scheduled work date as the processing target.

[0074] On the other hand, if the weather forecast is not rain, the process schedule creation unit 103 sets the sub-items in the current overhaul work plan as the processing targets in the order sorted by the sorting process in FIG. 18 (step 665).

[0075] Next, the process schedule creation unit 103 sets the standard operation time defined for the current item to be processed (hereinafter referred to as the "current standard operation time") as the time required for the operation of the current item to be processed (hereinafter referred to as the "current operation required time") (step 666). Specifically, the process schedule creation unit 103 extracts the standard operation time from the item management DB 211 using the item ID of the current item to be processed as a key, sets it as the current standard operation time, and uses this as the current operation required time as it is.

[0076] Next, the process schedule creation unit 103 sets the standard operation time defined for the next item to be processed (hereinafter referred to as the "next standard operation time") as the time required for the operation of the next item to be processed (hereinafter referred to as the "next operation required time") (step 667). Specifically, the process schedule creation unit 103 extracts the standard operation time from the item management DB 211 using the item ID of the next item to be processed as a key, sets it as the next standard operation time, and uses this as the next operation required time as it is.

[0077] Next, the process schedule creation unit 103 determines whether the current operation required time is less than or equal to the allocable operation time on the scheduled work date of the current item to be processed (step 668).

[0078] If the current operation required time is less than or equal to the allocable operation time, as shown in FIG. 19B, the process schedule creation unit 103 determines the current item to be processed as the work on the scheduled work date of the current item to be processed (step 681). Specifically, the process schedule creation unit 103 stores the information of the determined item in the work plan management DB 212 according to the construction ID, scheduled work date, business item ID, item ID, and work order. Note that the process schedule creation unit 103 may set the sequential number on the scheduled work date of the current item to be processed as the work order. In addition, the process schedule creation unit 103 subtracts the allocable operation time on the scheduled work date of the current item to be processed (step 682). Specifically, the process schedule creation unit 103 subtracts the allocable operation time by calculating "allocable operation time = allocable operation time - current operation required time".

[0079] On the one hand, when the current standard working hours are not less than the allocable working hours, as shown in FIG. 19B, the process schedule creation unit 103 determines a part of the current sub-items to be processed as the work on the scheduled work date of the current process target (step 683). A part of the current sub-items to be processed is the amount corresponding to the allocable working hours on the scheduled work date of the current process target among the current sub-items to be processed. Specifically, the process schedule creation unit 103 stores the information of the determined sub-items in the work plan management DB 212 according to the construction ID, scheduled work date, business item ID, sub-item ID, and work order. Incidentally, the process schedule creation unit 103 may set the sequential number on the scheduled work date of the current process target as the work order. In addition, the process schedule creation unit 103 calculates the new required working hours for the remaining work of the current sub-items to be processed (step 684). Specifically, the process schedule creation unit 103 calculates the new required working hours by calculating "new required working hours = current required working hours - allocable working hours on the scheduled work date of the current process target". Furthermore, the process schedule creation unit 103 sets the allocable working hours on the scheduled work date of the current process target to 0 (step 685).

[0080] Next, the process schedule creation unit 103 determines whether the required working hours for the next work exceed the allocable working hours (step 686). If the required working hours for the next work do not exceed the allocable working hours, the process schedule creation unit 103 returns the process to step 665 in FIG. 19A and sets the next sub-item as the process target. If the required working hours for the next work exceed the allocable working hours, the process schedule creation unit 103 determines whether all the scheduled work dates have been set as the process targets (step 687). If not all the scheduled work dates have been set as the process targets, that is, if there is a scheduled work date that has not been set as the process target, the process schedule creation unit 103 determines whether all the sub-items have been allocated (step 688). If not all the sub-items have been allocated, that is, if there is a sub-item that has not been allocated, the process schedule creation unit 103 returns the process to step 662 in FIG. 19A and sets the next scheduled work date as the process target. On the other hand, when all work scheduled days are targeted for processing in step 687, or when all sub-items are allocated in step 688, the process schedule creation unit 103 returns the process to FIG. 17.

[0081] In addition, in this operation example, there may be a case where, based on the work scheduled days registered in advance, it is not possible to allocate all sub-items to their respective work scheduled days. In such a case, the process schedule creation device 100 may display a message to that effect on the screen in step 606 of the first process schedule creation logic, add the work scheduled days, and then re-execute the first process schedule creation logic.

[0082] When the process schedule is automatically created by the first process schedule creation logic, the result is registered in the work plan management DB 212 and displayed on the system screen 410 as shown in FIG. 15.

[0083] On this system screen 410, the process schedule creation result is displayed in a form where a "●" is printed for business items that include one or more sub-items with a scheduled execution on the work scheduled day. Also, on the system screen 410, when the "Business Item" button 414 for each work scheduled day is clicked after the automatic generation of the process schedule, the terminal device 300 launches the system screen 430. FIG. 20 is a diagram showing the system screen 430. On this system screen 430, the business items for the selected work scheduled day are displayed in a list.

[0084] In this embodiment, after the operator has carried out the work, the operator registers the work performance of the workday in units of sub-items of business items. Specifically, when the hyperlink 415 set in the "●" of the business item for which the work has been carried out is clicked on the system screen 410 in FIG. 15, the system screen 440 is displayed on the terminal device 300. FIG. 21 is a diagram showing the system screen 440. On this system screen 440, the work result, the operator, and the estimated work time are selected or input in units of sub-items of business items. Specifically, as the work result, one of "work completed", "in progress", and "not started yet" is selected. As the operator, one person is selected from the list of operators. For the estimated work time, a value in units of time is input. After that, when the "performance save" button 441 is pressed, the data is registered in the work performance management DB 213. The sub-items of the business items for which "work completed" is selected as the work result are excluded from the planning target in the next process schedule creation logic.

[0085] As a result of the execution of the first process schedule creation logic, when one or more business items or sub-items are planned to be carried out on that workday, on the system screen example 410 in FIG. 15, "work start" is displayed in the "work progress" column 416 for each workday. Also, the "work progress" column 416 for each workday becomes "work completed" when the registration of the work performance for all the work planned on that workday is completed, that is, when all the work results are registered. FIG. 22 shows the system screen 410 at this time. As shown in FIG. 22, the "work progress" column 416 for each workday is automatically updated to "work completed".

[0086] After the work performance is registered, when the hyperlink 417 set for the name of the business item for each main part and inspection point is clicked on the system screen 410 in FIG. 22, the system screen 460 is displayed. FIG. 23 is a diagram showing the system screen 460. On this system screen 460, the work status of the sub-items associated with the selected business item is displayed. Then, when a sub-item with "completed work" is selected on the system screen 460 and the "performance cancellation" button 461 is clicked, the work performance of that sub-item is cleared, and the work result regarding the sub-item in the work performance management DB 213 is changed from "work completed" to "in progress". As a result, it becomes possible to return the selected sub-item to the target of the process schedule creation again.

[0087] After the first process schedule creation logic is executed, when the hyperlink 418 set in the "work progress" column 416 for each work day is clicked on the system screen 410 in FIG. 15 or FIG. 22, the system screen 470 is displayed on the terminal device 300. FIG. 24 is a diagram showing the system screen 470. On this system screen 470, the work progress of the selected work day can be changed. For the work day with the work progress changed to "plan creation", the work plan can be changed on the system screen 480. FIG. 25 is a diagram showing the system screen 480. On this system screen 480, a "delete" button 481 is displayed for business items including one or more sub-items of the implementation plan. When this "delete" button 481 is pressed, the information of the implementation plan is cleared. Also, when the "add" button 482 is pressed, the system screen 490 is displayed. FIG. 26 is a diagram showing the system screen 490. On this system screen 490, it becomes possible to add the work implementation plan in units of sub-items of the business item.

[0088] On the system screen 490, when a special note is entered in the "Special Note" column 491 and the "Register" button 492 is pressed, the special note is registered in the work plan management DB 212 in units of sub-items of business items. Then, the registered content can be presented to and confirmed by the operator on the system screen 440 in Fig. 21. In this embodiment, the case where the "Special Note" column 491 is utilized to instruct the operator who performs the work of the sub-items of the relevant business item will be taken as an example for explanation.

[0089] Generally, in the process of creating a process plan for an overhaul project, it is often necessary to regularly review and create the process plan due to factors such as weather and occurrence of troubles in project execution. Therefore, in this embodiment, it is assumed that after the work of the day is completed and the performance is registered during the construction period, the "Automatic Generation of Process Plan" button 413 on the system screen 410 in Fig. 15 is pressed, and the automatic process plan creation process is re-executed.

[0090] After the construction work is started and the work performance is registered, when the "Automatic Generation of Process Plan" button 413 is pressed, the process plan creation device 100 automatically creates a process plan by the second process plan creation logic.

[0091] Fig. 27 is a flowchart showing the flow of the second process plan creation logic.

[0092] As shown in the figure, in the process plan creation device 100, the project information acquisition unit 102 executes the processes of steps 701 to 703. Since the processes of steps 701 to 703 are the same as the processes of steps 601 to 603 in Fig. 17, the description is omitted.

[0093] Next, the project information acquisition unit 102 performs an unfinished item extraction process of extracting a group of unfinished sub-items from the group of sub-items of business items (step 704). Specifically, the project information acquisition unit 102 performs the unfinished item extraction process based on the information group regarding the sub-items of business items in the current overhaul project plan extracted in step 703.

[0094] Then, in the process schedule creation device 100, the process schedule creation unit 103 performs an alignment process for aligning the sub-item groups of business items (step 705). Specifically, the process schedule creation unit 103 performs the alignment process based on the information group regarding the sub-items with unfinished work among the sub-items of the business items in the current overhaul work plan extracted in step 704.

[0095] Next, the process schedule creation unit 103 performs a first allocation process for allocating the aligned sub-item groups of business items to working days (step 706). Specifically, the process schedule creation unit 103 performs the first allocation process based on the alignment result of the sub-item group with unfinished work in the current overhaul work plan in step 705.

[0096] After that, the screen creation unit 104 creates the system screen 410 and the system screen 430 based on the allocation result (step 707). Specifically, the screen creation unit 104 creates the system screen 410 and the system screen 430 based on the allocation result of the sub-item groups of business items to working days in the current overhaul work plan in step 706.

[0097] FIG. 28 is a flowchart showing the flow of the unfinished item extraction process in step 704 of FIG. 27.

[0098] As shown in the figure, first, the construction information acquisition unit 102 sets one sub-item among the sub-items of the business items in the current overhaul work plan as the processing target (step 721).

[0099] Next, the construction information acquisition unit 102 acquires the work result of the currently processed sub-item (step 722). Specifically, the construction information acquisition unit 102 searches the work performance management DB 213 using the sub-item ID of the current sub-item and the construction ID of the overhaul work as keys, and acquires the work result of the currently processed sub-item.

[0100] Next, the construction information acquisition unit 102 determines whether there is a work result (step 723). When there is no work result, the work information acquisition unit 102 holds the current item to be processed as uncompleted work internally (step 727). Then, the work information acquisition unit 102 advances the process to step 728.

[0101] When there is a work result, the work information acquisition unit 102 determines whether the work result is "work not started" (step 724). If the work result is "work not started", the work information acquisition unit 102 holds the current item to be processed as uncompleted work internally (step 727). Then, the work information acquisition unit 102 advances the process to step 728.

[0102] If the work result is not "work not started", the work information acquisition unit 102 determines whether the work result is "work completed" (step 725). If the work result is "work completed", the work information acquisition unit 102 does not need to extract the current item to be processed, and thus advances the process to step 728 as it is.

[0103] If the work result is not "work completed", that is, if the work result is "in progress", the work information acquisition unit 102 calculates the remaining work time of the current item to be processed (step 726). Specifically, the work information acquisition unit 102 calculates the remaining work time (Z) from the standard work time (X) in the item management DB 211 and the estimated work time (Y) in the work performance management DB 213 for the current item to be processed according to "Z = X - Y". Then, the work information acquisition unit 102 holds the current item to be processed as uncompleted work internally (step 727). Then, the work information acquisition unit 102 advances the process to step 728.

[0104] Next, the construction information acquisition unit 102 determines whether all sub-items are to be processed (step 728). If not all sub-items are to be processed, that is, if there are sub-items that are not to be processed, the process schedule creation unit 103 returns the process to step 721 and sets the next sub-item as the processing target. If all sub-items are to be processed, the construction information acquisition unit 102 extracts only the group of sub-items that are internally held as unfinished work (step 729). Specifically, among the group of sub-items of the work items in the current overhaul work plan, only the sub-items that are internally held as unfinished work in step 727 are extracted.

[0105] Since the flow of the alignment process in step 705 of FIG. 27 is the same as that shown in the flowchart of FIG. 18, the description thereof is omitted.

[0106] The first distribution process in step 706 of FIG. 27 is generally the same as that shown in the flowcharts of FIGS. 19A and 19B. However, in this case, the remaining working time (Z) calculated in the unfinished item extraction process of FIG. 28 is used as the standard working time of the sub-items in FIGS. 19A and 19B.

[0107] When the process schedule is automatically created by the second process schedule creation logic, the result will be displayed on the system screen 410 as shown in FIG. 15.

[0108] Also, when there is a delay in the overhaul work due to weather or troubles during the construction, the number of workers may be increased during the construction, or veteran workers may be temporarily dispatched to the site on a specific day to recover the progress delay. In such a case, in this embodiment, by applying the third process schedule creation logic, it is possible to create an effective process schedule.

[0109] FIG. 29 is a flowchart showing the flow of the third process schedule creation logic.

[0110] As shown in the figure, in the process schedule creation device 100, the work information acquisition unit 102 executes the processes of steps 801 to 804. Since the processes of steps 801 to 804 are the same as those of steps 701 to 704 in FIG. 27, the description thereof is omitted.

[0111] Then, in the process schedule creation device 100, the process schedule creation unit 103 performs an alignment process of aligning the sub-item groups of the business items (step 805). Specifically, the process schedule creation unit 103 performs the alignment process based on the information group regarding the sub-items with unfinished work among the sub-items of the business items in the current overhaul work plan extracted in step 804.

[0112] Next, the process schedule creation unit 103 performs a second allocation process of allocating the aligned sub-item groups of the business items to work days (step 806). Specifically, the process schedule creation unit 103 performs the second allocation process based on the alignment result of the sub-item group with unfinished work in the current overhaul work plan in step 805, taking into account the information of the newly dispatched workers.

[0113] After that, the screen creation unit 104 creates the system screen 410 and the system screen 430 based on the allocation result (step 807). Specifically, the screen creation unit 104 creates the system screen 410 and the system screen 430 based on the allocation result of the sub-item groups of the business items to work days in the current overhaul work plan in step 806.

[0114] Since the flow of the alignment process in step 805 of FIG. 29 is the same as that shown in the flowchart of FIG. 18, the description thereof is omitted.

[0115] FIGS. 30A and 30B are flowcharts showing the flow of the second allocation process in step 806 of FIG. 29.

[0116] As shown in FIG. 30A, the process sheet creation unit 103 executes the processes of steps 861 to 865. Since the processes of steps 861 to 865 are the same as the processes of steps 661 to 665 in FIG. 19A, the description thereof is omitted.

[0117] Next, the process sheet creation unit 103 calculates the time required for the work of the current item to be processed (current work required time) based on the standard work time (current standard work time) defined for the current item to be processed and the degree of the operator's work experience (step 866). Specifically, the process sheet creation unit 103 extracts the standard work time from the item management DB 211 using the item ID of the current item to be processed as a key, and sets it as the current standard work time. Further, if the operator ID is set in the work plan management DB 212, the process sheet creation unit 103 extracts the operator ID, and extracts the degree of work experience from the operator management DB 215 using this operator ID as a key. As described above, the degree of work experience is a value less than 1. Thereby, the process sheet creation unit 103 calculates the current work required time by multiplying the current standard work time by this degree of work experience.

[0118] Next, the process sheet creation unit 103 calculates the time required for the work of the next item to be processed (next work required time) based on the standard work time (next standard work time) defined for the next item to be processed and the degree of the operator's work experience (step 867). Specifically, the process sheet creation unit 103 extracts the standard work time from the item management DB 211 using the item ID of the next item to be processed as a key, and sets it as the next standard work time. Further, if the operator ID is set in the work plan management DB 212, the process sheet creation unit 103 extracts the operator ID, and extracts the degree of work experience from the operator management DB 215 using this operator ID as a key. As described above, the degree of work experience is a value less than 1. Thereby, the process sheet creation unit 103 calculates the next work required time by multiplying the next standard work time by this degree of work experience.

[0119] Next, the process sheet creation unit 103 executes the process of step 868. Since the process of step 868 is the same as the process of step 668 in FIG. 19A, the description thereof is omitted. Next, as shown in FIG. 30B, the process schedule creation unit 103 executes the processes of steps 881 to 888. Since the processes of steps 881 to 888 are the same as the processes of steps 681 to 688 in FIG. 19B, the description thereof is omitted.

[0120] [Summary] In the present embodiment, even a creator with little work experience can create a process schedule for the work for maintaining production equipment. As a result, for example, it is expected that the maintenance work within the delivery date can be carried out stably and without waste, that is, with the minimum unnecessary cost.

Description of Reference Numerals

[0121] 1... Process schedule creation system, 100... Process schedule creation device, 101... Reception unit, 102... Work information acquisition unit, 103... Process schedule creation unit, 104... Screen creation unit, 105... Transmission unit, 200... Database, 300... Terminal device

Claims

1. An acquisition unit that acquires a plurality of work items constituting the maintenance work of production equipment; An alignment unit that aligns the acquired plurality of work items, distributes them for each work scheduled date, creates a process schedule, and determines, among the plurality of work items, the work items to be implemented on each work scheduled date of the plurality of work scheduled dates so as to fit within the working hours of each work scheduled date; A registration unit that, after the work is carried out, registers the work performance of the work day as the work scheduled date in units of work items; Comprising: The registration unit can select one of "work completed", "in progress", and "not started" as the work result, and the work item for which "work completed" is selected as the work result is processed as out of the plan target when the next process schedule is created. A work procedure creation system for the maintenance of production equipment.

2. The registration unit updates the work progress to "work completed" when the registration of the work performance for all the work planned on the work day is completed. The work procedure creation system for the maintenance of production equipment according to Claim 1.

3. If the actual performance is cancelled after the registration of the work performance is completed, the registration unit changes the work result of the work item from "work completed" to "in progress", and returns it as the target of the next process schedule creation and processes it. The work procedure creation system for the maintenance of production equipment according to Claim 1.

4. The determination unit determines the work items to be implemented on each work scheduled date based on the remaining work time of the work items in progress. The work procedure creation system for the maintenance of production equipment according to Claim 1.

5. The determination unit determines the work items to be implemented on each work scheduled date based on the work time required to implement each work item. The work procedure creation system for the maintenance of production equipment according to Claim 1.

6. The determination unit changes the work time required according to the experience level of the worker. The work procedure creation system for the maintenance of production equipment according to Claim 5.

7. A step in which an acquisition unit of a computer acquires a plurality of work items constituting the maintenance work of production equipment; A step in which a determination unit of a computer aligns the acquired plurality of work items, distributes them for each work scheduled date, creates a process schedule, and determines, among the plurality of work items, the work items to be implemented on each work scheduled date of the plurality of work scheduled dates so as to fit within the working hours of each work scheduled date; After performing the operation, registering the work performance of the work day as the work schedule date for each work item; including; In the step of registering, one of "work completed", "in progress", and "not started" can be selected as the work result. For work items for which "work completed" is selected as the work result, they are treated as out of scope of planning when the next process schedule is created. A method for creating a work procedure for maintaining a production equipment machine.

8. On a computer, A function of obtaining a plurality of work items constituting the maintenance work of the production equipment machine; Aligning the obtained plurality of work items, creating a process schedule by distributing them for each work schedule date, and determining, among the plurality of work items, the work items to be performed on each work schedule date of the plurality of work schedule dates so as to fit within the working hours of each work schedule date; After performing the work, a function of registering the work performance of the work day as the work schedule date for each work item; to be realized, The registering function allows one of "work completed", "in progress", and "not started" to be selected as the work result. For work items for which "work completed" is selected as the work result, they are treated as out of scope of planning when the next process schedule is created. A program.

Images