Storage work assistance device, storage work assistance method, and program

Abstract

An aspect of the present invention is a storage work assistance device comprising: a storage work information acquisition unit that acquires storage work information including one or more storage works; a type associating unit that associates the type of object to be subjected to storage work with the storage work information; a storage work associating unit that associates the storage work included in the storage work information associated with the type of object as a storage work on the object; a receipt date acquisition unit that acquires the date of receipt of the object; and a notification unit that provides a notification of the date on which the storage work associated with the object is conducted according to the date acquired by the receipt date acquisition unit.

Description

Storage work support device, storage work support method, and program

[0001] The present invention relates to a storage operation support device, a storage operation support method, and a program technology.

[0002] Equipment, materials, and other objects used at construction sites must be stored in good condition.

[0003] Japanese Patent Application Laid-Open No. 2009-215075

[0004] The work required to store an object in good condition varies depending on the object. Furthermore, even for the same work, the cycle of performing the work may differ. These cycles must be calculated based on the date the object was received. As such, many factors are involved in storing an object in good condition, making it difficult to store the object in good condition.

[0005] In view of the above circumstances, an object of the present invention is to provide a technology that assists in storing objects in good condition.

[0006] One aspect of the present invention is a storage work support device that includes a storage work information acquisition unit that acquires storage work information including one or more storage works, a type correspondence unit that matches the type of object that is the subject of the storage work with the storage work information, a storage work correspondence unit that matches the storage work included in the storage work information that is associated with the type of object as storage work for the object, a receipt date acquisition unit that acquires the date the object was received, and a notification unit that notifies the schedule for performing the storage work associated with the object according to the date acquired by the receipt date acquisition unit.

[0007] One aspect of the present invention is a storage work support method comprising: a storage work information acquisition step of acquiring storage work information including one or more storage works; a type correspondence step of associating the storage work information with the type of object that is the subject of the storage work; a storage work correspondence step of associating the storage work included in the storage work information associated with the type of object as storage work for the object; a receipt date acquisition step of acquiring the date the object was received; and a notification step of notifying the schedule for performing the storage work associated with the object according to the date acquired by the receipt date acquisition step.

[0008] One aspect of the present invention is a program that causes a computer to function as a storage work information acquisition unit that acquires storage work information including one or more storage works, a type correspondence unit that matches the type of object that is the subject of the storage work with the storage work information, a storage work correspondence unit that matches the storage work included in the storage work information that is associated with the type of object as storage work for the object, a receipt date acquisition unit that acquires the date the object was received, and a notification unit that notifies the schedule for performing the storage work associated with the object based on the date acquired by the receipt date acquisition unit.

[0009] The present invention makes it possible to assist in the task of storing objects in good condition.

[0010] 1 is a diagram illustrating an example of a functional configuration of a storage work support device. FIG. 1 is a diagram illustrating an example of a storage form. FIG. 2 is a diagram illustrating an example of a storage work. FIG. 3 is a diagram illustrating an example of work association. FIG. 4 is a diagram illustrating an example of a storage form object type. FIG. 5 is a diagram illustrating an example of an object type. FIG. 6 is a diagram illustrating an example of a storage work object type. FIG. 7 is a diagram illustrating an example of an object storage location. FIG. 8 is a diagram illustrating an example of a storage work storage location. FIG. 9 is a diagram illustrating an example of an object association. FIG. 10 is a diagram illustrating an example of a stage. FIG. 11 is a diagram illustrating an example of storage work information. FIG. 12 is a diagram illustrating a schematic diagram of association by the storage work support device. A flowchart illustrating a processing flow related to association. A flowchart illustrating a notification processing flow. A diagram illustrating an example of a schedule notification. A diagram illustrating a schematic diagram of association between a storage location and a storage work. A flowchart illustrating a flow of an extraction processing. A diagram illustrating an example of extracted information. A flowchart illustrating a flow of a tracking processing. A diagram illustrating an example of a tracking list.

[0011] FIG. 1 illustrates an example of the functional configuration of a storage work assistance device 100. The storage work assistance device 100 includes a control unit 110, an input / output unit 120, and a storage unit 130. These components are implemented by a hardware processor, such as a central processing unit (CPU), executing a program (software). Some or all of these components may be implemented by hardware (including circuitry), such as a large-scale integration (LSI), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a graphics processing unit (GPU), or may be implemented by a combination of software and hardware. The program may be stored in advance in a storage device (a storage device with a non-transitory storage medium) such as a hard disk drive (HDD), a solid-state drive (SSD), or a flash memory. Alternatively, the program may be stored in a removable storage medium (a non-transitory storage medium) such as a DVD or CD-ROM, and installed by inserting the storage medium into a drive device.

[0012] The input / output unit 120 inputs and outputs various types of information, such as information input by an operator of the storage work support device 100, information output (displayed) to the operator, and information transmitted and received via communication.

[0013] The storage unit 130 includes a storage device such as an HDD, SSD, or flash memory. The storage unit 130 stores a storage form 131, a storage task 132, task related information 133, a storage form object type 134, an object type 135, a storage task object type 136, an object related information 137, a stage 138, an object storage location, and a storage task storage location. This information will be described below.

[0014] FIG. 2 is a diagram showing an example of the storage form 131. As shown in FIG. 2, the storage form 131 groups storage tasks based on the object, and is information in which information such as a storage form number, a form description, and jurisdiction is associated. The storage form number is information for uniquely identifying the storage form. The form description is a description of the object. The jurisdiction indicates the jurisdiction regarding the storage of the object.

[0015] FIG. 3 is a diagram showing an example of a storage operation 132. As shown in FIG. 3, the storage operation 132 indicates the contents of the storage operation, and is information to which information such as an operation code, an operation description, and remarks is associated. The operation code is information for uniquely identifying the storage operation. The operation description indicates the contents of the operation. The remarks indicate remarks about the storage operation. Note that in this embodiment, "storage operation" refers to an operation for storing an object in good condition, and includes various operations for storing an object in good condition, such as conservation work and maintenance work. In the following embodiments, "storage operation" may be simply referred to as "operation."

[0016] FIG. 4 is a diagram showing an example of the work association 133. As shown in FIG. 4, the work association 133 indicates the frequency of work and the current storage work stage, and is information in which information such as the above-mentioned work code, work frequency (week), and storage work stage is associated. The work frequency (week) is information indicating the work frequency in weeks. For example, a work frequency (week) of 1 indicates that the work is performed every other week. A work frequency (week) of 2 indicates that the work is performed every two weeks. The storage work stage indicates the stage at which the object is stored. In this embodiment, as an example, the object is used for construction, and three storage work stages are used: "warehouse storage," in which the object is stored in a warehouse before construction; "construction period," in which the object is under construction; and "completed," in which the construction period has ended. In the following description, the "storage work stage" may be simply referred to as a "stage."

[0017] Generally, different stages often result in different tasks being performed on the object, and the details of the tasks themselves are different. Therefore, by providing each task code indicating whether or not a task is to be performed for each stage, it becomes possible to perform appropriate storage tasks. For example, in the case of Figure 4, "X" indicates that the task will be performed, and "-" indicates that the task will not be performed. Therefore, the task with the task code SPA-006 can be performed at any storage task stage.

[0018] 5 is a diagram showing an example of the storage form object type 134. As shown in FIG. 5, the storage form object type 134 is information in which information such as a storage form and an object type is associated. One or more object types are associated with a storage form. The object type indicates the type of object. For example, the object type may be a generic name for classifying objects, such as a tire or a pump.

[0019] 6 is a diagram showing an example of the object type 135. As shown in FIG. 6, the object type 135 is information in which information such as the object type and the object is associated with each other. The object type 135 is information that associates the object type with the objects that belong to this object type. For example, if the object type 1 is a pump, the object 1-A may be a centrifugal pump, the object 1-B may be a propeller pump, and the object 1-C may be a viscous pump.

[0020] 7A is a diagram showing an example of the storage work object type 136. As shown in Fig. 7, the storage work object type 136 is information in which information such as a storage work and an object type is associated with each other. For example, it is information in which a pump is associated with a storage work for the pump.

[0021] FIG. 7B is a diagram showing an example of the object storage location 139. As shown in FIG. 7B, the object storage location 139 is information in which information such as an object and a storage location is associated with each other. For example, some objects at a plant construction site do not have a specific installation location. For example, pumps and static equipment have a specific installation location, but piping components such as piping valves and instrumentation components such as instrumentation valves do not have a specific installation location. There are such objects that do not have information about their installation location. The object storage location 139 is information in which such objects are associated with storage locations.

[0022] 7C is a diagram showing an example of the storage work storage location 140. As shown in FIG. 7C, the storage work storage location 140 is information in which information such as storage work and storage location is associated. The storage work storage location 140 is information in which information such as the storage work for an object that does not have information on the above-mentioned attachment location is associated.

[0023] FIG. 8 is a diagram showing an example of the object association 137. As shown in FIG. 8, the object association 137 is information in which information such as an object, a receipt date, a status flag, a date, and an execution result is associated with each other. For example, the object association 137 is information in which a pump, the date the pump was received, the status of the pump, the date the storage work was performed, and the execution result of the storage work are associated with each other. The object association 137 is provided for each object. The status flag is a flag indicating whether the storage state is in a specific state (e.g., a defective state). If the storage state has become a specific state even once, the status flag becomes a flag indicating the specific state. The execution result can store text or image data of an image of the object.

[0024] 9 is a diagram showing an example of stage 138. As shown in FIG. 9, stage 138 is information indicating the start and end dates of warehouse storage, the start and end dates of the construction period, and the start and end dates after completion. For example, storage operation stages input by an operator of storage operation support device 100 may be received by input / output unit 120 and stored in stage 138, or may be obtained from software that manages the process, or may be provided for each object.

[0025] FIG. 10 is a diagram showing an example of storage work information. The storage work information is information that associates the above-mentioned storage form with a storage work. It is assumed that storage form 131 and storage work 132 are previously stored in association with each other in storage unit 130. As shown in FIG. 5, multiple storage works may be associated with one storage form. In this way, storage work information includes one storage work.

[0026] Returning to the explanation of Fig. 1, the control unit 110 controls each unit of the storage work support device 100 to support the work of storing objects in good condition. The control unit 110 includes a storage work information acquisition unit 111, a type correspondence unit 112, a storage work correspondence unit 113, a receipt date acquisition unit 114, a notification unit 115, an extraction unit 116, an execution result acquisition unit 117, and a tracking unit 118. These will be explained with reference to Fig. 11 as well.

[0027] Fig. 11 is a diagram schematically showing the association by the storage work support device 100. Fig. 11 shows storage work information A and B and object types 1 and 2. Storage work information A includes storage works 1 to 3. Storage work information B includes storage works 4 and 5. Object type 1 includes objects 1-A, 1-B, and 1-C. Object type 2 includes objects 2-A and 2-B.

[0028] The storage work information acquisition unit 111 acquires storage work information including one or more storage works, as shown in Fig. 10. The type association unit 112 associates the types of objects that are the subject of the storage work with the storage work information. For example, as shown in Fig. 11, the type association unit 112 associates storage work information A with object types 1 and 2, and also associates storage work information B with object type 2.

[0029] The storage work association unit 113 associates the storage work included in the storage work information associated with the object type as the storage work for the object. For example, as shown in Fig. 11 , the storage work association unit 113 associates storage work 1 included in storage work information A as the storage work for objects 1-A, 1-B, and 1-C included in object type 1.

[0030] The receipt date acquisition unit 114 acquires the date on which the object was received. The receipt date acquisition unit 114 receives, for example, a date input by an operator of the storage work support device 100 via the input / output unit 120 and stores the date in the object association 137. The notification unit 115 notifies the schedule for performing the storage work associated with the object, according to the date acquired by the receipt date acquisition unit 114.

[0031] When a specific time period is specified, the extraction unit 116 extracts the storage work to be performed at the specified time period and the object for which the storage work will be performed. Specific extraction processing will be described later. The execution result acquisition unit 117 acquires the execution result of the storage work. The acquired execution result is stored in the execution result of the object association 137. The execution result includes the storage status of the object. The tracking unit 140 tracks objects that are in a specific storage status. Specific tracking processing will be described later.

[0032] 12 is a flowchart showing the process flow for the above-mentioned association. In FIG. 12, the storage work information acquisition unit 111 acquires storage work information including one or more storage works (step S101). The type association unit 112 associates the type of object to be subjected to the storage work with the storage work information (step S102). The storage work association unit 113 associates the storage work included in the storage work information associated with the object type as the storage work for the object (step S103), and ends the process.

[0033] Next, the notification process by the notification unit 115 will be described. Fig. 13 is a flowchart showing the flow of the notification process executed by the notification unit 115. This flowchart shows the process of notifying the schedule of management work for one object. Therefore, when notifying the schedule for multiple objects, the process is looped as many times as the number of objects.

[0034] The notification unit 115 acquires the current stage from the stage 138 (step S201). The notification unit 115 acquires the operation code corresponding to the object (step S202). As described above, the storage operation association unit 113 associates the storage operation included in the storage operation information associated with the type of object as the storage operation of the object.

[0035] The notification unit 115 determines whether or not there is a storage operation at the current stage (step S203). Since the operation association 133 described above associates an operation code with a storage operation stage, the notification unit 115 can determine whether or not there is a storage operation at the current stage by acquiring the operation association 133 from the storage unit 130.

[0036] If there is no storage work (step S203: NO), the notification unit 115 ends the process. If there is storage work (step S203: YES), the notification unit 115 acquires the receipt date of the object from the object-related 137 (step S204) and acquires the work frequency from the work-related 133 (step S205).

[0037] The notification unit 115 calculates the schedule for the storage work from the receipt date and the work frequency (step S206), notifies the user of the calculated schedule (step S207), and ends the process.

[0038] An example of a method for calculating the schedule for storage work will be described below. For example, if the schedule is divided into seven-day intervals starting from the date of receipt and the work frequency (weeks) is N (performed every N weeks), the storage work will be scheduled for weeks that are integer multiples of N+1, such as N+1 week, 2(N+1) week, ..., k(N+1) week (k is an integer equal to or greater than 1) from the date of receipt.

[0039] Regardless of the receipt date, the schedule may be divided into seven-day intervals in advance, and the storage work schedule may be set to the week that is an integer multiple of N+1 from the week in which the receipt date falls. For example, if the schedule is divided into periods such as April 1st to 7th, 8th to 15th, and 16th to 23rd, and the like, for objects received between April 1st and 7th and with the same work frequency (weekly), the storage work schedule will be the same even if the receipt date is different. Furthermore, as mentioned above, the stage changes and the storage work differs for each stage, so the receipt date also includes the day on which the stage changes.

[0040] FIG. 14 is a diagram showing an example of a schedule notification. In FIG. 14, the storage work schedules for objects 1 to 6 are indicated by horizontal bars along with the work codes. In this way, the notification unit 115 notifies information indicating the storage work (work code) along with the schedule. In FIG. 14, the receipt dates for objects 1 to 3 are set to the beginning of the first week, and the receipt date for object 6 is set to the middle of the first week. Objects 4 and 5 are assumed to have changed stages due to the start of construction work in the second week. Furthermore, as an example, the work frequency (week) for objects 1 and 4 is set to 1 week, the work frequency (week) for objects 2, 5, and 6 is set to 2 weeks, and the work frequency (week) for object 3 is set to 3 weeks.

[0041] In this case, the storage work schedule for object 1 is shown to be the second week, and the storage work schedule for object 2 is shown to be the third week. Also, the storage work schedule for objects 1, 3, 4, and 6 is shown to be the fourth week. And the storage work schedule for object 5 is shown to be the fourth week.

[0042] By notifying in this manner, the person performing the storage work will be aware of the schedule and can perform the storage work according to that schedule, thereby providing a technology that supports the work of storing objects in good condition.

[0043] Fig. 15 is a diagram showing a schematic diagram of the correspondence between storage locations and storage tasks. Fig. 15 shows storage task information A and B and storage locations 1, 2, and 3. Storage task information A includes storage tasks 1 to 3. Storage task information B includes storage tasks 4 and 5.

[0044] 15, storage location 1 is associated with storage work information A. Storage location 2 is associated with storage work information A and B. Storage location 3 is associated with storage work information A and B. In this way, in this embodiment, the association can be switched depending on whether the object to be stored has information about its installation position at the construction site. This makes it possible to deal with cases where there are insufficient personnel to manage each object, such as small-scale projects or module yards.

[0045] Next, a process for extracting storage work to be performed at a specified time and the objects to be subjected to the storage work when a specified time is specified will be described. Fig. 16 is a flowchart showing the flow of the extraction process executed by the extraction unit 116.

[0046] The extraction unit 116 acquires a time period (step S301). This time period may be, for example, a week or a date, and is acquired as specified by the operator. The extraction unit 116 acquires a stage corresponding to the time period from the stage 138 (step S302). As described above, the stage 138 records the start date and end date of each stage, so the extraction unit 116 can acquire a stage corresponding to the time period.

[0047] Next, the extraction unit 116 acquires the operation code corresponding to the object (step S303). As described above, the storage operation included in the storage operation information associated with the object type is associated as the storage operation for the object by the storage operation association unit 113. In addition, in this process, extraction processing is performed for all objects.

[0048] The extraction unit 116 determines whether or not there is a storage operation at the corresponding stage (step S304). Since the operation association 133 described above associates an operation code with a storage operation stage, the notification unit 115 can determine whether or not there is a storage operation at the corresponding stage by acquiring the operation association 133 from the storage unit 130.

[0049] If there is no storage work (step S304: NO), the extraction unit 116 proceeds to step S310. If there is storage work (step S304: YES), the notification unit 115 acquires the receipt date of the object from the object-related 137 (step S305) and acquires the work frequency from the work-related 133 (step S306).

[0050] The notification unit 115 calculates a schedule for the storage work from the receipt date and the work frequency (step S307) and determines whether the schedule corresponds to the period specified by the operator (step S308). If the schedule does not correspond to the period specified by the operator (step S308: NO), the extraction unit 116 proceeds to step S310. If the schedule corresponds to the period specified by the operator (step S308: YES), the extraction unit 116 stores the storage work and the target object (step S309).

[0051] The extraction unit 116 determines whether the extraction process for all objects has been completed (step S310). If the extraction process for all objects has not been completed (step S310: NO), the extraction unit 116 proceeds to step S303 to process objects that have not yet been extracted. If the extraction process for all objects has been completed (step S310: YES), the extraction unit 116 outputs the storage work stored in step S309 and the objects for which the storage work will be performed (step S311), and ends the process.

[0052] FIG. 17 shows an example of extracted information obtained by the extraction process. FIG. 17 shows the time period (week of April 18th) specified by the operator, the objects, and the storage work for those objects. This allows the operator to see at a glance the storage work to be performed during the specified time period and the objects for which the storage work will be performed. This makes it easy to plan the schedules of workers, resulting in more efficient operations.

[0053] Next, a process for tracking an object whose storage state is a specific state will be described. FIG. 18 is a flowchart showing the flow of the tracking process executed by the tracking unit 118. This extraction process is performed for all objects. The tracking unit 118 acquires a state flag of the object association 137 corresponding to the object (step S401). The tracking unit 118 determines whether the acquired state flag indicates a specific state (step S402). If the state flag does not indicate a specific state (step S402: NO), the tracking unit 118 proceeds to step S404.

[0054] If the status flag indicates a specific status (step S402: YES), the tracking unit 118 adds the object association of the object to the tracking list. The tracking unit 118 determines whether checking the status flags of all objects has been completed (step S404). If checking of all objects has not been completed (step S404: NO), the tracking unit 118 proceeds to step S401 to process objects whose status flags have not been checked. If checking of all objects has been completed (step S404: YES), the tracking unit 118 outputs the tracking list (step S404) and ends the process.

[0055] FIG. 19 is a diagram showing an example of a tracking list output by the tracking process. The tracking list shown in FIG. 19 shows, for each object, the date and the storage status on that date. As described above, the storage status is shown by text or image data of the object. For example, the storage status of pipe X on March 7, 2010 is shown in text as "Signs of corrosion present." The storage status of pump Y on March 7, 2010 is shown by an image link, and selecting the link displays the image.

[0056] By outputting the tracking list in this way, it is possible to track the storage status throughout all storage stages ("warehouse storage", "construction period", "post-completion"), for example.

[0057] Although an embodiment of the present invention has been described above in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and includes designs within the scope of the gist of the present invention.

[0058] The present invention is applicable to a technology that supports the work of storing objects in good condition.

[0059] REFERENCE SIGNS LIST 100 Storage work support device 110 Control unit 111 Storage work information acquisition unit 112 Type correspondence unit 113 Storage work correspondence unit 114 Receipt date acquisition unit 115 Notification unit 120 Input / output unit 130 Memory unit 131 Storage form 132 Storage work 133 Work related 134 Storage form object type 135 Object type 136 Storage work object type 137 Object related 138 Stage

Claims

1. a storage work information acquisition unit that acquires storage work information including one or more storage works; a type correlating unit for correlating the type of object to be stored with the storage operation information; a storage work corresponding unit that corresponds a storage work included in the storage work information that is associated with a type of the object as a storage work of the object; a receipt date acquisition unit that acquires a date on which the object was received; a notification unit that notifies a schedule of a storage operation associated with the object according to the date acquired by the receipt date acquisition unit; A storage work support device equipped with the above-mentioned.

2. The storage operation support device according to claim 1 , wherein the notification unit notifies information indicating the storage operation together with a schedule.

3. the type corresponding unit is capable of associating a storage location of an object to be subjected to a storage operation with the storage operation information, The storage work corresponding unit is capable of associating a storage work included in the storage work information associated with a storage location of the object as a storage work of the object. The storage operation support device according to claim 1 or 2.

4. the type corresponding unit and the storage operation corresponding unit switch the correspondence depending on whether the object to be stored has information on an attachment position at a construction site. The storage operation support device according to claim 3.

5. 2. A storage operation support device according to claim 1, further comprising an extraction unit that, when a predetermined time is designated, extracts storage operations to be performed at the designated predetermined time and objects for which the storage operations are to be performed.

6. An execution result acquisition unit that acquires an execution result of a storage operation, The execution result includes a storage state of the object; 2. The storage operation support device according to claim 1, further comprising a tracking unit for tracking an object in a specific storage state.

7. A storage work information acquisition step of acquiring storage work information including one or more storage works; a type corresponding step of corresponding a type of the object to be stored to the storage operation information; a storage work corresponding step of associating a storage work included in the storage work information associated with the type of the object as a storage work for the object; a receipt date acquisition step of acquiring a date on which the object was received; a notification step of notifying a schedule for performing the storage work associated with the object according to the date acquired by the receipt date acquisition step; A storage operation support method comprising the steps of:

8. Computer, a storage work information acquisition unit that acquires storage work information including one or more storage works; a type correlating unit for correlating the type of object to be stored with the storage operation information; a storage work corresponding unit that corresponds a storage work included in the storage work information that is associated with a type of the object as a storage work of the object; a receipt date acquisition unit that acquires a date on which the object was received; a notification unit that notifies a schedule of a storage operation associated with the object according to the date acquired by the receipt date acquisition unit; A program to make it function as such.