JP6798356B2 - Data management equipment and programs - Google Patents

Description

The present invention relates to a data management device and a program for managing managed data.

Conventionally, there is a data management system in which managed data associated with a plurality of accounts are registered in a server as a data management device and managed on the server. As an example of such a data management system, managed data related to various operations such as financial accounting, taxation, and labor generated by a business user such as a sole proprietor or a company is registered in a server, and the managed data is stored in the business. Some are jointly managed with professional users (tax accountants, certified accountants, social insurance labor consultants, etc.) entrusted by users (for example, Patent Document 1 and Patent Document 2).

In this data management system, the account of the expert user is set as a proxy account that can access the managed data of the account of the business operator who is the adviser. The expert user who holds the proxy account can browse the managed data newly registered by the business user, and can modify the managed data as necessary. As a result, the expert user can easily and surely make appropriate corrections to the managed data of the business operator user of the adviser. Further, the business user has an advantage that he / she can save the trouble of correcting the data by himself / herself with the advice of the expert user.

Japanese Unexamined Patent Publication No. 2004-13298 Japanese Unexamined Patent Publication No. 9-274628

However, the frequency with which the user of the proxy account needs to modify the newly registered managed data is usually the proficiency level of the user who registered the managed data and the type of managed data registered by the user. It varies greatly depending on such factors. Therefore, in the above-mentioned conventional technique, there is a problem that excess or deficiency is likely to occur in the work related to the confirmation and correction of the managed data by the user of the proxy account, and the managed data cannot be managed efficiently.

An object of the present invention is to provide a data management device and a program capable of managing managed data more efficiently.

To solve the above problems, the data management apparatus according to the present invention, the storage unit managed data generated in response to the input operation by each user of the plurality of accounts, in association with the account that the input operation is performed Corresponds to the dependent account according to the input operation by the user of the managed data registration means registered in and the proxy account previously associated with one or more specific dependent accounts among the plurality of accounts. The surrogate correction processing means for correcting the attached managed data, the correction history information related to the history of the correction of the managed data by the surrogate correction processing means in a predetermined period, and the subordination registered in the storage unit. Based on the managed data associated with the account, the load information generating means for generating the load information related to the assumed load of the correction work by the user of the proxy account, and the assumed load based on the load information. Output control means for causing the output unit to perform the corresponding output, and task registration for registering task information related to a task to be performed by each user of the plurality of accounts in the storage unit in association with each of the plurality of accounts. The load information includes means and a load value information indicating the magnitude of the assumed load, and the task registration means describes the correction work when the load value exceeds a predetermined reference value. The modified task information related to the task is registered in the storage unit in association with the proxy account, and the output control means outputs an output indicating the task related to the modified task to the output unit based on the modified task information. It is characterized by having it done .
Further, in the program according to the present invention, the computer provided in the data management device associates the managed data generated in response to the input operation by each user of the plurality of accounts with the account in which the input operation is performed. In response to an input operation by the user of the managed data registration means registered in the storage unit, the proxy account previously associated with one or more specific dependent accounts among the plurality of accounts, the dependent account. The proxy correction processing means for correcting the managed data associated with, the correction history information related to the history of correction of the managed data by the proxy correction processing means in a predetermined period, and the above-mentioned registered in the storage unit. A load information generating means that generates load information related to the assumed load of the correction work by the user of the proxy account based on the managed data associated with the subordinate account, and the assumed load based on the load information. An output control means for causing the output unit to perform corresponding output, and a task registration means for registering task information related to a task to be performed by each user of the plurality of accounts in the storage unit in association with each of the plurality of accounts. The load information includes information on a load value indicating the magnitude of the assumed load, and the task registration means relates to the correction work when the load value exceeds a predetermined reference value. The modified task information related to the task is registered in the storage unit in association with the proxy account, and the output control means outputs to the output unit indicating the task related to the modified task based on the modified task information. It is characterized by being able to.

According to the present invention, there is an effect that the managed data can be managed more efficiently.

It is a schematic block diagram of a management support system. It is a block diagram which shows the main functional structure of a server. It is a block diagram which shows the main functional composition of a terminal device. It is a figure which shows the content example of the account setting data. It is a figure which shows the example of the display screen for a business operator. It is a figure which shows the example of the transaction input display screen. It is a figure which shows the example of the display screen for professionals. It is a figure explaining the setting of the proficiency level rank. It is a figure which shows the example of the ToDo task display screen. It is a flowchart which shows the control procedure by the CPU of the operation start processing for professionals.

Hereinafter, embodiments of the data management device and program of the present invention will be described with reference to the drawings.

FIG. 1 is a schematic configuration diagram of the management support system 1 of the present embodiment.
The management support system 1 includes a server 2 (data management device) and a plurality of terminal devices 3. Further, the server 2 and the terminal device 3 are connected so as to be capable of information communication via the communication network 4. The management support system 1 registers business data related to various operations such as financial accounting, taxation, and labor in the business of a business operator such as an individual business owner or a company in the server 2, and this business data is collected from the business operator and the business operator. It is a system to realize a cloud service that supports management by joint management with contracted specialists (tax accountant, certified accountant, social insurance labor consultant, consultant, etc.). Further, the management support system 1 is an aspect of a data management system that manages data of a plurality of accounts on the server 2.

The server 2 stores and manages business data input from the terminal device 3 for each of a plurality of accounts. Further, when the terminal device 3 makes a login request with a specific account, the server 2 authenticates the account and establishes a login session. In addition, the server 2 executes various programs related to business management support on the login session, and performs processing for realizing various functions related to creation, correction, browsing, etc. of business data. Note that FIG. 1 illustrates a configuration in which the management support system 1 includes a single server 2, but the present invention is not limited to this, and the management support system 1 is configured by using a plurality of servers 2. May be good.

The terminal device 3 is a terminal device possessed by a user who manages a business, a user who is involved in the business (hereinafter referred to as a business operator user), or a user of the above-mentioned expert (hereinafter referred to as an expert user). Is. The terminal device 3 is, for example, a smartphone, a tablet PC (Personal Computer), a mobile phone, a PDA (Personal Digital Assistant), a notebook PC, a desktop PC, or the like. The terminal device 3 receives a user's input operation by software such as a browser, transmits it to the server 2, and displays the information received from the server 2. The management support system 1 of the present embodiment includes a plurality of terminal devices 3.

The communication network 4 is configured by the Internet, but may include a LAN (Local Area Network), a WAN (Wide Area Network), etc., and may include a telephone line, a dedicated line, a mobile communication network, and a communication satellite network. , CATV (Cable Television) line and the like may be included.

FIG. 2 is a block diagram showing a main functional configuration of the server 2.
The server 2 stores a CPU 21 (Central Processing Unit) (managed data registration means, proxy correction processing means, load information generation means, output control means, ranking means, task registration means), RAM 22 (Random Access Memory), and storage. A unit 23, an operation unit 24, a display unit 25, a communication unit 26, and the like are provided. Further, each part of the server 2 is connected via the bus 27.

The CPU 21 reads various programs 23a such as system programs and application programs stored in the storage unit 23, expands them in the work area of the RAM 22, and controls the operation of each unit of the server 2 according to the programs. For example, the CPU 21 generates a control signal for causing the display unit 35 of the terminal device 3 to display the execution result according to the execution result of the application program, and transmits the control signal to the terminal device 3 via the communication unit 26. To do.

The RAM 22 is, for example, a volatile memory and has a work area for temporarily storing various programs and data read by the CPU 21.

The storage unit 23 is composed of, for example, an HDD (Hard Disk Drive), an SSD (Solid State Drive), an EEPROM (Electrically Erasable Programmable Read Only Memory), a flash memory, or the like.
Various programs 23a executed by the CPU 21 and various data such as setting data are stored in the storage unit 23. The program 23a includes various control programs for controlling the operation of the server 2, various application programs such as a ToDo application program, an accounting application program, a payroll application program, a POP creation application program, and a sales aggregation management application program. The program 23a is stored in the storage unit 23 in the form of a computer-readable program code.
Further, in the storage unit 23, account setting data 23b related to account setting, business data 23c associated with each account, proficiency level data 23d (proficiency level information) related to proficiency level described later for each account, The load data 23e (load information) related to the load of the journal correction work described later for the business data 23c of each account and the task database related to the task data 23f (task information) referred to when the ToDo application program is executed are stored. There is. Of these, the business data 23c includes individual data (managed data) related to accounting, salary, POP, and sales aggregation management generated by the above-mentioned various application programs. In addition to this, the storage unit 23 stores authentication data and the like stored in association with information (ID, e-mail address, password) used for authentication at login for each account.

The operation unit 24 has, for example, a key input unit such as a keyboard and a pointing device such as a mouse. Further, the operation unit 24 receives an input operation (key input) for the key input unit and an input operation (position input) for the pointing device, and outputs the operation information to the CPU 21.

The display unit 25 is composed of, for example, an LCD (Liquid Crystal Display), an organic EL (Electro-Luminescence) display, or the like. The display unit 25 displays the operation status of the server 2 and the input contents of the operation unit 24 on the display screen according to the control signal output from the CPU 21.

The communication unit 26 is composed of, for example, a network card, a modem, a TA (Terminal Adapter), a router, and the like. The communication unit 26 communicates with an external device such as a terminal device 3 on the communication network 4 to transmit / receive data.

FIG. 3 is a block diagram showing a main functional configuration of the terminal device 3.
The terminal device 3 includes a CPU 31, a RAM 32, a storage unit 33, an operation unit 34, a display unit 35 (output unit), a communication unit 36, and the like. Further, each part of the terminal device 3 is connected via a bus 37.

The CPU 31 reads various programs such as system programs and application programs stored in the storage unit 33, develops them in the work area of the RAM 32, and controls the operation of each unit of the terminal device 3 according to the programs. For example, the CPU 31 executes an information display input program such as a browser to cause the communication unit 36 to transmit information based on the content of the user's input operation to the operation unit 34 to the server 2, or display the information received from the server 2. It is displayed on the unit 35.

The RAM 32 is, for example, a volatile memory and has a work area for temporarily storing various programs and data read by the CPU 31.

The storage unit 33 is composed of, for example, an HDD, an SSD, an EEPROM, a flash memory, or the like. Various programs executed by the CPU 31 and various data such as setting data are stored in the storage unit 33. The above program includes an information display input program such as a browser.

The operation unit 34 has, for example, a key input unit such as a keyboard, a pointing device such as a mouse, and a touch panel provided so as to be superimposed on the display screen of the display unit 35. As a touch panel, in addition to the capacitance method that detects contact based on the change in capacitance between the internal conductive film and the surface due to the contact of the surface with a fingertip or the like, a resistance film method and an electromagnetic induction method. Various methods such as the above can be used. The operation unit 34 receives an input operation (key input) for the key input unit and an input operation (position input) for the pointing device or the touch panel, and outputs the operation information to the CPU 31.

The display unit 35 is composed of, for example, an LCD or an organic EL display. The display unit 35 displays the processing result of the application program executed by the server 2 and the input contents by the operation unit 34 on the display screen (for example, in the application window of the browser) according to the control signal output from the CPU 31.

The communication unit 36 is composed of, for example, a network card, a modem, a TA, a router, and the like. Further, the communication unit 36 may be provided with an antenna, a modulation / demodulation circuit, a signal processing circuit, and the like, and may be configured to enable wireless communication. The communication unit 36 communicates with an external device such as a server 2 on the communication network 4 to transmit / receive data.

Next, the operation of the management support system 1 will be described.

<Overall operation and operation related to proxy setting>
In the management support system 1 of the present embodiment, an account is generated for a business user or an expert user, and the information of the account is stored in the account setting data 23b. The business operator user and the expert user can log in to the management support system 1 by inputting the authentication information related to their own account in the terminal device 3 and transmitting it to the server 2, and in the login session started by this. , Business data 23c on the server 2 associated with the account can be accessed. Specifically, by performing an input operation on the terminal device 3 and causing the server 2 to execute a predetermined application, it is possible to generate, modify, and browse business data 23c related to the logged-in account. In the following, the above login accompanied by the input of authentication information will also be referred to as "first login". In the management support system 1 of the present embodiment, authentication information is configured by a combination of an ID and a password, or a combination of an e-mail address and a password. The first login is performed when the authentication information input by the user on the predetermined login screen matches any of the authentication information in the authentication data stored in the storage unit 23.

Further, in the management support system 1 of the present embodiment, the account of the business operator user can be set as a proxy for the account of a specific expert user. When the first login is performed with the account of the expert user who has been set as a proxy (hereinafter, also referred to as the proxy account), the account of the business user who granted the proxy right to the proxy account in the login session. You can log in further (hereinafter also referred to as the dependent account), which allows you to access the data related to the dependent account. In the following, login with a subordinate account in a login session with a proxy account is also referred to as "second login". In this embodiment, it is assumed that the expert user has a proxy account. In this second login, it is not necessary to input the authentication information related to the subordinate account. Therefore, an expert user who has a proxy account does not need to know the credentials of the dependent account from the operator user who has the dependent account or have a separate account that can access the dependent account. By performing the first login with the proxy account owned by the home user and then performing the second login with the subordinate account, it is possible to easily access the business data 23c of the subordinate account.
The proxy setting is performed by associating the proxy account of the expert user with the subordinate account of the specific business user in the account setting data 23b.

FIG. 4 is a diagram showing an example of the contents of the account setting data 23b.
In the account setting data 23b, the data of each item of "email address", "proxy setting", and "subordinate account" is stored in association with each of the plurality of accounts.
In FIG. 4, the account is identified by the "ID" consisting of three digits, but the account identification method is not limited to this. For example, the account may be identified by using the character string input by the user as the "ID".
The "e-mail address" is a unique e-mail address that is different from each other among a plurality of accounts, and may form a part of the authentication information. This e-mail address is set, for example, by input from the user when the account is created.
The “proxy setting” is an item indicating whether or not the proxy right is set for the account, that is, whether or not the account is a proxy account. In FIG. 4, the presence / absence of proxy setting is indicated by the notation of “yes” and “no”, but in the actual account setting data 23b, it is regarded as 1-bit data.
The "subordinate account" is an item indicating an account for which a proxy right has been set for the proxy account, that is, a dependent account. For example, in FIG. 4, two accounts having IDs “014” and “035” are set as subordinate accounts with respect to the proxy account having ID “001”. In this way, two or more dependent accounts may be set for one surrogate account.
Note that the account setting data 23b may include items not shown in FIG. For example, an item indicating a password corresponding to each account, an item indicating a proxy account to be set as a proxy when the account is a subordinate account, and the like may be included.

The method of proxy setting in the account setting data 23b is not particularly limited, but is performed by, for example, the following operation. That is, an e-mail (approval e-mail) that prompts the target user to approve the proxy setting by inputting the e-mail address of the target user who wants to perform the proxy setting in a predetermined input form. ) Is sent. Then, when the target user performs the approval process on the approval website in which the URL is described in the approval e-mail, the account is associated with the target user in the account setting data 23b and is represented. The settings are made. In addition, if the target user does not have an account, an e-mail prompting you to create an account and approve the proxy setting will be sent, and if the target user's account is generated, it will be with the account. Proxy settings are made.
In the proxy setting of the present embodiment, the proxy setting for associating an account that is already a proxy account as a proxy account and the proxy setting for associating an account that is already a dependent account as a proxy account are not performed. The operation and processing related to the above are adjusted. As a result, proxy settings such as grandchild proxy and mutual proxy are not performed.

<Operation with the account of the operator user>
FIG. 5 is a diagram showing an example of a business operator display screen 50 displayed on the display unit 35 of the terminal device 3 when the first login is performed by the business operator user account.
At the top of the business display screen 50, the icon Ia for starting the ToDo application program described above, the icon Ib for starting the accounting application program, the icon Ic for starting the payroll application program, and the POP creation application program A menu bar including the icon Id for starting the application program and the icon Ie for starting the sales total management application program is displayed.
When the user selects each icon on the menu bar by a click operation or a touch operation, the screen transitions to a predetermined processing screen of the application corresponding to the selected icon.

Among the above programs, the ToDo application program is a program for registering the task data 23f related to the ToDo task in the task database of the storage unit 23 and displaying the ToDo task according to the contents of the task data 23f. ..
The accounting application program is a program for performing processing related to transaction journals, processing related to asset management, processing related to tax payment, etc., based on the accounting information included in the business data 23c.
The salary application program is a program for processing employee salary calculation based on salary information included in business data 23c.
The POP creation application program is a program for creating a POP (Point of Purchase advertising), which is an advertising medium for sales promotion used in shops and the like.
The sales aggregation management application program is a program for performing daily and monthly sales aggregation and analysis of stores based on the sales information included in the business data 23c.

FIG. 5 illustrates a state in which the icon Ib is selected and the accounting application program is executed. When the accounting application program is executed, a plurality of function icons 51 for executing processing related to various functions are displayed on the business operator display screen 50. Specifically, new entry and correction of transactions, viewing and editing of general ledger and journal, creation and viewing of consumption tax summary table and balance trial balance, cash account book, expense book, accounts payable book, accounts payable book, A function icon 51 corresponding to each function such as viewing and editing the deposit account book is displayed. When the user selects the function icon 51 by a click operation or a touch operation, the process corresponding to the selected function icon 51 is executed, and the screen can be transitioned to the display screen related to the process.

FIG. 6 is a diagram showing an example of a transaction input display screen 50a for performing new input or correction of a transaction. The transaction input display screen 50a is displayed on the display unit 35 of the terminal device 3 when the function icon 51 of "new transaction input" or "transaction correction" is selected on the business operator display screen 50 of FIG.
On the transaction input display screen 50a, after selecting the transaction category on the transaction category selection tab 52, enter the transaction date, settlement method, business partner, transaction description, account, and transaction amount in the text box 53, and then register button 54. By selecting, you can enter information related to transaction journals and modify it. The transaction journal data related to the transaction journals generated as a result of the input operation on the transaction input display screen 50a is stored in the storage unit 23 as a part of the business data 23c. This transaction journal data is an aspect of managed data.

<Operation with a proxy account of an expert user>
FIG. 7 is a diagram showing an example of a professional display screen 60 displayed on the display unit 35 of the terminal device 3 when the first login is performed by the proxy account of the professional user.
On the expert display screen 60, information on the subordinate accounts for which the proxy setting is made for the logged-in proxy account is displayed in a list. In the example of FIG. 7, the expert display screen 60 includes an advisor management screen 61 in which information about the business user corresponding to the subordinate account is listed.
Further, in the menu bar displayed at the upper part of the expert display screen 60, in addition to the same menu bar as the business operator display screen 50, an icon If for displaying the advisor management screen 61 is displayed. On the professional display screen 60, by selecting one of the icons Ia to Ie, the above-mentioned various application programs such as the ToDo application program can be executed, and the icon is displayed in a state related to the application. By selecting If, the screen can be changed to the advisor management screen 61.

On the advisor management screen 61 on the expert display screen 60, the name (store name) of the business user (advisor) corresponding to the subordinate account, the service use start date, the last update date of the business data 23c, and the transaction journal data are still registered. Number of unprocessed transactions (number of unprocessed journal entries), number of transactions for which the expert user has not yet confirmed the transaction journal data (number of unprocessed journal entries), proficiency rank of the dependent account, and the dependent The items of the assumed load when modifying the journal entry of the account and the proxy login icon 63 for performing proxy login with the dependent account are displayed. On the advisor management screen 61, by selecting the sort icon 62 for each item, it is possible to sort the corresponding item.

When the expert user selects the proxy login icon 63 corresponding to a specific subordinate account by a click operation or a touch operation on the advisor management screen 61, a second login with the subordinate account is performed without inputting the authentication information. The second login process for performing the above is executed. When the second login is performed, the business operator display screen 50 of FIG. 5 for the subordinate account that has performed the second login is displayed. Then, by invoking various application programs from the menu bar of the displayed business operator display screen 50, it is possible to view and edit the business data 23c of the business operator user corresponding to the subordinate account. For example, by displaying the transaction input display screen 50a of FIG. 6, the content of the transaction journal data input by the business operator user can be confirmed (hereinafter referred to as "journal confirmation"), and the journal confirmation can be performed. By modifying the input information on the transaction input display screen 50a according to the result, it is possible to modify the transaction journal data (hereinafter referred to as "journal correction") on behalf of the business operator user.
In this way, the expert user performs the first login with his / her surrogate account, then selects the surrogate login icon 63 and performs the second login with the subordinate account of the consulting business user. The business data 23c of the business user can be easily accessed. Then, according to the contents of the business data 23c, necessary advice and guidance are given to the business user of the adviser, and the business data 23c of the business user is directly corrected to correct the deficiencies and problems of the business data 23c. By doing so, it is possible to provide support to business users.

By the way, the frequency at which the expert user needs to correct the journal entry data newly registered by the business operator user usually varies greatly depending on the proficiency level of the business user who registered the transaction journal data. .. For example, for a highly proficient business user, even if the number of transaction journal data for which the expert user should confirm the journal (“number of unprocessed journal confirmation” on the advisor management screen 61) is large, there are few mistakes. Therefore, the load of journal correction often does not increase. On the other hand, for business users with low proficiency, even if the number of transaction journal data for which journal confirmation should be performed is small, it takes time to correct journals for individual transaction journal data, which is a heavy burden for expert users. There are many. Under these circumstances, when the expert user confirms the journal and corrects the journal data newly registered by each business user at a uniform frequency, it depends on the proficiency level of the business user. , The frequency is often excessive or insufficient.

Therefore, in the management support system 1 of the present embodiment, for each subordinate account, the proficiency rank of the user (business operator user) of the subordinate account regarding the registration of transaction journal data is calculated, and the subordinate accounts are ranked. Further, the proxy account is based on the proficiency rank associated with the dependent account and the amount of transaction journal data currently registered in the business data 23c of the storage unit 23 associated with the dependent account. The assumed load is calculated when the user (expert user) of the above performs the work for checking the journal and correcting the journal for the transaction journal data of the subordinate account (hereinafter, referred to as the journal correction work (correction work)). In the following, the calculation of these proficiency ranks and expected loads related to dependent accounts will be described in detail.
In the management support system 1, the proficiency level is calculated as a feature amount related to the subordinate account and associated with the subordinate account. However, for convenience of explanation, the proficiency rank associated with the subordinate account is referred to below. It is also described as the proficiency rank of the business user who owns the dependent account. Similarly, in the management support system 1, the above-mentioned assumed load is calculated as a feature amount related to the dependent account and associated with the dependent account. In the following, the assumed load associated with the dependent account is assigned to the dependent account. It is also described as the assumed load for the business user who owns (or for the transaction journal data of the business user).

In the management support system 1 of the present embodiment, for each subordinate account, the journal registration history information (registration history information) related to the registration history of the transaction journal data in the past predetermined period, and the expert of the transaction journal data in the predetermined period. Based on the journal correction history information (correction history information) related to the history of journal correction by the user, the proficiency rank of the business user (dependent account) who owns each subordinate account is calculated, and the business user (subordinate account) It is ranked and the result of this ranking is displayed on the advisor management screen 61.
Specifically, the number of transaction journal data newly generated in association with the subordinate account by each business user in the past predetermined period (hereinafter referred to as "the number of newly generated journal data") is the journal registration history information. The number of transaction journal data (hereinafter referred to as "the number of journal correction data") that has been corrected by an expert user (user of the proxy account) during the specified period is used as the journal correction history information and is new. The proficiency rank of each business user is calculated according to the ratio of the number of journal correction data to the number of generated journal data. On the advisor management screen 61 of FIG. 7, the number of newly generated journal data and the number of journal correction data in the latest predetermined period (in this embodiment, the period in which the latest 100 transaction journal data were generated) are set as the proficiency level. The rank calculated based on is listed in the "most recent" column. In addition, for reference, the rank calculated based on the number of newly generated journal data and the number of journal correction data in the entire period from the date when the business user starts using the service of the management support system 1 is "all period". It is also written in the column. In the present embodiment, calculating the proficiency rank of each business user and displaying it on the display unit 35 corresponds to the output related to the result of ranking of the business users. The expert user can grasp the proficiency level of each business user by referring to the proficiency level rank. The proficiency level rank related to each business user (subordinate account) is stored as proficiency level data 23d in the storage unit 23.

In addition, each business user (subordinate account) is based on the above-mentioned most recent proficiency rank and the number of transaction journal data that has not yet been accessed by the expert user in the proxy account, that is, the number of journal confirmation unprocessed transactions. ), Load information indicating the assumed load when confirming the journal of unconfirmed transaction journal data and correcting the journal is generated. This load information includes information on a load value indicating the magnitude of the assumed load, and the load value is displayed in the "confirmation" column of the "estimated load" on the advisor management screen 61. .. In the following, the load value for journal confirmation and journal correction of this transaction journal data will also be referred to as "confirmation load value". The expert user can adjust the frequency of journal correction work of transaction journal data for each business user (subordinate account) according to this confirmation load value.
In the advisor management screen 61 of FIG. 7, as an assumed load, "journal agency" representing the load value of the assumed load when registering transaction journal data for all unjournaled transactions on behalf of the business operator user. The column of is also provided. In the following, the load value for this journal agency will also be referred to as the "journal agency load value". The confirmation load value and the journal entry agency load value for each subordinate account are stored as load data 23e in the storage unit 23.

FIG. 8 is a diagram illustrating the setting of the proficiency level.
As shown in FIG. 8, the proficiency level of the present embodiment is assigned to new advisors in six stages from the highest proficiency level S to the lowest proficiency level E. There are 7 levels including rank N.
Of these, the proficiency level rank S has an appropriate journalizing rate P represented by (1-m / n) of 0.999 or more when the number of newly generated journal data is n and the number of journal correction data is m. This is the rank assigned to the operator user (subordinate account). Similarly, proficiency rank A is assigned to business users whose proper journal rate P is 0.995 or more and less than 0.999, and proficiency rank B is assigned to proper journal rate P of 0.990 or more and less than 0.995. The proficiency level C is assigned to the business user whose appropriate journal rate P is 0.980 or more and less than 0.990, and the proficiency rank D has the appropriate journal rate P of 0. It is assigned to business users whose proficiency level is 950 or more and less than 0.980, and proficiency rank E is assigned to business users whose appropriate journal rate P is less than 0.950. Business users with proficiency levels S to E correspond to journal experts, advanced journals, intermediate and advanced journals, intermediate journals, beginners, and beginners, respectively. As described above, in the present embodiment, the higher the appropriate journalizing rate P (that is, the smaller the ratio of the number of journal correction data m to the number of newly generated journal data n) is, the higher the proficiency level is calculated. Is assigned.
Further, the business user who has less than 100 cumulative registrations of transaction journal data is assigned a proficiency rank N indicating that he / she is a new adviser regardless of the appropriate journal rate P.

Further, as shown in FIG. 8, each proficiency level rank is associated with a load coefficient F used for calculating the confirmation load value. Specifically, the load coefficients F corresponding to the proficiency rank S / A / B / C / D / E / N are 1.0 / 1.1 / 1.2 / 1.4 / 2.0 /, respectively. It is set to 3.0 / 5.0. This load coefficient F represents the magnitude of the load of the journal correction work by the expert user for one transaction journal data generated by the business user of each proficiency rank. The load coefficient F of the proficiency level rank N is set as large as 5.0 when the business user of the new adviser usually has a low proficiency level and has an unexpected defect such as a setting error. This is because there are many transactions in the industry that are not familiar to expert users, and it takes time to confirm journal entries.

The data related to the calculation reference value of the appropriate journalizing rate P corresponding to each proficiency level rank and the value of the load coefficient F corresponding to each proficiency level rank are generated in advance and stored in the storage unit 23.
The calculation reference value of the appropriate journalizing rate P and the value of the load coefficient F in FIG. 8 are examples and are not limited thereto.

The confirmation load value in the "confirmation" column of the "estimated load" in FIG. 7 is calculated by multiplying the "number of unprocessed journal entry confirmation transactions" by the load coefficient F corresponding to the proficiency rank of each business user. To.
In addition, regarding the journal agency load value in the "journal agency" column of the "estimated load", the constant 3.0 in the "number of unprocessed journal registration transactions" (5.0 for business users with proficiency rank N). It is calculated by multiplying by. In the "journal agency", the expert user makes all the inputs on the transaction input display screen 50a of FIG. 6 in response to the request from the business operator, and 1 regardless of the proficiency level rank of the business operator user. This is because almost the same load is generated per case.
The load coefficient F calculated as described above for each business user can be changed according to an input operation from an expert user (user of a proxy account). In the present embodiment, the load coefficient F is not recognized by the user, but the expert user can change the proficiency level rank of each business operator user, and responds to the change in the proficiency level rank. The load coefficient F can be changed. The proficiency rank can be changed, for example, by selecting the proficiency rank change button 65 in FIG. 7 and then selecting an individual proficiency rank display frame. Instead of this, the load coefficient F may be directly changed after showing the information of the load coefficient F to the expert user.

Further, in the present embodiment, when the confirmation load value and the journal entry agency load value calculated as described above become equal to or more than a predetermined reference value (50 in this embodiment), the confirmation load value and the journal entry agency load value The part of the value that is greater than or equal to the reference value is highlighted. In the example of FIG. 7, since the confirmation load value and the journal entry agency load value for the business user of "Cafe Adps" are both 50 or more, the display frame of the confirmation load value and the journal entry agency load value is thickened. The highlight frame display 64 is made.
The above reference value is not limited to 50. Further, the expert user may be able to arbitrarily set the reference value.

Furthermore, if any of the confirmation load values is 50 or more, the expert user of the proxy account is notified that there is a business user with a large assumed load (there is a subordinate account), and the journal is confirmed. The task data 23f (correction task information) of the journal confirmation ToDo task for encouraging the work of is generated and registered in the task database of the storage unit 23. When the task data 23f of the journal confirmation ToDo task is registered in the task database and the input operation for selecting the icon Ia of the ToDo application program is performed, the ToDo task display screen including the display related to the journal confirmation ToDo task is displayed on the terminal. This is done on the display unit 35 of the device 3.
In addition to the case where the confirmation load value is 50 or more, the task data 23f of the journal confirmation ToDo task may be generated when any of the journal entry agency load values is 50 or more.

FIG. 9 is a diagram showing an example of the ToDo task display screen 70. FIG. 9 illustrates a ToDo task display screen 70 when a ToDo application program is executed on a smartphone as a terminal device 3.
On the ToDo task display screen 70, a task index list display area R in which task indexes Ta and Tb representing an outline of the ToDo task are listed is displayed below the menu bar. In the upper area R1 of the task index list display area R, the unprocessed task index Ta that has not processed the ToDo task is displayed in a list in the order of the earliest date (ascending order) based on the execution deadline date. ing. On the other hand, in the lower area R2 of the task index list display area R, the task indexes Tb that have processed the ToDo task are displayed in a list in the order of the latest date (descending order) based on the execution date. There is. The contents of the task data 23f (for example, registration date / time, execution deadline date, contents of ToDo task, application related to ToDo task, etc.) recorded in the task database recorded in the storage unit 23 are reflected in the task indexes Ta and Tb. Will be done. Further, in the task index Ta in the upper layer area R1, the content of the task to be processed, the icon Ig for transitioning to a predetermined screen of the application (the screen related to the content of the task to be processed), and the task process. The task completed button B that is selected and operated when this is done is displayed.

In the ToDo task display screen 70 of FIG. 9, the task index Ta related to the above-mentioned journal confirmation ToDo task is displayed at the uppermost part of the upper layer area R1. By this task index Ta, the expert user is notified that the assumed load related to the journal confirmation and journal correction of the transaction journal data is increasing for the advisor "Cafe Adps". By seeing this journal confirmation ToDo task and starting the journal correction work of the transaction journal data, the expert user can perform the journal correction work at an appropriate timing when the load value of the assumed load exceeds a predetermined size. it can.
In addition, on a display screen other than the ToDo task display screen 70 of FIG. 9 (for example, on the expert display screen 60 of FIG. 7), a display notifying that the journal confirmation ToDo task has been generated may also be performed.

<Operation control procedure for expert users>
Subsequently, in the management support system 1, the control procedure of the operation start process for the expert, which is executed when the operation for the expert user including the calculation of the proficiency level described above is started, will be described.

FIG. 10 is a flowchart showing a control procedure by the CPU 21 for the operation start processing for professionals.
The operation start process for the expert is started when the login request accompanied by the input of the authentication information related to the proxy account of the expert user is made by the input operation in the terminal device 3 and the authentication is successful.

When the expert operation start process is started, the CPU 21 performs a first login process for the expert user's proxy account (step S101).

The CPU 21 refers to the business data of each subordinate account associated with the surrogate account that made the first login, and for the business user corresponding to the subordinate account, the transaction journal newly generated in the past predetermined period. The number of data (number of newly generated journal data n) is acquired as journal registration history information, and the number of transaction journal data (number of journal correction data m) that has been corrected by an expert user during the predetermined period is the journal correction history. Acquired as information (step S102). Further, the CPU 21 acquires the number of journal registration unprocessed transactions and the number of journal confirmation unprocessed transactions for each business operator user (step S103).

Based on the journal registration history information and the journal correction history information acquired in step S102, the CPU 21 calculates the entire period and the latest proficiency rank of each business user by the above-mentioned method (step S104). The CPU 21 generates the proficiency level data 23d including the calculated proficiency level rank and stores it in the storage unit 23.

The CPU 21 calculates a load value indicating an assumed load of journal correction work by an expert user for each business user (step S105). That is, the CPU 21 refers to the proficiency level data 23d generated in step S104 and the table data in FIG. 8 to acquire the load coefficient corresponding to the calculated proficiency level rank, and confirms the journal entry acquired in step S103. The confirmed load value is calculated by multiplying the number of unprocessed transactions by the load coefficient. Further, the journal entry agency load value is calculated by multiplying the number of journal registration unprocessed transactions acquired in step S103 by a predetermined number (3.0 or 5.0). The CPU 21 generates load data 23e including the calculated confirmation load value and the journal entry agency load value, and stores the load data 23e in the storage unit 23.

The CPU 21 determines whether or not any of the calculated confirmation load value and the journal entry agency load value is 50 or more (step S106), and if there is a load value of 50 or more (YES in step S106). "), The task data 23f of the journal confirmation ToDo task is generated and registered in the task database of the storage unit 23 (step S107).

When the processing of step S107 is completed, or when it is determined in the processing of step S106 that all the confirmation load values and the journalizing agency load values are less than 50 (“NO” in step S107), the CPU 21 is the terminal device. The display unit 35 of 3 displays the professional display screen 60 (step S108). Here, the CPU 21 includes the number of journal registration unprocessed transactions and the number of journal confirmation unprocessed transactions acquired in step S103, the proficiency level rank calculated in step S104, and the confirmation load value and journal entry agency load calculated in step S105. A control signal for displaying the expert display screen 60 including the value information is generated and transmitted to the terminal device 3.
When the process of step S108 is completed, the CPU 21 ends the operation start process for professionals.

As described above, the server 2 in the management support system 1 of the present embodiment includes the CPU 21, and the CPU 21 uses the transaction journal data as the management target data generated in response to the input operation by each user of the plurality of accounts. , Registered in the storage unit 23 in association with the account for which the above input operation has been performed (managed data registration means), and a proxy associated in advance with one or more specific subordinate accounts among a plurality of accounts. The transaction journal data associated with the subordinate account is modified according to the input operation by the account user (expert user) (proxy correction processing means), and the journal correction history related to the correction history of the transaction journal data in a predetermined period. Based on the information and the transaction journal data associated with the subordinate account registered in the storage unit 23, load data 23e related to the assumed load of journal correction work by an expert user as a user of the proxy account is generated. Then, based on the load data 23e, the display unit 35 is made to display according to the assumed load (output control means).
According to such a configuration, the user (expert user) of the proxy account can refer to the display on the display unit 35 to correct the journal entry for the transaction journal data of the user (business user) of each subordinate account. It is possible to estimate the load when performing. As a result, for example, by giving priority to the journal correction work for the business user who is estimated to have a heavy load from the above display, there is an inconvenience that an unexpectedly large load is generated in the journal correction work of a specific business user. It can be made less likely to occur. Further, regarding the transaction journal data of the business user who is estimated to have a small load, it is possible to prevent the journal correction work from becoming excessively frequent by forgoing the journal correction work at that stage. Therefore, the expert user can perform support work (journal correction work) for the business user in a planned and timely manner. As described above, according to the server 2 as the data management device of the present embodiment, the transaction journal data can be managed more efficiently.

Further, the proxy account is associated with two or more subordinate accounts, and the CPU 21 ranks the two or more subordinate accounts according to the assumed load for each of the two or more subordinate accounts (ranking). Means), the display unit 35 is made to display the result of ranking (output control means). As a result, the expert user who holds the proxy account can easily identify the business user who has a large assumed load of journal correction work among the business users of the advisors corresponding to the two or more subordinate accounts. .. As a result, it is possible to greatly improve the management efficiency of the transaction journal data corresponding to each subordinate account, in particular, when the surrogate setting for a large number of subordinate accounts is made for the surrogate account of one expert user. it can.

Further, the load data 23e includes load value information indicating the magnitude of the assumed load, and the CPU 21 causes the display unit 35 to display according to the load value (output control means). As a result, the expert user can quantitatively grasp the magnitude of the assumed load. Therefore, since the start timing of the journal correction work can be adjusted more appropriately, the management efficiency of the transaction journal data can be further improved.

Further, when the load value exceeds a predetermined reference value, the CPU 21 causes the display unit 35 to perform a predetermined display indicating that the load value exceeds the reference value (output control means). As a result, the expert user can easily and surely grasp and identify the business user who needs special attention because the assumed load of the journal correction work is particularly large.

Further, the CPU 21 registers the task data 23f related to the task to be executed by each user of the plurality of accounts in the storage unit 23 in association with each of the plurality of accounts (task registration means), and the load value sets the reference value. When it exceeds, the task data 23f related to the journal confirmation ToDo task for the journal correction work is registered in the storage unit 23 in association with the proxy account of the expert user (task registration means), and based on this task data 23f, The display unit 35 is made to display the journal confirmation ToDo task for the journal correction work (output control means). By generating the journal confirmation ToDo task in this way, the expert user can more easily and surely grasp that there is a business user who needs attention because the assumed load of the journal correction work is particularly large. In addition, the expert user sees this journal ToDo task and starts the journal correction work of the transaction journal data, so that the journal correction work can be performed at an appropriate timing when the load value of the assumed load exceeds a predetermined size. Can be done.

Further, the CPU 21 loads the load value based on the journal registration history information, the journal correction history information, and the transaction journal data associated with the dependent account registered in the storage unit 23 related to the registration history of the transaction journal data in the predetermined period. Is calculated to generate load data 23e (load information generation means). As a result, a more accurate load value that takes into account the frequency of registration of transaction journal data by the business user in each subordinate account and the frequency of journal correction by the expert user in the proxy account for the transaction journal data can be obtained. Can be calculated. For example, it is possible to calculate an accurate load value even for a business user whose registration frequency of transaction journal data fluctuates greatly.

Further, the CPU 21 is a ratio of the number of transaction journal data whose journals have been corrected by an expert user in the predetermined period to the number of transaction journal data registered in association with the dependent account in the predetermined period. According to, a load coefficient related to the load size of the journal correction work is assigned to each dependent account, and the transaction journal data associated with the dependent account that has not yet been accessed by the expert user of the proxy account. The load value is calculated by multiplying the number of journal data by the load coefficient assigned to the dependent account (load information generation means). The above ratio represents the ratio of transaction journal data registered by each business user user that requires journal correction by an expert user. By using such a ratio, a more appropriate load coefficient can be assigned to each dependent account (business user). Further, by using the load coefficient, the load value can be calculated more accurately by a simple process.

In addition, the load factor for the dependent account can be changed according to the input operation from the expert user in the proxy account. Thereby, when there is a discrepancy between the load value based on the load coefficient assigned by the processing of the CPU 21 and the load actually felt by the expert user, the load value can be easily adjusted.

Further, the program of the present embodiment uses the computer provided on the server 2 as the data management device to generate transaction journal data as managed data generated in response to input operations by each user of a plurality of accounts. Managed data registration means to be registered in the storage unit 23 in association with the account for which the input operation has been performed, and the user of the proxy account previously associated with one or more specific subordinate accounts among the plurality of accounts ( A proxy correction processing means for correcting the transaction journal data associated with the subordinate account in response to an input operation by the expert user), journal correction history information related to the history of correction of the transaction journal data in a predetermined period, and a storage unit 23. Load information generating means for generating load data 23e related to the assumed load of journal correction work by an expert user as a user of the proxy account based on the transaction journal data associated with the subordinate account registered in Based on the load data 23e, the display unit 35 is made to function as an output control means for displaying according to the assumed load. According to such a program, the transaction journal data can be managed more efficiently by the server 2 as a data management device.

In the above description, an example in which the HDD or the like of the storage unit 23 is used as a computer-readable medium for the program according to the present invention has been disclosed, but the present invention is not limited to this example. As another computer-readable medium, a portable recording medium composed of a CD-ROM, a flash memory, or the like can be applied. A carrier wave is also applied to the present invention as a medium for providing data of a program according to the present invention via a communication line.

The description in the above embodiment is an example of the embodiment of the data management device and the program according to the present invention, and the present invention is not limited thereto.
For example, in the above embodiment, the load value is calculated based on the journal registration history information as the registration history information and the journal registration history information as the correction history information, but the load value is not limited to this, and the load value is calculated according to only the correction history information. May be calculated. For example, when the frequency of registration of transaction journal data by a business user can be regarded as almost constant, the number of corrections of transaction journal data in a predetermined period and the above-mentioned appropriate journal rate P are almost inversely proportional to each other. The load value can be calculated by calculating the proficiency level rank and the load coefficient F accordingly.

Further, in the above embodiment, the load data 23e indicating the assumed load has been described with reference to an example including the information of the load value indicating the magnitude of the assumed load, but the load data 23e does not include the information of the load value. It may be. For example, when there is a type of managed data that has a particularly large number of corrections in the past predetermined period, when the type of managed data is newly registered, a display indicating that the assumed load is large may be displayed. ..

Moreover, the managed data is not limited to transaction journal data. The management target data can be various individual data related to ToDo, accounting, salary, POP, and sales aggregation management generated by various application programs.

Further, in the above embodiment, as an example of displaying the proficiency level rank itself as the result display of the ranking of the business user (subordinate account), the mode of displaying the result of the ranking is not limited to this. .. For example, on the advisor management screen 61, the characters and backgrounds of the lines indicating the business user are color-coded according to the calculated proficiency rank, and the display order is such that the business users having the same proficiency rank are adjacent to each other. May be rearranged or marks according to the proficiency rank may be displayed.

Further, in the above embodiment, when the calculated confirmation load value or the journalizing agency load value is equal to or more than the predetermined reference value, the highlighted frame display 64 (FIG. 7) indicates the portion where the reference value or more is exceeded. , The mode of highlighting is not limited to this. For example, highlighting may be performed by changing the color in the frame that is equal to or higher than the reference value, the font of characters, or adding a predetermined mark. In addition, by coloring the characters and background of the line indicating the business user whose load value is equal to or higher than the reference value, or by displaying a predetermined mark, the business user can be made a business user of another line. It may be easy to distinguish from.

Further, in the above embodiment, as one aspect of the output according to the assumed load based on the load information, an example in which the advisor management screen 61 including the load value of the assumed load is displayed on the display unit 35 has been described, but the present invention is limited to this. It is not the intention to do it. The output according to the assumed load is, for example, a mode in which data including information on the assumed load is output to an external device, a mode in which an image such as a table containing information on the assumed load is printed by a printing device as an output unit, and a mode in which the estimated load The e-mail containing the information may be sent to the e-mail address of the user of the proxy account.

Further, the system to which the data management device of the present invention can be applied is not limited to the above-mentioned management support system 1. That is, the present invention is applied to any system used by a user who holds a normal account and an administrator user of a proxy account who can access data of the normal account by making proxy settings with the normal account. Can be applied.

Although some embodiments of the present invention have been described, the scope of the present invention is not limited to the above-described embodiments, but includes the scope of the invention described in the claims and the equivalent scope thereof.
The inventions described in the claims originally attached to the application of this application are added below. The claims in the appendix are as specified in the claims originally attached to the application for this application.
[Additional Notes]
<Claim 1>
A managed data registration means for registering managed data generated in response to an input operation by each user of a plurality of accounts in a storage unit in association with the account for which the input operation has been performed.
The managed data associated with the dependent account is modified in response to an input operation by the user of the proxy account previously associated with one or more specific dependent accounts among the plurality of accounts. Proxy correction processing means and
Based on the correction history information related to the correction history of the managed data by the proxy correction processing means in a predetermined period and the managed data associated with the dependent account registered in the storage unit, the said A load information generation means that generates load information related to the assumed load of correction work by the user of the proxy account,
An output control means that causes the output unit to output according to the assumed load based on the load information.
A data management device characterized by comprising.
<Claim 2>
The surrogate account is associated with two or more of the dependent accounts.
The data management device includes a ranking means for ranking the two or more subordinate accounts according to the assumed load for each of the two or more subordinate accounts.
The data management device according to claim 1, wherein the output control means causes the output unit to output an output related to the result of the ranking by the ranking means.
<Claim 3>
The load information includes load value information indicating the magnitude of the assumed load.
The data management device according to claim 1 or 2, wherein the output control means causes the output unit to output an output according to the load value.
<Claim 4>
The claim is characterized in that, when the load value exceeds a predetermined reference value, the output control means causes the output unit to perform a predetermined output indicating that the load value exceeds the reference value. Item 3. The data management device according to item 3.
<Claim 5>
A task registration means for registering task information related to a task to be performed by each user of the plurality of accounts in the storage unit in association with each of the plurality of accounts is provided.
When the load value exceeds the reference value, the task registration means registers the correction task information related to the task for the correction work in the storage unit in association with the proxy account.
The data management device according to claim 4, wherein the output control means causes the output unit to output an output indicating a task related to the correction work based on the correction task information.
<Claim 6>
The load information generating means corresponds to the registration history information related to the registration history of the managed data by the managed data registration means in the predetermined period, the modification history information, and the dependent account registered in the storage unit. The data management device according to any one of claims 3 to 5, wherein the load value is calculated based on the attached managed data and the load information is generated.
<Claim 7>
The load information generating means modifies the number of managed data registered in association with the dependent account in the predetermined period by the proxy correction processing means in the managed data in the predetermined period. A load coefficient related to the magnitude of the load of the correction work is assigned to each of the dependent accounts according to the ratio of the number of managed data, and among the managed data associated with the dependent account, from the user of the proxy account. The data management device according to claim 6, wherein the load value is calculated by multiplying the number of managed data that has not yet been accessed by the load coefficient assigned to the dependent account.
<Claim 8>
The data management device according to claim 7, wherein the load coefficient for the dependent account can be changed according to an input operation from the user of the proxy account.
<Claim 9>
The computer installed in the data management device
A managed data registration means for registering managed data generated in response to an input operation by each user of a plurality of accounts in a storage unit in association with the account for which the input operation has been performed.
The managed data associated with the dependent account is modified in response to an input operation by the user of the proxy account previously associated with one or more specific dependent accounts among the plurality of accounts. Proxy correction processing means,
Based on the correction history information related to the correction history of the managed data by the proxy correction processing means in a predetermined period and the managed data associated with the dependent account registered in the storage unit, the said Load information generation means that generates load information related to the assumed load of correction work by the user of the proxy account,
An output control means that causes the output unit to output according to the assumed load based on the load information.
A program characterized by functioning as.

1 Management support system 2 Server (data management device)
21 CPU (managed data registration means, proxy correction processing means, load information generation means, output control means, ranking means, task registration means)
22 RAM
23 Storage unit 23a Program 23b Account setting data 23c Business data (managed data)
23d Proficiency data 23e Load data (load information)
23f Task data (task information)
3 Terminal device 34 Operation unit 35 Display unit (output unit)
50 Business display screen 50a Transaction input display screen 60 Professional display screen 70 ToDo task display screen

Claims (6)

A managed data registration means for registering managed data generated in response to an input operation by each user of a plurality of accounts in a storage unit in association with the account for which the input operation has been performed.
The managed data associated with the dependent account is modified in response to an input operation by the user of the proxy account previously associated with one or more specific dependent accounts among the plurality of accounts. Proxy correction processing means and
Based on the correction history information related to the correction history of the managed data by the proxy correction processing means in a predetermined period and the managed data associated with the dependent account registered in the storage unit, the said A load information generation means that generates load information related to the assumed load of correction work by the user of the proxy account,
An output control means that causes the output unit to output according to the assumed load based on the load information.
A task registration means for registering task information related to a task to be performed by each user of the plurality of accounts in the storage unit in association with each of the plurality of accounts.
With
The load information includes load value information indicating the magnitude of the assumed load.
When the load value exceeds a predetermined reference value, the task registration means registers the correction task information related to the task for the correction work in the storage unit in association with the proxy account.
Based on the correction task information, the output control means causes the output unit to output an output indicating a task related to the correction work.
A data management device characterized by this. The surrogate account is associated with two or more of the dependent accounts.
The data management device includes a ranking means for ranking the two or more subordinate accounts according to the assumed load for each of the two or more subordinate accounts.
The output control means causes the output unit to output an output related to the result of the ranking by the ranking means .
The data management device according to claim 1. The load information generating means corresponds to the registration history information related to the registration history of the managed data by the managed data registration means in the predetermined period, the modification history information, and the dependent account registered in the storage unit. The load value is calculated based on the attached managed data to generate the load information.
The data management device according to claim 1 or 2. The load information generating means modifies the number of managed data registered in association with the dependent account in the predetermined period by the proxy correction processing means in the managed data in the predetermined period. A load coefficient related to the magnitude of the load of the correction work is assigned to each of the dependent accounts according to the ratio of the number of managed data, and among the managed data associated with the dependent account, from the user of the proxy account. The load value is calculated by multiplying the number of managed data that has not yet been accessed by the load coefficient assigned to the dependent account.
The data management device according to any one of claims 1 to 3, wherein the data management device is characterized by the above. The load factor for the dependent account can be changed according to an input operation from the user of the surrogate account.
The data management device according to claim 4. The computer installed in the data management device
A managed data registration means for registering managed data generated in response to an input operation by each user of a plurality of accounts in a storage unit in association with the account for which the input operation has been performed.
The managed data associated with the dependent account is modified in response to an input operation by the user of the proxy account previously associated with one or more specific dependent accounts among the plurality of accounts. Proxy correction processing means,
Based on the correction history information related to the correction history of the managed data by the proxy correction processing means in a predetermined period and the managed data associated with the dependent account registered in the storage unit, the said Load information generation means that generates load information related to the assumed load of correction work by the user of the proxy account,
An output control means that causes the output unit to output according to the assumed load based on the load information.
A task registration means for registering task information related to a task to be performed by each user of the plurality of accounts in the storage unit in association with each of the plurality of accounts.
To function as
The load information includes load value information indicating the magnitude of the assumed load.
When the load value exceeds a predetermined reference value, the task registration means registers the correction task information related to the task for the correction work in the storage unit in association with the proxy account.
Based on the correction task information, the output control means causes the output unit to output an output indicating a task related to the correction work.
A program characterized by that.

Images