JP2009059293A - Job management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a job management system that is allowed to operate only by access authority that follows examined-approved operation procedure data. <P>SOLUTION: The access authority over the operation of the job management system is defined as operation procedure data describing an operation period, user name, target job, authority level, permission command and operation purpose. Then, the operation procedure data are associated with an operation ID that is numbered during examining-approving the operation procedure data to be managed, and the operation of the job management system is allowed only by operation authority described in the operation procedure data associated with the operation ID to be designated during operation. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a job management system for managing jobs during operation execution.

Patent document 1 is mention | raise | lifted as a well-known technical document relevant to this invention. The technique described in Patent Document 1 improves the operability of the user by defining a controlled business procedure and performing an operation according to an instruction based on the procedure for the access authority at the time of update. That's it.
JP-A-6-282560

  However, in the case of the technique described in Patent Document 1, there is no limitation on the case where the user mistakenly executes a task that has not been instructed, and therefore the system may be erroneously operated. In addition, there is a problem in that it is necessary to determine the purpose of the work from the system operation result and to determine whether the operation is in accordance with the purpose of the instruction. .

  The present invention improves the above-described problems of the prior art, and the user defines the operation procedure as operation procedure data, and operates only with the access authority with the expiration date described in the operation procedure data that has been reviewed and approved. Is allowed to prevent operations other than erroneous operations and instructions. It is also possible to provide a job management system that facilitates the determination of whether the operation content is appropriate by providing a function for simultaneously displaying operation procedure data and operation results corresponding to the operation procedure data from the operation log. Objective.

  In order to achieve the above object, a job management system of the present invention is a job management system in which a job management server and a user terminal are communicably connected via a network, and the job management server has an operation period. Associating operation procedure data composed of data related to access authority including user name, target job, authority level, and permission command, and the operation procedure data and the operation ID numbered at the time of review / approval of the operation procedure data A data storage unit that stores a database to be managed, and operation procedure data management that permits operations only with the operation authority described in the operation procedure data associated with the operation ID specified at the time of operation execution Department and preparation And wherein the Rukoto.

  According to the job management system of the present invention, according to the operation procedure data that has been reviewed and approved, the operation authority of the job management system is set in detail as the operation period, user name, target job, authority level, permission command, It is possible to prevent the system from performing erroneous operations or performing operations other than instructions.

Hereinafter, an embodiment of a job management system to which the present invention is applied will be described. First, the configuration of the job management system will be described.
As shown in FIG. 1, the job management system in this embodiment includes a job management server 11 and a plurality of user terminals 12. The job management server 11 and the plurality of user terminals 12 are connected to be communicable with each other via the Internet 13 as a network.

The job management server 11 includes an operation procedure data management unit 14, an access control unit 15, an operation result management unit 16, a display control unit 17, and a data storage unit 18.
The operation procedure data management unit 14 has a function of examining and approving operation procedure data and issuing an operation ID.
The access control unit 15 has a function of acquiring operation procedure data having a matching operation ID from information registered in the access authority DB via the operation procedure data management unit 14. The operation procedure data of the acquired operation ID is confirmed by the access control unit 15 as to whether or not the operation can be executed, and if the access authority is executable, the operation of the operation procedure data is executed. The

  The operation result management unit 16 extracts the operation procedure data and operation log information of the corresponding operation ID from the access authority DB and operation log DB connected via the operation procedure data management unit 14 and displays the operation result based on the result displayed. It has a function of confirming whether or not the result is appropriate in comparison with the contents of the operation procedure data.

The display control unit 17 has a function of causing the user terminal 12 to display the operation extraction result, the contents of operation procedure data corresponding to the operation ID, and the like.
The data storage unit 18 stores an access authority database (DB) 19 and an operation log DB 20. In the access authority DB 19, operation procedure data is registered at any time by the operation procedure data management unit 14. In the operation log DB 20, the operation result management unit 16 registers operation execution results as needed.

Next, a method for creating operation procedure data will be described. First, the operation procedure data creation screen will be described.
As shown in FIG. 2, on the operation procedure data creation screen displayed by the display control unit 17 on the user terminal 12, an item necessary for creating the operation procedure data is designated, and an examination / approval request is sent to the administrator. Do. Each item is as follows.

Applicant column 21: The user name of the user who applies the operation procedure data to the administrator is described.
[Examination / approval request] button 22... This button is pressed when executing an examination / approval request to the manager of the operation procedure data.
Operation period column 23: This is a column for inputting a period during which the contents of the operation procedure data are valid. Even an approved operation cannot be executed outside the period specified here.

User name column 24: The user name of the user who executes the operation is input. It is also possible to specify a plurality of user names at the same time.
Target job column 25: A job to be executed is input. Only one job can be specified.
Authority level column 26: An authority level at the time of data manipulation by the operation is selected. If it is “reference”, only reading of data is permitted. On the other hand, if it is “update”, reading / writing of data is permitted.

Allowed command column 27: A command to be executed when the operation is executed is input. Only one command can be specified per operation procedure data.
Operation purpose column 28: The purpose of executing the operation is entered. The administrator first confirms the purpose of the operation entered in this column, and approves it after examining whether or not the operation procedure data is appropriate to achieve the purpose.

The user presses the [examination / approval request] button 22 after inputting necessary items in the fields 21, 23 to 28 from the user terminal 12. Then, the information input in each column 21, 23 to 28 is stored as data in the data storage unit 18 of the job management server 11.
The administrator reads the data by using dedicated software, and reviews and approves the operation procedure data.

Next, the operation procedure data review / approval screen will be described. As described above, the administrator approves the operation procedure data when the content of the operation procedure data received from the user is examined and judged to be appropriate. Here, the operation ID is automatically assigned when the operation procedure data is approved.
Each item on the operation procedure data examination / approval screen shown in FIG. 3 is as follows.

Examination / approver field 31: The name of the user who conducts the examination / approval is displayed. Administrators or specially authorized users can review and approve operational procedure data.
Unapproved list column 32: A list of operation procedure data for which examination / approval has not been completed among the operation procedure data for which examination / approval has been requested is displayed.
[Display] button 33... When this button is pressed, the contents of operation procedure data that have been requested for examination / approval but have not been examined are displayed.
Management ID column 34: An ID uniquely assigned to each job management system for managing the operation procedure data is displayed.

Applicant [examination request date and time] column 35 ... The user name of the applicant and the examination request date and time are displayed.
Operation procedure data column 36: The contents of the requested operation procedure data are displayed. However, the operation ID is not issued because examination / approval is not completed.
[Examination / approval] button 37... When this button is pressed, the displayed operation procedure data is examined and approved, and an operation ID is issued. Only operations approved here can be executed.

Next, a confirmation screen for approved operation procedure data will be described. The confirmation screen can be viewed by an administrator or a specially authorized user from the user terminal 12 or the like using dedicated display software. On the confirmation screen, the operation ID and access authority of the approved operation procedure data are confirmed.
Each item on the confirmation screen of the approved operation procedure data shown in FIG. 4 is as follows.

Approved list column 41: A list of approved operation procedure data is displayed. The format of the displayed content is “management ID [operation ID]”.
[Display] button 42: When the button is pressed, the contents of the approved operation procedure data are displayed.
Management ID column 43: An ID automatically assigned for managing the operation procedure data is displayed.

Applicant [examination request date and time] column 44: The user name of the applicant and the examination request date and time are displayed.
Examination / approver [examination / approval date / time] column 45: The user name of the examination / approval and the examination / approval date / time are displayed.
Operation procedure data column 46: Displays the contents of the approved operation procedure data. Since examination / approval has already been completed, the corresponding operation ID is also displayed.

Next, an operation result log display screen will be described. On this screen, it is possible to check a log that is a result of an investigation of an operation executed by the user. Specifically, the contents of the operation procedure data corresponding to the operation ID and the execution result are displayed by the display control unit 17.
Each item on the operation result log display screen shown in FIG. 5 is as follows.

Operation ID (required) column 51: This is a column for inputting an operation ID used as a search key when searching operation procedure data and an operation log. Since operation procedure data corresponding to the operation ID is searched, it is essential to enter the operation ID.
Display period (arbitrary) column 52: This is a column for inputting a period for searching the operation log when the operation ID is extracted from the entire operation log. The display period can be input arbitrarily, and if it is not input, the entire operation log is searched.
User name (arbitrary) column 53 is a column for inputting a user name for further extraction by the user from the search result extracted by the operation ID from the operation log. The input of the user name is arbitrary, and if it is not input, the operation ID is displayed for the logs of all users to which the operation ID corresponds.

[Display] button 54: When this button is pressed, the contents of the operation procedure data and the output result of the extracted operation log are displayed based on each information (51 to 53) of the input search setting. Is done.
Operation procedure data column 55: Displays the contents of the operation procedure data corresponding to the operation ID designated as the search key.
Operation log list field 56: Displays the log results extracted from the operation log according to the input search settings.

Next, an example of console screen output and operation log output during operation execution will be described.
As shown in FIG. 6, when an operation is executed, it is necessary to specify an operation ID as shown in operations 61 to 63. In addition, the operation log at the time of operation execution is a log 64 for the operation 61 due to a normal termination operation, a log 65 for an abnormal termination operation 62 due to an operation without an operation ID, and an abnormal termination due to an operation outside the operation period. Is output like a log 66 for the operation 63.

  If access authority is granted as in operation 61, the operation is executed. If access authority is not granted as in operation 62 or operation 63, an error message is displayed when the operation is executed, and the operation is executed. It is controlled so that it cannot be executed.

Next, an access authority table constituting the access authority DB 19 will be described.
As shown in FIG. 7, the access authority table constituting the access authority DB 19 includes a user operation management table 71, an operation ID management table 72, a review / approver management table 73, and an operation procedure data management table 74.
The timing when each table is updated and the value is registered is as follows.

・ When the [Examination / Approval Request] button 22 (FIG. 2) is pressed: The management number newly assigned to the operation procedure data management table 74, the applicant listed in the applicant column 21, the application date and time, and the operation The start date and end date and time, authority level, permission command, target job, and operation purpose information described in the period column 23 are registered. Further, the user name in the user name column 24 and the management ID of the operation procedure data management table 74 are registered in the user name and management ID of the user operation management table 71, respectively, and the management ID of the operation procedure data management table 74 is the operation ID. Also registered in the management ID of the management table 72. The operation ID in the operation ID management table 72 is still blank at this point.

When the [Review / Approval] button 37 (FIG. 3) is pressed The newly assigned operation ID is registered in the operation ID of the Review / Approver Management Table 73, and the Review / Approver in the Review / Approver column 31 Is registered in the review / approver of the review / approver management table 73. The current date and time is registered as the examination / approval date / time in the examination / approver management table 73. Further, the same value as that registered in the operation ID column of the examination / authorizer management table 73 is registered in the operation ID column of the operation ID management table 72.

Next, an operation in which data registered in each table is displayed by the display control unit 17 will be described.
-When the [Display] button 33 (FIG. 3) is pressed The management ID line in the operation procedure data management table 74 that matches the management ID in the unapproved list is searched. Then, the management ID of the retrieved row is in the management ID column 34 in FIG. 3, the applicant is the application date and time is the applicant [examination request date and time] column 35, and the start date and time and the end date and time is the operation period in the operation procedure data column 36. Are displayed respectively.

  Further, all the user names, target jobs, and authority levels of the management ID in the user operation management table 71 that matches the management ID of the retrieved row are displayed in the operation procedure data column 36 as the permission command and the operation purpose.

When the [Display] button 42 (FIG. 4) is pressed The management ID line in the operation procedure data management table 74 that matches the management ID in the approved list is searched. Then, the management ID of the retrieved row is in the management ID column 43 in FIG. 4, the applicant, the application date and time is in the applicant [examination request date and time] column 44, and the examination / approval that matches the operation ID in the approved list column 41 The examination / approver and the examination / approval date / time of the operation ID line in the person management table 73 are displayed in the examination / approval [examination / approval date / time] column 45, respectively.

  Also, the operation ID, start date / time, end date / time of the approved list column 41, all user names of the management ID in the user operation management table 71 that matches the management ID of the searched row, target job, authority level, permission command, The operation purpose is displayed in the operation procedure data column 46.

When the [Display] button 54 (FIG. 5) is pressed: the operation ID in the operation ID column 51, the start date / time in the operation procedure data management table 74, the end date / time, and the management ID in the user operation management table 71 that matches the management ID of the searched row All of the user name, target job, authority level, permission command, and operation purpose are displayed in the operation procedure data column 55, respectively. If there is a display period for the operation log, within the input period, if there is not, search the entire operation ID and extract the target row, and if the extracted result further has a user name, the input user If the name does not exist, the extracted result is output to the operation log list as it is.

Next, a procedure for performing access control will be described.
As shown in FIG. 8, first, a management ID and a user name are acquired from the user operation management table 71 (step S1). Next, the management ID of the user name in the user operation management table 71 that matches the user name of the user who executed the command is obtained (step S2). If no matching user name exists in the user operation management table 71, an access authority error occurs because the user is not registered in the operation procedure data management table 74 (step S3).

On the other hand, if a matching user name exists in the user operation management table 71, an operation ID corresponding to the management ID of the operation ID management table 72 that matches the management ID corresponding to the matching user name is obtained (step S4). ).
If the corresponding operation ID does not exist in the operation ID management table 72, the process returns to the process of acquiring the management ID and user name from the user operation management table 71 (step S5).

  On the other hand, if the corresponding operation ID exists in the operation ID management table 72, it is confirmed whether the permission command in the line that matches the search key with the management ID in the operation procedure data management table 74 is equal to the command executed as the operation. (Step S6). As shown in FIG. 9, when the permission command is not equal to the command executed as an operation (step S7), an access authority error due to a command designation error is generated (step S8).

  On the other hand, if they are equal, it is confirmed whether the target job in the value stored as the management ID search key in the operation procedure data management table 74 is equal to the command argument job executed as the operation (step S9). If they are not equal, an access authority error due to a job designation error occurs (step S8). If they are equal, it is confirmed that the start date / time in the value stored as the management ID search key in the operation procedure data management table 74 is before the command execution date / time at the time of operation execution (step S10).

If it is after the command execution date and time, an access authority error occurs because the operation is outside the operation period (step S8). On the other hand, if it is before the command execution date and time, it is confirmed that the end date and time in the value stored as the management ID search key in the operation procedure data management table 74 is after the command execution date and time at the time of operation execution (step S11). . If it is before the command execution date and time, an access authority error occurs because the operation is outside the operation period (step S8).
If it is after the command execution date and time, the command is executed with the authority level in the value stored as the search key of the management ID in the operation procedure data management table 74 designated as the authority level at the time of operation execution (step S12).

As described above, the job management system according to the present embodiment has the following effects.
-According to the operation procedure data that has been reviewed and approved, the operation authority (execution / execution authority) of the job management system can be set in detail, such as operation period, user name, target job, authority level, and permission command. In addition, erroneous operations and operations other than instructions can be prevented.
By extracting the operation result for each operation authority of the job management system from the operation log of the job management system and displaying it together with the operation procedure data, the validity of the operation result can be easily determined.

1 is a system configuration diagram of a job management system according to the present invention. FIG. Image of operation procedure data creation screen. Image of operation procedure data review / approval screen. Image of screen for confirming approved operation procedure data. Operation result log display screen image. An example of screen output and operation log output during operation execution. The example of a table list of access authority DB. The flowchart at the time of command execution. The flowchart at the time of command execution.

Explanation of symbols

DESCRIPTION OF SYMBOLS 11 ... Job management server, 12 ... User terminal, 13 ... Network, 14 ... Operation procedure data management part, 17 ... Display control part, 18 ... Data storage part.

Claims (2)

A job management system in which a job management server and a user terminal are communicably connected via a network,
The job management server
Operation procedure data composed of data related to access authority including operation period, user name, target job, authority level, and permission command, and operation procedure data, and operation ID numbered at the time of examination / approval of the operation procedure data A data storage unit storing a database for managing
A job management system comprising: an operation procedure data management unit that permits an operation only with the operation authority described in the operation procedure data associated with the operation ID specified at the time of operation execution. The job management system according to claim 1, further comprising: a display control unit that simultaneously displays an extraction result of an operation executed with the operation ID from an operation log and contents of operation procedure data corresponding to the operation ID.

Images