JP2011134163A - System, method, and program for supporting job assignment - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a system for automatically executing work assignment on the basis of the operation records of applications executed by a person in charge and the data use history. <P>SOLUTION: A system for supporting job assignment is configured to automatically register job duties in a business system. The system includes an operation-history storage region for recording prescribed operation histories in the business system together with information of users executing the operations, a person-in-charge management table for registering a person in charge for each client or for each job, and a job assignment processing part for registering the user executing the operations in the person-in-charge management table as the person in charge of a client or a job by referring to the operation history storage region and on the basis of the client name information or the job name information included in the operation histories. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to an assignment assignment support system, and more particularly to a system, method, and program for automatically assigning a person in charge based on an operation history of a business application in a computer system used in an accounting office, for example.

  In recent years, business systems in which various office tasks are digitized by computer systems have been used. In general, in office work, one or a plurality of persons in charge are assigned to each business item or customer, and the person in charge often handles the case with responsibility. For this reason, many business systems can register and manage a person in charge for each item or customer. In many cases, the registration, change, and deletion of the person in charge are set and registered by the user on the matter operation screen or the person-in-charge assignment screen.

  However, registration of the person in charge is cumbersome and, for example, in the case of an accounting office, the period for acting as a personal accounting service is only one year, or in the case of tax treatment of inheritance tax, it is only once in several years Sometimes the person in charge is changed. In such a case, it is often the case that the person in charge is forgotten or postponed, and the person in charge is often operated without being registered correctly.

  Regarding registration of a person in charge, a business system has been proposed in which a business application automatically registers a person in charge of taking over a business case (for example, Patent Document 1). In this business system, by managing the information of the department in charge and the staff in charge, including past history, it is possible to automatically acquire the person who takes over the business case from the organization information even if there is an organizational change. ing.

JP 2005-92619 A

  However, the system of Patent Document 1 acquires information on the current department in charge and the staff in charge from the organization information when there is a change in organization, and it is necessary to input takeover information. Therefore, there is a possibility that it is operated without being registered correctly by deferring input of takeover or forgetting.

  SUMMARY OF THE INVENTION The present invention has been made in view of the above problems, and an object of the present invention is to provide a system, method, and program for automatically assigning a person in charge based on a job execution record processed by a person in charge and a data access history.

  In order to achieve the above-described object, the present invention provides a person assignment support system for registering and managing a person in charge in a business system, generating a predetermined operation history in the business system based on a user operation, and performing the operation. Referring to the operation history storage area, the operation history generation management unit that records the information in the operation history storage area together with the information of the performed user, the person management table that registers the person in charge for each customer or item, and the operation history storage area And a charge assignment processing unit for registering the user who performed the operation as a customer or a charge person in the charge person management table based on the customer name information or the case name information included in And

  It is desirable that the staff assignment support system further includes a staff adjustment processing unit that replaces or deletes the staff registered in the staff management table according to a predetermined standard.

  The reference is preferably based on the last access time or access frequency for each person in charge of the customer or item data.

  In one embodiment, it is desirable that a job execution record related to a job executed by an application program based on a user operation is registered in the operation history storage area.

  In addition, a responsible assignment template in which conditions of operations or jobs to be assigned in charge are registered is provided, and the assigned assignment processing unit only selects those operations history or job execution records that match the assigned assignment template conditions. It is desirable to extract and register the person in charge in the person in charge management table.

  In this embodiment, it is desirable to provide a template changing means for changing the contents of the assigned assignment template in response to an input instruction from the operator.

  It is preferable that the person-in-charge processing section presents information on the person in charge to be registered to the operator of the system and asks whether or not to register before registering the person in charge of the matter in the person-in-charge management table.

  The present invention also relates to an assignment assignment support program in a business system including a person management table for registering a person in charge for each customer or project, the program stores a predetermined operation history in the business system, A step of recording in the operation history recording area together with information on the user who performed the operation, and referring to the operation history storage area, the person who performed the operation as a customer or a person in charge of the operation And a step of registering in the management table.

  Preferably, the program further causes the business system to execute a step of replacing or deleting a person in charge registered in the person in charge management table according to a predetermined standard.

  The reference is preferably based on the last access time or access frequency of the person in charge of the customer or the case data.

  The present invention further relates to a person assignment support method in a business system comprising a person-in-charge management table for registering a person in charge for each customer or project, in which the operation history record processing means has a predetermined operation history in the business system. In the operation history recording area together with the information of the user who performed the operation, and the assigned allocation processing means refers to the operation history storage area and applies the user who performed the operation to the operation And a step of registering in a person-in-charge management table as a customer or a person in charge of a matter.

  Preferably, the method further comprises a step in which the charge adjustment processing means replaces or deletes the person in charge registered in the person in charge management table according to a predetermined standard.

  According to the present invention, since the system automatically registers the responsibilities for each customer or project based on the operation history, the labor of manual responsibilities registration can be saved, operation with incorrect data due to input mistakes, input Operation in the absence of charge due to leakage can be effectively prevented.

  Further, if the person in charge registered in the person in charge management table is replaced or deleted according to a predetermined standard, the contents of the person in charge management table can always be kept in an optimum state.

  If the criteria for replacement or deletion of persons in charge is based on the last access or frequency of access to the target data, the person who has not executed the job for a long time or has not accessed the data for a long time, or the person in charge who only works occasionally is deleted. Can be replaced with a new person in charge and operated in an optimal state.

  In addition, by setting up a person-in-charge template that registers the operations to be assigned in charge and registering only the users who performed the tasks registered here as persons in charge, only those who have performed important work with responsibility Assigning a person in charge and effectively registering a person who has performed unimportant work as a person in charge can be effectively prevented.

  By making it possible for the user to change the registered contents of the assigned assignment template, it becomes possible to operate a system that is more suitable for the actual circumstances of the company or office that uses the system of the present application.

  Further, by obtaining the operator's approval at the time of registering the person in charge, it is possible to avoid the inconvenience of being registered as a person in charge when it is known that the person will not access the data thereafter.

FIG. 1 is a diagram showing a configuration example of a charge assignment support system according to the present invention. FIG. 2 is a functional block diagram showing details of the WS terminal 1 and the server 2 in the system shown in FIG. FIG. 3 is a diagram illustrating an example of registration contents of the job execution record DB 22 b of the server storage unit 22. FIG. 4 is a diagram illustrating a registration example of the customer master DB 22d of the server storage unit 22. FIG. 5 is a flowchart showing the operation of the login authentication process to the system of the present application. FIG. 6 is a flowchart for explaining job execution recording processing by the job execution recording generation management unit 16b. FIG. 7 is a flowchart for explaining the assignment assignment processing step by the assignment assignment processing unit 18a. FIG. 8 is a diagram showing an example of the assignment assignment template that the assignment assignment processing unit 18a collates at the time of assignment assignment. FIG. 9 is a diagram showing a processing image of the assignment assignment processing. FIG. 10 is a flowchart of an embodiment in which the person in charge who is registered the oldest is replaced by the person in charge adjustment unit 18b. FIG. 11 is a flowchart of an embodiment in which the person in charge who has not been accessed for a predetermined period (for example, one year) is replaced with the person who has been updated the oldest by the person in charge adjustment unit 18b. FIG. 12 is a flowchart of an embodiment in which the person in charge with the lowest access frequency in a predetermined period (for example, the latest three months) is replaced by the person in charge adjustment unit 18b. FIG. 13 is an example of a screen for explaining a person-in-charge determination process using the concept of automatic assignment person and current setting person according to an embodiment of the present invention. FIG. 14 is a diagram showing an example of using assigned assignment data according to the present invention. FIG. 15 is a diagram showing an example of using assigned assignment data according to the present invention. FIG. 16 is a diagram showing registered contents of the data access record DB according to an alternative embodiment of the present invention. FIG. 17 is a diagram showing an alternative configuration example (stand-alone type) of the assigned assignment support system according to the present invention. FIG. 18 is a diagram showing an alternative configuration example of the assigned assignment support system according to the present invention (a network is configured only with a plurality of independent (stand-alone) terminals without a server).

  Best modes for carrying out the present invention will be described below in detail with reference to the accompanying drawings.

  FIG. 1 is a diagram showing a configuration example of a charge assignment support system according to the present invention. As shown in FIG. 1, this system is a computer system constructed in an accounting office, for example, and is configured by connecting one or more workstation terminals (WS terminals) 1 and a server 2 via a network 3. . In the system according to the present embodiment, for example, in order to perform the work of an accounting office, each WS terminal 1 and server 2 are implemented with one or more application programs for accounting processing. Although the present embodiment is configured as a client server type system, the system of the present invention may be configured as a stand-alone type. In this case, the processing for data transfer between the communication unit 13 of the WS terminal 1 and the communication unit 23 (and the control unit 21) of the server 2 in the following description is omitted.

  The WS terminal 1 is an accounting processing device assigned to each person in charge of the accounting office. When there are a plurality of persons in charge, a plurality of WS terminals 1 exist and all are connected to the server 2 via a network. The WS terminal 1 can use, for example, a general-purpose personal computer, and includes a control unit 11 that controls the entire processing of the terminal, a storage unit 12 that stores necessary data, and a communication unit that communicates with the server 2 via the network 3. 13, a display unit 14 for presenting information to the user, and an input unit 15 for receiving user input. The input unit 15 includes, for example, a keyboard 16 and a mouse 17. In addition to the financial processing program used in the accounting office, the storage unit 12 stores a charge assignment support program according to the present invention, which is read and executed by the control unit 11 to thereby execute the method according to the present invention. A step is executed.

  In addition to the OS and database access program, the server 2 includes a control unit 21 realized by loading a management program (none of which is shown) into the storage unit, a storage unit 22 that stores various data and programs, And a communication unit 23 that performs communication via the network 3. The server may be, for example, a NAS (Network Attached Storage) device connected to the network 3 as long as the server can write / read information requested from the WS terminal 1. The network 3 is not limited to the local LAN, and may be a local LAN, the Internet, or the like. Therefore, the terminal 1 and the server 2 do not necessarily have to be installed at the same place.

  FIG. 2 is a functional block diagram showing details of the WS terminal 1 and the server 2 in the system shown in FIG. The control unit 11 of the WS terminal 1 includes an application execution unit 16, a login person manager 17, and a person assignment manager 18. Each element of the control unit 11 loads an individual module of an OS, an accounting / tax processing application program, and a responsible assignment support program according to the present invention into a random access memory (not shown), and a CPU (not shown). ) To execute each process.

  The application execution unit 16 is realized by loading an application program related to normal business accounting and finance into the storage unit 12, and an application function execution unit 16a that executes each function of the application program, and a predetermined operation by the user is executed. A job execution record generation management unit 16b for generating and managing a job execution record when the job execution record is generated. The generated job execution record is accumulated in the storage unit 22 of the server 2 via the communication unit 13 and the network 3. An example of the job execution record DB 22b in which the job execution record is registered is shown in FIG. The job execution record is record information for keeping operation records or access records for particularly important work in the accounting tax processing system in order to improve the efficiency of accounting and tax processing in accounting firms. Identification information (advisor ID), person identification information (person ID), job name indicating work category, more specific work content, date, work time, and work schedule In this case, information including a book table name (not shown) is included. The job execution record generation processing will be described in detail later using the processing flow of FIG.

  The login person manager 17 is a means for authenticating the person who logs in when executing the application. The person in charge who can log in to the system and use various applications has their user name and password registered in advance in the person-in-charge master DB 22e in the storage unit 22 of the server 2. The log-in person management unit 17 presents a log-in screen from the output unit 14 (not shown) when the application execution unit 16 starts the business application, and collates the input content with the registered content of the person-in-charge master DB 22e. If they match, the application execution unit 16 is allowed to start the application (login permission), and if they do not match, execution of the application is prohibited. In addition, information on the person in charge who logs in is stored in a temporary memory. The purpose of this login authentication is to acquire information on the person in charge of the operation, and may be performed at the application level or its module level, or at the user login level to the operating system of the terminal 1. Good.

  The assignment assignment management unit 18 is a characteristic part of the present invention, and a person assignment processing unit 18a for registering a predetermined work performer as a person in charge of the customer or the case, and a person in charge of deleting or replacing the person in charge as necessary. And an adjustment processing unit 18b. In this embodiment, the person in charge of each customer is registered in the customer master DB 22d in the storage unit 22 of the server 2 as managing the person in charge for each advisor (customer) of the accounting office.

  FIG. 4 is a diagram illustrating a registration example of the customer master DB 22d of the server storage unit 22. As shown in the figure, the customer master DB 22d registers a plurality of persons in charge (in this example, persons 1 to 4 are assumed in accordance with the actual situation of the accounting office) together with information on the update date and time for each advisor ID. It can be done. The customer ID information of the customer master DB 22e is, for example, a user having administrator authority at the time of accepting a new customer, increases the customer record, and the person-in-charge information of each customer is manually input in addition to the person-in-charge registration step described below. You may be able to register. As shown in FIG. 4, the information of the persons in charge 1 to 4 may be registered or may be partially blank.

  In the present invention, the person in charge is not for each customer but for each case (for example, in the case of an individual who is not a corporation, there are many spot requests, for example, an inheritance tax processing case only) or for each business category (for example, In large accounting firms, it is self-evident that it may be managed in such a way as to respond to the division of specialists for each category, such as corporate tax return, income tax return, etc. The configuration will be readily understood by those skilled in the art from the disclosure herein. Specific operations of the respective processing units 18a and 18b will be described in detail later with reference to flowcharts.

  The control unit 21 of the server 2 registers the data sent from the terminal 1 in the storage unit 22 according to the OS and the management program, extracts the requested data from the storage unit 22 and transmits it to the terminal 1. The storage unit 22 stores an application DB 22a that stores actual data of business applications, a job execution record DB 22b that accumulates job execution records generated by the WS terminal 1, and a management that registers the progress status of each customer or project. A DB 22c, the customer master DB 22d described above, and a person-in-charge master DB 22e for performing login management are provided.

  Next, the operation of the assignment assignment support method according to the present invention or the assignment assignment support program according to the present invention will be described in detail with reference to the flowcharts of FIG. FIG. 5 is a flowchart showing the operation of the login authentication process to the system of the present application. A person who is permitted to use the system of the present application has a user name and a login password registered in the person-in-charge master 22e of the server storage unit 22 in advance. This registration is performed in advance, for example, by a user having administrator authority from the user registration screen. Since the process itself is known in various computer systems, the details thereof are omitted. When the user starts the job menu (step S11), the log-in person management unit 17 of the control unit 11 presents the user name and password input screen from the output unit 14 to the user (step S12). It inquires about the contents of the person-in-charge master DB 22e of No. 2 (step S13). When the user name and password match, the login person-in-charge management unit 17 permits login and stores the user as a person in charge in a temporary memory (not shown) (step S14). A re-input is prompted (to step S12). In this way, it is grasped that the data access from the terminal 1 is from this user until logging out thereafter.

  Here, the management of the person in charge of login may be login management at the OS level related to access management to the terminal itself, login management at a level for operating the accounting / tax processing system, It may be login management for managing the availability of various applications. This is only required to be configured so that the name and identification code of the person who operated can be referred to when generating a job execution record by recording / managing in the recording unit. The person in charge can be registered and managed with the name information, and can be registered and managed with the identification information (person in charge ID) of the person in charge as described above.

  FIG. 6 is a flowchart for explaining job execution recording processing by the job execution recording generation management unit 16b. When an application program used in a normal operation of an accounting office is started by a logged-in user (step S21), the application execution unit 16 accepts work and book specification from the user, and reads out necessary data files from the application DB 22a. The process is started (step S22). Here, when the user performs an operation by operating the application (step S23), the application execution unit 16 determines whether or not the operation is a job execution recording target (step S24). This determination may be performed by referring to the application execution unit 16 having a reference table (not shown) in which processes to be recorded for job execution are registered in advance. Information indicating that the process is a job execution record target is included in the execution code of the process, and the application execution unit 16 may detect this. Here, when the process is a job execution record target (step 24: Y), the job execution record generation management unit 16b is necessary depending on the contents of the process (job name, work name / book name, consultant, etc.). Information is extracted, and the job execution record is registered in the job execution record DB 22b of the server 2 via the communication unit 13 and the network 3 (step S25). The job execution record is accumulated as shown in FIG. 3, and thereafter used for, for example, grasping the accounting process progress status for each customer and the assignment assignment process in the present invention. The advisor selection process may be performed in step S21 or S22, or may be performed before or after these steps.

  Thereafter, when the work currently being executed is completed by the user or the application (step S26), the operation / book table selection screen is displayed again (to step S22), or the application is ended by the user's selection (step S27). Here, if the accounting data is updated, the application DB 22a is updated.

  FIG. 7 is a flowchart for explaining the assignment assignment processing steps by the assignment assignment processing unit 18 a of the assignment assignment management unit 18. The assigned allocation processing unit 18a refers to the job execution record DB 22b shown in FIG. 3 at the time of creation of a job execution record by the application execution unit 16 or at a regular timing such as at the end of a day's business, for example. One record is extracted (step S31).

  Next, it is determined whether the job / work content of this record is the job / work content to be assigned in charge (step S32). In this determination, the job / work content / book name to be assigned in charge is registered in the assigned assignment template as shown in FIG. 8, for example, and the assigned assignment processing unit 18a sets the contents of the job execution record in this assigned assignment template. This can be realized by collating.

  In this embodiment, “in charge” means not only the work of the extracted job execution record work but the charge of the entire consultant for the job. In other words, it is conceivable that the range covered as the person in charge is assigned as the person in charge limited to the job / work registered in the assignment assignment template, but b) the range covered as the person in charge is registered in the assignment assignment template. The job execution record (or operation record, access record) or job execution record (or as the job execution record is examined one by one as shown in the flow of FIG. When it is determined that the assignment assignment process is to be performed based on the operation record, the access record, and the assignment assignment template, the advisor ID (or case ID) included in the job execution record is acquired, and the name of the advisor (or the case) And the person who performed the operation / operation is registered and managed as a person in charge of the general consultant (or project).In the case of a large-scale accounting firm, the above configuration a) is also useful, but for the operation of a relatively small accounting office, the configuration of b) is desirable. (B) will be explained on the assumption.

  In step S32, specifically, the job / work content (accounting input / data input, etc.) of the job execution record is compared with the description item of the assigned assignment template for each item, and if there is a match, assigned assignment is found. If not, skip that record. The person in charge is meaningful as a responsible person, so the person who is responsible for printing to some degree of important work, for example, the "Estimated balance sheet or monthly financial statement", which is an important document in the printing process, is responsible for the customer. If the job content is, for example, “ledger” printing, it is not an important document and is often not printed by a responsible person. In this case, the person in charge does not include it in the assigned assignment template. Prevent registration. In this way, the assignment assignment template functions as an index indicating the importance of the work of the advisor service in the accounting office, so that the assignment assignment process can be performed based on only the job execution record. In addition to the contents of the above, it is possible to perform the assignment allocation process that further considers the importance of the advisory service at the accounting office by determining whether to perform the assignment assignment process based on the determination index of the assignment assignment template It becomes possible. Here, the assignment assignment template in FIG. 8 can be edited by the user, and the assignment registration in accordance with the actual situation of each office can be realized in accordance with the processing method of each office, the position of the person in charge, etc. . Alternatively, the assigned assignment template may not be editable, or assigned assignment may be performed for all job execution records without the assigned assignment template itself (that is, step S32 is not performed). Even in this case, since it is possible to select for which work the job execution record is taken (the process of step S24 in FIG. 6), it is possible to narrow down the work targets to be assigned and assigned to some extent. If it is determined in step S32 that the assignment should be assigned, the process proceeds to step S33. If there is no need to assign the assignment, the process proceeds to the next record if there is any, or the process ends if there is no next record.

  When performing assignment assignment (step S32: Y), the assignment assignment processing unit 18a first refers to the customer master DB 22e and confirms whether or not the person in charge has already been registered as a person in charge in the customer record. (Step S33). If it is already registered as a person in charge, the process is terminated, and if it is not registered, it is confirmed whether or not there is a vacancy in the customer record (step S34). If there is a vacancy, the person in charge is assigned as the person in charge of the customer (step S35). If there is no vacancy, the process is terminated without registration, or the assignment assignment adjustment described in detail later. Steps are executed to replace the person in charge (step S36).

  FIG. 9 is a visualization of the assignment assignment process (steps S31 to S35) described here. In the original customer master DB 22d shown in FIG. 9A, for example, a record 2-4 is vacant in the record of company A, but there are already four persons in charge in the record of company E and there is no vacancy. It is. As shown in FIG. 9B, the assigned assignment processing unit 18a extracts one unprocessed record in the job execution record DB 22b, and if it is a assigned assignment job, the assigned assignment is available to the assigned person as a key. If there is a vacancy, it is registered as a new person in charge as shown in FIG. In this case, as a general rule, register it in the column for the number of the young person.

  Specifically, the job execution record in the first line of FIG. 9B includes “advisor ID = Company A; person in charge ID = Tanaka; job name = accounting data input; work content = data input; date = 2008/09/15; work time = 9: 00 ”is recorded. The assigned assignment processing unit 18a searches the assigned assignment template shown in FIG. 8 using the job name and the work contents as keys. As a result, the items “job name = accounting data input; work content = data input” match, so that it is understood that this job execution record is the target of the assignment assignment process. In this case, since it is determined that the person-in-charge ID = Tanaka needs to be assigned as the person in charge of the advisor ID = A company, the person-in-charge processing unit 18a next checks the availability of the customer master 22d, The assignment status of the person in charge of “advisor ID = A company” grasps that the person in charge 1 is Sato and the person in charge 2 and below is free (unregistered). In this case, the assignment assignment processing unit 18a registers the information of “person in charge ID = Tanaka” in the field of person in charge 2 which is the youngest number among the available persons in charge, and the “date” in the job execution record. = 2008/09/15 "is recorded (see FIG. 4).

  Further, the job execution record on the fourth line in FIG. 9B includes “advisor ID = B company; person in charge ID = Abe; job name = income tax declaration; work content = printing; date = 2008/09/15. Work time = 13: 20; book name = income tax report (only book name not shown) ”is recorded. When the assigned assignment processing unit 18a searches for the assigned assignment template shown in FIG. 8, the job execution record is matched with the item of “job name = income tax declaration; work content = print”, so that this job execution record is grasped as the subject of assigned assignment processing. . Then, when the availability of the customer master 22d is checked in the same manner as described above, since the field for charge 2 is empty, registration processing is performed here. Here, even if the printing process is generally not very important, the assignment assignment process is performed as an important process for handling the income tax return.

  Also, the job execution record on the fifth line in FIG. 9B includes “advisor ID = C company; person in charge ID = Tanaka; job name = accounting data input; work content = data input; date = 2008/09. / 15; work time = 9: 00 ”is recorded. When the assigned assignment processing unit 18a searches for the assigned assignment template shown in FIG. 8, the items of “job name = accounting data input; work content = data input” match, and therefore this job execution record is grasped as the assigned assignment processing target. Then, when checking the availability of the customer master 22d, the assignment status of the person in charge of “consultant ID = Company C” is in charge 1 = Sato, charge 2 = Tanaka, and Tanaka already in the job execution record has been registered. Know that there is. In this case, the assignment assignment processing unit 18a overwrites and updates the update date in the charge 2 portion of the company C based on the information “date = 2008/09/15” of the job execution record. At the time of assignment assignment in step S35, an inquiry such as “Register as a person in charge of customer XX (YES / NO)” may be issued to the user from the output unit 13, and registration may be made only in the case of YES.

  10 to 12 are flowcharts for explaining an example of the assigned assignment adjustment step according to the present invention. (1) Replace the oldest registered person in charge, (2) The oldest registered person in charge who has not been accessed for a predetermined period (for example, one year). An adjustment method may be considered in which the person in charge is replaced, or (3) the person in charge with the lowest access frequency in a predetermined period (for example, the latest three months) is replaced. Either method may be adopted depending on the implementation environment, or the user may be switched.

  FIG. 10 is a flowchart of the embodiment (1) in which the oldest registered person in charge is replaced. For example, when it is desired to register Mr. A as a person in charge of company B and all the persons in charge of company B are filled, the assigned allocation adjusting unit 18b of the control unit 11 refers to the customer master DB 22d in FIG. The update date of the person in charge who has already been registered is acquired (step S41). Next, the acquired information is compared to identify the person in charge of the oldest update date (step S42). Then, the specified person in charge is deleted and A is newly registered as a person in charge (step S43). In this way, Mr. A is replaced with the person in charge who has been updated the oldest.

  FIG. 11 is a flowchart of an embodiment in which the person in charge who has not been accessed for a predetermined period (for example, one year) of (2) above is replaced with the person in charge who has been updated the oldest. As a premise of the present embodiment, the charge assignment management unit 18 overwrites the update date of the customer master DB 22d in FIG. 4 each time the job execution record to be assigned is created in the charge assignment process. And In the same manner as described above, the assigned allocation adjustment unit 18b first refers to the customer master DB 22d, acquires the update date of the person already registered (step S51), and determines the person in charge of the oldest update date. It identifies (step S52). Next, attention is paid to the update date of the identified person in charge, and it is confirmed whether or not this update date is one year or more away from the current date (step S53). Then, if it is more than one year away, this person in charge is replaced with a new Mr. A (step S54). If it is not more than one year away, the process is terminated without being replaced with Mr. A. This prevents the person in charge who has accessed the job within one year from being replaced, and enables proper operation. The assumption of a period of one year is based on the fact that the accounting process and tax process of the accounting firm's advisor are separated by one year, but this is not intended to be limited to this example.

  FIG. 12 is a flowchart of an embodiment in which the person in charge having the lowest access frequency in the predetermined period (3) (for example, the latest three months) is replaced. As a premise of the present embodiment, it is assumed that job execution records for at least a predetermined period (for example, the latest three months) are accumulated in the job execution record DB 22b. When it is desired to register Mr. A as a person in charge of the company B, the person-in-charge adjustment unit 18b of the control unit 11 first refers to the access record DB 22b of the server storage unit 22 (step S61), and has already been registered with the company B. For the person in charge, the number of job executions to Company B during the predetermined period is tabulated (step S62). As a result, the person in charge with the smallest number of job executions to the company B data is identified as the person in charge with the lowest access frequency (step S63). Then, the identified person in charge is deleted and a new person A is registered as a person in charge (step S64). In the case of the present embodiment, even if the person in charge has the lowest job execution frequency, the registration is not deleted (cannot be replaced) if there are more than a predetermined number of job execution records during the counting period. Good.

  In all the above-mentioned embodiments, the adjustment method in the case where the person in charge is buried when trying to assign the person in charge is explained, but this process is periodically executed not for the purpose of replacing the person in charge but for the purpose of mere deletion. Also good. That is, for example, once a month, at night when the system load is low, the customer master DB 22d is processed for each customer in the same way as in FIG. 11 and FIG. Or a person in charge whose number of job executions within a predetermined period is equal to or less than a predetermined number is deleted from the person in charge of the customer. A detailed processing procedure in this case can be easily realized by those skilled in the art with reference to FIG. 11 or FIG. By processing in this way, it is possible to reduce the processing load at the time of actual assignment and to speed up the system during normal operation. In this case, the assigned allocation adjustment process may be performed by the control unit 11 on the WS terminal 1 side, but the assigned allocation adjustment unit 18b functions as it is in the control unit 2 of the server 2, and is integrated on the server side. You may make it process to.

  In this way, according to the present invention, the system automatically registers the responsibilities for each customer or project based on the job execution history, so that manual labor responsibilities are saved, and operation with inaccurate data due to input errors can be avoided. Therefore, it is possible to effectively prevent the operation in the absence of charge due to input leakage. Further, by replacing or deleting the person in charge registered in the person in charge management table according to a predetermined standard, the contents of the person in charge management table can always be kept in an optimum state.

  The assigned assignment data registered and managed in this way (that is, the registered content of the customer master DB 22d in the above embodiment) may be configured to be appropriately modified by the user. That is, the assigned allocation adjusting unit 18b displays the contents of the customer master DB 22d of FIG. 4 on the output unit 14 in response to a user request so that the user can directly register, delete, or replace the assigned person number. Good. Here, the replacement of the person-in-charge number is a process in which, for example, the person in charge registered as person in charge 4 is moved up to person in charge 1 when managed by persons in charge 1 to 4, and in this case, other registered persons in charge The numbers are decremented one by one. This is convenient when managing a person in charge with a higher responsibility by assigning a young number.

  Also, in one embodiment of the present invention, the “automatic assignment manager” in a state where the system has automatically assigned assignments by the processing as described above, and the “current setting manager” finally approved by the operator and registered. ”May be used to delete or move a person in charge automatically assigned until a definitive charge assignment is made. An example of the interface screen of this embodiment is shown in FIG. As shown in FIG. 13, the “automatic assignment” charge automatically assigned by the charge assignment management unit 18 through the above-described assignee assignment / adjustment process is displayed on the screen along with the “current setting” charge already registered in the system. For each person assigned automatically, it is possible to determine whether or not the operator actually reflects the current setting, and finally determine whether or not the setting can be set and registered (for example, the operator can set the lower right) It can be configured to be deleted or moved in the operation window). Since this process can be realized by, for example, an operation common to the spreadsheet program, an internal detailed description is omitted here. By operating this screen, the operator checks whether or not the person in charge of automatic allocation is appropriate. If it is not appropriate, the operator deletes or moves, and finally presses the registration button to determine the person in charge. The confirmed person in charge will be treated as “currently in charge of setting”.

  14 and 15 are diagrams showing examples of using the assigned assignment data. For example, when the customer master DB 22d has the registration contents shown in FIG. 4, when the user operates an appropriate application to call the person-in-charge display screen for each customer, the application execution unit 16 refers to the customer master DB 22d, and FIG. A screen as shown in (a) is output to the output unit 14. As shown in the figure, “Sato” is displayed for the person in charge 1 and “Tanaka” is displayed for the person in charge 2 as the person in charge of the company A, indicating that the persons in charge 3 and 4 are not registered. In addition, the user designates a person in charge so that only the customers or matters handled by the person in charge can be extracted. An example of this output screen is shown in FIG. As shown in the figure, when the person in charge “Tanaka” is designated, A company, C company, and D company are displayed in a list, and from this, the accounting data of each company can be called to perform work. Since this function itself is publicly known, detailed description of internal processing is omitted.

  In addition, a business application used in an accounting office can have a function to create a progress list based on jobs and work contents input for each customer. This is important from the job execution record of FIG. This is realized by extracting the existence / non-existence and input date / time of a simple job / work and collecting it as a progress status. FIG. 15A is a diagram showing the progress status list and the data structure of charge assignment for each customer at the same time. Under such a data structure, when the user operates the application and executes a command for displaying a progress list without narrowing down the person in charge, the progress statuses of all customers are listed as shown in FIG. Is done. Alternatively, when the person in charge is narrowed down to “Tanaka”, for example, and the progress list is displayed, as shown in FIG. 15C, only the progress of the customer who registered “Tanaka” as the person in charge is extracted and displayed. Here, if there is no mechanism for assigning a person in charge according to the present invention, the person in charge is not registered correctly, and the relationship between the person in charge and the advisor (or case) in charge becomes unclear. Even if you pick up, you will not be able to grasp the progress of the correct consultant. On the other hand, according to the present invention, only the responsible person is assigned to each consultant or case, so the relationship between the person in charge and the responsible consultant (or case) is unique, and the work as a responsible person is performed. By picking up only the processing, it is possible to accurately manage the progress of the target advisor. In addition, since the person in charge is assigned to the important process without omission, the progress management of the important process can be appropriately performed based on the correct person assignment. If the data is narrowed down and displayed in this way, it is not necessary to see extra data other than the customer that he is in charge of, and user convenience is improved.

  As mentioned above, although embodiment of this invention was described in detail, this invention is not limited to said Example, It can implement | achieve as various other alternative examples. For example, in the above-described embodiment, the system accumulates job execution records, and assigns responsible for the job execution. However, in other embodiments, this is not limited to this. For example, based on the access history to a database or a file You may make it perform charge assignment. That is, the system accumulates access records for each database and file in the manner as described above for job execution records, and appropriately determines the accessor as a person in charge. An example of the data access record stored in this embodiment is shown in FIG. As described above, the assignment assignment may be performed based on the access history to the actual data of the application.

  Further, for example, in the above server-client type embodiment, the application DB 22a, job execution record DB 22b, management DB 22c, customer master DB 22d, and person-in-charge master DB 22e are configured inside the server 2 (in the storage unit 22). However, you may comprise in the memory | storage part 12 of the terminal 1 like the alternative example of FIG. 17 (namely, stand-alone structure). Further, a system that collects necessary data in a storage unit of a terminal for an administrator after preparing a network configuration in which the terminals 1 are connected to each other as in the alternative example of FIG. 18 without preparing the server 2. A configuration can also be adopted.

  The assigned assignment support system according to the present invention can be widely used in various business systems in which a person in charge is managed for each customer or project, in addition to a business system of an accounting office.

DESCRIPTION OF SYMBOLS 1 Workstation terminal 11 Control part 12 Storage part 13 Communication part 14 Display part 15 Input part 16 Application execution part 16a Application function execution part 16b Job execution record production | generation management part 17 Login person in charge management part 18 Charge assignment management part 18a Charge assignment process Unit 18b Assigned allocation adjustment unit 2 Server 21 Control unit 22 Storage unit 22a Application DB
22b Access record DB
22c Management DB
22d Customer Master DB
22e Person in charge master DB
23 Communication Department

Claims (12)

In the assignment assignment support system that registers and manages project managers in the business system,
An operation history generation management unit that generates a predetermined operation history in the business system based on the user's operation and records it in the operation history storage area together with information on the user who performed the operation, and a person in charge for each customer or project Referring to the person-in-charge management table for registering and the operation history storage area, based on the customer name information or the case name information included in the operation history, the user who performed the operation is the customer or the person in charge of the case A charge assignment support system comprising a charge assignment processing unit registered in a charge manager table as a charge assignment support system.   2. The charge assignment support system according to claim 1, further comprising a charge adjustment processing unit for replacing or deleting a charge person registered in the charge person management table according to a predetermined standard.   3. The assignment assignment support system according to claim 2, wherein the reference is based on the last access time or access frequency of the person in charge to the customer or the matter data.   4. The assignment assignment support system according to claim 1, wherein a job execution record related to a job executed by an application program based on a user operation is registered in the operation history storage area. Assign assignment support system.   The charge assignment support system according to any one of claims 1 to 4, further comprising a charge assignment template in which an operation or job condition to be assigned is registered, and the charge assignment processing unit includes the operation assignment processing unit. A person assignment support system that extracts only records that meet the conditions of a person assignment template from a history or a job execution record, and registers the person in charge in a person management table.   6. The assignment assignment support system according to claim 5, further comprising template changing means for changing the contents of the assignment assignment template in response to an input instruction from an operator.   7. The person-in-charge support system according to claim 1, wherein the person-in-charge processing unit registers information on a person to be registered before registering a person in charge of a case in the person-in-charge management table. The assignment assignment support system characterized in that the system operator is presented to the system operator to inquire whether or not to register. In the assignment assignment support program in a business system comprising a person management table for registering a person in charge for each customer or case, the business system includes:
Recording a predetermined operation history in the business system in an operation history recording area together with information of a user who performed the operation;
A step of referring to the operation history storage area and registering the user who has performed the operation as a customer or a person in charge of the case in the person-in-charge management table based on the customer name information or the case name information included in the operation history The assignment assignment support program characterized by causing   9. The assignment assignment support program according to claim 8, further causing the business system to execute a step of replacing or deleting a person registered in the person management table according to a predetermined standard. program.   10. The assignment assignment support program according to claim 9, wherein the reference is based on the last access time or access frequency of the person in charge to the customer or the matter data. In the assignment assignment support method in the business system having a person management table for registering the person in charge for each customer or project,
An operation history recording processing unit for recording a predetermined operation history in the business system in an operation history recording area together with information of a user who performed the operation;
The person in charge processing means refers to the operation history storage area and based on the customer name information or the case name information included in the operation history, the person who performed the operation is the person in charge as the customer or the person in charge of the case. And a step of registering in the management table.   12. The assignment assignment support method according to claim 11, further comprising a step in which the charge adjustment processing means replaces or deletes the person in charge registered in the person in charge management table according to a predetermined standard. Support method.

Images