JP7013748B2 - Document management device, document management method and program - Google Patents

Description

The present invention relates to a document management device that manages documents, a document management method and a document management program executed by this document management.

Line work such as assembly and processing in factories is often performed according to the procedure manual, but machine malfunctions, failures, replacements, or changes in parts to be assembled (defective lots, permanent changes in parts, changes in specifications), etc. Therefore, if an event occurs in which the manufacturing procedure, etc. must be changed, the procedure manual also needs to be changed.

However, in general, defective parts are often temporary lot defects, and equipment failures are often temporary. Therefore, defective parts lots have been used up and normal lots have been entered. In some cases, or when the equipment recovers from a failure, it is necessary to undo the procedure that was temporarily changed, and it is also necessary to undo the procedure manual accordingly.

In addition, work procedure manuals are often version-managed by a document management device, but in shift-based factories, it is also necessary to hand over the procedure changes to the next person in charge, and in order to prevent omission of handing over, each person has to do so. It is important to change or restore the original managed by the document management device, not the runbook that you have.

In Patent Document 1, for example, when the administrator of an electronic document wants to temporarily allow a user named "Yamada" to print an electronic document having a document ID of "00000001", the electronic document management server After operating the input device 213 provided in 101 and changing the setting of the printability column from "printable" to "printable" to allow printing of an electronic document having a document ID of "00000001". Upon receiving a print completion notification from the printer indicating that the electronic document has been printed, the electronic document management system changes the contents of the printability column to the state before the authority of the electronic document was changed by the administrator. A document authority management device that automatically returns has been proposed.

Further, in Patent Document 2, document parts constituting the composite document are specified, and a configuration information table holding configuration information indicating the configuration of the document component group of the composite document is created by the configuration information table registration program and is used as a secondary storage device. When a new version of a document part is added to the configuration information registered in the configuration information table, a new document part is added, or a document part is deleted, the configuration information is updated by the compound document version update program. , A complex document management system that adds to the configuration information before update and registers the updated configuration information in the configuration information table, and reads and displays the configuration information table from the secondary storage device by the composite document version history display program. Has been proposed.

Further, in Patent Document 3, when the access permission attribute and the ID information for each function are set in the electronic document created by the application and the document is encrypted and stored and managed on the storage device, the attribute information can be easily changed from the PC. Based on the instruction, access permission information is set in the access information management table in the managed electronic document, and the attribute information is read out to expand or prohibit the attribute by adapting to the individual attribute change request for the attribute information. A document processing system has been proposed, which features a configuration in which attributes different from those at the time of registration are set for an electronic document that has already been created and update management is performed.

Japanese Unexamined Patent Publication No. 2007-200140 Japanese Unexamined Patent Publication No. 2000-259615 Japanese Unexamined Patent Publication No. 2004-355610

As mentioned above, in factories, etc., it is necessary to temporarily change or restore the procedure manual for work, but for example, a component defect → equipment failure occurs, and the component defect occurs first. Occurrence and resolution of multiple events may be staggered, as in the case of resolution. In such a case, instead of returning the version of the procedure manual, a complicated process of returning the procedure for avoiding the defect of the parts while leaving the procedure for avoiding the failure of the equipment occurs.

Furthermore, when there are a plurality of lines, some lines require an avoidance procedure and some do not.

In this way, when it is necessary to temporarily change the procedure manual due to various events, there is a problem that the process of changing and restoring the procedure manual becomes complicated and immediacy cannot be maintained. There is a demand for technology that can easily and accurately perform processes such as temporary changes and undoing. Further, such a request exists not only in the procedure manual in the line work but also in the scene of managing the application specifications and the like.

The technique disclosed in Patent Documents 1 to 3 is not a technique for changing or restoring a document such as a procedure manual in work, but a temporary change or restoration of the document is easy. It was not possible to provide a solution to the demand for technology that could be done accurately and accurately.

The present invention has been made in view of such a technical background, and is a document management capable of easily and accurately performing a process such as changing or restoring a document such as a procedure manual in line work. The subject is to provide a device, a document management method, and a document management program.

The above problem is solved by the following means.
(1) A registration means for registering one or more documents and a document whose content is changed according to an event that has occurred, and a document after the content change is associated with the event. When the document after the content change and the event are associated with each other by the association means and the association means, the document after the content change is managed as the latest document until the event is resolved, and the above-mentioned matter. A document management device characterized in that when the elephant is resolved, the document is returned to the document before the content change, or a management means for warning to return the document is provided.
(2) A first delivery control means for delivering the document to a predetermined delivery destination, the delivery control means including an individual and / or a group not affected by the event, for the document before the content change. The document management device according to item 1 above, which delivers a document to a delivery destination and delivers the changed document to a second delivery destination consisting of an individual and / or a group affected by the event.
(3) The document is a procedure manual in line work, the content change of the document is a change of the work content described in the procedure manual, and the distribution control means uses the procedure manual after the content change as the first step. 2. The document management device according to item 2 above, which is delivered to a worker on a line performing work affected by the event, which is the delivery destination of 2.
(4) The document is a procedure manual in the line work, the change in the content of the document is a change related to a lot of parts used in the line work, and the event is a change in the lot of parts used in the line work. The document management device according to any one of the above items 1 to 3, wherein the event is resolved by the end of use of the parts for the lot.
(5) The document is a procedure manual in the line work, the change in the content of the document is a change related to the equipment used in the line work, and the event is a change in the state of the equipment used in the line work. The document management device according to any one of items 1 to 3 above, wherein the event is resolved by the end of the change in the state of the equipment.
(6) The document is a procedure manual in the line work, the content change of the document is a change for avoiding the problem in the line work, and the event is a problem in the line work and a problem. The document management device according to any one of the above items 1 to 3, wherein the event is resolved by the resolution of the above.
(7) When the information indicating the start of the line work is input, the management means checks whether the event has been resolved, and if it has been resolved, returns or returns to the document before the content change. The document management device according to any one of the preceding paragraphs 3 to 6, which gives a warning as described above.
(8) Registration in which the document management device registers one or more documents, and also registers a document in which the content of one of the documents is changed according to an event that has occurred, and a document before the content change as a parent document. When the document after the content change is associated with the event by the step, the association step for associating the document after the content change with the event, and the association step, the event is described until the event is resolved. It is characterized by managing the document after the content change as the latest document, and when the above phenomenon is resolved, execute a management step to return to the document before the content change or to warn to return. Document management method to do.
(9) Register one or more documents in the CPU of the document management device, and register the document whose content is changed according to the event that occurred, and the document before the content change as the parent document. When the document after the content change and the event are associated by the registration step, the association step for associating the document after the content change with the event, and the association step, until the event is resolved. Manages the document after the content change as the latest document, and when the event is resolved, returns to the document before the content change, or performs a management step that warns to return. Document management program.

According to the invention described in the preceding paragraph (1), one or a plurality of documents are registered, and the document whose content is changed according to the event that has occurred is the parent of the document before the content change. It is registered as a document, and the document after the content change is associated with the event. In addition, when the document after the content change is associated with the event, the document after the content change is managed as the latest document until the event is resolved, and when the event is resolved, the document before the content change is restored. Or you will be warned to return.

In other words, the document after the content change is managed in association with the event that triggered the content change, and the document after the content change is updated to the latest document or the document before the content change based on whether the event has been resolved. Processing such as returning to can be performed easily and accurately.

According to the invention described in the preceding paragraph (2), the document before the content change is delivered to the first delivery destination consisting of individuals and / or groups not affected by the event, and the document after the content change is delivered to the event. It can be delivered to a second destination consisting of affected individuals and / or groups, and different documents can be delivered to the destination depending on whether the content change is affected or not.

According to the invention described in the preceding paragraph (3), the procedure manual after the change of the work contents of the procedure manual in the line work is delivered to the line worker who performs the work affected by the event which is the second delivery destination. Therefore, the worker to whom the procedure manual after the change of the work content is delivered can confirm the change of the procedure process content.

According to the invention described in the preceding paragraph (4), if there is a change related to the lot of parts used for the line work in the procedure manual in the line work, the procedure manual after the content change and the line work which is an event are changed. It is associated with the lot of parts used. In addition, when the event is resolved by the end of use of the parts for the lot, the parent's procedure manual before the content change is managed to be the latest procedure manual, or the parent's procedure manual is made the latest document. Therefore, when there is a change related to the lot, it is possible to easily and accurately perform the process of changing or undoing the procedure manual.

According to the invention described in the preceding paragraph (5), if there is a change in the contents of the procedure manual in the line work related to the equipment used for the line work, it is used for the procedure manual after the content change and the line work which is an event. It is associated with the change in the state of the equipment to be installed, and the procedure manual after the content change is managed as the latest document. In addition, when the event is resolved by the end of the equipment status change, the procedure manual is changed to the original procedure manual or a warning is issued to return to the procedure manual. It is possible to easily and accurately perform processes such as performing and restoring.

According to the invention described in the preceding paragraph (6), if there is a change in the content of the procedure manual in the line work to avoid problems in the line work, the procedure manual after the content change and the line work which is an event Is associated with the problem in. In addition, when the problem is resolved by solving the problem, a warning is given to return to the document before the content change or to return, so the process of changing or restoring the procedure manual is easy and accurate. It can be carried out.

According to the invention described in the preceding paragraph (7), when the information indicating the start of the line work is input, it is checked whether or not the event has been resolved, and if it has been resolved, whether to return to the document before the content change. , Or a warning to return.

According to the invention described in the preceding paragraph (8), the document after the content change is managed in association with the event that triggered the content change, and the document after the content change is used as the latest document until the event is resolved. When it is managed and the event is resolved, the document before the content change is restored, or a warning is issued to return, so when the event occurs, the content of the document is changed to make it the latest document or the original. Processing such as returning to can be performed easily and accurately.

According to the invention described in the preceding paragraph (9), one or a plurality of documents are registered, and a document whose content is changed according to an event that has occurred is registered, and the document is different from the document after the content change. A process that associates with an event, manages the document after the content change as the latest document until the event is resolved, and when the event is resolved, returns to the document before the content change or warns to return. , Can be executed by the CPU of the document management device.

It is a figure which shows the structure of the document management system which used the document management apparatus which concerns on one Embodiment of this invention. It is a block diagram which shows the structure of a document management apparatus. It is a figure for demonstrating an example of issue, reissue, change, and return (rollback) of a procedure manual which is an example of a document. (A) is a diagram showing document management data, (B) is a diagram showing user management data, (C) is a diagram showing parts management data, and (D) is a diagram showing equipment management data. It is a figure which shows the provisional update screen of a procedure manual. (A) is a diagram showing the document management data after the problem is solved, and (B) is a diagram showing the equipment management data after the problem is solved. (A) shows other examples of document management data, (B) shows other examples of parts management data, (C) shows other examples of equipment management data, and (D) shows problem management data. It is a figure. It is a figure which shows another example of the provisional update screen of a procedure manual. (A) is the document management data of FIG. 7 (A) after the problem is solved, (B) is the equipment management data of FIG. 7 (C) after the problem is solved, and (C) is FIG. 7 (D) after the problem is solved. It is a figure which shows each of the problem management data of). It is a flowchart which shows the operation of the document management apparatus when the user of each line uses a procedure manual. It is a flowchart which shows the registration process of the procedure manual whose content was changed. It is a continuation of the flowchart of FIG. 11 (A). It is a flowchart which shows the process of breaking the association between a procedure manual and a problem occurrence after the problem is solved about the procedure manual whose content was changed because the problem of a part or equipment occurred. It is a continuation of the flowchart of FIG. 12 (A).

Hereinafter, embodiments of the present invention will be described with reference to the drawings.

FIG. 1 is a block diagram showing a configuration of a document management system in which the document management device 1 according to the embodiment of the present invention is used.

The document management system includes a document management server 1 as a document management device, a parts management device 2, an equipment management device 3, a tablet terminal 4, an image forming device 5, a dashboard 6, and the like.

The document management server 1 manages a plurality of documents, users, and the like, and in this embodiment, it is composed of a personal computer (hereinafter, also referred to as a PC). In this embodiment, the document is a procedure manual for line work in a factory or the like, and the document management server 1 manages the procedure manual which is an electronic document.

FIG. 2 is a block diagram showing an electrical configuration of the document management server 1.

The document management server 1 includes a CPU 11, a ROM 12, a RAM 13, a storage unit 14, a display device 15, an input device 16, a network interface unit (network I / F unit) 17, and the like, and is connected to each other via a system bus 18. ..

The CPU 11 comprehensively controls the entire document management server 1 by executing a program stored in the ROM 12 or the like. In particular, in this embodiment, the CPU 11 controls the procedure manual when there is a change in the procedure manual or when the change is resolved, and is necessary when the user requests to output the procedure manual. Controls such as distribution of various procedure manuals to an image forming apparatus, a tablet terminal, etc., the details of which will be described later.

The ROM 12 is a storage medium for storing programs and other data for execution by the CPU 11.

The RAM 13 is a storage medium that provides a work area when the CPU 11 operates according to an operation program.

The storage unit 14 is composed of a storage medium such as a hard disk, and stores a procedure manual which is a plurality of document data, information about users belonging to each line, other various management data, application programs, and the like.

The display device 15 includes a CRT, a liquid crystal display device, and the like, and displays various messages, an input reception screen for the user, a selection screen, and the like.

The input device 16 is used for input operations by the user, and includes a keyboard, a mouse, and the like.

The network interface unit 17 functions as a communication means for transmitting and receiving data via a network between the component management device 2, the equipment management device 3, the tablet terminal 4, the image forming device 5, and the like, which are external devices.

The parts management device 2 manages parts used in line work, for example, management of entry / exit of assembled parts, inventory management, and the like, and is composed of a PC.

The equipment management device 3 manages equipment such as machines used in line work, and also manages whether the equipment is currently in operation or out of order, and is composed of a PC.

The tablet terminal 4 is a mobile terminal of a user who accesses a document management server 1 and requests distribution of a procedure manual, or displays an electronic document such as a procedure manual managed by the document management server 1 on a display screen. It is a device.

The image forming apparatus 5 is a printing apparatus that prints a procedure manual or the like managed by the document management server 1 on paper 7 by a user's operation.

The dashboard 6 is a shared bulletin board that displays an electronic document such as a procedure manual, and is provided for each line.

FIG. 3 is a diagram for explaining an example of issuance, reissue, change, and return (rollback) of the procedure manual. In the example shown in FIG. 3, there are two lines, line 1 and line 2, at the start of production. Further, a procedure manual A version 101 has been issued, and each user of line 1 and line 2 is working according to this procedure manual A version 101.

At some point after that, line 3 is newly established, along with which the procedure manual B version 102 is issued, and the procedure manual A version 101 is terminated and discontinued. Each user of line 1 to line 3 will work according to the procedure manual B version 102.

After the issuance of the procedure manual B version 102, it is assumed that the problem a occurs in the component 1 used in the line 2 and the line 3. The administrator of the line 2 and / or the line 3 adds a procedure for solving (avoiding) the problem to the procedure manual B version 102. That is, the content of the procedure manual B version 102 is changed, and the procedure manual B version repair a103, which is a correction procedure manual, is registered. Therefore, after the registration of the procedure manual B version repair a103, the procedure manual B version repair a103 becomes the latest procedure manual in the line 2 and the line 3, and the work is executed according to this procedure manual B version repair a103.

After that, since the problem c occurred in the equipment (machine) in the line 2, the manager of the line 2 adds the procedure for solving (avoiding) the problem to the procedure manual B version repair a103. That is, the content of the procedure manual B version repair a103 is changed, and the procedure manual B version repair a repair c104, which is a correction procedure manual, is registered. In line 2, this procedure manual B version repair a repair c104 becomes the latest procedure manual, and the work is executed according to the procedure manual B version repair a repair c104.

After that, when the problem a of the component 1 is solved in the line 2, the procedure manual B version repair c105 excluding the additional part for solving the problem a is registered from the procedure manual B version repair a repair c104.

After that, when the procedure manual C version 106, which is a revised version of the procedure manual B version, is issued, the procedure manual B version 102 ends and is discontinued. Along with this, for line 2, the procedure manual C version repair c107, which added the procedure for solving the problem c of the equipment that has not been solved yet to the procedure manual C version, was registered. The work is performed according to the repair c107.

On the other hand, in line 3, after the registration of the procedure manual B version repair a103, a problem b occurred in the equipment (machine), so the manager of the line 3 added the procedure for solving (avoiding) the problem to the procedure manual B version repair a103. do. That is, the content of the procedure manual B version repair a103 is changed, and the procedure manual B version repair a repair b108, which is a correction procedure manual, is registered.

After that, when the problem b of the equipment in the line 3 is solved, the latest procedure manual in the line 3 is the original procedure manual excluding the additional part for solving the problem b from the procedure manual B version repair a repair b108. It is rolled back to the procedure manual B version repair a103. Further, when the problem a regarding the component 1 is solved in the line 3, the procedure manual B version 102, which is the original procedure manual excluding the additional part for solving the problem a, is displayed from the procedure manual B version repair a105. Rolled back. After that, when the procedure manual C version 106, which is a revised version of the procedure manual B version, is issued, the latest procedure manual in line 3 becomes the procedure manual C version 106.

Since no problem has occurred in line 1, the procedure manual A version 101, the procedure manual B version 102, and the procedure manual C version 106 are used as they are as the procedure manual.

In this way, if a problem occurs in any of the lines, the procedure manual for that line will be changed, the changed procedure manual will be the latest procedure manual, and when the problem is resolved, the original procedure manual will be restored.

FIG. 4A is a diagram showing document management data managed by the document management server 1. The document management data and each procedure manual are stored in the storage unit 14 of the document management server 1.

The document management data includes items such as ID, name, parent file, status, registration date, end date, registrant, application line, and related problems. The item "ID" is identification information for uniquely identifying each procedure manual, the item "name" is the name of the procedure manual, and the item "parent file" is the base of the procedure manual. The name of the procedure manual, the item "status" is information on the current status, the item "registration date" indicates the date when the procedure manual was registered, and the item "end date" is the date when the procedure manual was completed. The item "registrant" is the registrant of the procedure manual, the item "applicable line" is the name of the line to which the procedure manual is applied, and the item "related problem" causes a problem as described later. It is for associating with the parts management data or equipment management data.

In the example of FIG. 4, seven procedure manuals of ID: File00 0 1 to File00 07 are registered and managed. The procedure manual A version with ID: File00 01 is issued at the start of production, and the procedure manual B version with ID: File00 02 is accompanied by the change of parts after the issuance of the procedure manual A version. Was issued. Due to the issuance of the B version of the procedure manual, the A version of the procedure manual has been terminated (discontinued) and is in an invalid state (status is invalid). The procedure manual B version 102 is in the valid state (status is valid). Both the procedure manual A version and the procedure manual B version are applied to all lines 1 to 3.

The procedure manual B version repair a having the ID: File 0000 3 is a modification of the procedure manual B version due to the problem a occurring in the parts 1 used in the line 2 and the line 3 . For example, since the hole diameter of the component 1 is large and it is easy to shift during assembly, the procedure is changed to fixing with a jig and caulking. This procedure is only for a predetermined lot of parts, and when the lot is used up, the procedure is returned to the original procedure, and the procedure manual is also returned to the parent file, the procedure manual B version. The applicable lines of the procedure manual B version repair a are only the line 2 and the line 3 in which the problem a occurs, and are not applied to the line 1. Further, this procedure manual B version repair a is associated with the part that has a problem, which is managed by the parts management data described later, and B0005, which is the ID of the part, is set in the item of "related problem". ..

The procedure manual B version repair b, which has an ID: File 0000 4, is a procedure manual B due to a problem b occurring in the equipment used in the line 3 in a state where the problem a has occurred in the component 1. This is a modification of the version a. For example, the motor and belt of the caulking machine are out of order and do not move temporarily, so the change is to temporarily turn the handle of the caulking machine manually to crimp. At that time, supplementary explanations such as how many rotations of the handle and how many mm of the piston line may be pushed out may be described. This work procedure is restored when the failure of the caulking machine is corrected , and the procedure manual is also returned to the parent file, procedure manual B version repair a. The application line of the procedure manual B version repair a repair b is only the line 3 in which the problem b occurs, and is not applied to the line 1 and the line 2. In addition, this procedure manual B version repair a repair b is associated with the equipment that caused the problem, which is managed by the equipment management data described later, and M0003, which is the ID of the equipment, is set in the item of "related problem". ing.

The procedure manual B version repair c, which has an ID: File00 05, is a procedure manual B version due to a problem c occurring in the equipment used in the line 2 while the problem a has occurred in the part 1. A change has been made to Osamu a. The changed work procedure is restored when the equipment failure is corrected , and the procedure manual is also returned to the parent file, procedure manual B version repair a. The application line of the procedure manual B version repair a repair c is only the line 2 in which the problem c occurs, and is not applied to the line 1 and the line 3. In addition, this procedure manual B version repair a repair c is associated with the equipment that caused the problem, which is managed by the equipment management data described later, and M0005, which is the ID of the equipment, is set in the item of "related problem". ing.

The procedure manual C version with ID: File0000 6 is a substitute for the procedure manual B version and is in a state of waiting for review. In addition, the procedure manual C version repair c with ID: File007 7 is a modification of the procedure manual C version due to a problem c in the equipment used in line 2, and is also awaiting review. Is.

FIG. 4B is a diagram showing user management data managed by the document management server 1. This user management data is also stored in the storage unit 14 of the document management server 1.

The user management data includes each item of ID, name, role, authority, and line. The item "ID" is identification information for uniquely identifying each user, the item "name" is the name of the user, the item "role" indicates the role of the user, and the item "authority" is the user's. It is an authority, and the item "line" indicates the name of the line to which the user's authority extends.

For example, the user name "Sato" of ID: User0001 belongs to the production control department and is shown to be the manager of all lines.

FIG. 4C is a diagram showing parts management data managed by the parts management device 2. The parts management data includes items such as ID, part name, lot number, warehousing date, quantity, remaining amount , input line, and problem management. The item "ID" is identification information for uniquely identifying each part, the item "part name" is the name of the part, the item " lot No." is the lot number of the part, and the item " The warehousing date is the date when the part was warehousing, the item "quantity" is the warehousing quantity of the part, the item " remaining amount " is the remaining stock quantity of the part, and the item "input line" is the part. Is the name of the line in which is used, and the item "problem management" is an item for setting the content of the problem for the part that caused the problem. In the example shown in FIG. 4C, it is shown that there is a problem in the hole diameter of the component with ID: B0005. Then, the component of ID: B0005 is associated with the procedure manual B version repair a which is the procedure manual of ID: File0003 in the document management data shown in FIG. 4 (A).

FIG. 4D is a diagram showing equipment management data managed by the equipment management device 3. The equipment management data includes each item of ID, equipment name, line, status, status details , and problem management. The item "ID" is identification information for uniquely identifying each equipment (machine), the item "equipment name" is the name of the equipment, and the item "line" is the line in which the equipment is used. It is a name, the item "status" is an item indicating whether the equipment is operating or out of order, the item "status details" is an item for setting detailed status information, and the item "problem management" causes a problem. It is an item to set the content of the problem about the equipment. In the example shown in FIG. 4 (D), it is shown that a failure has occurred in each of the facilities of ID: M0003 and M0005. Then, the equipment of ID: M0003 is associated with the procedure manual B version repair b which is the procedure manual of ID: File0004 in the document management data shown in FIG. 4 (A), and the equipment of ID: M0005 is shown in FIG. 4 (A). ) Is associated with the procedure manual B version repair c, which is the procedure manual of ID: File0005 in the document management data shown in).

Next, the operation of the document management system shown in FIG. 1 will be described focusing on the operation of the document management server 1.

As described above, the document management server 1 manages the procedure manual as an electronic document and also manages the user. The user can request the document management server 1 to distribute the procedure manual in the range that he / she is in charge of from the tablet terminal 4 or the like, and the document management server 1 requests the requesting tablet terminal 4 or the image forming apparatus 5. The procedure manual is distributed so that the user can view the procedure manual on the tablet terminal 4 or print it on the paper 7 with the image forming apparatus 5. Further, the document management server 1 distributes the latest procedure manual for each line to the dashboard 6, and users belonging to each line can view and confirm the latest procedure manual on the dashboard 6.

Furthermore, users with higher authority (for example, line leaders and users in the production control department) can register, update, and end the procedure manual.

The parts management device 2 manages the parts management data described with reference to FIG. 4 (C) for the parts used in each line, and the parts management data is added or added by the person in charge each time a new part is received. The data is updated according to the usage status of the parts. When a problem occurs with a part, the person in charge sets (describes) that the problem has occurred in the item of "problem management" in the part management data.

Similarly, the equipment management device 3 manages the equipment management data described in FIG. 4 (D) for the equipment (machine) used in each line, and the person in charge manages the equipment every time a new equipment is installed. Data is added. When a failure occurs in the equipment, the person in charge sets (describes) that the failure has occurred in the "problem management" item of the equipment management data, and the status item is changed to "in failure".

On the other hand, the work on each line is performed according to the procedure manual, but if a problem occurs in a part or the equipment breaks down, the contents of the work procedure will be changed in the line using the part or equipment. Therefore, with the approval of an authorized leader, the person in charge creates a procedure manual that reflects the content change and registers it in the document management server 1. At the same time, document management data is created in association with the newly registered procedure manual, such as ID: File0003 to File0005 shown in FIG. 4A, and each item is set and additionally registered. The "Status" item is "Valid". The newly registered runbook will be the latest runbook for the corresponding line.

Registration of the procedure manual in the document management server 1 and additional registration of the document management data may be performed directly using the input device 16 of the document management server 1, or may be performed directly from the terminal device of the person in charge via the network. This may be done by accessing the document management server 1.

Further, the component ID (for example, B0005) or the equipment ID (for example, M0003 and M0005) of the corresponding component management data is input in the item of "related problem" of the added document management data. This input is performed, for example, as follows.

That is, when the document management data is added, the provisional update screen of the procedure manual as shown in FIG. 5 is displayed on the display device 15 of the document management server 1 or the display unit of the terminal device of the person in charge, and the added procedure manual is displayed. The input field 151 of the component ID or the equipment ID associated with is displayed. At this time, the part ID of the part management data in which the problem occurred (B0005 in the example of FIG. 4C) and the equipment ID of the equipment management data in which the problem occurred (M0003 and M0005 in the example of FIG. 4D). May be displayed in a list and let the person in charge select it.

When the person in charge inputs and confirms the part ID or equipment ID that caused the problem that caused the addition of the procedure manual, the part entered in the "Related problem" item of the added procedure manual. An ID or equipment ID is set, and the added procedure manual is associated with the input part ID or equipment ID. Among the document management data shown in FIG. 4A, IDs: File00 0 3 to File00 0 5 show states associated with the component ID: B0005 and the equipment IDs: M0003 and M0005, respectively.

Here, the procedure manual after the content change may be manually created by the person in charge, but if the document management server 1 has an automatic procedure manual creation function, it may be created by that function. Specifically, for example, a photograph is taken of the state of fixing with a jig, the procedure and precautions are described by handwriting, etc., and three sheets including the front and back pages to be inserted are scanned by a scanner. The document management server 1 compares and collates the scan data of the previous and next pages with the data of each already registered procedure manual, identifies the procedure manual to which the scan data is added, and scans the scan data excluding the previous and next pages. Create a new procedure manual by adding it between the pages of.

Next, when the problem that has occurred in the part or equipment is solved, the person in charge manages the parts or equipment for which the problem has been solved by the parts management data or equipment management managed by the parts management device 2 or the equipment management device 3. Delete the contents set in the "Problem management" item of the data. For example, as shown in the equipment management data of FIG. 6B, since the failure that occurred in the equipment of ID: M0003 and M0005 has been resolved, the "failure" set in the problem management item is deleted. .. By this deletion, "Running" is set in the "Status" item.

After that, the document management server 1 sets the "status" item of the document management data associated with the failure that occurred in the equipment of ID: M0003 and M0005 to "invalid" at a predetermined timing, thereby setting the procedure manual. Return to the procedure manual before the change.

Specifically, as shown in the document management data of FIG. 6A, the document server 1 has the IDs: File0004 and File0005 associated with the equipments of ID: M0003 and M0005 for each item of the status. Set "Disable". As a result, the latest procedure manuals of line 2 and line 3 are returned to the parent file, procedure manual B version repair a, respectively.

Here, the timing for setting the "status" item of the document management data to "invalid" is not limited, but may be, for example, when the user accesses the document management server 1 to check the procedure manual. , It may be a preset timing, or it may be performed at the same time when the content set in the "problem management" item of the parts management data or the equipment management data is deleted. In addition, in order to count the work time per process of the line, there is an effort to record the work start time and the work end time using a barcode reader. In addition, it is common practice to pick up multiple assembly parts from the parts warehouse, combine them into a single tray, and then provide them to the line, with lot information and barcodes in the parts set. Is attached, and when the work start of the parts set, that is, at the start of the line work, the information of the work start by reading the barcode is input, so that the document management server 1 can check whether the problem is solved. You may check and perform the process of setting the "status" item of the document management data to "invalid". Alternatively, a warning may be given to the operator so that the item of "status" is manually set to "invalid". Specifically, a method of displaying the fact on the tablet terminal 4 or notifying the operator by a buzzer or a lamp can be mentioned.

As described above, in this embodiment, one or a plurality of procedure manuals are registered, and the procedure manual in which the contents of any of the procedure manuals are changed according to the change of the parts lot or the failure of the equipment that has occurred is described. The procedure manual before the content change is registered as a parent document together with the registration date, and the procedure manual after the content change is associated with the changed parts and the failed equipment. In addition, "valid" is set in the status item and managed so that the procedure manual after the content change becomes the latest procedure manual. In addition, when the parts lot change or equipment failure is resolved, the status of the procedure manual after the content change is automatically changed to "invalid" or a warning is given to change it to "invalid". It is changed to "invalid" by manual operation such as, and it is managed so that the procedure manual before the change, which is the parent document, becomes the latest document.

In other words, the procedure manual after the content change is managed by associating it with the event such as the change of the parts lot or the equipment failure that triggered the content change, and the procedure manual after the content change is the latest until the event is resolved. It is managed as a document, and when the event is resolved, it automatically returns to the procedure manual before the content change based on the user's operation, so when the event occurs, the content of the procedure manual can be changed to make it the latest document. , Undoing, etc. can be performed easily and accurately.

In the embodiment described above, the document management data of FIG. 4A and the parts lot shown in the parts management data of FIG. 4C and / or the equipment shown in the equipment management data of FIG. 4D are used. Although the case of directly associating has been described, the problem management data may be created and the problem shown in the problem management data may be associated with the document management data as described with reference to FIG. 7.

FIG. 7A is a diagram showing document management data registered and managed by the document management server 1. The items of this document management data are the same as the items of the document management data shown in FIG. 4A, but each document of document ID: File00 0 3 to ID: File00 0 5 in the item of "related problems". "Issue001 to issu003" are set in each.

FIG. 7B is a diagram showing parts management data registered and managed by the parts management device 2. The item of this part management data is the same as the item of the part management data shown in FIG. 4C, but "issue001" is set for the part of the part ID: B0005 in the item of "related problem". Has been done.

FIG. 7C is a diagram showing equipment management data registered and managed by the equipment management device 3. The items of this equipment management data are the same as the items of the equipment management data shown in FIG. 4 (D), but in the item of "related problems", each equipment of equipment ID: M0003 and ID: M0005 is used. "Issue 002" and "issu 003" are set respectively.

FIG. 7D is a diagram showing problem management data registered and managed by the document management server 1. This problem management data is data that collectively manages problems that have occurred in parts and equipment, and each time a problem occurs in parts and equipment, a person in charge or the like creates problem management data.

The problem management data includes ID, problem content, association, ID, lot, and status items. The item "ID" is identification information for uniquely identifying the problem that has occurred, the item "problem content" is an item indicating the content of the problem that has occurred, and the item "related" is a problem related to parts management or equipment management. The item "ID" is an item indicating the ID of the part or equipment in which the problem occurred, and the item "lot" is an item indicating the part lot number when the problem occurred in the part. Yes, the item "status" is an item indicating whether the problem is occurring or solved.

In the example shown in FIG. 7 (D), three problems of ID: issu001 to ID: issu003 are occurring, ID: issu001 is a problem related to the part of part ID: B0005, and ID: issu002 is the equipment ID. : It is a problem related to the equipment of M0003, and ID: issu003 is shown to be a problem related to the equipment of equipment ID: M0005.

In the example of FIG. 7, when a problem occurs in a part or equipment, the person in charge additionally registers new data with an ID in the problem management data and inputs and sets necessary items in each item of the added problem management data. Then, set "Currently occurring" in the "Status" item. Further, among the parts management data shown in FIG. 7 (B), the item of "problem management" of the parts management data in which the problem occurred, and "of the equipment management data shown in FIG. 7 (C)" of the equipment management data in which the problem occurred. Enter the ID of the newly registered problem management data in the "Problem management" item. The input may be automatically performed by the parts management device 2 or the equipment management device 3 based on the input request from the document management server 1.

On the other hand, if a problem occurs with a part or equipment, the content of the work procedure will be changed on the line using the part or equipment, so the person in charge will reflect the content change with the approval of the authorized leader. Create the procedure manual and register it in the document management server 1. At the same time, document management data is created in association with the newly registered procedure manual, such as ID: File0003 to File0005 shown in FIG. 7A, and each item is set and additionally registered. The "Status" item is "Valid". The newly registered runbook will be the latest runbook for the corresponding line. Enter the ID of the corresponding problem management data (for example, issu001) in the "Related problem" item of the added document management data. This input is performed, for example, as follows.

That is, when the document management data is added, the provisional update screen of the procedure manual as shown in FIG. 8 is displayed on the display unit of the display device of the document management server 1 or the terminal device of the person in charge, and the added procedure manual is displayed. Display the selection field of the associated problem ID.

When the person in charge selects and confirms the problem ID that caused the addition of the procedure manual, the selected problem ID is set in the "Related problem" item of the document management data corresponding to the added procedure manual. And the added procedure is associated with the corresponding problem in the problem management data.

Next, when the problem occurring in the parts or equipment is solved, the person in charge inputs and sets "solve" in the "status" item of the problem management data for the problem management data in which the problem is solved. For example, as shown in FIG. 9C, since the problems of ID: issu002 and ID: issu003 have been solved, "solve" is input in the "state" item of the corresponding problem management data. At the same time, for the parts management data and / or the equipment management data, the problem ID associated with the item of "problem management" is deleted. In this example, as shown in the equipment management data in FIG. 9B, the problem ID set in the item of "problem management" of the management data of the equipment IDM0003 and M0005 is deleted. By deleting the problem ID, the "status" item changes to "operating". When "solve" is input in the "status" item of the problem management data, the document management server 1 asks the parts management device 2 and / or the equipment management device 3 for the parts whose problems have been solved. The equipment is requested to delete the problem ID associated with the "problem management" item of the management data, and based on this request, the parts management device 2 and / or the equipment management device 3 deletes the problem ID. , You may enter "in operation" in the "status" item.

After that, the document management server 1 returns the procedure manual to the procedure manual before the change by setting the "status" item of the document management data associated with the issue002 and the issue003 to "invalid" at a predetermined timing.

Specifically, as shown in the document management data of FIG. 9A, the document server 1 sets "invalid" for each item of the status for the IDs: File0004 and File0005 associated with issu002 and issu003, respectively. Set. As a result, the procedure manuals of line 2 and line 3 are returned to the procedure manual B version repair a, which is the parent file, respectively.

Here, the timing for setting the "status" item of the document management data to "invalid" is not limited, but as described in the example of FIG. 7, for example, the document management server 1 for the user to check the procedure manual. It may be when you access to, it may be a preset timing, or when the content set in the "Problem management" item of the parts management data or equipment management data is deleted. It may be done at the same time. Further, when the work start information by reading the barcode is input at the start of the work of the parts set, that is, at the start of the line work, the document management server 1 checks whether the problem is solved and manages the document. You may perform the process of setting the item of "status" of the data to "invalid". Alternatively, a warning may be given to the operator so that the item of "status" is manually set to "invalid".

Also in this embodiment, the procedure manual after the content change and the event such as the problem that triggered the content change are managed in association with each other, and the procedure manual after the content change is managed as the latest document until the event is resolved. When the event is resolved, the procedure manual is automatically restored or based on the user's operation, so the content of the procedure manual is changed due to the occurrence of the event and the latest document is used. Processing such as returning can be performed easily and accurately.

FIG. 10 is a flowchart showing the operation of the document management server 1 when the user of each line uses the procedure manual. The processes shown in the flowchart of FIG. 10 and the flowcharts after FIG. 11 are executed by operating the CPU 11 of the document management server 1 according to an operation program stored in the storage unit 14 or the like.

In step S01, user authentication is performed for direct access to the document management server 1 by the user or access via the tablet terminal 4, and in step S02, the line to which the user belongs or the user works based on the user management data. Check if you are the person in charge.

Next, in step S03, the procedure manual of the user's work range is extracted with reference to the document management data. For example, when the user belongs to line 1, the procedure manual for line 1 is extracted. Subsequently, in step S04, the version of the procedure manual, for example, the procedure manual A version, the procedure manual B version, the procedure manual C version, and the like are checked, and then in step S05, the latest version of each version is checked.

Next, in step S06, it is checked whether the date is the latest, and if it is not the latest (NO in step S06), the date with the latest date is selected in step S07, and then the process returns to step S06. If the date is the latest in step S06 (YES in step S06), in step S08, it is determined whether or not the "status" item is "valid". If it is not "valid" (NO in step S08), in step S09, the existence of the procedure manual one before the date is checked. If there is a procedure manual one date before (YES in step S09), the procedure manual is selected in step S10, and then the process returns to step S08. If there is no procedure manual whose date is one before in step S09 (NO in step S09), the procedure manual does not exist, so the process ends. In this case, the user may be notified that the procedure manual does not exist by displaying it on the screen.

In step S08, if the item of "status" is "valid" (YES in step S08), in step S11, it is checked whether or not there is a child procedure manual having the same parent that is within the user's responsibility. If not (NO in step S11), the process proceeds to step S16, and the procedure manual specified in step S08 is output. As an output method, the procedure manual may be transmitted to the image forming apparatus 5 for printing, or may be transmitted to the tablet terminal 4 for display.

In step S11, if there is a child procedure manual having the same parent that is within the user's responsibility (YES in step S11), the process proceeds to step S12, and there is a procedure manual in which the "status" item is "valid". To find out. If there is no "valid" procedure manual (NO in step S12), the process proceeds to step S16 to output the procedure manual. If there is a "valid" runbook (YES in step S12), check if there are multiple "valid" runbooks in step S13, and if there are not more than one (NO in step S13). The procedure manual is selected as an output material, and the procedure manual is output in step S16. If there are a plurality of "valid" procedure manuals (YES in step S13), the changed parts are combined in step S15, and then the combined procedure manual is output in step S16.

In this way, the latest procedure manual according to the line to which the user or group accessing the document management server 1 belongs is specified and distributed from the document management server 1. Therefore, the procedure manual to be delivered may differ depending on the line to which the user or group belongs. In this case, the procedure manual after the content change is delivered to the user or group belonging to any line, and the procedure manual is delivered to the other line. The procedure manual before the content change is delivered to the users and groups to which it belongs.

FIG. 11A is a flowchart showing the registration process of the procedure manual whose contents have been changed, and FIG. 11B is a continuation thereof.

After user authentication is performed in step S21, it is determined in step S22 whether to acquire or modify the procedure manual based on the user operation. If the procedure manual is acquired (acquired in step S22), the process proceeds to the process shown in the flowchart of FIG. If the procedure manual is modified (corrected in step S22), it is checked in step S23 whether the user has the leader authority, and if not (NO in step S23), "registration" is performed in step S24. After displaying a message indicating that "leader approval is required in order to reflect the above", the process proceeds to step S25. If the user has leader authority (YES in step S23), the process proceeds to step S25 as it is.

In step S25, the changed part of the procedure manual including the previous and next pages is accepted. Specifically, the changed part of the procedure manual including the front and back pages is read by a scanner (not shown).

Next, in step S26, it is checked whether or not the automatic judgment function of the base procedure manual is on, and if it is on (YES in step S26), in step S27, the user's range of responsibility is narrowed down to the official version procedure manual. Extract the list with. Then, in step S28, pattern matching is performed on a page-by-page basis for the official version of the procedure manual and the read changed portion, and the base procedure manual is specified.

Next, in step S29, it is determined whether or not the base procedure manual can be uniquely specified, and if it can be specified (YES in step S29), the process proceeds to step S31. If it cannot be specified (NO in step S29), in step S30, a list of official version procedure manuals of the user's range of responsibility is displayed and the user is made to select, and then the process proceeds to step S31. Even if the automatic judgment function of the base procedure manual is not turned on in step S26 (NO in step S26), in step S30, after displaying the list of the official version procedure manual of the user's area of responsibility and letting the user select it, The process proceeds to step S31.

In step S31, a confirmation screen is displayed as to whether or not the specified base procedure manual is acceptable, or whether or not the user-selected procedure manual is acceptable.

When the OK button is pressed by the user on the confirmation screen, in step S32, the page of the changed part is combined with the base procedure manual, the changed procedure manual (corrected version) is temporarily created, and the number is assigned to the document management data. And register the procedure manual.

Next, in step S33, it is checked whether or not the user has the leader authority, and if the user does not have the user authority (NO in step S33), in step S34, the fact that the temporary registration is completed is displayed on the screen, and the process is performed. finish. The temporary registration is displayed, for example, by displaying the procedure manual B version repair a (provisional).

In step S33, if the user has leader authority (YES in step S33), in step S35, a message asking whether to register the association between the created new procedure manual and the problem management data is displayed, and the user associates. If you do not choose to register (NO in step S36), in step S37, the registration is completed and the process ends.

If the user chooses to register the association (YES in step S36), the problem management data is accessed in step S38, and the "status" item is set to "occurring" in the problem management data of the user's area of responsibility. After acquiring the data, the acquired problem management data is displayed in a list as shown in FIG. 8 in step S39, and the selection of desired problem management data is accepted in step S40.

Next, in step S41, the problem ID of the selected problem management data is registered in the "related problem" item of the changed procedure manual, and then in step S42, the registration is completed, for example, the name of the procedure manual. It is displayed together with (for example, procedure manual B version repair a).

FIG. 12A is a flowchart showing a process of canceling the association between the procedure manual and the occurrence of the problem after the problem is solved for the procedure manual whose contents have been changed due to the occurrence of a problem of parts or equipment. Yes, the figure (B) is a continuation of that. In this example, when the user of each line uses the procedure manual, the association is released. The problem that occurred is shown when it is managed by the problem management data.

As described above, when the problem of the part or the equipment is solved, the person in charge sets "solve" in the item of "status" for the data in which the problem is solved among the problem management data.

After that, when the user who wants to output the procedure manual accesses the document management server 1, the document management server 1 authenticates the user in step S51, and then in step S52, the line to which the user belongs or the user is assigned based on the user management data. Check if you are the person in charge of the work.

Next, in step S53, the latest procedure manual of the user's work range is extracted with reference to the document management data, and then in step S54, the problem ID is set in the "related problem" item of the extracted procedure manual. It is confirmed whether or not it is set, and it is determined in step S55 whether or not the problem ID is set.

If the problem ID is not set (NO in step S55), the process proceeds to step S04. If the problem ID is set (YES in step S55), after confirming the problem management data in step S56, is there any problem management data in which the item of "status" is "solved" in step S57? Judge whether or not. If not (NO in step S57), the process proceeds to step S04. If there is problem management data in which the item of "status" is "solved" (YES in step S57), the problem ID of the problem management data in which "solved" is set in step S58 is associated. After changing the status of the procedure manual to "invalid", the process proceeds to step S04.

The procedure manual whose status is "Invalid" is excluded from the latest procedure manual, and its parent document, the procedure manual, becomes the latest procedure manual.

Since steps S04 to S16 are the same as steps S04 to S16 in the flowchart of FIG. 10, the same step numbers are assigned and the description thereof will be omitted.

Although one embodiment of the present invention has been described above, the present invention is not limited to the above embodiment. For example, we have described the case where the document is a runbook used for line work, but it can be applied to documents that require work such as temporary change or undo, for example, the specification of the application that is temporarily changed. It can also be applied to books.

Further, although the parts management device 2 and the equipment management device 3 are configured as devices separate from the document management server 1, the parts management data and the equipment management data may be managed by the document management server 1 together with the documents. ..

1 Document management server (document management device)
11 CPU
14 Memory
15 Display device
2 Parts management device 3 Equipment management device 4 Tablet terminal 5 Image forming device 101-108 Procedure manual (document)

Claims (9)

A registration method for registering one or more documents and for registering a document whose contents are changed according to an event that has occurred.
Associating means for associating the changed document with the above-mentioned event,
When the document after the content change is associated with the event by the association means, the document after the content change is managed as the latest document until the event is resolved, and the event is resolved. If so, a management measure that warns you to revert to or revert to the original document,
A document management device characterized by being equipped with. A delivery control means for delivering the document to a predetermined delivery destination is provided.
The delivery control means distributes the document before the content change to the first delivery destination consisting of individuals and / or groups not affected by the event, and the document after the content change is affected by the event. The document management device according to claim 1, which is delivered to a second delivery destination consisting of an individual and / or a group. The document is a procedure manual in line work, the content change of the document is a change of the work content described in the procedure manual, and the distribution control means distributes the procedure manual after the content change to the second distribution. The document management device according to claim 2, which is delivered to a worker on a line performing work affected by the above-mentioned event. The document is a procedure manual in the line work, and the content change of the document is a change related to a lot of parts used in the line work.
The document management device according to any one of claims 1 to 3, wherein the event is a change in a lot of parts used for line work, and the event is resolved by the end of use of the parts for the lot. The document is a procedure manual in the line work, and the content change of the document is a change related to the equipment used for the line work.
The document management device according to any one of claims 1 to 3, wherein the event is a state change of equipment used for line work, and the event is resolved by the end of the state change of equipment. The document is a procedure manual in the line work, and the content change of the document is a change for avoiding a problem in the line work.
The document management device according to any one of claims 1 to 3, wherein the event is a problem in line work, and the problem is solved by solving the problem. When the information indicating the start of the line work is input, the management means checks whether the event has been resolved, and if so, reverts to the document before the content change or warns to return. The document management device according to any one of claims 3 to 6. The document management device
A registration step of registering one or more documents and registering the document whose contents are changed according to the event that occurred and the document before the contents change as the parent document.
An association step that associates the changed document with the event,
When the document after the content change is associated with the event by the association step, the document after the content change is managed as the latest document until the event is resolved, and the event is resolved. If so, a management step that warns you to revert to or revert to the original document,
A document management method characterized by running. To the CPU of the document management device
A registration step of registering one or more documents and registering the document whose contents are changed according to the event that occurred and the document before the contents change as the parent document.
An association step that associates the changed document with the event,
When the document after the content change is associated with the event by the association step, the document after the content change is managed as the latest document until the event is resolved, and the event is resolved. If so, a management step that warns you to revert to or revert to the original document,
A document management program for running.

Images