JP2006079257A - Business management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a business management system for quantitative and scientific projects by focusing on numerical data derived from emails received and sent. <P>SOLUTION: The business management system comprises a document storage operation part 103, a document storage and display part 104, a document receiving/sending process part 101, a document storage part 102, a comparison reference part 107, a process operation part 105, a document processing part 106 and a process display part 108. About the business that is performed within determined ranges, the numerical data of documents received and sent in relation to the business are collected using a predetermined and stored in one or more kinds of determined cycles. A comparison is made between numerical reference values predetermined for the different cycles and stored values, and differences between corresponding parts are determined. If the differences exceed a separately determined threshold value, the business is determined to be abnormal. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention appropriately manages project operations such as steel manufacturing and power plants according to the passage of time, thereby supporting the smooth progress of the project operations, and accurately grasping the amount of the project operations. The present invention relates to a business management system that supports a business person in charge to easily promote business.

  Projects for constructing various plant facilities are based on made-to-order production, and user companies that want to optimize their facilities and equipment supplier companies that should comply with the constraints on equipment production while responding to this requirement are companies It is necessary to work together to achieve the objectives. For this purpose, formal communication is required by sending and receiving documents within the same company or between different companies such as a user company and a supplier company. In addition, the combination of information exchange by e-mail and official document exchange by paper document is a basic aspect of communication within and between companies even in recent build-to-order projects.

  One of the characteristics of a project for constructing such various plant facilities is that there are very many interested parties. On the user company side, there are three parties: the production operator who uses the equipment finally delivered, the mechanical engineer responsible for the mechanical aspects of the equipment, and the electrical engineer responsible for the electrical aspects. Will at least exist. Furthermore, since user companies often place orders for construction companies, construction companies, etc., these companies are also interested parties. In addition, there are trading companies and supplier companies of mechanical equipment and electrical equipment among the supplier companies that deliver equipment. Each supplier company has a planning department, a design department, a production department, a start-up adjustment department, etc. The total number of stakeholders in a build-to-order project that builds plant equipment often exceeds ten.

  For this reason, once a problem occurs in the course of a project, it often takes a complicated process to solve it. In this situation, especially for large-scale projects, experienced project managers (hereinafter abbreviated as “PM”) that gather inside each company at the user company and each supplier company and serve as a negotiating contact outside the company. Is often appointed to promote the project smoothly. However, such PM work is a typical atypical work, and it is difficult to quantitatively grasp the amount of work. For example, is it sufficient for one PM, or is it necessary for a PM of a minor or a minor? Also, it was customary to determine empirically whether to increase or decrease according to the progress of the project. Furthermore, it is empirically pointed out that the overall transition of the project is visible, reported to the senior management who oversees the project members and PM, and information is shared to predict the occurrence of problems and take appropriate measures. It was handled manually. Considering how to manage future projects that are becoming increasingly complex, it is clear that there is a limit to the empirical processing as described above, and it has been conventionally recognized that quantitative and scientific processing should be performed. However, the reality is that there was no appropriate means for realization.

  Promoting such a project is based on collaborative work within a company and between different companies, and as a means for this collaborative work, communication is required by sending and receiving documents that can be referred to as evidence later. The format of this document was only sending and receiving paper documents by mail and telex communication several decades ago, but with the development and diversification of communication means in recent years, faxes and e-mails will be used. In particular, the use of e-mail has increased dramatically in recent years. In a specific project at an electronics manufacturer, the PM in charge of managing the project investigated the number of e-mails in the total number of documents sent and received regarding the project within the company and between other companies. , About 86%. This 86% figure indicates that most of the documents sent and received for the purpose of managing the project are e-mails. Therefore, in order to grasp the status of the project, only e-mails are taken out and examined. Even so, it is clear that many people do not make a mistake.

Conventionally, as an example focusing on the number and frequency of information to be sent and received, it is configured so that the viewer can also send content to the website, and the number of calls per sender in that environment In some cases, data such as the average number of calls per predetermined period is collected, this data is evaluated by a predetermined method, and a privilege is given to a caller who has obtained high evaluation (for example, see Patent Document 1). . The evaluation formulas (1) and (2) are as follows.
Rs = Rs (Pc1, Pc2,... Pcn)
= X1 * Pc1 + x2 * Pc2 +... Xn * Pcn + (1) Formula Pci = Pci (n, t, p, Pc_prc)
= Pc_prc + a * n + b * t + c * p (2) where
Rs: Evaluation formula of the sender
Pci: Evaluation formula for the i-th content sent
n: Number of times content is used
t: Average content usage time
P: User evaluation score for the caller
Pc_prc: Points until just before
a, b, c, x1, x2... xn: weighting

JP 2003-303154 A (page 2-3, formula 2)

  Since the evaluation formula of the conventional example is configured as in the above formulas (1) and (2), not only the number of transmissions (i) but also the number of usages (n), usage time (t), etc. In addition to elements being mixed, the concept of grasping changes in frequency and frequency over time is poor, and it is difficult to apply to project operations such as steel manufacturing and power plants that are operated over a long period of time. Had the disadvantages.

  The present invention has been made to solve the above problems, and provides a business management system for quantitative and scientific projects by focusing on numerical data derived from incoming and outgoing e-mails. To do.

  The business management system according to the present invention comprises a document storage operation unit, a document storage display unit, a document reception / transmission processing unit, a document storage unit, a comparison reference unit, a processing operation unit, a document processing unit, and a processing display unit. With respect to the work to be performed, the numerical data is collected and stored in a predetermined method for a document sent and received in relation to the work, and is stored in advance for each period. Comparing and referencing the determined reference numerical value and the stored value to obtain a difference in corresponding parts, and determining the abnormal situation of the business by the fact that the difference exceeds a threshold value separately determined .

  Since the present invention is capable of performing business determination by focusing on numerical data of documents sent and received in response to the progress of atypical business such as project management, and can perform accurate business management. It is a progressive thing that contributes to the smooth progress of business.

Embodiment 1 FIG.
Embodiment 1 of the present invention will be described below with reference to FIGS. 1 is a block diagram showing a configuration of a business management system according to Embodiment 1 of the present invention, FIG. 2 is a graph showing an example of a monthly change in the number of e-mails sent and received, and FIG. 3 is a diagram showing an example of a reference pattern FIG. 4 is a view showing an output display example, and FIG. 5 is a flowchart showing a series of operations.
In FIG. 1, an e-mail receiving / sending processing unit 101 is received and sent by a first manager who operates the first embodiment, for example, a PM (project manager) such as a large-scale plant such as a steel plant or a power plant. This is for extracting from the various miscellaneous e-mails only e-mails related to the project in charge of the e-mail and storing them in the e-mail storage unit 102. The e-mail storage unit 102 stores the data processed by the e-mail reception / transmission processing unit 101 and converted into a database. The save operation unit 103 and the save display unit 104 are used for the PM as the first administrator to input a necessary send / receive instruction to the e-mail send / receive processing unit 101 and display the result. used. Next, when the processing operation unit 105 is operated by a second manager who operates the first embodiment, which is designated in advance in the operation of the system, for example, PM or a senior manager located in a senior level thereof, the electronic The mail processing unit 106 later uses the database stored in the email storage unit 102 and the data of the comparison reference unit 107 that stores the parameters extracted from the email group of similar projects that have already been completed. A prescribed quantitative process is performed, and the result is displayed on the process display unit 108.

  Next, the operation will be described in detail. First, the e-mail receiving / sending processor 101 sends e-mails related to the project in charge from various miscellaneous e-mails received / transmitted by the first manager who operates the first embodiment, for example, PM. Since it is intended to distinguish and collect only by using a personal computer (hereinafter abbreviated as “personal computer”) that is usually on the market and using an e-mail software function installed on the personal computer, realizable. In addition, this collection work is not special, and it is realized by creating a folder for e-mail classification using the e-mail software function that is usually on the market and placing the related e-mail under that folder Is possible. As a result of these series of operations and transmission / reception processing, the e-mail storage unit 102 stores only e-mails transmitted / received regarding the project.

  Next, an operation when the processing operation unit 105 is operated by the second administrator who operates the first embodiment will be described (step S1 in FIG. 5). The purpose of the second manager to operate and operate the first embodiment is whether the progress of the project currently in progress is appropriate, the delay of the process and the occurrence of problems, that is, the signs of “project collapse” This is for the purpose of grasping that there is no macro. Therefore, the target project is designated here (step S2 in FIG. 5). The e-mail processing unit 106 extracts two parameters, that is, extraction of the parameters of the project-related e-mail stored in the e-mail storage unit 102 and the group of e-mails of similar projects already completed stored in the comparison reference unit 107. Perform comparison with the extracted parameters.

  First, the extraction of parameters of the project-related email stored in the email storage unit 102 in the first embodiment is executed by counting the number of monthly emails sent and received (FIG. 5). Step S3). FIG. 2 shows the transition of the total number of e-mails sent and received by the PM in the current project. In FIG. 2, the horizontal axis indicates the number of months of the project, and the number of months “0” corresponds to the time of the order. The vertical axis indicates the total number of emails sent and received by the PM. Therefore, the line graph 201 represents the transition of the number of e-mails from the four months before receiving an order for this project. The extraction of the parameter of the number of monthly emails is the first function of the email processing unit 106.

  Next, in accordance with an instruction input by the second administrator using the processing operation unit 105, the e-mail processing unit 106 should refer to the project from the reference pattern group stored in the comparison reference unit 107. A pattern is called (step S4 in FIG. 5). A broken line 301 in FIG. 3 indicates a pattern to be referred to for the project. As shown in the figure, the polygonal line 301 increases rapidly from the time of receiving an order and becomes a high level constant value at the planning, designing and manufacturing stage, and has a peak value when the device is shipped. The installation, wiring, and operation start stages after the shipment of the equipment are also constant values, and rapidly decrease after the customer performs acceptance inspection after a necessary period after the operation starts. Such a pattern is peculiar to a business type that provides support for installation, wiring, and operation after the shipment of equipment, such as a large-scale plant such as a steel plant or a power plant. Further, when an order is used as a reference point, the period of planning, design and production, the period from order to shipment, the period from shipment to acceptance, that is, the reference process is negotiated for each project. Each period of the broken line 301 is corrected according to the data of each period input by the second manager (steps S5 and S6 in FIG. 5). Next, the e-mail processing unit 106 adjusts the monthly transition of the total number of e-mails received and transmitted for the project shown in the line graph 201 in FIG. 2 and the reference pattern (step S7 in FIG. 5).

  This specific algorithm is shown in Table 1.

In Table 1, first, (1) the number of elapsed months (0 to 12 months) and (2) the total number of incoming and outgoing mails are shown. Next, (3) the reference pattern was 0 at the time of ordering, 250 at the time of planning / design / production, 410 at the time of shipment, and 200 after the shipment. Each sum is obtained, and the multiplication factor for the reference pattern is 2796 ÷ 2965 = 0.944 (3) (4) The corrected reference pattern is determined, and (5) the difference rate is obtained. For example, for an elapsed month of 6 months, 186 ÷ 236 = 0.744 (4) is obtained (step S8 in FIG. 5).

  Next, the e-mail processing unit 106 compares the threshold value given for (5) difference rate in Table 1 and (6) performs abnormality determination (step S9 in FIG. 5). Abnormal circumstances such as project collapse appear as extreme gaps from (4) the modified reference pattern, but generally (5) projects with a difference rate of 0.5 or less, or 2.0 or more You should doubt the collapse. However, it is clear that this is not the case for the project. Finally, the electronic mail processing unit 106 outputs Table 1 and FIG. 4 as an illustration to the processing display unit 108, and displays them (steps S10 and S11 in FIG. 5). In FIG. 4, a broken line 401 corresponds to the corrected reference pattern. If there is an abnormality, a special marking is made on the corresponding part of FIG. 4, but it is not displayed because there is no abnormality in the project.

  A series of operations in the first embodiment of the present invention described in detail above is shown as a flowchart in FIG. However, the operations until the e-mail is stored can be realized by using the commercially available personal computer and the e-mail software function installed on the personal computer as described above, and are therefore shown in the figure. Absent. In addition, it is understood that an e-mail generally belongs to an individual, and after the use is made based on the discretion of the individual in practice, the PM of the first administrator in Embodiment 1 of the present invention. Although it is actually discarded, in the operation of the first embodiment of the present invention, this discarding is prohibited, and it is necessary to store all e-mails sent and received as the project progresses. The storage period is not the end of the project, but the number of e-mails sent and received stored after the end of the project must be referred to. This should be done with specific standards. Although the number of e-mails sent and received in the first embodiment is counted monthly, the application of various periods such as every week, every ten days, etc. should be decided according to the work contents of the project. Yes, and flexible periods such as extending the period can be applied when there is little change before the end of the project.

Embodiment 2. FIG.
The second embodiment of the present invention will be described below. The configuration of the second embodiment of the present invention is the same as that of the first embodiment. In addition, regarding the operation, the first administrator who operates the second embodiment distinguishes and collects only e-mails related to the project that he / she is in charge of, that is, a commercially available personal computer It is exactly the same until the e-mail storage unit 102 stores only e-mails sent and received regarding the project by operating using the e-mail software function installed in the personal computer. FIG. 6 is a view showing an output display example according to Embodiment 2 of the present invention, and FIG. 7 is a flowchart showing a series of operations.

  Next, in the second embodiment, an algorithm from a viewpoint different from that of the first embodiment is used. In other words, since the e-mails received sequentially according to the progress of the project are so-called inputs, and the sent e-mails are outputs, it is assumed that the relationship between inputs and outputs should fall within a certain appropriate range. This assumption was also confirmed in the results of the survey. In general, the number of sent emails is a fraction of the number of received emails. This is because many of the received e-mails are received indirectly, that is, as a copy. This ratio depends on the contents of the project, that is, the scale and the number of stakeholders. It is possible to detect an abnormal state by formally comparing the number of received emails versus the number of outgoing emails. For example, if the number of outgoing calls is significantly smaller than the number of incoming calls, this indicates a delay in the progress of the project or the occurrence of a problem. The second embodiment of the present invention is based on such knowledge.

  This specific algorithm is shown in Table 2.

The project based on the data in Table 2 is the same as in Table 1. First, (1) Elapsed months (0-12 months), (7) Received mails, (8) Outgoing mails, (9) Transmission-to-reception ratio, that is, (transmission-to-reception ratio) = (number of outgoing mails) ÷ (number of received mails) (5) is shown. For example, at the time of shipment, that is, when the number of elapsed months is 9 months, 81 ÷ 330 = 0.245 (6). Therefore, first, the total number of received and transmitted messages is calculated (step S14 in FIG. 7). Next, the ratio of the number of received messages to the number of messages to be referred to (reference value) is considered to represent the business details of the project. (7) Reference by total number of received emails and (8) outgoing emails The ratio is selected as a reference value, and the reference value is calculated (step S15 in FIG. 7). That is, (reference ratio) = (total value of outgoing mail up to the number of elapsed months) / (total value of outgoing mail up to the number of elapsed months) (7). Specifically, 787/2009 = 0.392 (8). With respect to this reference ratio (standard value), (9) transmission-to-reception ratio is calculated sequentially for each elapsed month (step S16 in FIG. 7), and (10) the difference rate is calculated for each elapsed month (step in FIG. 7). S17). The difference ratio is compared with a given threshold value (step S18 in FIG. 7). Abnormal circumstances such as project collapse appear as extreme gaps from the reference ratio (standard value), but in general, when (10) the difference rate is 0.5 or less, or 2.0 or more You should doubt the collapse of the project. In the case of the project, this is the case when the order is received, that is, (1) when the number of months elapsed is 0 months. At this time, it is clear that the project has the least movement, and the total number of incoming and outgoing e-mails is significantly smaller than the number of months that have passed since then. . However, the logic of excluding from the abnormality determination in advance when the total number of received / sent mails is extremely small is not used. The reason for this is to prevent missed abnormalities from being missed even though information exchange by e-mail should be actively performed in the course of project progress. Of course, the final decision is made by the second administrator.

  Finally, the e-mail processing unit 106 outputs FIG. 6 to the processing display unit 108 as illustrated in Table 2 and displays it (steps 19 and 20 in FIG. 7). In FIG. 6, the horizontal axis represents the number of received mails, and the vertical axis represents the number of outgoing mails. A dotted line 601 in the figure represents the reference value 0.392 in Table 2. Data for each elapsed month is displayed as plot points on the distribution chart. For example, the plot point 602 corresponds to the time of shipment, that is, the number of months elapsed, that is, the equation (6). The plot point 603 corresponds to the time when the order is received in Table 2, that is, the number of elapsed months is 0 months. Plot points that have undergone abnormality determination are displayed with their colors changed from those of other plot points. However, since they cannot be shown in this specification, their shapes are changed in FIG. A series of operations of the second embodiment of the present invention described in detail above is shown as a flowchart in FIG. However, the operations until the e-mail is stored can be realized by using the commercially available personal computer and the e-mail software function installed on the personal computer as described above, and are therefore shown in the figure. Absent.

Embodiment 3 FIG.
In the first and second embodiments, the processing is performed by paying attention to the number of received and transmitted cases as numerical data derived from the e-mail received and transmitted regarding the project. However, it is pointed out that numerical data is not necessarily limited to the number of cases. Since an e-mail can be searched for e-mail text contained therein, as a third embodiment, a specific keyword, for example, “problem” or “issue” is designated as a keyword, and all e-mails sent and received are sent and received. It is possible to find the number of appearances from month to month, and find out the progress of the project and signs of project collapse from the trend. This method is different from the so-called “text mining method”. What is called “text mining method” is to search the inside of the text to search for the meaning of the keyword such as keyword search and relation of a plurality of keywords. In the third embodiment of the present invention, This is because we do not go into the meaning of such text and focus on numerical data such as the number of monthly appearances. The purpose of this invention is not to enter the project, but to detect abnormalities such as project collapse from its formal characteristics, and to make it as visible as possible. .

Embodiment 4 FIG.
Further, as an embodiment different from the above-described Embodiments 1, 2, and 3, attention can be paid to the capacity of e-mails sent and received regarding the project as target numerical data. Focusing on numerical data such as the capacity of incoming and outgoing e-mails, it is possible to detect anomalies from a peculiar situation of sudden increase or decrease in capacity.

Embodiment 5. FIG.
By the way, as for the first to fourth embodiments, e-mails sent and received by the PM regarding the project are picked up. This is because, as mentioned above, the number of e-mails is almost all of the total number of documents sent and received in a specific project. Therefore, to understand the status of the project, only e-mail was taken out and examined. However, it is based on the premise that there is no mistaken judgment. However, it is necessary to consider that there are cases where such assumptions do not apply. This is a case where a project is managed by a trading company rather than the manufacturer assumed in the first to fourth embodiments. In this case, a large proportion of documents are exchanged between companies. In the case of trading companies operating in the Bar, it is impossible to deny the possibility that a third party is maliciously monitoring the sending and receiving of the document information. Email is not used frequently because it is difficult to keep. In addition, trading companies are carrying out various projects at the same time, and since there are many and stakeholder stakeholders outside the company, the method of sharing the encryption method in incoming and outgoing e-mails is to a malicious third party. The fact that there is a high possibility that the encryption method will be leaked is one reason why email is not frequently used. Therefore, until now, fax has been used as the simplest way to ensure the “disposable security”, that is, to transmit the official document to the other party while maintaining the necessary security at the required time. The feature is that the ratio of paper documents to be sent and received is very large. However, trading companies need to manage projects and predict the collapse of projects as well as manufacturers. In view of this situation, Embodiment 5 of the present invention targets not only electronic mail but also paper documents including faxes as the number of received and transmitted documents. As numerical data for paper documents, the number and number of paper documents received and transmitted are adopted. The number of cases is summed with the number of e-mails to be sent and received, and the number of sheets is determined as a deemed capacity per sheet and summed with the capacity of e-mails. The processing operation unit 105 of the business management system of the present invention shown in FIG. By inputting to a personal computer from a well-known input operation unit (not shown), it is possible to realize the same effects as those of the first, second and fourth embodiments of the present invention.

Embodiment 6 FIG.
The first object of the present invention is to determine the status of a business by collecting the numerical data with a predetermined period for a document sent and received in relation to the business as described above. However, the present invention can be applied not only to the above-described business situation determination but also to business plan development. This will be described below as a sixth embodiment. In the configuration of FIG. 1, the system configuration in the first embodiment or the like of the present invention is shown, but when the project is completed, the actual numerical data of e-mails received and transmitted by the PM in the project is extracted. It is possible.

  Generally, a project starts with an order received from a customer and ends with a time when it is accepted by the customer. Therefore, if the period recognized for business planning is defined as the start time to the end time, the project is received during this period. The results shown in Table 3 are obtained as an example of the number of sent emails.

  Table 3 shows an example of this, which was accepted by the customer after 26 months from the order. The total number of e-mails sent and received during this period is 5,171. The average value per month is 191.5 as shown in Table 3, and the maximum number of e-mails sent and received is 9 months elapsed. There were 411 cases as of the month. Note that at the end of the project, when there were over 300 e-mails to be sent and received, that is, for 8 months and 9 months, there was no room for involvement in other projects. It was possible to get involved in other projects during the period.

In view of such considerations, the sixth embodiment adopts an absolute value as a reference numerical value instead of the reference pattern as in the first embodiment. That is, in the sixth embodiment, when the number of e-mails sent / received monthly exceeds 300 in the configuration shown in FIG. Based on the judgment, the work of the PM is reviewed to concentrate on the project whose number exceeds 300. A flowchart in the case of the sixth embodiment is shown in FIG. Here, steps S1 to S3 and step S14 are the same as those in the first embodiment in FIG. 5 and the second embodiment in FIG. 7, respectively, and the number of e-mails sent and received monthly in step S21 is 300. When the number is exceeded, it is systematically determined to be abnormal for convenience, and an abnormal display is made on the processing display unit 108. Based on this systematic judgment, the senior manager moves to review the work of the PM and concentrate on projects with more than 300 cases.
In the sixth embodiment, the number of cases is adopted as the numerical data of the e-mail to be sent and received, but it is needless to say that the capacity of the e-mail is adopted.

  Although the present invention initially targeted project progress management as described above, official documents were exchanged in all operations in a company, and a substantial part of them was converted to e-mail. At present, it is pointed out that the fields to which the present invention can be applied are extremely wide. Generally speaking, it will be apparent that the present invention can be applied to a series of documents sent and received in correspondence with a defined business range, that is, a paper document including a fax and an e-mail. .

  As described above in detail, the present invention performs business management by judging business by paying attention to numerical data of documents sent and received in response to the progress of atypical business such as project management. It is a progressive thing that contributes to the smooth progress of business.

It is a block diagram which shows the structure of the business management system of Embodiment 1 of this invention. It is a graph which shows an example of the monthly change of the number of the emails transmitted / received in Embodiment 1 of this invention. It is a figure which shows an example of the reference pattern in Embodiment 1 of this invention. It is a figure which shows the example of an output display in Embodiment 1 of this invention. It is a flowchart which shows a series of operation | movement in Embodiment 1 of this invention. It is a figure which shows the example of an output display in Embodiment 2 of this invention. It is a flowchart which shows a series of operation | movement in Embodiment 2 of this invention. It is a flowchart which shows a series of operation | movement in Embodiment 6 of this invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 101 E-mail reception / transmission processing part 102 E-mail preservation | save part 103 Save operation part 104 Save display part 105 Process operation part 106 E-mail process part 107 Comparison reference part 108 Process display part

Claims (7)

  Consists of a document storage operation unit, document storage display unit, document reception / transmission processing unit, document storage unit, comparison reference unit, processing operation unit, document processing unit, and processing display unit. With respect to a document received and transmitted in relation, the numerical data is collected and stored by a predetermined method by setting one or more types of cycles, and a predetermined reference value and the stored value are stored for each cycle. A business management system characterized in that a difference between corresponding parts is obtained by comparison and reference, and an abnormal state of the business is determined when the difference exceeds a threshold value determined separately.   A document storage operation unit for inputting an instruction for receiving / transmitting a necessary document, a document storage / display unit for displaying an input result of the document storage operation unit, and a document related to a specific job among various miscellaneous documents received / transmitted. A document reception / transmission processing unit that collects and processes only, a document storage unit that stores data processed by the document reception / transmission processing unit, and a document group similar to the specific business that has already been completed A comparison reference unit that stores the processed parameters as reference numerical values, a processing operation unit that is operated as necessary, and a database that is stored in the document storage unit and the comparison reference unit when the processing operation unit is operated. A document processing unit that executes a comparison with a parameter extracted from a document group of a similar business to the specific business that has already been completed, and a process display unit that displays a result of the document processing unit. The document reception / transmission processing unit and the document storage unit, with respect to a specific job to be performed with a predetermined range, send one or more types of numerical data to a document to be received / transmitted in relation to the job by a predetermined method The document processing unit obtains a difference between corresponding parts by comparing and referring to a predetermined reference numerical value and the stored value for each cycle, and the difference is separately determined. A business management system characterized in that an abnormal situation of a business is judged by exceeding a threshold value.   3. The business management system according to claim 1, wherein the document includes at least one of a paper document including an electronic mail and a fax.   The business management system according to any one of claims 1 to 3, wherein the number of documents sent and received is used as the numerical data or parameter.   4. The business management system according to claim 1, wherein a ratio between the number of received documents and the number of transmitted documents in the same period is used as the numerical data or parameter.   The business management system according to any one of claims 1 to 3, wherein a capacity of a document to be sent and received is adopted as numerical data or a parameter.   4. The business management system according to claim 1, wherein the number of appearances of a keyword included in a document to be received and transmitted is adopted as numerical data or a parameter.

Images