JP2005202931A - Information processor management system, information processor management method, program, and recording medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To automate a work flow of a request for operation, an application for approval, operation execution, an operation result report, and log holding management, for an operation object device which requires approval procedures when being operated. <P>SOLUTION: An operation information management PC 100 requests an approving PC 400 to approve operation request information of an operation object PC 300, for which an application is made by a personal terminal 200, and confirms approval and instructs the operation object PC 300 to execute an approved operation corresponding to the personal terminal to reflect operation request information and stores and manages operation request information transmitted from the personal terminal 200, an approval result of the operation request information, and a reflection result of the operation request information, in an operation application DB 150. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to an information processing apparatus management system, an information processing apparatus management method, a program, and a recording medium for managing an operation for an information processing apparatus that requires an approval procedure when performing an operation.

  In an ISMS (Information Security Management System) approval acquisition department, when performing operations such as changing the settings of a server PC, a routine application process such as acquisition of operation approval and the result of operation remains as a log.

  For this reason, conventionally, the approval contents are documented for each approval application, and the application approver is selected.

Patent Document 1 is a document of a data processing system that automates the process of permitting database data update on the condition that the approval of the administrator is received.
JP 2000-259477 A

  However, conventionally, as described above, it has been very complicated because it is necessary to document the approval contents for each approval application, select an application approver, and manage the documents thereafter.

  In addition, when applying the operation described in the application form to the operation target PC, the administrator of the operation target PC understood the operation content described in the approval application document and applied it manually. There was also a possibility that a situation would occur where an incorrect operation (operation different from the application) was performed.

  Furthermore, since the application approver who approves the application needs to grasp the status of the operation target PC for approval, all the application approvers must give the operation authority of the operation target PC to the operation target. There was a problem in terms of maintainability of the PC.

  In addition, the applicant has to apply in consideration of the exclusivity with other setting change applications, which is very complicated. Here, “exclusive” means, for example, that an unapproved operation application “c: ¥ temp delete” has been submitted first, followed by an operation application “c: ¥ temp access authority change” This refers to a case in which execution of an operation application submitted later is affected (cannot be executed) depending on whether the previous operation application is approved and executed. Conventionally, since the operation application is also document submission, it has been difficult to grasp what operation application has been submitted first.

  Furthermore, the application related to the previously applied operation cannot be performed unless the application is approved, and it is very complicated.

  The present invention has been made to solve the above-described problems, and an object of the present invention is to request the approval device whether the operation information management device approves the operation request information applied from the operation request device. The operation request information reflected from the operation request device is reflected by instructing the operation target device to execute the operation corresponding to the operation request information that has been confirmed and approved, and the operation request information is transmitted. By storing and managing the information approval result and the reflection result of the operation request information in the database, operation request, approval application, operation execution, operation result report, log for the operation target device that requires the approval procedure when performing the operation To provide an information processing device management system, an information processing device management method, a program, and a recording medium that can automate a workflow up to retention management.

  The first invention of the present invention approves when performing operations (all operations that can be controlled by the system, such as creating and deleting folders and files in information processing devices, adding accounts, starting services, and shutting down). An operation request device (personal terminal 200 shown in FIG. 1) for applying an operation request to an operation target device (operation target PC 300 shown in FIG. 1) that requires a procedure, and an operation information management device (FIG. 1) that manages the requested operation request. In the information processing device management system in which the operation information management PC 100) shown in FIG. 1, the approval device that approves the requested operation request (the approver PC 400 shown in FIG. 1), and the operation target device are communicably connected. The operation information management device is a first storage means for sequentially storing and managing the requested operation request information (the hard disk 105 shown in FIG. 2 and the operation dependency shown in FIG. 3). Application DB 150) and approval confirmation means for requesting the approval device to approve approval of the applied operation request information (processing by the CPU 101 shown in FIG. 2, steps S305 to S306 in FIGS. 12 and 20) And reflecting means for reflecting the operation request information by instructing the operation target apparatus to execute the operation corresponding to the operation request information confirmed to be approved by the approval confirmation means (processing by the CPU 101 shown in FIG. 2, FIG. 14 and steps S310 and S311) of FIG.

  The second invention of the present invention is a result registration means for registering and controlling the operation request information transmitted from the operation request device, the approval result of the operation request information, and the reflection result of the operation request information in the first storage means. (Processing by the CPU 101 shown in FIG. 2, step S312 in FIGS. 15 and 20).

  According to a third aspect of the present invention, the operation information management device includes a result report means (FIG. 15) for transmitting the reflection result of the operation request information to an information processing device of a predetermined manager.

  According to a fourth aspect of the present invention, the operation information management device is configured so that a relationship between the requested operation request information and other operation request information applied before the operation request information is determined by an operation executed first. A first determination means for determining whether or not the operation to be executed later is an exclusive relationship that cannot be executed (processing by the CPU 101 shown in FIG. 2, step S302 in FIG. 10 and FIG. 20); If it is determined that the relationship between the operation request information applied by one determination means and the other operation request information applied before the operation request information is an exclusive relationship, the operation request information is applied And refusal means for refusal (processing by the CPU 101 shown in FIG. 2, steps S301 to S311 in FIGS. 9 and 20).

  According to a fifth aspect of the present invention, on the assumption that the operation request information can be reflected in the first storage means by the reflecting means, the related next operation request information is approved before the operation request information is approved. Can be stored (preceding request shown in FIG. 8).

  According to a sixth aspect of the present invention, the operation request information includes information on the applicant, and the operation information management device stores a second storage unit that stores operation authority information assigned to each applicant. (Based on the operation authority list 900 shown in FIG. 9) and the operation authority information stored in the second storage means, whether the requested operation request information is applied by an authorized applicant The second determination means for determining whether or not the operation request information is applied by an authorized applicant by the second determination means (the process by the CPU 101 shown in FIG. 2, step S301 in FIGS. 9 and 20). In the case where it is determined that the information is not the first one, first notification means for notifying the operation requesting apparatus that sent the operation request information to that effect (processing by the CPU 101 shown in FIG. 2, processing in FIGS. 9 and 20) Step S3 And having 3) and the.

  According to a seventh aspect of the present invention, the operation information management device includes third storage means (unapproved operation permission authority list 1100 shown in FIG. 11) storing authority information that can be operated without approval for each operation content. Based on the authority information stored in the second storage means and the operation authority information that can be operated without approval stored in the third storage means, the requested operation request information is operated without approval. And a third determination means (process by the CPU 101 shown in FIG. 2, step S304 in FIG. 11 and FIG. 20) for determining whether or not the application has been made by an applicant having a possible operation authority. The approval confirmation means determines that the requested operation request information by the third determination means has been applied by an applicant having an operation authority that can be operated without approval. For operation request information That approve bypass the confirmation (step S304 → S308 of FIG. 20) that is characterized.

  According to an eighth aspect of the present invention, the operation information management device is executed after the operation request information and the operation request information when the operation request information is reflected on the operation target device by the reflecting means. 4th determination means (FIG. 2) which determines whether the relationship with the other operation request information of waiting is an exclusive relationship in which the operation performed later by the operation performed previously becomes impossible. The processing by the CPU 101 shown in FIG. 14, step S308 in FIG. 14 and FIG. 20 and the relationship between the operation request information and other operation request information executed after the operation request information by the fourth determination means are exclusive. If it is determined that there is, second notification means for notifying information indicating that to the operation requesting apparatus that is the transmission source of the other operation request information that has an exclusive relationship with the operation request information (step S309 in FIG. 20). ) Characterized in that it has a.

  According to a ninth aspect of the present invention, the operation information management apparatus includes a fourth storage unit (approval type list 1200 shown in FIG. 12) storing an approval type for each operation content. Changes and controls the approval confirmation method for the requested operation request information based on the approval type stored in the fourth storage means (FIG. 12).

  According to a tenth aspect of the present invention, the operation request device is an acquisition means for acquiring system configuration information of the operation target device (processing by a CPU (not shown) of the personal terminal 200 shown in FIG. 1, steps of FIGS. 6 and 19 S201, S202) and display means for displaying a virtual operation screen capable of virtually operating the operation target device based on the system configuration information acquired by the acquisition means (processing by a CPU (not shown) of the personal terminal 200 shown in FIG. 1, Step S203 in FIG. 7 and FIG. 19 and creation means (personal terminal 200 shown in FIG. 1) for creating operation request information for the operation target device based on the virtual operation on the virtual operation screen displayed by the display means. The processing by the CPU (not shown), step S205 in FIG. 6 and FIG. 19, and the operation request information created by the creating means (Processing by the CPU (not shown) of the personal terminal 200 shown in FIG. 1, FIG. 6, step S206 of FIG. 19) application means for making an application sends sense apparatus and having a.

  According to an eleventh aspect of the present invention, the operation information management device includes a second storage unit (operation authority list 900 shown in FIG. 9) storing operation authority information assigned to each applicant, and the requested operation. Whether the relationship between the request information and other operation request information applied prior to the operation request information is an exclusive relationship that makes it impossible to execute an operation executed later by an operation executed earlier The first determination means for determining the process (the processing by the CPU 101 shown in FIG. 2, step S302 in FIGS. 10 and 21), the operation request information applied by the first determination means, and the application before the operation request information When it is determined that the relationship with the other operation request information is an exclusive relationship, the second operation request information is rejected according to the operation authority of the applicant stored in the second storage means. 2 rejection means (shown in FIG. 2 Treatment with PU 101, and having a step S322) in step S312~ Figure 22 of FIG. 21.

  In a twelfth aspect of the present invention, the operation information management device reflects the system configuration information of the operation target device at a predetermined time, the operation request information stored in the first storage means, and the operation request information. Based on the result, it has a confirmation means (process by the CPU 101 shown in FIG. 2, steps S2-1 to S2-12 in FIG. 24) for confirming whether or not the operation target device is consistent. And

  In a thirteenth aspect of the present invention, the operation information management device reflects the system configuration information at a predetermined time of the operation target device, the operation request information stored in the first storage means, and the operation request information. Based on the result, it has a reproduction means (process by the CPU 101 shown in FIG. 2, steps S3-1 to S3-9 in FIG. 30) for reproducing the past state of the operation target device so as to be virtually operable. To do.

  The fourteenth aspect of the present invention is an operation requesting device (personal terminal 200 shown in FIG. 1) for applying for an operation request to an operation target device (operation target PC 300 shown in FIG. 1) that requires an approval procedure when performing an operation. And an operation information management apparatus (operation information management shown in FIG. 1) having first storage means (hard disk 105 shown in FIG. 2, operation request application DB 150 shown in FIG. 3) for sequentially storing and managing the requested operation request information. In the information processing apparatus management method in the information processing apparatus management system in which the PC 100) and the approval apparatus that approves the requested operation request (the authentication PC 400 shown in FIG. 1 and the operation target apparatus) are communicably connected. Approval confirmation process in the operation information management device for requesting the approval device to confirm whether or not the requested operation request information can be approved (see FIGS. 12 and 20). Steps S305 to S306), and a reflection step (FIGS. 14 and 20) that transmits an operation execution instruction corresponding to the operation request information approved in the approval confirmation step to the operation target device and acquires the execution result. Steps S310 and S311), and a result registration step of registering the operation request information transmitted from the operation requesting device, the approval result of the operation request information, and the reflection result of the operation request information in the first storage means (FIG. 15 and step S312 of FIG. 20).

  The fifteenth aspect of the present invention is a program for executing the information processing apparatus management method described in the fourteenth aspect.

  A sixteenth aspect of the present invention is characterized in that a program for executing the information processing apparatus management method described in the fourteenth aspect is stored in a recording medium so as to be readable by a computer.

  According to the present invention, the operation information management device requests the approval device to confirm whether the operation request information requested from the operation request device is approved, and confirms the operation corresponding to the operation request information approved. The operation request information is reflected by instructing the operation target device to execute, and the operation request information transmitted from the operation request device, the approval result of the operation request information, and the reflection result of the operation request information are stored and managed in a database. Therefore, it is possible to automate the workflow from operation request, approval application, operation execution, operation result report to the operation target device that requires the approval procedure when performing the operation, simplify the various procedures, create application documents, It is possible to reduce the management burden and to ensure that the requested operation details are reflected in the operation target device and that the operation content is invariant. That. Also, assuming that the previously requested operation request information can be reflected, it is possible to apply for the next related operation request information before approving the operation request information, so that the previously requested operation request is permitted. As a result, prior to the approval of the previous operation request, it is possible to sequentially apply for the next related operation request (plurality), and the operation request process can be performed efficiently.

  In addition, when the operation information management device determines that the operation request information is not applied by an authorized applicant based on the operation authority information assigned to each applicant, the operation request information Since the application is rejected, an application from an unauthorized user can be rejected in advance to improve the maintainability of the information processing apparatus.

  In addition, the operation information management apparatus determines that the relationship between the requested operation request information and the other operation request information applied prior to the operation request information is such that an operation executed later by an operation executed first is not executed. When it is determined that the exclusive relationship becomes possible, information indicating that is notified to the operation requesting apparatus that is the transmission source of the operation request information, so that the user is aware of the exclusivity with other setting change applications. You can apply for an operation request without

  Furthermore, the operation information management device is applied by an applicant who has the operation authority that can be operated without approval based on the authority information and the operation authority information that can be operated without approval. If the requested operation request information is determined to have been applied by an applicant who has an operation authority that can be operated without approval, the approval for the operation request information is approved. Since confirmation is omitted, depending on the applicant's authority and operation content, the operation can be applied without obtaining the approval of the approver, and the efficiency of the approval process can be greatly improved.

  In addition, since the operation information management device changes and controls the approval confirmation method for the requested operation request information based on the approval type for each operation content, the approval condition is automatically determined and the approval process is made efficient. Can do.

  Further, the operation requesting device acquires system configuration information of the operation target device, displays a virtual operation screen on which the operation target device can be virtually operated based on the acquired system configuration information, and displays the displayed virtual operation Operation request information for the operation target device is created based on a virtual operation on the screen, and the created operation request information is sent to the operation information management device for application. The operation content information can be easily created based on the operational feeling as if the target device is operated.

  Therefore, the ISMS approval acquisition department automates a routine application process, such as acquiring operation approvals and operating results, etc. when performing operations such as changing the settings of information processing devices such as servers. The production and management are greatly simplified to improve efficiency, and the maintainability of the information processing apparatus can be improved by tracking the cause when an inconsistency is detected and automatically auditing the operation target device.

[First Embodiment]
FIG. 1 is a system configuration diagram illustrating an example of an information processing apparatus management system according to the first embodiment of this invention.

  In FIG. 1, reference numeral 300 denotes an operation target PC, which is an information processing apparatus that is actually an operation target. Reference numeral 200 denotes a personal terminal, which is an information processing apparatus for an operation requester to request an operation.

  Reference numeral 100 denotes an operation information management PC that causes the operation target PC 300 to perform an operation based on operation request information from the personal terminal 200. The operation request application database (DB) 150 stores and manages operation request information applied from the personal terminal 200 under the control of the operation information management PC 100. Reference numeral 1500 denotes an operation result report DB 1500 shown in FIG.

  Reference numeral 400 denotes a plurality of approver PCs, which return approval / denial information to the operation information management PC 100 based on an approval request from the operation information management PC 100.

  The operation information management PC 100 and the operation target PC 300 shown in this embodiment use expressions such as a PC and a terminal, but are not limited to personal computers or the like, and are workstations or other information processing apparatuses. Also good.

  The personal terminal 200 is not limited to a personal computer or the like, and may be a PDA, a workstation, or other information processing apparatus.

  This information processing apparatus management system automates a workflow from approval request to operation execution and operation result report when an operation is performed on a PC (operation target PC 300) that requires an approval procedure when performing an operation. Automating a series of routine application processes such as obtaining approval of operations and leaving a log of operation results that occur when performing operations such as changing the settings of a server PC such as an ISMS approval acquisition department This simplifies various procedures and reduces the burden of creating and managing application documents. In the present embodiment, “operation” refers to all operations that can be controlled by this system, such as creating and deleting folders and files on the PC, adding accounts, starting services, and shutting down.

  FIG. 2 is a block diagram showing a configuration of the operation information management PC 100 shown in FIG.

  In FIG. 2, reference numeral 101 denotes a CPU which controls each device based on a program stored in the hard disk 105 or other recording medium (storage medium).

  Reference numeral 102 denotes a memory that functions as a main memory, work area, and the like of the CPU 1.

  An I / O control unit 103 controls input / output with a keyboard 107, a pointing device such as a mouse 108, the printer 109, and the network 500.

  A video controller 104 controls the display on the monitor 106. On the hard disk 105, an operation request application DB 150 and an operation result report DB 1500 shown in FIG. The hard disk 105 stores in advance an operation authority list 900 shown in FIG. 9, which will be described later, an unapproved operation permission authority list 1100 shown in FIG. 11, and an approval type list 1200 shown in FIG. Furthermore, the hard disk 105 has an approval waiting operation request information storage area 600 shown in FIG.

  Note that the operation information management PC 100 shown in FIG. 1 does not necessarily include the monitor 106, the keyboard 107, the mouse 108, and the printer 109.

  Also, the personal terminal 200, the operation target PC 300, and the approver PC 400 shown in FIG. 1 have the same hardware configuration as the operation information management PC 100 shown in FIG. However, the above-mentioned DBs are not mounted and data is not stored in the hard disk 105.

  FIG. 3 is a schematic diagram showing a record structure of the operation request application DB 150 shown in FIG.

  As shown in FIG. 3, the operation request application DB 150 includes an operation management number (ID) 151, an applicant 152, an application content 153, an application date 154, an application result 155, an application file name 156, and the like.

  The operation management number (ID) 151 indicates a number that is sequentially given to the operation information management PC 100 in the order of application acceptance. The applicant 152 corresponds to information that can identify the applicant. The application content 153 includes information that can identify the operation target PC on the network (for example, “Server001”) and information that can specify the operation for the operation target PC (for example, the request content “create new share”, the object “directory, ¥¥ Server001 ¥ tmp ¥ template ”, access right to be granted“ read / write ”) and other information input by the applicant when applying for an operation request (for example, planned usage capacity“ 1 GByte ”, reason for application / additional“ work schedule of staff ” To apply for sharing the above directory in order to store

  The application date 154 corresponds to the date when the application is accepted in the operation information management PC 100.

  The application result 155 includes information regarding approval and information regarding work. The information regarding the approval includes an approval route indicating the approved route, such as an approval date indicating the date of approval, an approval record filled in by the approver at the time of approval. The information about the work includes a work date indicating the date on which the operation is reflected, a work record indicating the content of the actual operation (for example, “created the specified directory. It has been verified. ”), Including information on special notes regarding the work.

  The application form file name 156 indicates the file name of the application form 160 shown in FIG.

  FIG. 4 is a schematic diagram showing an example of an application form corresponding to the application form file name 156 shown in FIG.

  The application form 160 shown in FIG. 4 includes the operation request application information to be registered and various management information (user management) stored in the hard disk 105 when the operation information management PC 100 registers the operation request application information in the operation request application DB 150. Information, PC management information, etc.) is created by the operation information management PC 100 and stored in the hard disk 105.

  4, 161 is an application date, which is generated from the application date 154 in the operation request application DB 150 shown in FIG.

  Reference numeral 162 denotes an applicant name, employee number, department or company name, and is generated based on the applicant 152 and user management information in the operation request application DB 150 shown in FIG.

  Further, reference numeral 163 denotes information such as the target department, target server, request contents, target object, target organization, access right to be granted, planned use capacity, reason for application / addition, etc., and the application in the operation request application DB 150 shown in FIG. It is generated based on the contents 153 and PC management information. Reference numeral 166 denotes an application form name, which is generated based on the application content 153 in the operation request application form DB 150 shown in FIG.

  Reference numeral 164 denotes information such as an approval date and an approval record, which is generated based on the application result 155 and the like in the operation request application DB 150 shown in FIG. Reference numeral 167 denotes approval route information, which is generated based on the application result 155 or the like in the operation request application DB 150 shown in FIG.

  Reference numeral 165 denotes information such as a work date, a work record, and a special note, which is generated based on the application result 155 in the operation request application DB 150 shown in FIG.

  FIG. 5 is a flowchart for explaining a series of processes from application of an operation request to operation result reporting in the management system shown in FIG. 1, and S1 to S13 indicate each step.

  When an operation of the operation target PC 300 is desired, first, operation request information is created in step S1 of FIG. 5, and then, in step S2 of FIG. 5, an operation application is made based on the operation request information created in step S1. Do. Hereinafter, the creation and application procedure of the operation request information will be described in detail with reference to FIGS.

  FIG. 6 is a diagram showing in detail the creation and application procedure of the operation request information shown in steps S1 and S2 of FIG. 5, and the same components as those in FIG. 5 are denoted by the same reference numerals.

  As shown in FIG. 6, when the operation of the operation target PC 300 is desired, first, in step S1-1, information necessary for opening the operation request information creation screen (virtual window) shown in FIG. 7 on the personal terminal 200. The personal terminal 200 requests and obtains (system configuration information including file management information such as the directory configuration and file configuration of the operation target PC 300) from the operation target PC 300. In step S1-2, the personal terminal 200 acquires the operation request information. A creation screen (virtual window) is displayed (opened) on the monitor 700 of the personal terminal 200, and operation request information is created based on an operation on the virtual window. An example of the operation request information creation screen (virtual window) is shown in FIG.

  On the operation request information creation screen (virtual window) 701 shown in FIG. 7, the user can perform operations similar to those actually performed on the operation target PC 300, and perform operations on the virtual window 701. Thus, an operation request to the operation target PC 300 can be created and applied. When an operation is performed on the virtual window 701, the personal terminal 200 displays an interface for inputting information for the operation on the monitor 700 of the personal terminal 200. For example, when an operation for creating a new directory on the operation target PC 300 is performed on the virtual window 701, an interface for inputting “scheduled usage” and “reason for application / addition” of the created directory is displayed. Shall.

  When the user performs a desired operation using the GUI of the virtual window 701 and inputs information regarding the operation, the personal terminal 200 creates operation request information based on the operation and information corresponding to the operation. The operation request information has the same configuration as the record configuration in the operation request application DB 150 shown in FIG. However, at this time, the applicant name in the applicant 152, the target server in the application content 153, the request content, the target, the planned usage, the reason for application, the supplementary reason, etc. It is assumed that the other information is sequentially stored every time the process proceeds.

  Next, in step S2, the personal terminal 200 applies (registers) the operation request information by transmitting the operation request information created in step S1-2 in FIG. 6 to the operation information management PC 100, and the operation information management PC 100 The received operation request information is received, and the received operation request information waiting for approval is spooled in the approval request operation storage area 600 in the hard disk 105 or the memory 102.

  Note that the operation request information creation and application processing can be performed prior to execution of the operation request waiting for execution, assuming that the operation request waiting for execution is executed correctly. Hereinafter, creation of this operation request information (preceding request) will be described with reference to FIG.

  FIG. 8 is a diagram showing in detail the creation of operation request information (preceding request).

  As shown in FIG. 8, operation request information that cannot be operated unless the operation management ID 1 is processed can be registered on the assumption that an operation waiting for approval is executed.

  For example, assuming that the folder creation “c: \ temp \ template” of the operation management ID1 is approved, prior to the approval and execution of the operation management ID1, the file “readme.txt” is stored in the “c: \ temp \ template”. Can issue a creation operation request.

  As a result, assuming that the requested operation is successfully approved and executed, a plurality of operation requests can be applied sequentially, and the operation request process can be performed efficiently.

  Returning to the description of FIG.

  Next, in step S3 in FIG. 5, a determination process is performed to determine whether or not the operation application performed in step S2 has been issued by a user having appropriate authority. Hereinafter, the authority verification procedure of the operation requester will be described with reference to FIG.

  FIG. 9 is a diagram showing in detail the authority verification procedure of the operation requester shown in step S3 of FIG.

  As shown in FIG. 9, the operation information management PC 100 has appropriate authority for the operation request information from the personal terminal 200 registered in step S2 based on the operation authority list 900 stored in the hard disk 105 in advance. A process for determining whether or not the user has issued is performed.

  The operation authority list 900 includes a name 901 indicating the user's name and an authority 902 indicating the user's authority. The authority 902 includes “rejection”, “general authority”, “position authority”, “administrator authority”, and the like in ascending order of authority. When the authority 902 is “rejected”, no authority is given and all operation requests are rejected. Further, when the authority 902 is “general authority”, “position authority”, “administrator authority”, etc., the unapproved operation authority based on the unapproved operation permission authority list 1100 shown in FIG. 11 described later is given. Shall.

  Therefore, in the example shown in FIG. 9, the operation information management PC 100 has appropriate authority for the operation request information applied from the users “Yoko Yamada”, “Yumi Sato”, “Kenichi Ito”, “Yuji Koizumi”. A user who does not have an appropriate authority for the operation request information applied by the user “Ichiro Kimura” or the unregistered user “John”. The operation request is rejected.

  Returning to the description of FIG.

  If it is determined in step S3 of FIG. 5 that the operation application performed in step S2 is not issued by a user having an appropriate authority, the process directly proceeds to step S13.

  On the other hand, if it is determined in step S3 in FIG. 5 that the operation application performed in step S2 is issued by a user having appropriate authority, the process proceeds to step S4 in FIG. 5 and performed in step S2. Judgment processing is performed to determine if the operation application is exclusive with other application contents.

  If it is determined in step S4 of FIG. 5 that the operation application performed in step S2 has an exclusive problem with other application contents, an operation corresponding to the operation application performed in step S2 in step S5. Is notified to the operation applicant who performed in step S2, and the process proceeds to step S6 in FIG.

  On the other hand, if it is determined in step S4 in FIG. 5 that the operation application performed in step S2 has no problem on exclusion with other application contents, the process directly proceeds to step S6 in FIG. Hereinafter, the exclusive verification and notification procedure with the other operation applications will be described with reference to FIG.

  FIG. 10 is a diagram showing in detail the exclusive verification and notification procedure with other operation applications shown in steps S4 and S5 of FIG.

  As shown in FIG. 10, in step S4, the operation information management PC 100 waits for other approval requests in which the operation request information from the personal terminal 200 applied (registered) in step S2 is stored in the operation request application DB 150. It is determined whether or not there is a problem in exclusion with the operation request information.

  If the requested operation request information relates to an operation that can be performed without any problem even after all other operation request information waiting for approval has been approved and all operations have been executed, If there is an operation that cannot be performed after any other operation request information waiting for approval is approved and the operation is executed, it is determined that there is a problem on exclusion. .

  For example, when a folder creation “c: ¥ image” with management ID 4 shown in FIG. 10 is applied as operation request information, all operation request information (management IDs 1 to 3) waiting for approval is approved and all operations are executed. Since the folder creation “c: ¥ image” of the management ID 4 can be performed without any problem, it is determined that the folder creation “c: ¥ image” of the management ID 4 is “no problem on exclusion”.

  Also, when the folder creation “c: \ html \ toppage \ menu” of the management ID 5 shown in FIG. 10 is applied as the operation request information, the folder deletion “c: \ html \ toppage” of the management ID 3 waiting for approval is approved. Since the folder creation “c: \ html \ toppage \ menu” of the management ID 5 cannot be performed after the execution, the folder creation “c: \ html \ toppage \ menu” of the management ID 5 It is determined that there is a problem on exclusion.

  If it is determined in step S5 that “exclusive problem exists”, the applicant's personal terminal 200 displays a warning indicating that the applied operation is an operation that has an exclusive problem with other approval-waiting operations. Notify It is assumed that the personal terminal 200 that has received the warning notification displays the warning notification in a pop-up manner.

  Returning to the description of FIG.

  Next, in step S6 of FIG. 5, it is determined whether or not the operation application performed in step S2 is an operation that requires the approval of the approver. Hereinafter, the determination procedure of the operation requiring the approval will be described with reference to FIG.

  FIG. 11 is a diagram showing in detail the determination procedure of the operation requiring the approval shown in step S6 of FIG.

  As shown in FIG. 11, the operation information management PC 100 determines in step S6 the individual who has applied (registered) in step S2 based on the operation authority list 900 and the unapproved operation permission authority list 1100 stored in the hard disk 105. A process of determining whether or not the operation request information from the terminal 200 is an operation that requires approval is performed.

  The unapproved operation-permitted authority list 1100 includes operation contents 1101 and authority 1102 indicating authority that allows the operation contents 1101 to be operated without approval. The authority 1102 includes “general authority”, “position authority”, “administrator authority”, and the like in ascending order of authority.

  That is, in this determination process, for example, if the operation content “create folder” is an application from a user having authority of “general authority” or higher, it is determined that the operation can be performed without approval, and the operation content “delete folder” is determined. Determines that it is possible to operate without approval if it is an application from a user with authority higher than "title authority", and if the operation content "shutdown" is an application from a user with "administrator authority" Judge that the operation is possible without approval.

  Therefore, in the example illustrated in FIG. 11, when the user “Yoko Yamada” requests the operation content “create folder”, the operation information management PC 100 determines that the authority of the user “Yoko Yamada” from the operation authority list 900 is “general authority”. Since it is understood from the unapproved operation permission authority list 1100 that the operation contents “folder creation” can be operated without approval is “general authority” or more, the operation contents “folder requested by the user“ Yoko Yamada ”is requested. The operation request application “create” is determined as “operation is possible without approval”.

  In addition, when the user “Kenichi Ito” requests the operation content “shutdown”, the authority of the user “Kenichi Ito” is recognized as “title authority” from the operation authority list 900, and the operation content “shutdown” is obtained from the unauthorized operation permission authority list 1100 ”Can be operated without approval.“ Administrator authority ”is understood, so the operation request application“ Shutdown ”requested by the user“ Ito Kenichi ”is judged as“ Approval is required for operation ”. To do.

  Returning to the description of FIG.

  If it is determined in step S6 in FIG. 5 that the operation corresponding to the operation application performed in step S2 is not an operation that requires approval (approval is not required), the process proceeds to step S10 in FIG.

  On the other hand, if it is determined in step S6 of FIG. 5 that the operation corresponding to the operation application performed in step S2 is an operation that requires approval, the operation content corresponding to the operation application performed in step S2 is determined in step S7. Is transmitted to the approver, the process proceeds to step S8 in FIG. 5, the approval result is received from the approver, and the process proceeds to step S9 in FIG. Hereinafter, this operation approval confirmation procedure will be described with reference to FIG.

  FIG. 12 is a diagram showing in detail the operation approval confirmation procedure shown in steps S7 and S8 of FIG.

  As shown in FIG. 12, the operation information management PC 100 determines the operation request information from the personal terminal 200 applied (registered) in step S2 based on the approval type list 1200 stored in the hard disk 105 in step S7. Process to confirm approval.

  The approval type list 1200 includes an operation content 1201 and an approval type 1202 for the operation content 1201. The approval types 1202 include “single approval”, “designated approval (designated approver PC information)”, “approval for all”, and the like.

  The approval type “single approval” can be operated as an approval if an approval request is sent to all approver PCs and an approval is returned from any of the approver PCs.

  The approval type “designated approval” is operable when an approval request is sent to the designated approver PC and the approval is returned from the approver PC.

  Furthermore, the approval type “approval for all” is operable when an approval request is sent to all approver PCs and approval is returned from all the approver PCs.

  For example, in the example illustrated in FIG. 12, when the operation information management PC 100 has applied for an operation request for the operation content “folder creation”, the approval type list 1200 indicates that the approval type is “single approval”. An approval request for an operation request application for the operation content “create folder” is issued to all approver PCs (S7), and if approval is received from any approver PC, it is determined that the approval has been received (S8).

  Further, when an operation request for the operation content “delete folder” is applied, the operation information management PC 100 knows from the approval type list 1200 that the approval type is “designated approval (approver PC (2))”. An approval request for an operation request application for the content “delete folder” is sent to the approver PC (2) (S7), and if approval is received from the approver PC (2), it is determined that the approval has been received (S8).

  Further, when an operation request for the operation content “shutdown” is applied, the operation information management PC 100 knows from the approval type list 1200 that the approval type is “approval for all”. An approval request is sent to all approver PCs (S7), and if approval is received from all approver PCs, it is determined that approval has been received (S8).

  It is assumed that the IP address of each approver PC is set in advance and stored in the hard disk 105. In addition, the approver PC 400 that has received this approval request pops up the approval request screen. In addition, when approval is no longer necessary due to approval by another approver PC or the like, this approval request screen is closed by an instruction from the operation information management PC 100. Furthermore, since each approver can grasp the state of the operation target PC 300 using the virtual window 701 shown in FIG. 7, each approver can operate even if the operation authority of the operation target PC 300 is not given. Approval processing can be performed by grasping the state of the PC 300.

  Although not shown in the flowchart, the operation information management PC 100 spools the operation request information stored in the approval waiting operation request information storage area 600 and outputs the approval result (when received). Information indicating the approval result is added to the application request result 155 of the operation request information, and the operation request information is stored in the operation request application DB 150.

  Further, at this timing, the operation information management PC 100 creates the application form 160 shown in FIG. 4 and stores it in the hard disk 105, and the file name of the created application form is the application form file name in the operation request information. Stored in 156. Note that the timing of the storage processing in the operation request application DB 150 and the creation processing of the application 160 is not limited to this timing. For example, it may be the timing of step S13 in FIG.

  Note that the operation request information determined to require no approval in step S6 is similarly stored in the operation request application DB 150 and created in the application 160.

  Returning to the description of FIG.

  Then, in step S9 in FIG. 5, it is determined whether or not the execution of the operation corresponding to the operation application performed in step S2 has been approved. If it is determined that the operation has not been approved, the process directly proceeds to step S13.

  On the other hand, if it is determined in step S9 in FIG. 5 that the execution of the operation corresponding to the operation application performed in step S2 is approved, the process proceeds to step S10.

  Then, in step S10, among the operations waiting for the operation, this operation (operation corresponding to the operation request information approved in step S9 or the operation request information determined not to require approval in step S6) is caused. It is determined whether there is operation request information that results in an exclusive operation. Hereinafter, the exclusive verification procedure of this approval operation will be described with reference to FIG.

  FIG. 13 is a diagram showing in detail the exclusive verification procedure of the approval operation shown in step S10 of FIG.

  As shown in FIG. 13, the operation information management PC 100 determines in step S10 the operation request information determined to have been approved in step S9 (or the operation corresponding to the operation request information determined to be unnecessary in step S6, That is, by performing an operation corresponding to the operation request information to be reflected on the operation target PC 300, is the other approval request operation request information stored in the approval request operation request information storage area 600 subject to exclusion? A determination process of whether or not is performed.

  This determination process is performed when all the operation request information waiting for approval can be executed without any problem even after the operation corresponding to the approved operation request information is executed. On the other hand, after executing the operation corresponding to the approved operation request information, all the operation request information waiting for approval cannot be executed without any problem. If it is determined that there is operation request information waiting for approval that becomes an exclusive operation due to this operation, it is determined.

  For example, in the example illustrated in FIG. 13, when the folder deletion “c: \ temp \ template” with the management ID 1 is approved, the management ID 3 is executed after the folder deletion “c: \ temp \ template” with the management ID 1 is executed. The folder creation “c: \ temp \ template \ DB” cannot be executed without any problem, and it is determined that “there is operation request information waiting for approval that becomes an exclusive operation due to this operation”.

  Returning to the description of FIG.

  Then, in step S10 of FIG. 5, among the operations waiting for operation, this operation (operation corresponding to the operation request information approved in step S9 or the operation request information determined not to require approval in step S6). If it is determined that there is an operation that becomes an exclusive operation due to the cause, the process proceeds to step S11, and among the operations waiting for operation, this operation (the operation approved in step S9 or the approval in step S6 is required) If there is an operation corresponding to the operation request information determined to be not), a warning notification is sent to the personal terminal 200 that has requested an operation that would result in an exclusive operation, and the process proceeds to step S12. It is assumed that the personal terminal 200 receiving this notification displays the warning notification in a pop-up manner.

  On the other hand, in step S10 of FIG. 5, this operation (the operation approved in step S9 or the operation corresponding to the operation request information determined not to require approval in step S6) among the operations waiting for operation is the cause. If it is determined that there is no operation that becomes an exclusive operation, the process proceeds to step S12 in FIG.

  In step S12 of FIG. 5, the operation content is reflected on the operation target PC 300, and the process proceeds to step S13. Hereinafter, a procedure for reflecting the operation content will be described with reference to FIG.

  FIG. 14 is a diagram showing in detail the procedure for reflecting the operation content shown in step S12 of FIG.

  As shown in FIG. 14, the operation information management PC 100 determines the operation request information determined in step S12 as being approved in step S9 or the operation request information corresponding to the operation request information determined as not requiring approval in step S6. The operation execution instruction is transmitted to the operation target PC 300. Then, the application resident on the operation target PC that has received the operation execution instruction performs an operation based on the operation instruction. At this time, it is assumed that the operation target PC 300 returns the operation result to the operation information management PC 100, and the operation information management PC 100 acquires the operation result.

  Through these processes, the operation content corresponding to the operation request application can be reflected in the operation target PC 300.

  Returning to the description of FIG.

  Then, in step S13 in FIG. 5, the operation result report is generated and the DB is registered, and the process is terminated. The operation result report creation procedure will be described below with reference to FIG.

  FIG. 15 is a diagram showing in detail the operation result report creation procedure shown in step S13 of FIG.

  As shown in FIG. 15, in step S13, the operation information management PC 100 creates an operation result report (operation result report information) corresponding to the operation request information for which the operation content reflection processing was performed in step S12. The report information ID is attached and registered in the operation result report DB 1500 constructed in the hard disk 105, and the operation result report is transmitted to the personal terminal 200 such as a security / network administrator.

  The operation result report registered in the operation result report DB 1500 can be viewed from the personal terminal 200.

  It is assumed that the IP address and the like of the personal terminal 200 such as a security / network administrator are set in advance and stored in the hard disk 105.

  Further, the operation information management PC 100 obtains information based on the operation result at the timing of registration of the operation result report in the operation result report DB 1500, the application result 155 in the operation request information registered in the operation request application DB 150, and The information is stored in the information 165 in the application form 160.

  With the above processing, when an operation such as a setting change of the information processing apparatus in the ISMS approval acquisition department is performed, it is possible to realize a function of leaving an operation approval acquisition / operation result as a log.

  Hereinafter, a PC operation workflow in the management system of the present invention will be described in comparison with a conventional PC operation workflow with reference to FIGS.

  FIGS. 16 and 17 are schematic diagrams for explaining the PC operation workflow in the management system of the present invention. FIGS. 16A and 17A show the conventional PC operation workflow, and FIG. FIG. 17B shows a PC operation workflow according to the present invention.

  First, in the conventional PC operation workflow, as shown in FIGS. 16A and 17A, a person 1601 requesting the PC operation asks the PC operation approver 1602 for approval. Since this approval process is performed on a document basis, it is very complicated.

  Next, since the person 1601 requesting the operation of the PC cannot directly operate the operation target PC 300, the person 1601 requesting the operation of the PC requests the PC administrator 1603 to perform the operation.

  Then, the PC administrator 1603 operates the operation target PC 300 on behalf of 1601. At this time, since the operation request is also made on a document basis, the operation content is not accurately transmitted to the PC administrator 1603, and an operation error may occur.

  Then, the person 1601 requesting the operation of the PC reports the operation result to the security / network administrator 1604. Since this report is also made on a document basis, document management is very complicated.

  On the other hand, in the PC operation workflow according to the present embodiment, as shown in FIGS. 16B and 17B, a person 1601 requesting the PC operation operates on the PC he wants to operate. Data (operation request information) is created on the personal terminal 200, and the created operation data (operation request information) is transmitted from the personal terminal 200 to the operation information management PC 100.

  Then, the operation information management PC 100 confirms the approval of the personal terminal of the PC operation approver 1602 and, when approved, transmits operation data (operation instruction) to the operation target PC 300 and reflects the operation contents on the operation target PC 300. Let

  Finally, the operation information management PC 100 transmits operation result report information to the personal terminal of the security / network administrator 1604.

  As described above, in the PC operation workflow of this embodiment, everything from the operation approval to the operation application to the operation PC is performed online.

  In this way, the manual operation is only the operation request information creation work by the person 1601 who requests the operation of the PC, and all the processes from the subsequent operation approval application to the operation result report being issued It is possible to simplify the PC operation workflow by automating the control by the information management PC 100.

  The operation on the operation target PC is also performed based on the operation request information (created by the virtual operation on the virtual screen 701) created by the person 1601 who requests the PC operation. Therefore, it is possible to prevent an operation different from the requested operation from being executed due to misunderstanding of the operation content, as in the case where the conventional PC administrator 1603 performs on behalf of the agent, It can be reflected on the PC without fail. That is, the operation request information created based on the operation of the user who requests the operation is reflected in the actual PC operation as electronic information, so that the invariance of the operation content is guaranteed.

  In addition, since all documents including approval documents such as operation request documents are automatically created by a virtual operation on the virtual screen 701 shown in FIG. 7, the labor for document creation can be greatly simplified. . In addition, since management of the operation request document and the like is also managed by the operation request document DB 150 under the control of the operation information management PC 100, the labor for document management can be greatly simplified.

  Furthermore, since the operation approval condition is also determined based on the operation content under the control of the operation information management PC 100, the approval condition determination can be simplified and the approval efficiency can be greatly improved.

  Further, it is possible to improve the maintainability of the PC by limiting the users to whom the operation authority is given without directly operating the operation target PC 300 by the operation requester.

  Assuming that the previous approval application is permitted as shown in FIG. 8, a prior approval application for accepting the next related approval application can be made from the personal terminal 200. You can apply for the next approval without waiting for the result. That is, the operation information management PC 100 can accept a plurality of approval applications, and spools the accepted approval applications.

  Furthermore, the operation requester and the approver can apply for and approve the operation without having to be aware of the exclusive relationship with other setting change contents. In the present embodiment, exclusion means that, for example, an unapproved operation application “c: ¥ temp delete” is first submitted, and then an operation application “c: ¥ temp access authority change” is submitted. In this case, it refers to a case where the next operation is affected (becomes impossible) depending on whether the previous operation application is approved or not.

  Further, depending on the user level of the applicant (operation authority list 900) and the operation content (unapproved operation permission authority list 1100), the operation information management PC 100 applies the operation without obtaining the approval of the approver. Condition determination is simplified.

  Furthermore, since the operation request information can be generated on the virtual OS window 701 in the personal terminal 200, the operation can be performed with the same operational feeling as when the operation target PC is actually operated. However, the operation request information can be easily generated.

  Hereinafter, the control processing in the information processing apparatus management system of the present invention will be described with reference to FIGS.

  FIG. 18 is a flowchart showing an example of a first control processing procedure in the information processing apparatus management system of the present invention. Note that the processing of this flowchart corresponds to the processing of the application resident on the operation target PC 300 shown in FIG. 1, and is stored in a recording medium (storage medium) (not shown) by a CPU (not shown) in the operation target PC 300. It is executed based on. S101 to S105 indicate each step.

  First, in step S101, it is determined whether an operation target PC information acquisition request has been received from the personal terminal 200. If it is determined that an operation target PC information acquisition request has been received from the personal terminal 200, step S102 is performed. The operation target PC information (system configuration information of the operation target PC 300 itself) is transmitted to the requesting personal terminal, and the process proceeds to step S103. Note that the details of the processing in step S102 are shown in FIG. 6, and detailed description thereof is omitted here.

  On the other hand, if it is determined in step S101 that an operation target PC information acquisition request from the personal terminal 200 has not been received, the process directly proceeds to step S103.

  Next, in step S103, it is determined whether or not an operation execution instruction from the operation information management PC 100 has been received. If it is determined that an operation execution instruction from the operation information management PC 100 has been received, in step S104, a step is performed. The operation corresponding to the operation execution instruction received in S103 is executed, the execution result is transmitted to the operation information management PC 100 (S105), and the process returns to step S101. Note that the details of the processing in step S104 are shown in FIG. 14, and detailed description thereof is omitted here.

  On the other hand, if it is determined in step S103 that an operation execution instruction has not been received from the operation information management PC 100, the process directly returns to step S101.

  FIG. 19 is a flowchart showing an example of a second control processing procedure in the information processing apparatus management system of the present invention. Note that the processing of this flowchart corresponds to the processing of the application executed on the personal terminal 200 shown in FIG. 1, and is stored in a recording medium (storage medium) (not shown) by a CPU (not shown) in the personal terminal 200. It is executed based on. Moreover, S201-S212 shows each step.

  When the operation target PC is selected, the process is started, and an operation target PC information acquisition request is transmitted to the selected operation target PC 300 in step S201.

  In step S202, the process waits until the operation target PC information is received from the operation target PC 300. If it is determined that the operation target PC information has been received, in step S203, the operation request creation virtual window 701 (FIG. 7) is displayed on the personal terminal. It is displayed on 200 monitors 700.

  In step S204, it is determined whether or not there is an operation on the virtual window 701. If it is determined that there is no operation on the virtual window 701, the process proceeds to step S211 as it is.

  On the other hand, if it is determined in step S204 that there is an operation on the virtual window 701, operation request information is created based on the operation on the virtual window 701 in step S205, and the operation request information is displayed in step S206. It is transmitted to the operation information management PC 100. The details of the processing in steps S201 to S206 are shown in FIGS. 6 to 8, and detailed description thereof is omitted here.

  Next, in step S207, it is determined whether or not the warning information from the operation information management PC 100 (the warning notified in step S5 in FIG. 5) has been received. In S208, the received warning information is displayed on the monitor 700 of the personal terminal 200 to prompt the user to input whether to cancel or continue the corresponding operation request.

  In step S209, it is determined whether or not an instruction to cancel the operation request is input. If it is determined that an instruction to cancel the operation request is input, the virtual window performed in step S204 is displayed in step S210. Is canceled (the virtual window is returned to the state before the operation performed in step S204), and the process proceeds to step S204.

  On the other hand, if it is determined in step S209 that an instruction to cancel the operation request has not been input (an instruction to continue the operation has been input), the process directly returns to step S204.

  On the other hand, if it is determined in step S207 that warning information from the operation information management PC 100 has not been received, it is determined in step S211 whether or not there has been an end operation from the user, and it is determined that there has been no end operation. Returns to step S204.

  On the other hand, if it is determined in step S211 that the user has performed an end operation, the operation request creation virtual window 701 is closed in step S212, and the process ends.

  FIG. 20 is a flowchart showing an example of a third control processing procedure in the information processing apparatus management system of the present invention. Note that the processing of this flowchart corresponds to the processing of an application resident on the operation information management PC 100 shown in FIG. 1, and the hard disk 105 or a recording medium (not shown) (not shown) by the CPU 101 in the operation information management PC 100 shown in FIG. The program is executed based on a program stored in a storage medium. S301 to S312 indicate each step.

  First, when there is an operation application from the personal terminal 200 (operation request information is received), in step S301, it is determined whether or not the operation application has been issued by a user with appropriate authority. Note that the details of the processing in step S301 are shown in FIG. 9, and thus detailed description thereof is omitted here.

  If it is determined in step S301 that the operation application is not issued by a user having appropriate authority, the process directly proceeds to step S312.

  On the other hand, if it is determined in step S301 that the operation application is issued by a user having an appropriate authority, the process proceeds to step S302, and the operation application has no problem on exclusion with other application contents. The determination process is performed.

  If it is determined in step S302 that the operation application has no problem with exclusion of other application contents, the process directly proceeds to step S304.

  On the other hand, if it is determined in step S302 that the operation application has an exclusive problem with other application contents, in step S303, it is determined that the operation corresponding to the operation application is an exclusion target operation. The personal terminal 200 that has performed the notification is notified, and the process proceeds to step S304. Since details of the processes in steps S302 and S303 are shown in FIG. 10, detailed description thereof is omitted here.

  Next, in step S304, it is determined whether the operation application is an operation that requires the approval of the approver. Note that the details of the processing in step S304 are shown in FIG. 11, and detailed description thereof is omitted here.

  If it is determined in step S304 that the operation corresponding to the operation application is not an operation that requires approval (approval is not required), the process directly proceeds to step S308.

  On the other hand, if it is determined in step S304 that the operation corresponding to the operation application is an operation that requires approval, the operation content corresponding to the operation application is transmitted to the approver PC 400 in step S305, and the operation proceeds to step S306. The process waits until an approval result is received from the approver PC 400. If it is determined that the approval result is received from the approver PC 400, the process proceeds to step S307. The details of the processes in steps S305 and S306 are shown in FIG.

  In step S307, it is determined whether or not the execution of the operation corresponding to the operation application has been approved. If it is determined that the operation has not been approved, the process directly proceeds to step S312.

  On the other hand, if it is determined in step S307 that the execution of the operation corresponding to the operation application has been approved, the process proceeds to step S308, and among the operations waiting for the operation, the exclusive operation is caused by the operation corresponding to the operation application. It is determined whether there is operation request information that becomes. Note that the details of the processing in step S308 are shown in FIG. 13, and thus detailed description thereof is omitted here.

  If it is determined in step S308 that there is an operation that becomes an exclusive operation due to the operation corresponding to the operation application in the operation waiting operation, the process proceeds to step S309, and the operation waiting operation is performed. In particular, a warning notification is sent to the personal terminal 200 that has requested an operation that becomes an exclusive operation due to the operation corresponding to the operation application, and the process proceeds to step S310.

  On the other hand, if it is determined in step S308 that there is no operation that becomes an exclusive operation due to the operation corresponding to the operation application among the operations waiting for operation, the process directly proceeds to step S310.

  In step S310, an operation content execution instruction is transmitted to the operation target PC 300, an execution result is received from the operation target PC 300 (S311), and the process proceeds to step S312. The details of the processes in steps S310 and S311 are shown in FIG.

  In step S312, the operation result report is generated and the DB is registered, and the process is terminated. Note that details of the processing in step S312 are shown in FIG. 15, and detailed description thereof is omitted here.

  In the above embodiment, the configuration has been described in which the operation information management PC 100 generates the application form 160 shown in FIG. 4 when registering the operation request information in the operation request form DB 150. However, in response to an instruction from the administrator or the like. Accordingly, the operation information management PC 100 may create the application form 160 shown in FIG. 4 based on the operation request form DB 150.

  2 shows the case where the operation request application DB 150 shown in FIG. 3 and the operation result report DB 1500 shown in FIG. 15 are mounted on the hard disk 105 of the operation information management PC 100. FIG. The operation request application DB 150 shown and the operation result report DB 1500 shown in FIG. 15 may be mounted on another information processing apparatus with which the operation information management PC 100 can communicate via a network.

  Further, FIG. 1 shows that one operation information management PC 100 manages operation information of one operation target PC 300, but one operation information management PC 100 displays operation information of a plurality of operation target PCs 300. You may comprise so that it may manage.

  A plurality of operation information management PCs 100 may be provided in the information processing apparatus management system.

  Further, the function of the operation information management PC 100 may be implemented in the operation target PC 300.

  Further, the function of the operation information management PC 200 may be installed in the operation target PC 300.

  Further, the operation information management PC 100 may be configured to implement an operation request information creation function of the personal terminal 200.

  In addition, although the configuration in which the personal terminal 200 acquires the information for opening the virtual window 701 from the operation target PC 300 directly from the operation target PC 300 has been described, the information for the personal terminal 200 to open the virtual window 701 from the operation target PC 300 is described. May be obtained from the operation information management PC 100. In this case, the operation information management PC 100 holds the system configuration information of the operation target PC 300 and updates it every time an operation execution instruction is given.

  Further, the configuration in which the personal terminal 200 creates the operation request information by displaying the virtual window 701 illustrated in FIG. 7 and causing the user to operate the virtual window 701 has been described. The operation request information may be created by inputting a command on the command line.

  In the present embodiment, the operation information management PC 100 is configured to sequentially instruct the operation target PC 300 to execute approved and executable operation requests. However, the folder creation “c: ¥ abc” and the folder deletion “c” are performed. : If a plurality of operation requests with canceling operation contents similar to the state where the operation such as “: abc” is not performed are spooled and there is no influence on the other operation waiting operation requests, the above cancellations are canceled. A configuration may be adopted in which a plurality of operation requests are canceled and control is performed so that execution instructions are not given to the operation target PC 300.

  Further, the operation information management PC 100, before instructing execution of a deletion operation such as folder deletion “c: \ abc”, file deletion “c: \ abc \ efg.xyz”, etc., The personal terminal 200 may be configured to transmit a message indicating that the folder / file deletion operation is requested. In this case, it may be a simple warning message, or it may be configured such that whether or not deletion is performed and whether or not the deletion operation is executed is controlled based on a response indicating whether or not deletion is possible.

  In addition, when a user requests a creation operation of a folder, a file, or the like, the user may input an attribute indicating whether or not a deletion operation request is made, and include the attribute in the operation request. . The operation information management PC 100 controls whether or not to send the deletion notification based on this attribute.

  Furthermore, the personal terminal 200 may be configured to transmit (apply) operation request information for each operation, or may be configured to apply for a plurality of operation request information collectively.

  In addition, the personal terminal 200 may have an undo function for performing an operation on the virtual window 701 immediately after the operation on the virtual window 701 in order to create operation request information. Note that after the operation request information has already been transmitted (applied) to the operation information management PC 100, a request to cancel the operation request information is transmitted from the personal terminal 200 to the operation information management PC 100.

  Furthermore, the personal terminal 200 may be configured to perform the operation request information transmission process after the confirmation process by the user.

  Further, the operation information management PC 100 may be configured to process operation requests sequentially in the order of application, and an operation request from a user having a specific authority or higher is configured to be capable of interrupt processing based on a request from the user. Also good.

  Furthermore, the operation information management PC 100 may be configured to cancel an operation request waiting for an operation in response to a request from a user who has made an operation request or a user having administrator authority.

  The information processing apparatus management system of the present invention can be used for the following purposes.

  For example, in the case of conducting a training or the like, it is assumed that PCs are temporarily lent to those who take the training. In such a situation, it is not preferable to give administrative authority to the trainees. Therefore, when changing the setting of the assigned PC, the administrator uses the information processing apparatus management system of the present invention to update the settings of the PCs of the trainees via the remote, temporarily to the trainees. This is used to manage the operation of a PC that has been lent.

  In this case, the PC given to the trainees is the operation target PC 300 in this embodiment. The administrator becomes the “operation requester”, and the PC used by the administrator becomes the personal terminal 200.

  It is also possible to apply for a change in the setting of the PC using the PC to which the trainees themselves have been assigned. In this case, the PCs of the trainees are the personal terminal 200 + the operation target PC 300 in the present embodiment. The administrator becomes an “approver”, and the PC used by the administrator becomes the approver PC 400.

  As a result, in the case of lending a PC to a trainee in a new employee training, etc., when lending a PC temporarily, operation is performed under the control of the administrator without giving the administrator authority to the recipient. Make it possible.

  As described above, the system shown in the present embodiment can perform everything from approval application to operation execution and operation result report when an operation is performed on a PC (operation target PC 300) that requires an approval procedure when performing an operation. This is an information processing device management system that automates workflows, and a series of routines such as the acquisition of operation approvals and the log of operation results that occur when operations such as changing the settings of a server PC such as an ISMS approval acquisition department are performed By automating a simple application process, it is possible to simplify various procedures and reduce the burden of creating and managing application documents.

[Second Embodiment]
In the first embodiment, when it is determined that the new application content has an exclusive problem with the other application content applied before the new application, the new applicant is uniformly asked. Although the configuration for warning is described, even if it is determined that the new application content has an exclusive problem with the other application content applied before the new application, the new applicant is a third party. If the applicant has the authority (cancellation over general authority) to discard the operation application, the new application content may be prioritized over the other application content. . Hereinafter, this embodiment will be described with reference to FIGS.

  In the present embodiment, the authority that allows the new applicant to discard the third-party operation application is an authority higher than the general authority specified in the operation authority list 900 shown in FIG.

  21 and 22 are flowcharts showing an example of a fourth control processing procedure in the information processing apparatus management system of the present invention. Note that the processing of this flowchart corresponds to the processing of an application resident on the operation information management PC 100 in the second embodiment of the present invention, and the hard disk 105 or not shown by the CPU 101 in the operation information management PC 100 shown in FIG. It is executed based on a program stored in a recording medium (storage medium). S301 to S322 indicate each step. Furthermore, the same step number is attached | subjected to the step same as FIG.

  In step S302, if the CPU 101 determines that the operation application has an exclusive problem with other application contents applied before the operation application, in step S313, the authority of the applicant of the operation application Is determined based on the operation authority list 900 shown in FIG.

  In step S313, if the CPU 101 determines that the authority of the applicant of the operation application is general authority, the process proceeds to step S303, and the operation application indicating that the operation corresponding to the operation application is an exclusive operation. The personal terminal 200 that has performed the notification is notified.

  On the other hand, when the CPU 101 determines in step S313 that the authority of the applicant for the operation application is higher than the general authority, the process proceeds to step S314 (FIG. 22).

  Next, in step S314, the CPU 101 issues an operation application cancellation request notification to the application source of the other application to be canceled, and in step S315, the CPU 101 waits for a response for canceling the requested operation application. .

  If the CPU 101 determines in step S315 that the predetermined time has elapsed, the process proceeds to step S316 regardless of whether there is a response, and determines the cancellation request result.

  In step S316, if the CPU 101 determines that the request for canceling the operation application has not been accepted by the application source for the operation to be canceled, in step S317, it is determined that the operation is an exclusive operation for adding application cancellation. The personal terminal 200 that has made the operation application is notified, and the process proceeds to step S304.

  If the CPU 101 determines in step S316 that the request for canceling the operation application has been accepted by the application source for the cancellation target operation, the CPU 101 cancels the application for the cancellation target operation in step S322 and advances the process to step S304. .

  Further, in step S316, if the CPU 101 determines that there is no response from the application source of the operation to be canceled, the process proceeds to step S318 in order to make the operation approver perform the operation cancellation determination on behalf of the person. .

  In step S318, the CPU 101 transmits a cancellation determination request for the operation to be canceled to the approver PC 400, proceeds to step S319, waits until an approval result is received from the approver PC 400, and receives the approval result from the approver PC 400. When it determines with having received, it progresses to step S320.

  In step S320, the CPU 101 determines the result of the cancellation determination request for the operation to be canceled, and if it is determined that the cancel request has not been accepted by the approver PC 400, the process proceeds to step S317.

  On the other hand, if the CPU 101 determines in step S320 that the cancel request has been entrusted by the approver PC 400, the process proceeds to step S321 to issue a notification of cancellation to the applicant for the cancel target operation, and in step S322. Then, the application for the cancellation target operation is canceled, and the process proceeds to step S304.

  By the above processing, even if the new application content is exclusive with other application content applied before the new application, the applicant of the new application content discards the third-party operation application. If you are an applicant who has the authority to do this (above general authority), you can prioritize the new application contents over the other application contents, and flexibly respond to the applicant's authority. Application processing can be performed.

  In this embodiment, when it is determined that the relationship between the requested operation request information and other operation request information applied before the operation request information is an exclusive relationship, the operation authority of the applicant is In the case of higher than general authority, a request has been made to cancel the other application information, and according to the cancellation request result, the other application information is canceled (the other application information is rejected). When it is determined that the relationship between the requested operation request information and the other operation request information applied before the operation request information is an exclusive relationship, the applicant's operation authority applies for the other application information. If it is above the user's operation authority, the other application information is forcibly canceled (the other application information is forcibly rejected), and the notification of the cancellation is sent to the applicant of the other application information. You may comprise so that it may be performed.

[Third Embodiment]
In the first embodiment, the configuration for managing and controlling the operation request has been described. However, based on the operation request stored in the operation request application DB 150 and the operation result stored in the operation result report DB 1500, the operation target PC 300 You may comprise so that the function (automatic audit function) which performs an audit may be provided. The embodiment will be described below.

  First, before executing the automatic audit function, the administrator needs to save the audit start state of the operation target PC 300 as a preparation for starting the audit of the operation target PC 300.

  Hereinafter, with reference to FIG. 23, a process for saving the audit start state of the operation target PC 300 (audit status saving process) will be described.

  FIG. 23 is a flowchart showing an example of a fifth control processing procedure in the information processing apparatus management system of the present invention. Note that the processing of this flowchart corresponds to the processing of an application resident on the operation information management PC 100 in the third embodiment of the present invention, and the hard disk 105 or not shown by the CPU 101 in the operation information management PC 100 shown in FIG. It is executed based on a program stored in a recording medium (storage medium). S401 and S402 indicate each step.

  When the operation target PC 300 is selected from the personal terminal 200 authenticated to be operated by the administrator or the like by an authentication process (not shown) and notified that the start of the audit is instructed, the process is started, and step S401 is started. The CPU 101 transmits a request for acquiring the status information of the operation target PC to the selected operation target PC 300, and the status information of the operation target PC transmitted from the operation target PC 300 (such as the directory configuration and file configuration of the operation target PC 300). All the status information of the operation target PC 300 including the file management information at this time) is received as the audit start status.

  Next, in step S <b> 402, the CPU 101 generates an “audit status” that is an object obtained by virtually constructing the state of the operation target PC from the audit start state of the operation target PC 300 received in step S <b> 401 and stores it in the hard disk 105. The process is terminated.

  Hereinafter, a function (automatic audit process) for auditing the operation target PC based on the operation request information and the operation result information will be described with reference to the flowchart of FIG.

  FIG. 24 is a flowchart showing an example of a sixth control processing procedure in the information processing apparatus management system of the present invention. Note that the processing of this flowchart corresponds to the processing of an application resident on the operation information management PC 100 in the third embodiment of the present invention, and the hard disk 105 or not shown by the CPU 101 in the operation information management PC 100 shown in FIG. It is executed based on a program stored in a recording medium (storage medium). S2-1 to S2-12 indicate each step.

  When the operation target PC 300 is selected from the personal terminal 200 that has been authenticated to be operated by an administrator or the like by an authentication process (not shown), and when it is notified that the execution of the audit process has been instructed, the process starts. In S <b> 2-1, the CPU 101 acquires the audit status of the selected operation target PC 300 from the hard disk 105 and stores it in the memory 102.

  Next, in step S2-2, the CPU 101 acquires the operation request information of the operation target PC 300 from the operation request application DB, and in step S2-3, the operation result report information of the operation target PC 300 from the operation result report DB 1500. Are stored in the memory 102, respectively. In step S2-2, the operation request information issued for the first time after the start of the audit (the operation request information with the oldest issue date after the start of the audit) at the time of the initial processing (at the time of the first round of the loop) At the time of the second and subsequent processing (at the time of processing after the second lap of the loop), operation request information issued at the second and subsequent times after the start of the audit is acquired in order of the date of issue. Similarly, operation result report information is acquired in step S2-3.

  The configuration of the operation result report DB 1500 is shown below.

  FIG. 25 is a schematic diagram showing a record structure of the operation result report DB 1500 shown in FIG.

  As shown in FIG. 25, the operation result report DB 1500 includes an operation result report information ID (ID) 1501, an operation request application application 1502, an operation execution date 1503, an investigation result 1504, and the like.

  The operation result report information ID (ID) 1501 indicates a number that is sequentially given in the order of execution of application contents in the operation information management PC 100. The operation request application ID 1502 indicates the number of the operation request application ID (ID) 151 in the operation request application DB for performing this operation. The operation execution date 1502 corresponds to the date when the operation is executed on the operation target PC 300. The operation result 1504 is a work record indicating the content of the actual operation (for example, “The specified directory has been created. After the specified directory is created, the accessibility is verified.”), The operation is actually performed. Information of the operation target PC 300 after the operation and the work completion status (normal / abnormal).

  Hereinafter, the description returns to the flowchart of FIG.

  Next, in step S2-4, the CPU 101 compares the operation request information acquired in step S2-2 with the operation result report information acquired in step S2-3, and verifies the consistency between the operation request and the operation result. To do.

  If the CPU 101 determines in step S2-4 that the verification result is “match”, the process proceeds directly to step S2-6.

  On the other hand, if the CPU 101 determines in step S2-4 that the verification result is “mismatch”, in step S2-5, the CPU 101 determines that the operation request information acquired in step S2-2 and step S2- 3 is registered in the audit result DB (shown in FIG. 26) that there is an inconsistency in the contents of the operation result report information acquired in step 3 (2601 in FIG. 26), and the process proceeds to step S2-6.

  The audit result DB is an area for temporarily storing defect information exposed in the result of the audit of the operation target PC based on the operation request information and the operation result information, and is stored in the memory 102 or the hard disk 105. Secured and referred to when creating an audit result report shown in FIG. The table contents are shown in FIG. 26 below.

  FIG. 26 is a schematic diagram showing a configuration of an audit result table and a matching type table in an audit result DB held in the memory 102 or the hard disk 105 shown in FIG.

  As shown in FIG. 26, the audit result table of the audit result DB is composed of operation request information ID (corresponding to the operation management number 151 shown in FIG. 3), operation result report information ID, matching ID, and the like.

  When the consistency ID is “−1”, the operation request and the operation result are inconsistent. When the consistency ID is “−2”, the audit status state and the operation result are inconsistent. When the matching ID is “−3”, it indicates that the audit status and the operation target PC are inconsistent.

  Hereinafter, the description returns to the flowchart of FIG.

  Next, in step S2-6, the CPU 101 reflects the contents of the operation request information acquired in step S2-2 to the audit status. In step S2-7, the CPU 101 reflects in step S2-6. The result is compared with the contents of the operation result report information acquired in step S2-3, and the consistency between the reflection result and the operation result is verified.

  If the CPU 101 determines in step S2-7 that the verification result is “match”, the process proceeds directly to step S2-9.

  On the other hand, when the CPU 101 determines in step S2-7 that the verification result is “mismatch”, in step S2-8, the CPU 101 reflects the reflection result in step S2-6 (ie, step S2- 2, the fact that there is a discrepancy between the contents of the operation result report information acquired in step S2-3 is registered in the audit result DB (2602 in FIG. 26). The process proceeds to step S2-9.

  Next, in step S2-9, the CPU 101 determines whether both the operation request information acquired in step S2-2 and the operation result report information acquired in step S2-3 have a remaining number. If it is determined that there is a process, the process returns to step S2-2, and the processes after step S2-2 are repeated.

  On the other hand, if the CPU 101 determines in step S2-9 that both the operation request information acquired in step S2-2 and the operation result report information acquired in step S2-3 have no remaining number, step S2- The process proceeds to 10.

  Next, in step S2-10, the CPU 101 transmits a request for acquiring the status information of the operation target PC to the operation target PC, and returns the status information of the operation target PC returned from the operation target PC 300 (directory configuration of the operation target PC 300). , All the status information of the operation target PC at this point including file management information such as the file structure), and finally updated by the acquired operation target PC 300 and the processing of steps S2-2 to S2-9. Compared with the audit status of the operation target PC 300, the consistency is verified.

  If the CPU 101 determines in step S2-10 that the verification result is “match”, the process proceeds directly to step S2-12.

  On the other hand, if the CPU 101 determines in step S2-10 that the verification result is “inconsistent”, in step S2-11, the CPU 101 checks the audit status verified in step S2-10 and the operation target PC 300. The state difference is registered in the audit result DB (2603 in FIG. 26), and the process proceeds to step S2-12.

  Next, in step S2-12, the CPU 101 creates an audit result report shown in FIG. 27 based on the contents of the audit result DB, stores it in the hard disk 105, and transmits it to the personal terminal 200 that instructed the audit processing. Then, the information is displayed on the monitor 700 of the personal terminal 200, and the process ends.

  FIG. 27 is a schematic diagram showing an example of the audit result report created in step S2-12 in FIG.

  The report 1600 shown in FIG. 27 includes the contents registered in the operation request application DB 150 of the operation request application information by the operation information management PC 100, the contents registered in the investigation result report DB 1500 of the investigation result information by the operation target PC 300, It is assumed that the operation information management PC 100 creates and stores it in the hard disk 105 based on the result of comparing the states of the operation target PC 300.

  27, reference numeral 1601 denotes an audit date, which is generated from the operation execution date 1504 in the operation result report DB 1500 shown in FIG.

  Reference numeral 1602 denotes an audit manager, employee number, department or company name, and is generated based on user information when an audit execution is instructed from the personal terminal 200.

  Further, reference numeral 1603 denotes information such as a target department, a target server, an audit reason, an audit target resource, an audit target period, and remarks.

  Reference numeral 1604 denotes an audit start date, an audit end date, and an audit required time, which are generated based on the time when the operation information management PC 100 started the audit, the time when the audit was completed, and the time required for the audit. An audit result 1605 is generated based on a difference between the operation request application DB 150 shown in FIG. 3 and the operation result report DB 1500 shown in FIG.

  With the above processing, the administrator etc. can manually audit the operation target PC 300 based on the operation request stored in the operation request application DB 150 and the operation result stored in the operation result report DB 1500 simply by giving an audit instruction. This can be done without going through the process, and the auditing work can be made more efficient.

  In the present embodiment, the configuration in which the audit process is registered in the audit result DB only in the case of inconsistency has been described, but the configuration in which both the consistency and the inconsistency are registered in the audit result DB is described. May be. FIG. 28 shows an audit result DB in which both cases of matching and mismatching are registered.

  FIG. 28 is a schematic diagram showing the structure of the audit result table and the consistency type table of the audit result DB held in the memory 102 or the hard disk 105 shown in FIG. 1, and both cases of matching and mismatching are registered. Corresponds to the case.

  As shown in FIG. 28, when the consistency ID is “0”, the operation request and the operation result are consistent, and when the consistency ID is “1”, the audit status state and the operation result are consistent. When the consistency ID is “2”, it indicates that the audit status and the operation target PC are consistent.

  When the consistency ID is “−1”, the operation request and the operation result are inconsistent. When the consistency ID is “−2”, the audit status state and the operation result are inconsistent. When the matching ID is “−3”, it indicates that the audit status and the operation target PC are inconsistent.

[Fourth Embodiment]
In the first embodiment, the configuration for managing and controlling the operation request has been described. However, based on the operation request stored in the operation request application DB 150 and the operation result stored in the operation result report DB 1500, the operation target PC 300 You may comprise so that the function (past condition reference function) which refers the past condition may be provided. The embodiment will be described below.

  First, before executing the past situation reference function, the administrator needs to save the operation start state of the operation target PC as preparation for operation start of the operation target PC.

  Hereinafter, with reference to FIG. 29, a process for storing the operation start state of the operation target PC 300 (operation status storage process) will be described.

  FIG. 29 is a flowchart showing an example of a seventh control processing procedure in the information processing apparatus management system of the present invention. Note that the processing of this flowchart corresponds to the processing of an application resident on the operation information management PC 100 in the fourth embodiment of the present invention, and the hard disk 105 or not shown by the CPU 101 in the operation information management PC 100 shown in FIG. It is executed based on a program stored in a recording medium (storage medium). S501 and S502 indicate the respective steps.

  When the operation target PC is selected from the personal terminal 200 that has been authenticated by an administrator (not shown) and is instructed to start the operation, the process is started. Step S501 The CPU 101 transmits an acquisition request for the status information of the operation target PC 300 to the selected operation target PC 300, and the status information of the operation target PC 300 transmitted from the operation target PC 300 (such as the directory configuration and file configuration of the operation target PC 300). All the state information of the operation target PC 300 including the file management information at this time) is received as the operation start state.

  Next, in step S <b> 502, the CPU 101 generates an “operation status” that is an object obtained by virtually constructing the state of the operation target PC from the operation start state of the operation target PC 300 received in step S <b> 501 and saves it in the hard disk 105. The process is terminated.

  Hereinafter, a function (past situation reference process) for referring to the past situation of the operation target PC based on the operation request information and the operation result information will be described with reference to the flowchart of FIG.

  FIG. 30 is a flowchart showing an example of an eighth control processing procedure in the information processing apparatus management system of the present invention. Note that the processing of this flowchart corresponds to the processing of an application resident on the operation information management PC 100 in the fourth embodiment of the present invention, and the hard disk 105 or not shown by the CPU 101 in the operation information management PC 100 shown in FIG. It is executed based on a program stored in a recording medium (storage medium). S3-1 to S3-9 indicate each step.

  When the operation target PC 300 is selected from the personal terminal 200 and notified that execution of the operation status reference process is instructed, the process starts. In step S3-1, the CPU 101 operates the selected operation object PC 300. The status is acquired from the hard disk 105 and held on the memory 102.

  Next, in step S <b> 3-2, the CPU 101 acquires the state reference date and time of the operation target PC 300 from the personal terminal 200 that has instructed the past situation reference process.

  Next, in step S3-3, the CPU 101 acquires the operation request information of the operation target PC 300 from the operation request application DB, and in step S3-4, the operation result report information of the operation target PC 300 from the operation result report DB 1500. Are stored in the memory 102, respectively. In step S3-3, the operation request information issued for the first time after the start of the operation (the operation request information with the oldest issue date after the start of operation) at the time of the initial processing (at the time of the first round of the loop) During the second and subsequent processing (during the second and subsequent rounds of the loop), operation request information issued after the second operation is acquired in order of date of issue. Similarly, operation result report information is acquired in step S3-4.

  Next, in step S3-5, the CPU 101 refers to the operation result report information acquired in step S3-4, and determines whether or not the operation request information acquired in step S3-3 has been applied to the operation target PC 300. . This determination is made because the operation may be denied by the approver.

  If the CPU 101 determines in step S3-5 that the operation request acquired in step S3-3 has been applied to the operation target PC 300, in step S3-6, the CPU 101 displays the operation request content in the operation status. Is reflected, and the process proceeds to step S3-7.

  On the other hand, if the CPU 101 determines in step S3-5 that the operation request acquired in step S3-3 has not been applied to the operation target PC 300, the process directly proceeds to step S3-7.

  Next, in step S3-7, the CPU 101 determines whether both the operation request information acquired in step S3-3 and the operation result report information acquired in step S3-4 have a remaining number. If it is determined that there is, there is a return to step S3-3, and the processing after step S3-3 is repeated.

  On the other hand, if the CPU 101 determines in step S3-7 that both the operation request information acquired in step S3-3 and the operation result report information acquired in step S3-4 have no remaining number, step S3- Proceed to step 8.

  In step S3-8, the CPU 101 constructs a virtual UI of the operation target PC 300 based on the operation status of the operation target PC that is finally updated by the processing in steps S3-3 to S3-7. The status reference date and time of the virtual UI is stored in the memory 102 or the hard disk 105 as “display status status date”.

  In step S3-9, the CPU 101 transmits the virtual UI screen (shown in FIG. 31) of the operation target PC 300 constructed in step S3-8 to the personal terminal 200 that has instructed the past situation reference process. The information is displayed on the monitor 700 of 200, and the process is terminated.

  FIG. 31 is a schematic diagram illustrating an example of a virtual UI screen of the operation target PC 300 displayed on the monitor 700 of the personal terminal 200 in step S3-9 in FIG.

  On the virtual UI screen 3101 shown in FIG. 31, the user can perform the same operation as that actually performed on the operation target PC 300. By performing an operation on the virtual UI screen 3101, the past of the operation target PC 300 is displayed. You can refer to the situation.

  In the virtual UI 3101, reference numeral 3102 denotes a display desktop date and time, which indicates “the status date and time of the operation target PC displayed on the virtual UI screen”. This display desktop date and time 3102 can be changed by directly inputting a desired date and time using a pointing device and a keyboard (not shown) of the personal terminal 200. The display desktop date and time 3102 can also be changed by instructing 3103 and 3104 with a pointing device (not shown) of the personal terminal 200. When the display desktop date and time 3102 is changed, the changed display desktop date and time 3102 is transmitted from the personal terminal 200 to the operation information management PC 100 as “the status date and time of the operation target PC displayed on the virtual UI screen”. A new virtual UI screen corresponding to the transmitted “status date and time of the operation target PC displayed on the virtual UI screen” is generated by the operation information management PC 100 and returned to the personal terminal 200 (virtual UI display date switching processing). The virtual UI display date / time switching process is shown in FIG.

  FIG. 32 is a flowchart showing an example of a ninth control processing procedure in the information processing apparatus management system of the present invention. Note that the processing of this flowchart corresponds to the processing of an application resident on the operation information management PC 100 in the fourth embodiment of the present invention, and the hard disk 105 or not shown by the CPU 101 in the operation information management PC 100 shown in FIG. It is executed based on a program stored in a recording medium (storage medium). S601 to S611 indicate each step.

  First, when the “status date and time of the operation target PC to be displayed on the virtual UI screen” transmitted from the personal terminal 200 is received, the processing is started, and in step S601, the CPU 101 displays the received “operation target to be displayed on the virtual UI screen. PC status date and time ”is acquired.

  Next, in step S <b> 602, the CPU 101 compares the “status date / time of the operation target PC displayed on the virtual UI screen” with the “display status status date / time”, and the “display status status date / time” is the “virtual UI screen”. If it is determined that it is newer than the “state date and time of the operation target PC to be displayed”, the process proceeds to step S603.

  In steps S <b> 603 and S <b> 604, the CPU 101 obtains the latest operation request information and operation result report information before “display status state date” and after “operation target PC state date displayed on the virtual UI screen”. Then, the process proceeds to step S605. Although not shown in the flowchart, in steps S603 and S604, the latest operation request information before “display status status date” and after “operation target PC status date displayed on virtual UI screen”. If the operation result report information does not exist, the “display status state date and time” is updated to “the operation target PC state date and time displayed on the virtual UI screen”, and the process returns to step S602.

  Next, in step S605, the CPU 101 refers to the operation result report information acquired in step S604, determines whether the operation request information acquired in step S603 has been applied to the operation target PC, and determines that the operation has been applied. In step S606, the CPU 101 deletes the reflection of the contents of the operation request from the operation status, updates the “display status state date and time” to the date and time of the operation request information acquired in step S603, and proceeds to step S602. The processing is returned, and the processing of steps S603 to S606 is repeated until the date and time of the "status date and time of the operation target PC displayed on the virtual UI screen" and the "display status status date and time" become equal.

  On the other hand, if the CPU 101 determines in step S605 that the operation request information acquired in step S603 has not been applied to the operation target PC, the “display status state date” is stored in the operation request information acquired in step S603. The date is updated, and the process returns to step S602.

  If the CPU 101 determines in step S602 that the “display status state date” is older than the “operation target PC state date displayed on the virtual UI screen”, the process proceeds to step S607.

  In steps S <b> 607 and S <b> 608, the CPU 101 obtains the oldest operation request information and operation result report information after “display status state date” and before “operation target PC state date displayed on the virtual UI screen”. Then, the process proceeds to step S609. Although not shown in the flowchart, in steps S607 and S608, the oldest operation request information after “display status state date” and before “operation target PC state date displayed on virtual UI screen”. If the operation result report information does not exist, the “display status state date and time” is updated to “the operation target PC state date and time displayed on the virtual UI screen”, and the process returns to step S602.

  Next, in step S609, the CPU 101 refers to the operation result report information acquired in step S608, determines whether the operation request information acquired in step S607 has been applied to the operation target PC, and determines that the operation has been applied. In step S610, the CPU 101 reflects the contents of the operation request in the operation status, updates the “display status state date and time” to the date and time of the operation request information acquired in step S607, and performs the process in step S602. The processing in steps S607 to S610 is repeated until the “status date and time of the operation target PC displayed on the virtual UI screen” is equal to the “status date and time of the display status”.

  On the other hand, if the CPU 101 determines in step S609 that the operation request information acquired in step S607 has not been applied to the operation target PC, the “display status state date” is stored in the operation request information acquired in step S607. The date is updated, and the process returns to step S602.

  If the CPU 101 determines in step S602 that the “display status state date and time” and the “operation target PC state date and time displayed on the virtual UI screen” are equal, in step S611, the CPU 101 determines the operation status. Based on the above, the virtual UI of the operation target PC is constructed, the virtual UI screen of the constructed operation target PC is transmitted to the personal terminal 200 and displayed on the monitor 700 of the personal terminal 200, and the process is terminated.

  With the above processing, simply by instructing the state reference date and time of the operation target PC, the operation target PC can be stored based on the operation request stored in the operation request application DB 150 and the operation result stored in the operation result report information DB 1500. It is possible to easily refer to the past state.

  In this embodiment, the operation status at a predetermined time point is stored, and the operation based on the operation request information and the operation result report information is reflected on the stored operation status at the predetermined time point. The configuration of reproducing the past state of the operation target PC so as to be virtually operable has been described. However, the operation status is generated from the state of the operation target PC at the past situation reference time, and the operation status is generated from the generated operation status. The reflection of the operation based on the request information and the operation result report information may be deleted, and the past state of the operation target PC may be reproduced so as to be virtually operable.

  Further, in the operation on the operation request information creation screen (virtual window) 701 shown in FIG. 7, a change operation in each file stored in the operation target PC can be performed. The operation request information generated by the change operation in the file includes the request for the change in each file stored in the operation target PC (that is, the operation result report information also includes the operation target information). The operation result of the change in each file saved in the PC is included), and the contents of the past file of the operation target PC are also restored by reflecting the operation based on the operation request information and the operation result report information. can do.

  In addition, all the structures which combined all or each of any modification of each embodiment are also included in this invention.

  Further, the configuration and contents of the various data shown are not limited to this, and it is needless to say that the various data and configurations are configured according to applications and purposes.

  Although one embodiment has been described above, the present invention can take an embodiment as, for example, a system, apparatus, method, program, or recording medium, and specifically includes a plurality of devices. The present invention may be applied to a system including a single device.

  Hereinafter, differences between Patent Document 1 shown in the background art column and the information processing apparatus management system shown in the present embodiment will be described.

  Patent Document 1 automates an approval process for updating data that requires administrator approval, and updates data with a monitoring condition that permits data update on condition that the administrator has received approval. It is described that the approval request can be automated.

  On the other hand, in the information processing apparatus management system shown in the present embodiment, an operation approval acquisition / operation result and the like when an operation such as a setting change of an information processing apparatus such as a server is performed in an ISMS approval acquisition department is left as a log A typical application process such as the above is automated. First, in this respect, it is greatly different from the one that merely manages the approval of data update.

  That is, the purpose of Patent Document 1 is merely to automate the approval process at the time of data update and the update process at the time of receiving the approval, not to store and manage the approval acquisition / processing result as a log, There is no description about such a log management configuration. Therefore, the information processing apparatus management system according to the present embodiment cannot be configured even if the data update described in Patent Document 1 is replaced with an operation on the information processing apparatus.

  Since the information processing apparatus management system according to the present embodiment has the log management configuration described above, operation approval acquisition and operation results when an operation such as setting change of an information processing apparatus such as a server is performed in an ISMS approval acquisition department, etc. In addition to automating routine application processes, such as leaving a log as a log, it is possible to create and manage approval documents defined by the ISMS approval acquisition department.

  Further, in the information processing apparatus management system according to the present embodiment, when it is determined that the relationship between the requested operation request and another operation request applied before the operation request is an exclusive relationship, Information indicating this is notified to the operation requesting apparatus that is the transmission source of the operation request information, and such a configuration is not disclosed or suggested in the above-mentioned Patent Document 1.

  As described above, the above-described Patent Document 1 and the information processing apparatus management system according to this embodiment are different in all purposes, configurations, and effects.

  The points described above are considered matters to be particularly noted when considering the difference between the information processing apparatus management system shown in the present embodiment and the above-mentioned Patent Document 1.

  Hereinafter, the configuration of a data processing program that can be read by an apparatus constituting the information processing apparatus management system according to the present invention will be described with reference to the memory map shown in FIG.

  FIG. 33 is a diagram for explaining a memory map of a recording medium (storage medium) for storing various data processing programs that can be read (read) by an apparatus constituting the information processing apparatus management system according to the present invention.

  Although not specifically shown, information for managing a program group stored in the recording medium, for example, version information, creator, etc. is also stored, and information depending on the OS on the program reading side, for example, a program is identified and displayed. Icons may also be stored.

  Further, data depending on various programs is also managed in the directory. In addition, when a program or data to be installed is compressed, a program to be decompressed may be stored.

  The functions shown in FIGS. 18, 19, 20, 21, 22, 23, 24, 29, 30, and 32 in this embodiment are performed by a host computer by a program installed from the outside. It may be. In this case, the present invention is applied even when an information group including a program is supplied to the output device from a recording medium such as a CD-ROM, a flash memory, or an FD, or from an external recording medium via a network. Is.

  As described above, a recording medium in which a program code of software for realizing the functions of the above-described embodiments is recorded is supplied to the system or apparatus, and the computer (or CPU or MPU) of the system or apparatus is stored in the recording medium. It goes without saying that the object of the present invention can also be achieved by reading and executing the program code.

  In this case, the program code itself read from the recording medium realizes the novel function of the present invention, and the recording medium storing the program code constitutes the present invention.

  As a recording medium for supplying the program code, for example, a flexible disk, hard disk, optical disk, magneto-optical disk, CD-ROM, CD-R, DVD-ROM, magnetic tape, nonvolatile memory card, ROM, EEPROM, A silicon disk or the like can be used.

  Further, by executing the program code read by the computer, not only the functions of the above-described embodiments are realized, but also an OS (operating system) or the like running on the computer based on the instruction of the program code. It goes without saying that a case where the function of the above-described embodiment is realized by performing part or all of the actual processing and the processing is included.

  Furthermore, after the program code read from the recording medium is written in a memory provided in a function expansion board inserted in the computer or a function expansion unit connected to the computer, the function expansion is performed based on the instruction of the program code. It goes without saying that the case where the CPU or the like provided in the board or the function expansion unit performs part or all of the actual processing and the functions of the above-described embodiments are realized by the processing.

  Further, the present invention may be applied to a system composed of a plurality of devices or an apparatus composed of a single device. Needless to say, the present invention can be applied to a case where the present invention is achieved by supplying a program to a system or apparatus. In this case, by reading a recording medium storing a program represented by software for achieving the present invention into the system or apparatus, the system or apparatus can enjoy the effects of the present invention.

  Furthermore, by downloading and reading out a program represented by software for achieving the present invention from a server, database, etc. on a network using a communication program, the system or apparatus can enjoy the effects of the present invention. It becomes.

  By setting the operation target PC 300 as an information processing apparatus in the ISMS approval acquisition department, the information processing apparatus management system of the present embodiment leaves a log of the operation acquisition acquisition / operation result of the information processing apparatus operation in the ISMS approval acquisition department, etc. It can be applied to automating routine application processes.

1 is a system configuration diagram illustrating an example of an information processing device management system according to a first embodiment of this invention. It is a block diagram which shows the structure of the operation information management PC shown in FIG. It is a schematic diagram which shows the record structure of the operation request application DB shown in FIG. It is a schematic diagram which shows an example of the application corresponding to the application file name shown in FIG. It is a flowchart explaining a series of processes from the application of the operation request to the operation result report in the management system shown in FIG. It is a figure which shows in detail the preparation and application procedure of the operation request information shown in step S1 of FIG. It is a schematic diagram which shows an example of the creation screen (virtual window) of operation request information. It is a figure which shows preparation of operation request information (preceding request) in detail. It is a figure which shows in detail the authority verification procedure of the operation requester shown to step S3 of FIG. It is a figure which shows in detail the exclusive verification and notification procedure with the other operation application shown to step S4, S5 of FIG. It is a figure which shows in detail the determination procedure of operation which requires the approval shown to step S6 of FIG. It is a figure which shows the operation approval confirmation procedure shown to step S7, S8 of FIG. 5 in detail. It is a figure which shows the exclusive verification procedure of the approval operation shown to FIG.5 S10 in detail. FIG. 6 is a diagram showing in detail a procedure for reflecting the operation content shown in step S12 of FIG. It is a figure which shows the operation result report preparation procedure shown in step S13 of FIG. 5 in detail. It is a schematic diagram explaining the PC operation workflow in the management system of this invention. It is a schematic diagram explaining the PC operation workflow in the management system of this invention. It is a flowchart which shows an example of the 1st control processing procedure in the information processing apparatus management system of this invention. It is a flowchart which shows an example of the 2nd control processing procedure in the information processing apparatus management system of this invention. It is a flowchart which shows an example of the 3rd control processing procedure in the information processing apparatus management system of this invention. It is a flowchart which shows an example of the 4th control processing procedure in the information processing apparatus management system of this invention. It is a flowchart which shows an example of the 4th control processing procedure in the information processing apparatus management system of this invention. It is a flowchart which shows an example of the 5th control processing procedure in the information processing apparatus management system of this invention. It is a flowchart which shows an example of the 6th control processing procedure in the information processing apparatus management system of this invention. It is a schematic diagram which shows the record structure of operation result report DB shown in FIG. FIG. 2 is a schematic diagram illustrating a configuration of an audit result table and a matching type table of an audit result DB held in the memory or the hard disk illustrated in FIG. 1. It is a schematic diagram which shows an example of the audit result report produced by step S2-12 of FIG. FIG. 2 is a schematic diagram illustrating a configuration of an audit result table and a matching type table of an audit result DB held in the memory or the hard disk illustrated in FIG. 1. It is a flowchart which shows an example of the 7th control processing procedure in the information processing apparatus management system of this invention. It is a flowchart which shows an example of the 8th control processing procedure in the information processing apparatus management system of this invention. It is a schematic diagram which shows an example of the virtual UI screen of operation target PC displayed on the monitor of a personal terminal in step S3-9 of FIG. It is a flowchart which shows an example of the 9th control processing procedure in the information processing apparatus management system of this invention. It is a figure explaining the memory map of the recording medium (storage medium) which stores the various data processing program which can be read (read) with the apparatus which comprises the information processing apparatus management system which concerns on this invention.

Explanation of symbols

100 Operation information management PC
150 Operation Request Application DB
200 Personal terminal 300 Operation target PC
400 Approved PC

Claims (16)

An operation request device that applies an operation request to an operation target device that requires an approval procedure when performing an operation, an operation information management device that manages the applied operation request, and an approval device that approves the applied operation request And an information processing apparatus management system in which the operation target apparatus is communicably connected,
The operation information management device includes:
First storage means for sequentially storing and managing the requested operation request information;
Approval confirmation means for requesting the approval device to confirm whether or not the approval for the requested operation request information is permitted;
Reflecting means for transmitting an operation execution instruction corresponding to the operation request information confirmed to be approved by the approval confirmation means to the operation target device and acquiring the execution result;
An information processing apparatus management system comprising:   The operation information management device includes operation request information transmitted from the operation request device, an approval result of the operation request information, and a result registration unit for registering and controlling the reflection result of the operation request information in the first storage unit. The information processing apparatus management system according to claim 1, further comprising:   The information processing apparatus management system according to claim 1, wherein the operation information management apparatus includes a result report unit that transmits a reflection result of the operation request information to an information processing apparatus of a predetermined administrator. The operation information management device includes:
The relationship between the requested operation request information and other operation request information applied before the operation request information is an exclusive relationship in which an operation executed later by an operation executed earlier cannot be executed. First determination means for determining whether or not there is;
When it is determined that the relationship between the operation request information applied by the first determination unit and other operation request information applied before the operation request information is an exclusive relationship, A first refusal means for refusing the application;
The information processing apparatus management system according to claim 1, further comprising:   Assuming that the operation request information can be reflected by the reflecting means, the first storage means can store related next operation request information before the approval of the operation request information. The information processing apparatus management system according to claim 1. The operation request information includes information on the applicant,
The operation information management device includes:
A second storage means for storing operation authority information assigned to each applicant;
Based on the operation authority information stored in the second storage means, second determination means for determining whether or not the requested operation request information is applied by an authorized applicant;
When it is determined by the second determination means that the operation request information is not applied by an authorized applicant, information indicating that is notified to the operation request apparatus that is the transmission source of the operation request information First notification means;
The information processing apparatus management system according to claim 1, comprising: The operation information management device includes:
Third storage means storing authority information that can be operated without approval for each operation content;
Based on the authority information stored in the second storage means and the operation authority information that can be operated without approval stored in the third storage means, the requested operation request information can be operated without approval. And a third determination means for determining whether or not the application has been made by an applicant having a proper operation authority,
If it is determined by the third determination means that the requested operation request information has been applied by an applicant who has an operation authority that can be operated without approval, the approval confirmation means 7. The information processing apparatus management system according to claim 6, wherein approval confirmation for the request information is omitted. The operation information management device includes:
When reflecting the operation request information to the operation target device by the reflecting means, the relationship between the operation request information and other operation request information waiting to be executed after the operation request information is executed first. A fourth determination means for determining whether or not the operation executed later by the operation is an exclusive relationship in which the operation cannot be executed;
When it is determined by the fourth determination means that the relationship between the operation request information and other operation request information executed after the operation request information is an exclusive relationship, information indicating that is displayed in the operation Second notification means for notifying the operation requesting device that is the transmission source of other operation request information that has an exclusive relationship with the request information;
The information processing apparatus management system according to claim 1, comprising: The operation information management device includes:
A fourth storage unit that stores an approval type for each operation content;
9. The approval confirmation unit changes and controls an approval confirmation method for the applied operation request information based on an approval type stored in the fourth storage unit. Information processing apparatus management system described in 1. The operation request device is:
Obtaining means for obtaining system configuration information of the operation target device;
Display means for displaying a virtual operation screen capable of virtually operating the operation target device based on the system configuration information acquired by the acquisition means;
Creating means for creating operation request information for the operation target device based on a virtual operation on the virtual operation screen displayed by the display means;
Application means for sending the operation request information created by the creation means to the operation information management device for application;
The information processing apparatus management system according to claim 1, comprising: The operation information management device includes:
A second storage means for storing operation authority information assigned to each applicant;
The relationship between the requested operation request information and other operation request information applied before the operation request information is an exclusive relationship in which an operation executed later by an operation executed earlier cannot be executed. First determination means for determining whether or not there is;
When it is determined that the relationship between the operation request information applied by the first determination means and other operation request information applied before the operation request information is an exclusive relationship, the second storage means A second refusal means for refusing the other operation request information according to the stored operation authority of the applicant;
The information processing apparatus management system according to claim 1, further comprising: The operation information management device includes:
Based on the system configuration information of the operation target device at a predetermined time, the operation request information stored in the first storage means, and the reflection result of the operation request information, the consistency of the operation target device is maintained. The information processing apparatus management system according to claim 2, further comprising confirmation means for confirming whether or not the information exists. The operation information management device includes:
Based on the system configuration information at a predetermined time of the operation target device, the operation request information stored in the first storage unit, and a reflection result of the operation request information, the past state of the operation target device is virtually determined. The information processing apparatus management system according to any one of claims 1 to 12, further comprising reproduction means for reproducing in an operable manner. An operation request device that applies an operation request to an operation target device that requires an approval procedure when performing an operation, an operation information management device that has a first storage unit that sequentially stores and manages the applied operation request information, and an application In an information processing apparatus management method in an information processing apparatus management system in which an approval apparatus that approves an operation request that has been made and the operation target apparatus are connected to be communicable,
An approval confirmation step in the operation information management device for requesting and confirming whether or not the approval device is approved for the requested operation request information;
A reflection step of transmitting an operation execution instruction corresponding to the operation request information approved in the approval confirmation step to the operation target device and acquiring the execution result;
A result registration step of registering the operation request information transmitted from the operation request device, the approval result of the operation request information, and the reflection result of the operation request information in the first storage unit;
An information processing apparatus management method characterized by comprising:   A program for executing the information processing apparatus management method according to claim 14.   A recording medium storing a computer-readable program for executing the information processing apparatus management method according to claim 14.