JP7449708B2 - Business management system - Google Patents

Description

The present invention relates to a business management system for managing corporate business and a program therefor.

In recent years, as the need for work style reform has been called out, an increasing number of companies are introducing RPA (Robotic Process Automation) as a means to streamline operations. However, when trying to automate and improve the efficiency of business management systems using RPA, generating RPA definition information requires expert consulting and user familiarization, making RPA a familiar tool. I cannot go so far as to say that it has.

In addition, as a negative effect caused by the introduction of RPA, each user creates half-finished RPA definition information, etc., but it is not managed properly, and so-called stray RPA spreads and overwhelms the capacity of storage devices. There is a problem in that automatic programs run without proper processing, causing problems in business operations, and it is desired to properly manage RPA programs and definition information.

For example, in Patent Document 1, the problem is to detect what should be automated from daily computer operations and automatically generate software robot definition information for automation. an operation history detection and recording section that records the operations performed by a human as an operation history in a storage section; an operation source identification section that determines whether the recorded operation was performed by a software robot or a human; In the case of operations, the operation content comparison unit searches for repeated similar operations by comparing the operation history of the relevant location with the operation history recorded in the past, and similar operations were repeatedly performed over and over again. In this case, a software robot definition information generation system is disclosed that includes a software robot definition information generation unit that generates software robot definition information based on the operation history of the corresponding location.

Furthermore, in Patent Document 2, the problem is to appropriately maintain and manage software robots, and an acquisition unit that acquires availability information including information on availability of applications or information on availability of access destinations, and software A detection unit that detects an operation of the robot, an application executed by the software robot based on the detection of the operation of the software robot, an access destination of the application, and definition information indicating processing content using the application. A management system is disclosed that includes a determination unit that determines whether or not a software robot is being managed based on the associated operation information and the availability information.

Japanese Patent Application Publication No. 2019-169044 JP2019-168945A

However, in the software robot definition information generation system of Patent Document 1, software robot definition information (RPA definition information) is automatically generated by comparing user operation histories, but after accumulating a large number of operation histories, Unless it is executed, the necessary definition information will not be generated, and even if a software robot is introduced, it will not immediately help improve business efficiency.

In addition, the management system of Patent Document 2 performs appropriate maintenance and management of software, such as omission of updates for managed software, and the business management system can be used efficiently and widely by introducing RPA. However, no consideration has been taken to prevent the spread of unnecessary definition files.

In view of the above circumstances, it is an object of the present invention to improve business efficiency by making it easier to introduce and use RPA tools in a business management system. Furthermore, it is an object of the present invention to appropriately manage RPA tools and RPA definition information linked to a business management system.

In order to achieve the above object, a business management system according to an embodiment of the present invention includes a plurality of business devices each having a business management program installed therein for managing the business of a company, and a business management system in which the business management program in the business device is installed. and a business management device that manages execution. Among the plurality of business devices, at least the plurality of business devices for administrators store an RPA (Robotic Process Automation) tool and RPA definition information that defines processing content using the RPA tool. The business management device includes a first control unit including an RPA execution determination unit that determines whether RPA definition information of the RPA tool of the administrator business device can be executed, depending on a state of the business management program. The plurality of business devices have a second control section including an RPA execution control section that executes the RPA tool according to the determination result of the RPA execution determination section.

According to this configuration, the security of the business management system can be guaranteed from the status of the business management program, and even if the administrator is absent, other administrators can use the RPA tool to execute RPA definition information on their behalf. Therefore, the use of RPA improves business efficiency.

The business management device may store operation authority condition information that is linked to login ID information for each employee including the administrator and indicates each employee's operation authority regarding execution of the RPA tool. In this case, the RPA execution determination unit determines whether or not the RPA definition information of each of the RPA tools can be executed, according to the operation authority condition information and the status information of the employee or the company in the business management program. It's okay.

According to this configuration, appropriate management of the RPA tool can be performed based on the operating authority conditions and the employee or company status information in the business management program. Status information includes the status of employees who have logged in with their IDs, such as their attendance at work, attendance, etc. (whether they are alone in the room, etc.), normal times/end of term (busy season), before and after the general meeting of shareholders, individual abilities (qualifications or not), etc. It is.

The operating authority condition information may include operating authority condition information indicating limited operating authority for the business program using the proxy-only ID. In this case, the first control unit determines that the administrator starts the business management program using the proxy-only ID, and that the RPA execution determination unit determines that the administrator can execute the RPA tool. In this case, the system has an ID authority control unit that stores RPA definition information indicating the operation of the RPA tool by the administrator using the representative ID in association with the restrictive operation authority condition information. Good too.

According to this configuration, the administrator can automatically execute the RPA definition information of the RPA tool operated by the administrator logged in with the proxy-only ID in a limited manner, making it easy for the administrator to check and select the appropriate RPA tool. Can be managed. In addition, since the procedure for changing RPA definition information based on the operations of one administrator to RPA definition information based on the operations of another administrator is automated, the frequency and range of use of RPA tools is expanded, and the effectiveness of RPA tools is increased. It will be put to good use. This makes it easier to introduce and use RPA tools and improves business efficiency.

The ID authority control unit stores the RPA definition information stored when one administrator executes the RPA tool based on the operation authority condition information, and allows another administrator to use a proxy ID for the first administrator. The information may be stored in association with the login ID information of the other administrator so that the information can be operated using the .

According to this configuration, other administrators can automatically execute the RPA definition information created by one administrator in a limited manner, making it easier for other administrators to perform work on their behalf, making it easier to introduce and use RPA tools. This will improve work efficiency.

The business management program may be a work management or room entry management application.

According to this configuration, RPA definition information can be executed on behalf of the administrator using the RPA tool according to the administrator's work status or entry status, so the status of the administrator's absence or the status of the work place can be confirmed. Appropriate RPA tool management can be performed.

A business management program according to another embodiment of the present invention includes a business management program that includes:
a step of starting an RPA tool;
a step of reading RPA definition information that defines processing content using the RPA tool;
acquiring a determination result of whether or not the RPA definition information can be executed, determined according to the state of the business management program;
and executing the RPA tool according to the determination result.

As described above, according to the present invention, RPA tools can be easily introduced and used in a business management system, thereby improving business efficiency.

Further, according to the present invention, RPA tools and RPA definition information linked to a business management system can be appropriately managed. However, these effects do not limit the present invention.

1 is a configuration diagram of a business management system according to an embodiment of the present invention. FIG. 1 is a configuration diagram of a business management device and a business device according to an embodiment of the present invention. It is an explanatory diagram of login ID information concerning an embodiment of the present invention. FIG. 3 is an explanatory diagram of operation authority conditions according to the embodiment of the present invention. FIG. 2 is an explanatory diagram of transaction information and RPA determination levels according to an embodiment of the present invention. FIG. 3 is a flow diagram of RPA execution determination according to an embodiment of the present invention. FIG. 2 is an explanatory diagram of the operating state of the RPA tool according to the embodiment of the present invention. FIG. 2 is an explanatory diagram of the operating state of the RPA tool according to the embodiment of the present invention. FIG. 3 is a diagram showing an example of printing a weekly report form created by the RPA tool according to the embodiment of the present invention.

Embodiments of the present invention will be described below with reference to the drawings. Although the following embodiments are preferred specific examples of the present invention and disclose various preferred techniques, the technical scope of the present invention is not limited to these aspects.

[Business management system configuration]
FIG. 1 is a configuration diagram of a business management system according to an embodiment of the present invention.

As shown in the figure, the business management system is constructed within a company and includes a business management device 100 (server), an administrator's business devices 200 (A-C), and employee business devices 200 (D, E). ...), which are communicably connected via a network 50 (for example, an in-house LAN).

A business management system is a business management system that mainly processes corporate business such as personnel, employment, and payroll. A business management program is stored in advance in each business device 200 of the employee.

The business devices 200 of employees who have authority as a main administrator and a sub-administrator (hereinafter referred to simply as both administrators) have various business management programs such as personnel, employment, and payroll installed on them. The person's business device 200 has at least a business management program such as work installed therein. Of course, business applications necessary for each job of each employee, such as an office suite, a browser, and CAD (Computer-Aided Design), are stored as appropriate.

Further, the business device 200 of an employee who has administrator authority stores an RPA tool and RPA definition information that defines the processing content using the RPA tool.

RPA is software that automates the work that humans mainly do using computers, and is also called a software robot. In this embodiment, we will introduce a ready-made software robot application to automate business processes. It is called RPA tool.

The administrator's business device 200 is, for example, a desktop-type PC (Personal Computer), and the employee's business device 200 includes a so-called PDA (Personal Computer) such as a notebook PC, a tablet, or a smartphone, in addition to the above-mentioned desktop-type PC. Digital Assistance) is also included.

In addition, administrators include the main administrator who is the so-called department head who manages business in each department, the deputy administrator who assists the main administrator, the administrator of the human resources department who is in charge of human resources, payroll, etc. This includes system administrators who are in charge of internal networks.

[Configuration of business management device and business device]
FIG. 2 is a diagram showing the configuration of the business management device 100 and the business device 200.

As shown in the figure, the business management device 200 includes a control unit 11 (CPU; Central Processing Unit), a storage unit 12 (HDD (Hard Disk Drive), RAM (Random Access Memory), ROM (Read Only Memory), etc. 200), and a communication interface 13, which is composed of, for example, an NIC (Network Interface Card) or a wireless communication interface, and is responsible for communication processing with the business device 200. Further, the business management device 200 may include a display device and an input device as appropriate.

The control unit 11 of the business management device 100 includes an ID authority control unit 111, an RPA execution determination unit 112, and a determination level control unit 113 as functional modules.

The ID authority control unit 111 manages and determines whether another administrator can perform work on a certain administrator's RPA tool on the basis of operation authority condition information, which will be described later.

The RPA execution determination unit 112 determines whether RPA definition information of an RPA (Robotic Process Automation) tool possessed by the administrator's business device 200 can be executed, depending on the state of the business management program installed in the business device 200.

The judgment level control unit 113 changes the executable level (RPA judgment level) according to the state of the target business management program, management tool, etc. when executing or recording RPA definition information of the RPA tool. and set it.

The storage unit 12 also stores login ID information 121, operation authority condition information 122, employee master information 123, master authority information 124, transaction information 125, and execution log information 126. Details of each piece of information will be described later.

The business device 200 includes a control unit 21 (CPU), a storage unit 22 (database composed of HDD, RAM, ROM, etc.), a communication interface 23 consisting of, for example, a NIC or a wireless communication interface, and a display device 24 (for example, a liquid crystal display). display, organic EL display, etc.) and an input device 25 (mouse, touch panel, etc.).

The storage unit 22 stores the RPA tool 221, a plurality of RPA definition information 222, and a plurality of business management programs 223. Examples of the individual work management programs 223 include a work management program, an entry management program, a personnel management program, a salary management program, etc., and the RPA definition information 222 includes information for each work management program and each work management program. It is stored for each different task used.

Further, among the business devices 200, the business devices 200 (AC) particularly for administrators include an RPA execution control unit 211 and a definition conversion control unit 212 as functional modules of the control unit 21.

The RPA execution control unit 211 executes the RPA tool 221 according to the determination result of the RPA execution determination unit 111.

The definition conversion control unit 212 can convert the RPA definition information 222 depending on the difference in hardware (mouse, touch panel, display, etc.) used by the user for operation.

The business management device 100 and the business device 200 are communicably connected via communication interfaces 13 and 23 with each other. As shown in FIG. 1, there are a plurality of business devices 200, among which there are a plurality of business devices 200 for administrators, and a large number of business devices 200 for employees are also connected to the network 50. The detailed configuration of other business devices 200 will be omitted.

[Login ID information]
FIG. 3 is an explanatory diagram of the login ID information 121 according to the present embodiment.

As mentioned above, login IDs are assigned to administrators, sub-administrators, and employees individually, and the login IDs are used for various programs and tools (PR1,...PR4, RPA execution) in the business management device 100. , RPA recording).

Further, authentication data (password, etc.) is linked to each login ID. The authentication data may be the same as that stored in the employee master information 123. Additionally, a login ID in which license information for a plurality of business management programs 223 is set is also stored.

Each login ID is associated with information indicating the scope of management of the employee by the administrator (whether or not the administrator can perform alternative work or view data on behalf of the employee). For example, a main manager includes all employees in his/her management scope, but a sub-manager's management scope is limited to excluding the main manager.

Here, whether or not the RPA tool 221 can perform the proxy work is ultimately determined by the ID authority control unit 111 based on operation authority condition information 122, which will be described later. Basically, the administrator is not only able to perform work on behalf of the target users registered in the management scope, but also execute the business management program 223 using the RPA definition information 222 in the main administrator's RPA tool 221, for example. etc., can be carried out by the sub-administrator to a limited extent. The present embodiment is devised so that the sub-administrator can also record the operation history by using the proxy-only ID (Z). The function of the proxy-only ID will be described later.

[Operation authority condition information]
FIG. 4 is an explanatory diagram of the operation authority condition information 122 according to the present embodiment.

The operation authority condition information 122 indicates the limited operation authority of the business program 223 using the proxy-only ID, and indicates the type of business management program or business management program that can perform proxy actions using the proxy-only ID. Operation details are registered. As shown in the figure, the operating authority regarding the RPA tool 22 is also set as this operating authority condition.

On the other hand, each business management program 223 is allowed to be operated by a proxy ID depending on the management range of the login ID described above. Therefore, it can be said that the management scope of the login ID is a constant and unchanging operational authority condition for employees, which is the management scope of each administrator.

For simplicity, it is assumed that there is one main administrator in this case. Further, although there is one sub-administrator and one system administrator, there may be many employees. The operation authority conditions include not only the authority to record and execute the RPA definition information 222 of the RPA tool 221 according to the hierarchy such as the main administrator, sub-administrator, and employee, but also the operation authority condition by a substitute. It is set. Further, among the operating authority conditions for a proxy, more limited operating authority conditions are also set for, for example, a system administrator or an employee who is not an administrator. Details of the operating authority conditions for the proxy will be described later.

[Transaction information and RPA judgment level]
FIG. 5 is an explanatory diagram of the transaction information 125 and RPA determination level of the business management program 223 according to this embodiment.

The RPA judgment level is based on the status of the target business management program 223 or management tool when executing or recording the RPA definition information 222 of the RPA tool 221, i.e., the state of the business management program 223 or the management tool, that is, the company, employee, etc. The executable level is set by changing the executable level according to the status information (transaction information 125). For example, level 3 is the most severe restriction state, and level 1 is the most relaxed restriction state.

Each of the business management programs 223 has strict restrictions during normal times, but the restrictions are relaxed during busy periods, for example. This does not mean the level of restriction on the execution content of each business management program 223 itself, but the level of restriction on the execution and recording of the business management program 223 using the RPA tool 22.

As shown in the figure, the details of the transaction information 125 (status information) include the manager's attendance and departure, location (room), beginning/end of term, closing date, end of the year, and timing such as after the general meeting of shareholders. In addition to these, for example, the manager's individual abilities (qualifications, etc.), occupancy status (whether alone or with other employees), etc. may be used as status information. .

[Operation of business management system]
Next, the operation of the business management system configured as above will be explained. In the following explanation, the control unit 11 of the business management device 100 and the control unit 21 of the business device 200 will be explained as the main operating entities, but the operation will be performed by the control program included in the business management device 100 and the control unit 21 of the business device 200. It is executed in cooperation with the business management program and other programs installed on the computer.

FIG. 6 is a flow diagram of RPA execution determination processing according to this embodiment. Furthermore, FIGS. 7 and 8 are explanatory diagrams of the operating state of the RPA tool according to the present embodiment. As an example, a state in which a work management program of a work management application is operated will be described. In this embodiment, a so-called ERP (Enterprise Resources Planning) type business program package is shown in which a work management program, an entry management program, a salary management program, and other accounting programs (not shown) can be operated in an integrated manner. There is.

As shown in FIG. 6, the control unit 21 of the business device 200 first receives an operation from a user (for example, a substitute administrator such as a deputy administrator) to start the execution/recording of the business management program 223 by the RPA tool 221 ( Step S1).

For example, as shown in 1) of FIG. 7, a proxy administrator performs a login operation to the work management program on the login screen 71 displayed on the display device 24 of the business device 200. The startup button 72 of the RPA tool 221 is embedded, for example, in the task bar at the bottom of the screen, and when the proxy administrator presses it, the login screen 71 is displayed.

Note that the RPA tool 221 may be activated before logging in, and the employment management program may be activated by selecting the employment management program from the business management programs 223 linked to the activated RPA tool 221. If the RPA tool 221 is linked only to the employment management program, the screen 1) in FIG. 7 is automatically transitioned to when the RPA tool 221 is started.

As shown in 2) of FIG. 7, in this example, the proxy administrator enters the ID of the proxy Z on the login screen 71 and performs a login operation.

Then, as shown in FIG. 3), an input instruction dialog 73 is displayed that requests the input of the personal ID and password of the proxy administrator who will perform the proxy operation.

In response to this, as shown in FIG. 4), when the proxy administrator enters a personal ID and password and performs a login operation, the control unit 21 requests the business management device 100 to inquire about ID authority conditions. (Step S2 in FIG. 6). At this time, the ID and password at the time of logging in to the business device 200 may be inherited as they are, and in that case, the input shown in 4) of FIG. 7 is skipped. The ID authority condition inquiry request includes the proxy-only ID and the personal ID of the proxy administrator.

When inquiring about the ID authority conditions, the proxy administrator performs a proxy authority designation operation on the proxy authority designation screen 81 as shown in 1) of FIG. In this case, based on the login information as a sub-administrator, the employees within the scope of management and the department head to whom they belong are displayed in a list, but the department head can select, and the employees under other scope of management are displayed in a list. The person cannot choose.

Returning to FIG. 6, when the control unit 11 of the business management device 100 receives the above-mentioned ID authority condition inquiry request, the ID authority control unit 111 sends the above-mentioned proxy-only ID and the personal information of the proxy administrator who requested the operation by the proxy. Based on the ID, proxy target user information that enables proxy operations is acquired (step S21). In this case, all employees included in the management range of the proxy-only ID fall under this category. However, based on the operation authority condition information 122 shown in FIG. 4, the substitute operation authority is granted to the sub-administrator in the absence of the main administrator, so the sub-administrator selects the operation of the main administrator. It is now possible.

Here, the definition conversion control unit 212 may convert the RPA definition information 222 and call the business management program 223 according to the contents. Note that the definition conversion control unit 212 is capable of converting the RPA definition information 222 depending on the difference in hardware used by the user for operation, but the conversion process is particularly difficult in the case of business devices with the same specifications. Not performed.

Next, the control unit 11 uses the RPA execution determination unit 112 to obtain the access authority to the business management program 223, the RPA definition information 222 of the RPA tool 221, etc. by referring to the operation authority condition information 122 granted to the proxy target user. Then, it further accesses the transaction information 125, executes the RPA determination level determination process based on the operation authority condition information 122, and transmits the determination result to the business device 200 (step S22).

When the control unit 21 of the business device 200 receives the determination result regarding the operation authority condition (step S3), it determines whether the determination result is executable, limitedly executable, or not executable (step S4). .

If execution is not possible, the control unit 21 displays a message to that effect on the display device 24, and ends the process.

If it is possible to execute the program in a limited manner, the control unit 21 sets the content of limitations (for example, the type of business management program, business management program operation, etc.) (step S5). In this case, the set limited content may be displayed on the display device 24 and notified to the proxy target user.

If it is executable and if the setting of the above-mentioned limitation contents is completed, the control unit 21 starts the RPA tool (step S5).

In this case, a confirmation dialog 82 indicating the details of the operating authority as shown in FIG. 8 (2) is displayed on the display device 24, and then the login to the work management program is executed.

Returning to FIG. 6, when the RPA execution control unit 211 detects a new business management program 223 to be executed by the RPA tool (for example, employment/entering/payroll/personnel program) (step S6), the RPA execution control unit 211 detects a new business management program 223 to be executed by the RPA tool (step S6). The RPA determination level set for the transaction is inquired of the business management device 100 (step S7).

Upon receiving the inquiry about the RPA judgment level, the judgment level control unit 113 of the business management device 100 reads the current transaction information 125 of the business management program that is the subject of the inquiry.

Then, the determination level control unit 113 of the business management device 100 refers to the transaction information 125, determines the level of the business management program 223 to be inquired that is set according to the transaction information (step S23), and sets the determined level to The information shown is returned to the business device 200.

Upon receiving the judgment level information (step S8), the RPA execution control unit 211 sets the judgment level in the target business management program 223 (step S9).

The RPA execution control unit 211 repeats the determination level setting process in S7 to S9 each time a new business management program is detected.

Then, when the proxy administrator instructs the RPA tool 221 to terminate (YES in step S10), the RPA execution control unit 211 sends the execution log of the business management program 223 by the RPA tool 221 up to that point to the business management device 100. At the same time (step S11), it is recorded as new RPA definition information 222, and the RPA tool 221 is stopped (step S13).

When the business management device 100 receives the execution log, it records it in the database as execution log information 126 (step 24).

The automatic execution processing of the business management program 223 by the RPA tool 221 is shown in 3) and subsequent parts of FIG. Further, FIG. 9 shows an example of printing a weekly work report created by the RPA tool 221.

3) in the same figure shows a state in which the RPA tool 221 selects the employment management program from among the business management programs 223 using the menu button 84 from the business management program selection screen 83, and furthermore, the RPA tool 212 selects the employment management program This shows a state in which "daily/weekly processing" is selected from a task menu (not shown) and then weekly work report processing is selected from the list in the task area 85.

Subsequently, as shown in FIG. 4), the RPA tool 221 selects the department and individual to be subjected to the weekly work report creation process from the individual specification dialog 86 superimposed on the task area 85.

Then, as shown in FIG. 9, the weekly work report of the RPA tool 221 is displayed and printed.

The RPA tool 221 either finishes the process or returns to the selection of another employee and repeats the print process in the same way. When the process is finished, the delegated administrator clicks the RPA tool on the task bar shown in 1) in FIG. From the tool start button 72, the RPA tool 221 is terminated.

In this way, the RPA tool 221 of this example performs the printing process of the weekly work report of the affiliated employee, which is normally performed by the main manager, on behalf of the sub-manager. Assume that on this day, the main administrator was on a long vacation due to personal business.

As described above, the RPA tool 221 in this case sequentially records the operation status on behalf of the sub-administrator as RPA definition information 222, and after the operation is completed, the entire operation is recorded as the generated RPA definition information 222 on the business management device. 100 and record it. Here, the RPA definition information 222 is not stored in the business device 200 of the sub-administrator.

In addition, in the execution log information 126, when the operation by the proxy is completed, the fact that the sub-administrator performed the process using the proxy-only ID and the content of the work are recorded in a limited manner.

In this way, the target user (main administrator) who has been processed by the proxy can verify the work results of the deputy administrator using the proxy-only ID, and can manage the business from the RPA tool 221. Calls the program 223, extracts and reads the RPA definition information 222 recorded by the sub-administrator from the execution log data that records the proxy work, executes the business management program again according to the contents, and checks and verifies the operation status. I can do it.

That is, in this case, the ID authority control unit 111 causes the administrator to start the business management program 223 using the proxy-only ID, and causes the RPA execution determination unit 112 to cause the administrator to execute the RPA tool 221. If it is determined that the RPA tool 221 is operated by the administrator using the proxy ID, RPA definition information 222 is stored in association with the restrictive operation authority condition information 122. .

Note that the operational authority/reference authority of the proxy-only ID is limited in advance within the scope of the operational authority/reference authority held by the sub-administrator, and the restriction is applied to the transaction information 125 of the main administrator (specifically, A feature of this embodiment is that the status changes depending on the employment situation, the status of being absent, and that an application for long-term leave has been accepted.

Therefore, according to this embodiment, the RPA tool can be easily introduced and used in the business management system, and business efficiency can be improved.

Furthermore, according to this embodiment, the RPA tool and RPA definition information 222 connected to the business management system can be appropriately managed.

[Modified example]
The present invention is not limited to the above-described embodiments, and may be modified in various ways without departing from the gist of the present invention.

[Other Examples]
Utilizing the present invention, RPA definition information 222 may be stored in the business management device 100 using the RPA tool 221, such as monthly tasks normally performed by the main administrator. Such RPA definition information 222 is normally restricted so that it cannot be read or manipulated even by a sub-administrator. However, when the main administrator is absent and the sub-administrator has to carry out business processing on his/her behalf without knowing the details of the process, the main administrator's transaction information 125 (employment information) must be referred to, and special In the case of a long vacation or the like due to circumstances, it is also effective to relax the restriction information on proxy operations based on that information and to enable execution of the target RPA definition information 222.

That is, the ID authority control unit 111 allows another administrator to manage the RPA definition information 222 stored by one administrator executing the RPA tool 221 based on the operation authority condition information 122. The information may be stored in association with the login ID information of the other administrator so that the administrator can operate using the proxy ID.

In this case, it is possible not only to share the RPA definition information 222 or to execute the RPA tool 221 using the RPA definition information 222 only with information that the main administrator is absent, but also to enable transactions in the work management program 223. By changing the restrictions according to the state of the information 125, the RPA tool 221 can be used effectively, the execution of unauthorized RPA tools 221 can be prohibited, the RPA definition information 222 can be thoroughly managed, and administrators such as stray RPA can It is possible to suppress phenomena such as the spread of absent RPA definition information 222.

[Other additional matters]
The business management device 100 may be configured to change the operation authority condition information 122 based on a combination of transaction information 125 of a plurality of business management programs 223. For example, the transaction information 125 of the room entry management program may enable the operation of the business management program 223 that handles confidential information in a specific private room.

Further, a software robot different from the RPA tool 221 may automatically determine the operator and set the operation authority condition information 122.

Furthermore, when there are a wide variety of combinations of the operation authority condition information 122, it is also effective to utilize deep learning technology using big data to determine the RPA determination level.

It is also possible to combine at least two of the characteristic parts according to the present invention described above. That is, the various characteristic portions described in each embodiment may be arbitrarily combined without distinction between each embodiment. Further, the various effects described above are merely examples and are not limited, and other effects may also be exhibited.

Furthermore, the present invention can be modified as appropriate within the scope or spirit of the invention that can be read from the claims and the specification as a whole, and a business management system that involves such modifications may also be modified without departing from the technical spirit of the present invention. include.

The technology of the present invention can be suitably used in a business management system that performs corporate business processes such as personnel affairs, employment, and payroll.

11, 21...Control units 12, 22...Storage units 13, 23...Communication interface 24...Display device 25...Input device 50...Network 71...Login screen 72...RPA tool start button 73...Input instruction dialog 81...Delegation authority specification screen 82...Confirmation dialog 83...Business management program selection screen 84...Menu button 85...Task area 86...Personal specification dialog 100...Business management device 111...ID authority control section 112...RPA execution judgment section 113...Judgment level control section 121...Login ID information 122...operation authority condition information 123...employee master information 124...master authority information 125...transaction information 126...execution log information 200...business device 211...RPA execution control unit 212...definition conversion control unit 221...RPA tool 222... RPA definition information 223...Business management program

Claims (4)

Multiple business devices, each with a business management program installed to manage the company's business,
a business management device that manages execution of the business management program in the business device;
Among the plurality of business devices, at least the plurality of business devices for administrators include an RPA (Robotic Process Automation) tool and RPA definition information that defines processing contents using the RPA tool for each of the business management programs. remember and
The business management device includes:
a first control unit including an RPA execution determination unit that determines whether RPA definition information of the RPA tool of the administrator business device is executable according to a state of the business management program;
Stores status information indicating the current status of employees including managers or the company, and the status information includes the qualifications of the employee requesting execution of the business management program, and the attendance of the manager of the employee. including information regarding the status or whether the business is in a busy season;
When the RPA execution determination unit receives a request for execution of the RPA tool by the employee from any of the business devices, the RPA execution determination unit acquires RPA definition information of the RPA tool from the business device, and executes the RPA definition information and the RPA definition information. Based on the status information at the time of the execution request, setting a determination level for restricting execution situations of the RPA tool, and determining whether or not the execution is possible based on the determination level;
The plurality of business devices receive the determination result of the RPA execution determination unit and information indicating the determination level from the business management device , and when the determination result is executable, execute the RPA tool according to the determination level. A business management system having a second control unit having an RPA execution control unit for execution. Multiple business devices, each with a business management program installed to manage the company's business,
a business management device that manages execution of the business management program in the business device;
equipped with
At least a business device for an administrator among the plurality of business devices stores an RPA (Robotic Process Automation) tool and RPA definition information that defines processing contents using the RPA tool for each of the business management programs,
The business management device includes:
a first control unit including an RPA execution determination unit that determines whether RPA definition information of the RPA tool of the administrator business device is executable according to a state of the business management program;
The plurality of business devices receive information indicating the determination result of the RPA execution determination unit from the business management device, and have a second RPA execution control unit that executes the RPA tool when the determination result is executable. has a control section,
The business management device stores operational authority condition information that is linked to login ID information for each employee including the administrator and indicates operational authority for each employee regarding execution of the RPA tool,
When the RPA execution determination unit receives a request for execution of the RPA tool by the employee from any of the business devices, the RPA execution determination unit acquires RPA definition information of the RPA tool from the business device, and executes the RPA definition information and the RPA definition information. Based on the operation authority condition information, determining whether or not the RPA definition information of the RPA tool can be executed according to the operation authority condition information granted to the employee who requested the execution request ;
The operating authority condition information includes information indicating limited operating authority of the business management program using a proxy-only ID,
The first control unit receives information from the business device indicating that the administrator has started the business management program using the proxy-only ID, and the RPA execution determination unit When it is determined that the RPA tool is executable, the administrator receives RPA definition information indicating a log of the operation of the RPA tool using the proxy ID from the business device, and applies the RPA definition information to the restriction. The ID authority control unit further includes an ID authority control unit that stores operation authority condition information in association with operation authority condition information indicating operational authority.
Business management system. The business management system according to claim 2 ,
The ID authority control unit may store RPA definition information stored when one administrator executes the RPA tool based on the operation authority condition information, so that another administrator can use a representative ID for the one administrator. A business management system that stores login ID information in association with the other administrator's login ID information so that it can be operated using. A business management system according to any one of claims 1 to 3 ,
The business management program is a business management system that is a work management or room entry management application.

Images