JP6408232B2 - Document management method - Google Patents

Description

  The present invention relates to a document management method.

  2. Description of the Related Art A manufacturing process process management system that performs manufacturing history management by attaching a barcode to a product and reading the barcode in each manufacturing process is known (see, for example, Patent Document 1). Also, in the assembly process of products on the production line, a lot card is attached to the product and a part card is attached to the part. When selecting a part, the lot card and the part code are read and related to each other, so that the association rules are correct. There is known a manufacturing management system that checks whether or not to prevent a mistake in selecting a part (see, for example, Patent Document 2).

  Conventionally, in the acceptance work of application documents such as insurance documents sent from the user, as in the technique described in Patent Document 1, a form barcode is pasted on the received application documents, and sorting, cutting, scanning, etc. History is managed by performing an operation of reading a form barcode in a process. In addition, as in the lot management method described in Patent Document 2, the received application documents are managed by a set called a batch, and a batch confirmation slip on which a management barcode for identifying the batch is printed and a plurality of application documents. At the same time, the process history is managed by associating the management barcode and the form barcode.

Japanese Patent Laid-Open No. 5-233641 Japanese Patent Laid-Open No. 2001-325019

However, there may be incomplete forms in the accepted application documents. This incomplete form (incomplete form) can only be managed manually until the deficiency is resolved. There is a risk of missing defective forms before they are resolved. In addition, in the telephone inquiry to solve the deficiencies, the operator is calling while looking at the deficient forms that are the actual ones, so the work is complicated and there is a possibility that the deficient forms are lost.
Therefore, the present invention has been made in view of the above circumstances, and an object thereof is to provide a document management method capable of managing application documents safely and correctly.

[1] In order to solve the above problems, a document management method according to an aspect of the present invention is a document management method for registering text information described by a user in an application document provided with a machine reading code in a database. The process management server issues a first confirmation code that issues a normal confirmation code corresponding to a predetermined number of normal documents that are application documents that are not defective and a defect confirmation code that corresponds to each defective document that is a defective application document. a step, the process control server, a first normal documents association step of associating the predetermined number of machine-readable code the normal check code, the process control server, the machine-readable code on the deficiencies confirmation code a first incomplete documents association step for associating in a one-to-one, the data input device, and a machine-readable code of the predetermined number of the associated normal verification code What has a registration step of registering the text information described in the normal documents of the predetermined number in the database.

[2] In the document management method according to [1] above, the terminal generates a normal confirmation slip provided with the normal confirmation code and a deficiency confirmation voucher for the amount of defective documents provided with the deficiency confirmation code. The first normal document correlating step reads the normal confirmation code provided on the normal confirmation slip and the machine reading code provided on each of the predetermined number of normal documents. The first deficient document correlating step is performed by reading deficiency confirmation codes provided in the deficiency confirmation slips and machine reading codes provided in the deficient documents, respectively.
[3] In the document management method according to [1], the terminal includes a normal confirmation slip provided with the normal confirmation code and document management number information indicating the predetermined number in the first generation step; A deficiency confirmation slip corresponding to the deficient document quantity provided with the deficiency confirmation code is generated.
[4] In the document management method described in [3] above, when there is a new deficient document in the predetermined number of normal documents, the process management server confirms a new deficiency check corresponding to the new deficient document. a second issuing step of issuing a code, the terminal, a new document management number information representing the number obtained by subtracting the number of the new deficiencies documents several said indicating normal verification code and the document management number information And a second generation process for generating a new deficiency confirmation voucher provided with the new deficiency confirmation code and the process management server in the new deficiency confirmation voucher. A second deficient document relationship that reads the new deficiency confirmation code provided and the machine reading code provided in the new deficient document and relates the machine reading code to the new deficiency confirmation code on a one-to-one basis. Process and Further comprising: a.
[5] In the document management method according to any one of [1] to [4], an image information generation step in which a scanner device generates image information of the defective document, and the data input device includes the defective document. An input step for inputting the text information described in the above, a correlation step in which the data input device relates the image information and the text information according to a machine reading code provided in the incomplete document, and call information A list generation process in which the management server generates a deficient document confirmation list including at least telephone number information based on the text information, and call history information relating to deficiency complementation obtained by the terminal of the outbound device And an associating step for associating with the deficient document confirmation list.

  According to the present invention, application documents can be managed safely and correctly.

1 is a schematic block diagram of an example of a document management system to which a document management method according to an embodiment is applied. It is a figure explaining the outline | summary of management of the application document sent from the user. It is a figure explaining the outline | summary of management of an application document, when a defect document is newly discovered from a normal document in the stage which once distinguishes and manages a normal document and a defect document. It is a figure which shows the example of a data structure of the confirmation slip ID management list which a process management server stores in batch information DB. It is a figure which shows the example of a data structure of the form ID management list which a process management server stores in batch information DB. FIG. 10 is a diagram illustrating an example in which a process management server updates a confirmation form ID management list stored in a batch information DB when a defective document is newly found from normal documents. FIG. 10 is a diagram illustrating an example in which a process management server updates a form ID management list stored in a batch information DB when a defective document is newly found from normal documents. It is a figure which shows the example of a data structure of the deficient document confirmation list stored in customer DB of a call information management server. It is a figure which shows the example of the outline sequence of a document management system.

Hereinafter, embodiments for carrying out the present invention will be described in detail with reference to the drawings.
The present embodiment is an example of a document management method and a document management system for receiving an application document sent from a user and managing the received application document. The application document is, for example, a document in which the user or his / her representative fills in the intention to apply for receiving provision of a predetermined service and the details of the application, and personal information such as name, address, and telephone number.

  FIG. 1 is a schematic block diagram of an example of a document management system to which a document management method according to this embodiment is applied. As shown in FIG. 1, the document management system 1 includes a process management server 10, a personal information management server 20, a call information management server 30, a process management apparatus 40, a scanner apparatus 50, and a data input apparatus 60. , Outbound device 70 and network 80.

  The process management server 10, personal information management server 20, call information management server 30, process management apparatus 40, scanner apparatus 50, data input apparatus 60, and outbound apparatus 70 are respectively connected via the network 80. It is connected. The network 80 is a computer network such as a local area network (LAN), for example.

  The process management server 10 is a server device that manages various work processes and the like of document reception work. The process management server 10 includes a setting information DB 11, a batch information DB 12, and a process information DB 13. The setting information DB 11 manages business information for each business. The business information is information including customer information, project name, and the like. The batch information DB 12 manages the confirmation slip of the batch when handling a plurality of application documents as one set (batch). The process information DB 13 manages processes such as sorting, cutting, and scanning.

  The personal information management server 20 is a server device that manages personal information described in application documents. The personal information here is, for example, an address, a name, a telephone number, an e-mail address, information relating to an individual regarding application, and the like. The personal information management server 20 includes an image DB 21 and an index DB 22. The image DB 21 registers image information (image data) for each form of the application document captured by the scanner device 50. The index DB 22 registers text information (including personal information) in a description column for each form of the application document input by the data input device 60.

  The call information management server 30 is a server device that manages confirmation information regarding incomplete documents. The call information management server 30 includes a customer DB 31. The customer DB registers information for confirming incomplete documents by calling and information obtained by confirming by calling.

  The process management device 40 is a device that registers business information and prints a batch confirmation form. The process management apparatus 40 includes a terminal 41, a printer 42, and a barcode reader 43. The terminal 41 is realized by a computer device. The printer 42 is a device that prints a confirmation slip. The bar code reader 43 is a reading device that reads a bar code that is a machine reading code.

The scanner device 50 is a capturing device that captures each form of application documents as an image.
The data input device 60 is a device for inputting text information of an application document entered by a user by an operator's operation.

  The out-band device 70 is a device that presents an image of an incomplete document and the operator calls according to the image. The outbound device 70 includes a terminal 71, a telephone 72, and a headset 73. The terminal 71 is realized by a computer device. The telephone 72 and the headset 73 are used in a call work by an operator.

  FIG. 2 is a diagram for explaining an outline of management of application documents sent from the user. As shown in FIG. 2, the received application documents are managed through the stages of “classification of normal / incomplete documents”, “issue of confirmation slip ID / confirmation slip”, and “correspondence between confirmation slip and document”. Is done.

  In the “classification of normal / deficient documents” stage, the application documents are classified into normal documents and deficient documents. The application document is composed of one or more forms. The application document is provided with a machine reading code in which a form ID (form code) for identifying the form is recorded for each form. Specifically, a barcode that can be read by the barcode reader 43 and the scanner device 50 is printed or affixed to each form.

  The normal document is a document in which all the forms are prepared as application documents, the form is not damaged and cannot be processed, and the form is not leaked, the seal is missing, and no mistake is found. A deficient document is a document in which there are missing or damaged forms in the application documents, omissions in the forms, missing omissions, or errors. The normal document and the defective document are classified manually by a classification operator or by a sorting machine.

  Next, in the “issue of confirmation voucher ID / confirmation voucher” stage, a plurality of normal documents are collected into an arbitrary set (batch) for each trader's order. Then, the process management server 10 issues a normal confirmation form ID (normal confirmation code) that is identification information of the normal confirmation form for each batch. Moreover, the process management server 10 issues a deficiency confirmation slip ID (deficiency confirmation code) for each deficient document. The process management server 10 associates a business ID for identifying a business, flag information indicating whether the business is normal or incomplete (normal / defective flag), a confirmation slip ID, and the number (number) of forms corresponding to the confirmation slip. A confirmation slip ID management list is generated. The process management server 10 registers the confirmation slip ID management list in the batch information DB 12.

  The process management apparatus 40 causes the printer 42 to print a normal confirmation form describing the normal confirmation form ID and the number (“3”) issued by the process management server 10. In addition, the process management apparatus 40 causes the printer 42 to print a defect confirmation slip describing the defect confirmation slip ID and the number (“1”) issued by the process management server 10.

  Next, in the “association between confirmation form and document” stage, the operator associates and manages the normal confirmation form and the normal document for each batch. Further, the operator manages the deficient document and the deficiency confirmation slip in association with each deficient document. The process management server 10 also associates the confirmation slip ID of the confirmation slip, the old confirmation slip ID that is the history of the confirmation slip ID of the confirmation slip, and the form ID of the slip corresponding to the confirmation slip. Generate a management list. The process management server 10 registers the form ID management list in the batch information DB 12.

  FIG. 3 is a diagram for explaining an outline of management of application documents when a new defective document is found from a normal document in a stage where normal documents and defective documents are once managed separately. As shown in FIG. 3, when a new defective document is found from the normal documents in the “find defective document from normal documents” stage, the new defective document is pulled out from the batch of normal documents.

  Next, at the stage of “issue of new deficiency confirmation slip ID / confirmation voucher”, the process management server 10 assigns a new deficiency confirmation voucher ID (new deficiency confirmation code) for the batch from which a new deficient document has been extracted. Issue. Further, the process management apparatus 40 causes the printer 42 to print a revised normal confirmation form that describes a new number (“2”) obtained by subtracting the number of new defective documents from the number of batches. Further, the process management apparatus 40 causes the printer 42 to print a new deficiency confirmation voucher describing the new deficiency confirmation voucher ID and the number (“1”) issued by the process management server 10.

  Next, in the “association of confirmation form and document” stage, the operator associates and manages the revised normal confirmation form and the normal document. The operator also manages the new deficiency document and the new deficiency confirmation slip in association with each other. Further, the process management server 10 creates a new defect check slip ID of the new defect check slip, a new slip slip form ID, and a check slip ID (formerly old check slip to which this defect slip was previously associated). The form ID management list registered in the batch information DB 12 is updated in association with the confirmation form ID).

Next, an example of the data configuration of data used in the present embodiment will be described.
FIG. 4 is a diagram illustrating an example of the data configuration of the confirmation form ID management list stored in the batch information DB 12 by the process management server 10. As shown in FIG. 4, the confirmation slip ID management list includes items of business ID, normal / defective flag, confirmation slip ID, and number in association with each other. The business ID is identification information indicating the business of the application document (for example, information indicating “Apply for △ Company's ΔΔ Insurance”). The normal / defective flag is flag information indicating the type of the confirmation slip, and is represented by “normal” or “defective”, for example. The confirmation form ID is identification information of a confirmation form (a normal confirmation form or an incomplete confirmation form). The number is the number of forms associated with the confirmation slip.

  In the example of the confirmation form ID management list of FIG. 4, the number of batches of a normal document whose business ID is “ZZZ” is “3”, and the normal confirmation form ID of the normal confirmation form is “C001”. Further, the number of batches of the defective document having the business ID “ZZZ” is “1”, and the defect confirmation slip ID of the defect confirmation slip is “F002”.

  FIG. 5 is a diagram illustrating an example of the data configuration of the form ID management list stored in the batch information DB 12 by the process management server 10. As shown in FIG. 5, the form ID management list includes items of confirmation form ID, old confirmation form ID, and form ID in association with each other. The confirmation form ID is identification information of a confirmation form (a normal confirmation form or an incomplete confirmation form). The old confirmation form ID is a confirmation form ID (history) before being changed. The form ID is form identification information associated with the confirmation form.

  In the example of the form ID management list in FIG. 5, when referring to FIG. 4, the confirmation ID (normal confirmation form) with the confirmation form ID “C001” has the form IDs “DC001” and “DC002”. A certain form is related. In addition, a confirmation slip (deficiency confirmation slip) with a confirmation slip ID “F002” is associated with a slip with a slip ID “DC009”.

  FIG. 6 is a diagram showing an example in which the process management server 10 updates the confirmation form ID management list stored in the batch information DB 12 when a new defective document is found from normal documents. In the example of the confirmation form ID management list of FIG. 6, the number of normal documents of the normal confirmation form having the confirmation form ID “C001” is “2” with respect to the confirmation form ID management list shown in FIG. A new deficiency confirmation voucher record whose new deficiency confirmation voucher ID is “F003” is added to the third line.

  FIG. 7 is a diagram showing an example in which the process management server 10 updates the form ID management list stored in the batch information DB 12 when a new defective document is found from normal documents. In the example of the form ID management list in FIG. 7, the record on the second line in FIG. 5 is updated as shown in FIG. That is, when a form with the form ID “DC002” is found as a new deficient form, the process management server 10 assigns the deficiency confirmation form ID “F003” of the new deficiency confirmation form corresponding to this new deficient form. The form ID “DC002” is associated, and the normal confirmation form ID “C001” of the normal confirmation form originally associated with the form ID “DC002” is recorded as the old confirmation form ID.

  FIG. 8 is a diagram illustrating an example of the data configuration of the deficient document confirmation list stored in the customer DB 31 of the call information management server 30. As shown in FIG. 8, the defective document confirmation list is associated with items of form ID, name, address, telephone number, and call history information. The form ID is identification information of a defective form. The name is information indicating the name of the user related to the deficient form. The address is information representing the address of the user. The telephone number is information indicating the telephone number of the user. The call history information is information (history information) obtained by the operator calling the user. The deficient document confirmation list is generated by the call information management server 30 based on the personal information stored in the index DB 22 of the personal information management server 20.

Next, the operation of the document management system 1 according to the present embodiment will be described.
FIG. 9 is a diagram showing an example of a schematic sequence of the document management system 1. The broken line blocks J1 to J6 shown in the vertical column at the left end of FIG. 9 show the contents of each work process of the received application document.

First, the operation of the process management device 40 will be described.
In step S1 in the business registration J1, the terminal 41 of the process management apparatus 40 inputs business information by an operator's operation. The business information is information that identifies a business. Specifically, for example, the business information includes customer identification information for identifying a customer and service identification information for identifying a service. Next, the terminal 41 transmits business information to the process management server 10.

  Next, in step S2 of the confirmation slip printing J2, the terminal 41 of the process management apparatus 40 obtains the number of printed sheets representing the number of printed sheets of the normal confirmation sheet and the incomplete confirmation sheet, which are obtained by sorting the normal document and the incomplete document, Document management number information indicating the number of forms per one normal confirmation slip is transmitted to the process management server 10.

Next, in step S3 of the confirmation slip printing J2, the terminal 41 of the process management apparatus 40 receives the print instruction command transmitted by the process management server 10 by the process of step S12 described later. This print instruction command includes a normal confirmation slip ID and document management number information of the normal confirmation slip, and a defect confirmation slip ID of the defect confirmation slip.
Next, the terminal 41 causes the printer 42 to print the normal confirmation slip describing the normal confirmation slip ID and the document management number information and the defect confirmation slip describing the defect confirmation slip ID and the document management number information “1”. . In other words, the terminal 41 generates a normal confirmation slip provided with a normal confirmation code and document management number information indicating a predetermined number, and a deficiency confirmation voucher corresponding to a deficient document quantity provided with a deficiency confirmation code (first Production process).

  Next, in step S4 in the association J3 between the confirmation form and the form, the terminal 41 of the process management apparatus 40 instructs the process management server 10 to associate the normal confirmation form ID and the deficiency confirmation form ID with the form ID.

  Next, when a new deficient document is found from normal documents in the extraction of new deficient forms J4, in step S5, the terminal 41 of the process management apparatus 40 confirms the normality corresponding to the batch including the deficient documents. A form ID and a form ID for an incomplete document are designated, and re-creation instruction information is transmitted to the process management server 10.

Next, in step S6 in extracting a new defective form J4, the terminal 41 of the process management apparatus 40 receives the print instruction command transmitted by the process management server 10 in the process of step S14 described later. This print instruction command includes the normal check slip ID and document management number information of the revised normal check slip, and the new deficiency check slip ID of the new deficiency check slip.
Next, the terminal 41 includes a revised normal confirmation vote describing the normal confirmation vote ID and the revised document management number information, a new defect confirmation vote describing the new defect confirmation vote ID and the document management number information “1”, Is printed by the printer 42. That is, the terminal 41 has a new normal confirmation slip provided with new document management number information representing the number obtained by subtracting the number of new defective documents from the number indicated by the normal confirmation code and the document management number information, and A new deficiency confirmation slip provided with a new deficiency confirmation code is generated (second generation step).

Next, the operation of the process management server 10 will be described.
In step S11 in the business management J1, the process management server 10 receives the business information transmitted by the terminal 41 of the process management apparatus 40 by the process in step S1. The process management server 10 issues a business ID for the received business information, associates the business information with this business ID, and registers it in the setting information DB 11.

Next, in step S12 of the confirmation slip printing J2, the process management server 10 receives the number of printed sheets information and the document management number information transmitted by the terminal 41 of the process management apparatus 40 by the process of step S2.
Next, the process management server 10 issues a normal confirmation slip ID for the number of printed normal confirmation slips and a defect confirmation slip ID for the number of printed defective confirmation slips. That is, the process management server 10 issues a normal confirmation code corresponding to a predetermined number of normal documents that are application documents having no deficiencies and deficiency confirmation codes corresponding to deficient documents that are deficient application documents (No. 1). 1 issuance process).
Next, the process management server 10 generates a confirmation voucher ID management list in which the business ID, normality / deficiency flag, confirmation voucher ID, and number are related, and stores this confirmation voucher ID management list in the batch information DB 12. Store.
Next, the process management server 10 transmits to the process management apparatus 40 a pair of normal confirmation slip IDs and document management count information for the number of prints and a deficiency check slip ID for the number of prints.

Next, in step S13 in the association J3 between the confirmation form and the form, the normal confirmation form ID, the deficiency confirmation form ID, and the form ID designated by the terminal 41 of the process management apparatus 40 by the process of step S4 are received.
Next, the process management server 10 generates a form ID management list in which the confirmation form ID, the old confirmation form ID, and the form ID are associated, and stores this form ID management list in the batch information DB 12. That is, the process management server 10 reads the normal confirmation code provided on the normal confirmation slip and the machine reading code provided on each of the predetermined number of normal documents, and associates the predetermined number of machine reading codes with the normal confirmation code. (First normal document association process). Further, the process management server 10 reads the deficiency confirmation code provided in each deficiency confirmation slip and the machine reading code provided in each deficient document, and associates the machine reading code with the deficiency confirmation code on a one-to-one basis ( First deficient document association process).

Next, in step S14 in the extraction of a new defective form J4, the process management server 10 receives the re-creation instruction information transmitted by the terminal 41 of the process management apparatus 40 by the process of step S5, and the designated normal confirmation form An ID (a normal confirmation slip ID corresponding to a batch including defective documents) and a form ID for the defective documents are acquired.
Next, the process management server 10 issues a new defect confirmation slip ID. That is, the process management server 10 issues a new defect check code corresponding to the new defect document (second issue process).
Next, the process management server 10 adds a record including a new deficiency confirmation voucher ID for the new deficiency confirmation voucher to the confirmation voucher ID management list stored in the batch information DB 12.
Next, the process management server 10 updates the confirmation slip ID corresponding to the new defect confirmation slip in the form ID management list stored in the batch information DB 12 with the new defect confirmation slip ID, and sets the old confirmation slip ID to the original normal state. Update with confirmation slip ID. That is, the process management server 10 reads the new deficiency confirmation code provided in the new deficiency confirmation slip and the machine reading code provided in the new deficiency document, and adds 1 to the new deficiency confirmation code. One-to-one relationship (second deficient document association step).
Next, the process management server 10 transmits to the process management apparatus 40 a print instruction command including the revised normal confirmation form ID and the revised document management number information pair and the new deficiency confirmation form ID.

Next, the operation of the scanner device 50 will be described.
In step S21 in the scan and data input J5 of the form, the scanning device 50 performs the operation of the normal confirmation form ID corresponding to the batch including the normal document, the form ID of the normal document, and the normal document by an operation by the operator. The image is captured and the image information is stored in the image DB 21 of the personal information management server 20. That is, the scanner device 50 generates image information of an incomplete document (image information generation step).
Similarly, by the operation by the operator, the scanning device 50 captures the defect confirmation slip ID corresponding to the defective document, the form ID of the defective document, and the image of the defective document, and stores the image information in the personal information management server 20. Store in the image DB 21.
Here, for example, the file name of the image data stored in the image DB 21 may be a form ID.

Next, the operation of the data input device 60 will be described.
In step S31 in the scan and data input J5 of the form, the data input device 60 reads the image information corresponding to the desired form ID from the image DB of the personal information management server 20.

Next, in step S32 in the scan and data input J5 of the form, the data input device 60 inputs the form ID of the normal document and the text information (personal information) described in the user included in the image information by an operation by the operator. The form ID and text information of the normal document are stored in the index DB 22 of the personal information management server 20. That is, the data input device 60 registers text information described in a predetermined number of normal documents in the database in accordance with a predetermined number of machine reading codes related to the normal confirmation code (registration step).
Similarly, by the operation by the operator, the data input device 60 inputs the document ID of the incomplete document and the text information (personal information) described by the user included in the image information, and the form ID and text information of the incomplete document are input to the personal information. Stored in the index DB 22 of the management server 20. That is, the data input device 60 inputs the text information described in the incomplete document (input process). Further, the data input device 60 associates the image information and the text information according to the machine reading code provided in the incomplete document (association step).

Next, the operation of the outbound device 70 will be described.
In step S41 in the deficient form inquiry response J6, the terminal 71 of the outbound device 70 transmits an instruction to create a deficient document confirmation list.
Next, in step S42 in the inquiry response J6 J6, the terminal 71 refers to the defect document confirmation list registered in the customer DB 31 of the call information management server 30 and corresponds to the document ID in the defect document confirmation list. The image information of the defective form is read from the image DB 21 of the personal information management server 20.

  Next, in step S43 in the inquiry response J6 of the defective form, the outbound device 70 uses the telephone 72 and the headset 73 as a result of the call to the customer, and the information obtained as a call history information is a defective document confirmation list. Add to The terminal 71 may register the call history information in the customer DB 31 in association with the deficient document confirmation list using the form ID as a key. That is, the terminal 71 of the outbound device 70 associates the call history information regarding the deficiency supplement obtained by the call with the deficient document confirmation list (relation process).

Next, the operation of the call information management server 30 will be described.
In step S51 in the deficient form inquiry response J6, an instruction to create a deficient document confirmation list transmitted by the terminal 71 of the outbound device 70 by the processing in step S41 is received.
Next, the call information management server 30 acquires personal information from the index DB 22 of the personal information management server 20, generates a defective document confirmation list based on the personal information, and stores the defective document confirmation list in the customer DB. To do. That is, the call information management server 30 generates a deficient document confirmation list including at least information of the telephone number based on the text information (list generation step).

As described above, the document management method according to the present embodiment registers the text information described by the user in the application document provided with the machine reading code in the database. In this document management method, a normal confirmation code corresponding to a predetermined number of normal documents that are application documents having no deficiencies and a deficiency confirmation code corresponding to each deficient document that is a deficient application document are issued. It has an issue process. The document management method includes a first generation step of generating a normal confirmation form provided with a normal confirmation code and a deficiency confirmation form corresponding to the number of deficient documents provided with a deficiency confirmation code. The document management method reads the normal confirmation code provided on the normal confirmation slip and the machine reading codes provided on each of the predetermined number of normal documents, and associates the predetermined number of machine reading codes with the normal confirmation code. A first normal document associating step; This document management method reads the deficiency confirmation code provided in each deficiency confirmation slip and the machine reading code provided in each deficient document, and associates the machine reading code with the deficiency confirmation code on a one-to-one basis. 1 deficient document association process. The document management method includes a registration step of registering text information described in a predetermined number of normal documents in a database according to a predetermined number of machine reading codes associated with the normal confirmation code.
With this configuration, individual management of defective documents can be realized, and the risk of losing the actual defective documents can be prevented or reduced, and application documents can be managed safely and correctly.

  In the first generation step, a normal confirmation slip provided with a normal confirmation code and document management number information indicating a predetermined number and a deficiency confirmation slip corresponding to the number of defective documents provided with a deficiency confirmation code are generated. It may be.

The document management method according to the present embodiment includes a second issuance step of issuing a new deficiency confirmation code corresponding to a new deficient document when there is a new deficient document in a predetermined number of normal documents; A new normal confirmation slip with new document management number information representing the number obtained by subtracting the number of new defective documents from the number indicated by the normal confirmation code and document management number information, and a new defect confirmation code The second generation step for generating the new deficiency confirmation slip provided, the new deficiency confirmation code provided in the new deficiency confirmation voucher and the machine reading code provided in the new deficiency document are read, and a new A second deficient document relating step of relating the machine reading code to the deficiency confirmation code on a one-to-one basis.
With this configuration, even if a new deficient document is found in the normal document once it is classified into a normal document and a deficient document, the deficient document is managed individually, even if a new deficient document is found in the normal document. It is possible to prevent or reduce the risk of losing the password and to manage the application documents safely and correctly.

In addition, the document management method according to the present embodiment includes an image information generation step for generating image information of a defective document, an input step for inputting text information described in the defective document, and image information and text information as the defective document. An association step for relating according to a provided machine reading code, a list generation step for generating a deficient document confirmation list including at least telephone number information based on text information, and a complement for deficiencies obtained by calling An additional recording step of additionally adding the call history information to the incomplete document confirmation list may be included.
With this configuration, it is not necessary for the operator to make a phone call while looking at the incomplete document, so that the work is simplified and efficient, and there is a risk that the incomplete document will be lost. Can be prevented or reduced.

  In the present embodiment, the normal confirmation slip and the defect confirmation slip provided with the barcode are printed first, and the barcode on each confirmation slip is read and related to the barcode on the normal document and the defective document. In addition to this, for example, the associated application software is started in the process management apparatus 40 corresponding to normal documents and deficient documents, and the normal confirmation deficiency ID or deficiency confirmation voucher ID specified by the execution of the associated application software is supported. The barcode of a normal document or a defective document to be read may be read and related.

  In this embodiment, a bar code is used as the machine reading code. However, any barcode can be used as long as it can be read by a machine, and a two-dimensional code, a list of numerical values that can be recognized by OCR, and other symbols may be used.

  Moreover, you may make it implement | achieve a part of function of the process management server 10 which is embodiment mentioned above with a computer. In this case, a program for realizing the function is recorded on a computer-readable recording medium, the program recorded on the recording medium is read into a computer system, and the computer system executes the function to thereby execute the function. It may be realized. The computer system includes an operating system (OS) and hardware of peripheral devices. The computer-readable recording medium is a portable recording medium such as a flexible disk, a magneto-optical disk, an optical disk, or a memory card, and a storage device such as a magnetic hard disk or a solid state drive provided in the computer system. Furthermore, a computer-readable recording medium dynamically holds a program for a short time, such as a computer network such as the Internet, and a communication line when transmitting a program via a telephone line or a cellular phone network. In addition, a server that holds a program for a certain period of time, such as a volatile memory inside a computer system serving as a server device or a client in that case, may be included. Further, the above program may be for realizing a part of the above-described functions, and further, may be realized by combining the above-described functions with a program already recorded in the computer system. Good.

  As mentioned above, although embodiment of this invention was explained in full detail with reference to drawings, the specific structure is not restricted to that embodiment, The design of the range which does not deviate from the summary of this invention, etc. are included.

  DESCRIPTION OF SYMBOLS 1 ... Document management system, 10 ... Process management server, 11 ... Setting information DB, 12 ... Batch information DB, 13 ... Process information DB, 20 ... Personal information management server, 21 ... Image DB, 22 ... Index DB, 30 ... Rack Electric information management server, 31 ... Customer DB, 40 ... Process management device, 41 ... Terminal, 42 ... Printer, 43 ... Bar code reader, 50 ... Scanner device, 60 ... Data input device, 70 ... Outbound device, 71 ... Terminal, 72 ... Telephone, 73 ... Headset, 80 ... Network

Claims (5)

A document management method for registering text information written by a user in an application document provided with a machine reading code in a database,
A first issuance process in which the process management server issues a normal confirmation code corresponding to a predetermined number of normal documents that are application documents having no deficiencies and a deficiency confirmation code corresponding to each of the deficient documents that are deficient application documents; ,
A first normal document associating step in which the process management server relates the predetermined number of machine reading codes to the normal confirmation code;
A step of associating the deficient document with the deficiency confirmation code in a one-to-one relationship with the machine reading code;
A registration step in which the data input device registers text information described in the predetermined number of normal documents in the database according to the predetermined number of machine reading codes associated with the normality confirmation code;
Document management method. The terminal further includes a first generation step of generating a normal confirmation slip provided with the normal confirmation code and a deficiency confirmation voucher for a deficient document quantity provided with the deficiency confirmation code;
The first normal document associating step is performed by reading the normal confirmation code provided on the normal confirmation slip and the machine reading code provided on each of the predetermined number of normal documents,
The first deficient document association step is performed by reading a deficiency confirmation code provided for each deficiency confirmation slip and a machine reading code provided for each deficient document,
The document management method according to claim 1. In the first generation step, the terminal confirms the deficiency confirmation for the deficient document quantity provided with the normal confirmation slip provided with the normal confirmation code and the document management number information indicating the predetermined number, and the deficiency confirmation code. Generate votes and
The document management method according to claim 2. If there are new deficient documents in the predetermined number of normal documents,
A second issuing step in which the process management server issues a new deficiency confirmation code corresponding to the new deficient document;
The terminal, the normal verification code and the document new normal verification slip and a new document management number information representing the number obtained by subtracting the number of the new deficiencies documents provided from number indicating the management number information, And a second generation step of generating a new deficiency confirmation slip provided with the new deficiency confirmation code,
The process management server reads the new deficiency confirmation code provided in the new deficiency confirmation slip and the machine reading code provided in the new deficiency document, and adds the machine reading code to the new deficiency confirmation code. A second deficient document correlation process that relates one-to-one;
The document management method according to claim 3, further comprising: An image information generating step in which the scanner device generates image information of the incomplete document;
An input step in which the data input device inputs text information described in the incomplete document;
An association step in which the data input device relates the image information and the text information according to a machine reading code provided in the defective document;
The call information management server generates a deficient document confirmation list including at least information of a telephone number based on the text information;
An association process in which the terminal of the outbound device associates call history information related to deficiency supplement obtained by call with the deficient document confirmation list;
The document management method according to any one of claims 1 to 4, further comprising:

Images