GB2339039A

GB2339039A - Document management system

Info

Publication number: GB2339039A
Application number: GB9906853A
Authority: GB
Inventors: Yoshito Kobayashi; Hiroshi Sakurai
Original assignee: Mitsubishi Electric Corp
Current assignee: Mitsubishi Electric Corp
Priority date: 1998-03-26
Filing date: 1999-03-24
Publication date: 2000-01-12
Anticipated expiration: 2019-03-24
Also published as: GB2339039B; KR19990078054A; JPH11272538A; GB9906853D0

Description

2339039 DOCUMENT MANAGEMENT SYSTEM This invention relates to a document

management system and more particularly to a document management system for managing document data files on a server in a server-client mode, wherein a database is used to handle a document management flow of registering, approving, issuing, and receiving documents and document information managed on a number of servers individually and information required for managing documents can be linked.

Hitherto, mainly, electronic mail has been used among persons in charge (users) for registering, approving, issuing, and receiving document data files handled in a work flow. Thus, a master document data file moves on a network and unified management,of the master document data file cannot be executed on a server. A document preparation management system reported in JP-A-4-357558 is named as a related art similar to the technical idea of the invention. in the conventional document preparation management system reported in JP-A-4-357558, one or more first areas from which data can be read only by persons havIng the read right and one or more second areas into which data can be wri te only by - I - persons having the write right are set in predetermined f -Jelds of a form and even for one slip, for example, data read from the specific area and data write intothe specificarea canbe limited.

The configuration difference between the technical idea of the invention and the conventional document preparation management system will be discussed. In the invention, histories of registering, approving, issuing, and receiving all document data files are managed on a database, but in the conventional document preparation management system, histories themselves are not managed and histories of registering, approving, issuing, and receiving document data files are not managed.

Next, the function difference based on the configuration difference between the technical idea of the invention and the conventional document preparation management system will be discussed. In the invention, histories of registering, approving, issuing, and receiving document data files in every format can be retained, but in the conventional document pre-aration management system, histories of registering, approving, issuing, and receiving document data files only in one determined format can be retained.

For example, an electronic mail document distribution 4 method and system reported in JP-A-5-48647, a mail informaL.Lon management system in a distributed mail system reported in JP-A-6-195275, and a mail destination determination method reported 'n JP-71-5-1914448 are named as related arts smilar to the zechn--Ical idea of the invention in the viewpoint of a lin"l-age 2 (conjunction) system in a distributed server environment using electronic mail and a database between servers.

First, in the conventional electronic mail document distribution method and system reported in JP-A-5-48647, when an electronic mail document is distributed between servers, it is sent via several servers; at the time the optimum distribution path is found by searching a destination database placed in each server. The technical idea of the invention differs from the conventional electronic mail document distribution method and system remarkably in object and means (configuration) in that in the invention, a document is managed with the database and electronic mail I's used as means for transferring information on the document between servers; while in the method and system disclosed in JP-A-5-48647, the database is used as means for determining the optimum distribution path of each electronic mail document.

Next, in the conventional mail information management system in a distributed mail system reported in JP-A-6-195275, when electronic mail is transmitted and received, additional functions such as returned mail arrival check, read or unread check, and deletion of transmitted mail are provided without changing an alrea-dy existing mail system. The technical idea of the invention. also differs from the conventional mail inf ormation management system:temarkably in object and means in that in the invention, electronic mail is used as means for managing documents managed with the --Jatab-ase in the dist-ributed server environment; while in the system disclosed in JP-A-6-195275, the system for adding additional information to electronic mail and the information management system are used as means for managing electronic mail itself.

In the conventional mail destination determination method reported in JPA-5-1914448, when an electronic mail document is distributed between servers, it is sent via several servers; at the time the optimum distribution path is automatically determined according to organization and function information existing in terminals in a distribution manner. Like the above-described JP-A-5-48647, the JP-A-5-1914448 describes the method of determining the optimum distribution path of each electronic mail document. It differs from the technical idea of the invention remarkably in object and means.

In a conventional server-to-server linkage (conjunction) document management system, a method of constructing distributed databases using already existing database functions and synchronizing the contents of the databases is known as a general method for transferring document management information between servers if change occurs in document management information stored in a server.

The configuration difference between the technical idea of the invention and the conventional server-to-server linkage (conjunction) document management system will be discussed. In the invention, the databases for managing documents be--ween zhe servers are not directly linked and electronic mail is used as A I means for transferring database information; in the conventional document management system, the databases need to be constructed as distributed databases.

The function difference based on the configuration difference between the technical idea of the invention and the conventional document management system will be discussed. In the invention, the databases for managing documents can be managed separately in the servers. In contrast, in the conventional document management system, distributed databases need to be constructed. If change occurs in document information managed on a database or information required for managing documents, it can be reflected on document management systems managed on the databases in other servers by electronic mail.

In the conventional server-to-server linkage (con-unction) document management system described above, the databases operating on the servers are constructed as distributed databases and thus cannot be managed separately and in addition, construction of the distributed databases entails cost. As the number of servers increases, when distributed databases are constructed, server-to-server linkage (conjunction) definitions explosively grow and it becomes substantially difficult to const-'ruct. the distributed databases.

it is -therefore an object of the invention to provide a document management system wherein when document management is executed between servers in conjunction with each other, the servers can be separately managed by using electronic mail as means for transferring information between the servers, the document management system being provided at low costs because distributed databases need not be constructed and enabling linkage (conjunction) if the number of servers is increased. According to a first aspect of the present invention, there is provided a document management system comprising: a first server including: a first memory for storing a first document database; means for retrieving said first document database from said first memory; means for reading, when said retrieving means retrieves updated information from the first document database, the updated information from the -first document database to process the updated information into electric mail information; and first information communication means for transmitting the electric mail information; a second server including: a second memory for storing a second document database; second information communication means for receiving the electronic mail inf ormat ion transmitted by said first inf ormation co,mmunication means; and means for updating the second document database on the basis of contents of the electronic mail information received by said second info.-mation corn-munication means.

According to a second aspect of the present invention, there is provide the document management system as- described in the first aspect of the present invention further comprising:

a client server including third information communication means for transmitting information to said first server; and wherein the first document database is updated on the basis of processing contents performed in said first server through said client server.

According to the document management system of the present invention, information to be updated in said first document database may be at least one of document registration information, document revision registration information, document scrapping registration information, document approval information, document approval rejection information, document issuance information, document demand information, document reception acknowledgement information, new creation user information, user deletion information, new creation department information., department deletion information, representative approval user set information, and document representative approval information.

The invention will be flirther described by way of non-limitative example with reference to the accompanying drawings, in which:

FIG. 1 is a block diagram showing a configuration of a document mEnagement system of a first embodiment according to the invention.

7 FIG. 2 is a diagram showing a document management organization in the document management system shown in FIG. 1.

FIG. 3 is a diagram showing a document management flow of the document management system shown in FIG. 1.

FIG. 4 is a diagram showing the relationship between the document management flow shown in FIG. 3 and document flow management means.

FIG. 5 is a diagram showing the correspondence between a document issuance management table in the document flow management means shown in FIG. -4 and processes.

FIG. 6 is a flowchar t showing a document registration processing flow in a client in the document flow management means shown in FIG. 4.

FIG. 7 is a flowchart showing a document approval processing flow in a client in the document flow management means shown in FIG. 4.

FIG. 8 is a flowchart showing a document issuance processing flow in a client in the document flow management means shown in FIG. 4.

FIG. 9 is a block diagram showing the configu-ration of a document management system of a second embodiment according to the invention.

FIG. 10 is a diagram showing conjunction means between servers in the document management system shown in FIG. 9.

FIG. 11 is a flowchart to show a documel-t issuance orocesSing -flow -for the part of issuance in the conjunczlon me-ans between servers shown in FIG. 10.

FIG. 12 is a flowchart to show a document reception processing flow for the part of reception in the conjunction means between servers shown in FIG. 10.

(First embodiment) In a first embodimen t of the invention, a document management system for registering and revising quality documents in maintenance and management of quality documents, for example, in an ISO (International Organization for Standardization) 9000 quality system will be discussed.

FIG. 1 is a block diagram to show the configuration of the document management system of the -first embodiment according to the invention. In the figure, numeral I denotes a magneto-optic disk as a large-capacity auxiliary storage unit, numeral 2 denotes a hard disk as a normal auxiliary storage unit, numeral 3 denotes a server such as a PC server to which the magneto-optic: disk 1 and the hard disk 2 are connected, and numerals 4 and 5 denote clients such as PC clients. Numeral 6 denotes a network for connecting the server 3 and the clients 4 and 5, numeral 7 denotes an image printer for printing document data -'registered in the client 5, and numeral 8 denotes an image 9 reader for inputting document data to the client 5 in an image format.

The document management system of the embodiment uses the magneto-optic disk 1 and the hard disk 2 as the auxiliary storage units, but the scope of the invention is not limited to them. Any other auxiliary storage unit than the magneto-optic disk 1 or the hard disk 2 may be used as required. In the document management system of the embodiment, the client 4, 5 and the server 3 are separated from each other, but the scope of -the invention is not limitedtoit. One machine may serve as both a client and a server.

Document data may be input in the image format as required; it may be input in any other format.

Next, FIG. 2 is a diagram to show a document management organization in the document management system shown in FIG. 1.

Quality documents such as quality manuals, instruction manuals, procedure manuals, and quality records must be managed by the users having the authority to do it. First, a creator, registerer 11 in a design department creates and registers a document and an approver 12 in a quality control department approves registration of the registered document. An issuer 13 in a manufacture management department issues the approved document and a user 14 in a manufacture department receives the issued document.

Next, FIG. 3 is a di agram to show a document management f low o_- the document management system shown in FIG. 1. A documnent flow among users will be discussed with reference to FIG. 1. To - make a request for registering a document, drawing, quality record created with a wordprocessor, CAD, etc., the creator, registerer 11 in the design department sends the document to the approver 12 in the quality control department. To reject the document sent from the creator, registerer 11 in the design department, the approver 12 in the quality control returns the document to the creator, registerer 11 in the design department. On the other hand, to approve the document sent from the creator, registerer 11 in the design department, the approver 12 in the quality control sends the document to the issuer 13 in the manufacture management department to make a request for issuing the approved document.

If a request is made for issuing a document, the issuer 13 in the manufacture management department sends the issued or revised document to the user 14 in the manufacture department; if a document is scrapped, the issuer 13 collects the old-edition document from the user 14 in the manufacture department. The user 14 in the manufacture department can retrieve and read documents in the system.

Next, FIG. 4 is a diagram to show the relationship between the document management flow shown in FIG. 3 and document flow management 7-neans. Document flow management means 15 has a function o--,r managing a document flow of registration, approval, issuing, and reception for all users of the creator, registerer 11 to the approver 12 to the issuer 13 to the user 14.

Nex-., FTG. 5 is a diagram to show the correspondence between a d0cument issuance management table in the document flow management means shown in FIG. 4 and processes. To send a document to a related department, a correspondence list between documents and document destination departments is provided as a document-by-document destination list and is referenced in an issuance process and a scrapping process. The issuance process includes an issuance notification, reception acknowledgement, etc., and the scrapping process includes a scrapping notification, collection acknowledgment, etc. Document status management information is provided in a list format and is referenced in the issuance process, the scrapping process, and a demand process.

The demand process includes a demand notification, etc. The demand notification mentioned here means demanding that issuance notification reception acknowledgement should be returned.

Next, FIG. 6 is a flowchart to show a document registration processing flow in a client in the document flow management means shown in FIG. 4. First, for example, the client 5 operated by the creator, registerer 11 receives document registration request data entered by the creator, registerer 11 at step Sl, -then receives a document data file to be registered in the server 3 at step S2.

The client 5 prepares document attribute information consisting of six information pieces of a document title, keyword, document number, revision subnumber format, expiration date, and approver and one information piece of registration date prepared by the system as management information attached to the received document data file and user-set information at s--ep S3. Then, the client 5 repares document data file management information p I of a document file name (file name used by the system), file size, and file creation date required for managing the document data f ile in the server 3 at step S4, and registers the prepared document attribute information and document data file management information in a database in the server at step S5.

The document management system of the embodiment uses the seven information pieces of the document title, keyword, document number, revision subnumber format, expiration date, approver, and registration date, but the scope of the invention is not limited to them. The types and number of document attribute information pieces are not defined and therefore the document attribute information may be added, deleted, or changed as desired as necessary. The document attribute information includes information attached to the document, known at the stage of registering the document and information of the document approver,name, the document issuer name, etc., added in a work flow through steps of document approval, issuance, etc.

The docun.ent management system of the embodiment uses the three information pieces of the document file name, file size, and -file creation date as the document data file management -;nformat4on, but r-he scope of the invention is not limited to them. The document data file management information is not defined and thereffore may be added, deleted, or changed as desired as necessary.

Next, F-72. 7 is a flowchart to show a document approval processing flow in a client in the document flow management means shown in FIG. 4. First, for example, the client.5 operated by the approver 12 receives document approval request data entered by the approver 12 at step S11, then checks approval execution/approval rejection determination information for approval execution or approval rejection at step S12.

Next, if the determination result based on the approval execution/approval rejection determination information is flapproval rejection" at step S12, the client 5 prepares approval rejection information indicating the approval rejector and the approval rejection date at step S13. Then, the client 5 prepares document data file management information as approval rejection indicating the document file name, file size, and file creation date required for managing the document in the server 3 at step S14 and registers the prepared approval rejection information and document data file management information as approval rejection in the database in the server 3 at step S15.

If the determination result based on the approval executiori/approval rejection determination information is Irapproval execution" at step S12, the client 5 prepares approval execution information indicating the approval executor and the approval execution date at step S16. Document data file management information as approval execution indicating the document file name, file size, and file creation date required.For managing the document in the server 3 is prepared when the dccumert is registered. 7hen, the client 5 registers the prepared approval execution information and document data file management information as approval execution in the database in the server 3 at step S17.

The document management system of the embodiment uses the four information pieces of the approval executor, approval rejector, approval execution date, and approval rejection date as the approval execution/rejection information, but the scope of the invention is not limited to them. The types and number of approval execution/rejection information pieces are not defined and therefore the approval execution/rejection information may be added, de leted, or changed as desired as necessary.

The document management system of the embodiment uses the three information pieces of the document file name, file size, and file creation date as the document data file management information, but the scope of the invention is not limited to them.

The document data file management information is not defined and therefore may be added, deleted, or changed as desired as necessary.

Next, FIG. 8 is a flowchart to show a document issuance processing flow in a client in the document flow management means shown in FIG. 4. First, for example, the client 5 operated by the issuer 13 receives document issuance request data entered by the issuer 13 at step S21, then receives processing type information indicating any of issuance, scrapping, or demand at step S22.

Next, the client 5 prepares issuance information indicating the issuer, issuance date, and des tination at step S23, then prepares document data file management information indicating the document file name, file size, and file creation date required for managing the document in the server 3 at step S24 and registers the prepared issuance information and document data file management information in the database in the server 3 at step S25.

The document management system of the embodiment uses the three information pieces of the issuer, issuance date, and destination as the issuance information, but the scope of the invention is not limited to them. The types and number of issuance information pieces are not defined and therefore the issuance information may be added, deleted, or changed as desired as necessary.

The document data file management -inf ormation is not defined and therefore may be added, deleted, or changed as desired as necessary.

The document management system of the embodiment uses the three information pieces of issuance, scrapping, and demand as t,e processing type information, but the scope of the invention is not limited to them. The processing type -inform-=t-ion is not defined and therefore maybe added, deleted, or changed as desired as necessary.

Thus, in the embodiment, when document registration, approval, issuance, or reception processing is performed, a history of document flow management of processing performed through the client 5 is managed on the database in the server 3, so that registration, approval, issuance, and reception history management can be executed for all document data files. The master document is managed on the server 3 in a unified manner so that the processing state of document registration, approval, issuance, and reception can be known and that document registration, approval, issuance, and reception can be executed.

Thus, if the document is being registered, approved, issued, or received, the master document can always be referenced and the document being processed can be prevented from being lost. Since the master document is not moved to the client 4 or 5, the trouble of copying the document being processed can be saved and extra disk space can also be saved.

(Second embodiment) In a second embodiment of the invention, a document management system for managing documents between independent servers in conjunction with each other in document data file management. The document data files managed in a single server are similar to those in the document management system of the f -irst embodiment previously described with reference to FIGS. 1 to 5 and therefore only the mode of executing document management between servers in conjunction with each other will be discussed.

FIG. 9 is a block diagram to show the configuration of the document management system of the second embodiment according to the invention. Parts identical with or similar to those previously described with reference to FIG. 1 are denoted by the same reference numerals in FIG. 9. In FIG. 9, numeral 21 denotes a magneto-optic disk as a large-capacity auxiliary storage unit, numeral 22 denotes a hard disk as a normal auxiliary storage unit, numeral 23 denotes a server such as a PC server to which the magneto-optic disk 21 and th"e hard disk 22 are connected, and numerals 24 and 25 denote clients such as PC clients. Numeral 26 denotes a network for connecting the server 23 and the clients 24 and 25, numeral 27 denotes an image printer for printing document data registered in the client 25, and numeral 28 denotes an image reader for inputting document data to the client 25 in an image format. Numeral 29 is a network for connecting the networks 6 and 26.

The document management system of the embodiment uses the magneto-optic disk 21 and the hard disk 22 as the auxiliary storage units, but the scope of the invention is not limited to them. Any other auxiliary storage unit than the magneto-optic disk 21 or the hard disk 22 may be used as required. In the document management system of the embodiment, the client 4, 5, 24, 25 and the server 3, 23 are separated from each other, but the scope of the invention is not limited to it. One machine may serve as both a client and a server. Document data may be input in the image format as required; it may be input in any o-ther format than the image format.

Next, FIG. 10 is a diagram to show conjunction means between servers in the document management system shown in FIG. 9. When processing of document registration, approval /approval rejection, issuance, or reception is performed through a client 31 or 32 connected to a server A, information indicating document registration, approval/approval rejection, issuance, or reception is added to or changed i n a document database 33 managed in the server A accordingly. When processing of document registration, approval/approval rejection, issuance, or reception is performed through a client 41 or 42 connected to a server B, inLEormation indicating document registration, approval /approval rejection, issuance, or reception is added to or changed in a document database 43 managed in the server B accordingly. The detailed description on this topic is similar to that given in the first embodiment and therefore will not be given again.

A DB information communication program 34 in the server A searches the database 33 in the server A every given time and gathers information as to whether or not information indicating document registration, approval/approval rejection, issuance, or reception is added to or changed in the database 33 from the database 33. If the information indicating document registration, approval/approval rejection, issuance, or reception is added to or changed in the database 33 in the server A, then the DB information communication program 34 in the server A reads the information concerning document registration, approval /approval rejection, issuance, or reception added to or changed in the database 33 from the database 33, and transmits the added or changed information read from the database 33 to the server B by electronic mail.

When receiving the electronic mail transmitted from the server A, a DB information communication program 44 in the server B updates the database43 in th e server B according to the electronic mail contents. If the information indicating document registration, approval/approval rejection, issuance, or reception is thus added to or changed in the document database 43 in the server B, approval/approval rejection, issuance, or reception processing is performed on the client 41, 42 connected to the server B based on the added or changed information.

The DB information communication program 44 in the server B searches the database 43 in the server B every given time and gathers information as to whether or not information indicating document registration, approval /approval rejection, issuance, or receotion is added to or changed in the document database 43 from the document database 43. If the information indicating document registration, approval /approval rejection, issuance, or reception is added to or changed in the document database 43 in the server B, zhen the DB information communication program L':' in the server B reads the information concerning document registration, approval /approval rejection, issuance, or reception added to or changed in the document database 43 from the document database 43, and transmits the added or changed information read from the database 43 to the server Aby electronic mail. When receiving the electronic mail transmitted from the server B, the DB information communication program 34 in the server A updates the database 33 in the server A according to the electronic mail contents.

FIG. 11 is a flowchart to show a document issuance processing flow for the part of issuance in the conjunction means between servers shown in FIG. 10. First, if the issuance processing previously described with reference to FIG. 8 in the first embodiment is performed in the server A, the DB information communication program 34 in the server A searches the database 33 for issuance information indicating issuance of the document at step S31.

If the issuance information indicating issuance of the document is found from the database 33 as the search result at step S32,. the DB information communication program 34 in the server A processes and prepares the issuance information indicating when who issues what document to what department as electronic mail information at step S33 and transmits the prepared issuance information to the server B by electronic mail at step S34. When receiving the electronic mail sent from the server A at step S35, the DB information communication program 44 in the server B analyzes the electronic mail contents at step S36 and extracts the issuance information indicating when who issues what document to what department.

The DB information communication program 44 in the server B updates the database 43 in the server B based on the issuance information extracted from the received electronic mail at step S37. If the issuance information indicating issuance of the document is not found from the database 33 as the search result at step S32, the DB information communication program 34 in the server A skips steps 33-37 (issuance processing) and terminates processing.

FIG. 12 is a flowchart to show a document reception processing f low for the part of reception in the conjunction means between servers shown in FIG. 10. First, if reception processing is performed in the server B, the DB information communication program 44 in the server B searches the database 43 for reception i nf ormation indicating reception of the document at step S4 1. If the reception information indicating reception of the document is found from the database 43 as the search result at step S42, the DB information communication program 44 in the server B processes and prepares the reception information indicating when who receives what document as electronic mail information at step Sg3 and transmits the prepared reception information to the server A by electronic mail at step S44.

When receiving the reception information sent through the eiectronic mail from the server B at step S45, the DB -informatio.r.1 cc-Lmunication orogram 34 in the server A analyzes the elect-ron-ic mail (reception information) contents at step S46 and extracts the reception information indicating when who issues what document. The DB information communication program 34 in the server A updates the database 33 in the server A based on the reception information extracted from the electronic mail at step S47. If the reception information indicating reception of the document is not found as the search result at step S42, the DB information communication program 44 in the server B skips steps 43-47 (reception processing) and terminates processing.

Thus, in the embodiment, when document management is executed in the servers A and B in conjunction with each other, information managed in the document database 33 in the server A individually and information managed in the document database 43 in the server B individually are linked with each other with electronic mail as media without constructing distributed databases. Thus, the database 33 in the server A and the database 4 3 in the server B can be managed individually for easy management, and moreover it is not necessary to construct distributed databases, -so that costs can be reduced. Here, two servers are adopted, but if the number of servers is increased, linkage (conjunction) is also enabled.

If the number of servers is increased and distributed databases are constructed, it is feared that the amount and frequency of transaction for synchronizing the databases with each other may be ve-ry increased, causing the load on the networ< to crow explosively. In the embodiment, however, when document management is executed in the servers in conjunction with each other, information managed in one document database in one server individually and information managed in another document database in another server individually are linked with each other with electronic mail as media without,constructing distributed databases. Thus, the adverse effect of increasing the load on the network can be lessened.

In the present invention, a document management system comprises a first server having a first document database and first information communication means for searching the first document database, if updated information is found in the first document database, the first information communication means for reading the updated i.nf ormation from the first document database, processing the information as electronic mail information, and transmitting the electronic mail information to a second server and the second server having a second document database and second information communication means, upon reception of electronic mail transmitted from the first information communication means, for updat.ing the second document database based on the contents of the received electronic mail, whereby when document management is executed between servers in conjunction with each other, electronic mail is used as means for transferring information between the servers, so that the servers can be separately managed and distributed databases need not be constructed, thus the document management system can be provided at low costs and enables linkage (conjunction) if the number of servers is increased.

In the present invention, the first document database is updated based on the processing contents performed through a client connected to the first server, so that the first document database can be updated efficiently.

In the present invention, update information in the first document database is at least one of document registration information, document revision registration information, document scrapping registration information, document approval information, document approval rejection information, document issuance information, document demand information, document reception acknowledgement information, new creation user information, user deletion information, new creation department information, department deletion information, representative approval user set information, and document representative approval information. Thus, document management can be executed between the servers in conjunction with each other based on the update information.

Claims

1. A document management system comprising: a first server including: a first memory for storing a first document database; means for retrieving said first document database from said first memory; means for reading, when said retrieving means retrieves updated information from the first document database, the updated information from the first document database to process the updated information into electric mail information; and first information communication means for transmitting the electric mail information; a second server including: a second memory for storing a second document database; second information communication means for receiving the electronic mail information transmitted by said first information communication means; and means for updating the second document database on the basis of contents of the electronic mail information received by said second information communication means.

2. The document management system as claimed in claim I further comprising: a client server including third information communication means for transmitting information to said first se.-ver; and wherein the first document database is updated on the basis of processing contents performed in -said first server through said client server.

3. The document management system as claimed in claim I or 2, wherein information to be updated in said first document database is at least one of document registration information, document revision registration information, document scrapping registration information, document approval information, document approval rejection information, document issuance information, document demand information, document reception acknowledgement information, new creation user information, user deletion information, new creation department information, department deletion information, representative approval user set information, and document representative approval information.

4. A document management system constructed and arranged to operate substantially as hereinbefore described with reference to and as illustrated in the accompanying drawings.

27 -