JP2013127656A - Operation procedure creation support system and creation method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To present a correction place corresponding to the change point of configuration information with respect to the operation procedure of an information system when changing the configuration information of the information system.SOLUTION: A component creation function 110 of an operation procedure design server 101 for supporting the creation of the operation procedure of an information system makes common procedures into components from the past operation procedures, and creates a procedure component DB 120 in a storage 102. Also, a configuration management function 111 defines a correspondence relation between each procedure component and system configuration information and operation information which is prerequisite for the procedure component, and creates a configuration requirement tree 121. A correction evaluation function 114 evaluates the change necessity of procedure components used in the already created operation procedure when any change is generated in the configuration of the information system, and presents an influential part corresponding to a change in the operation procedure and correction content corresponding to the configuration change.

Description

  The present invention relates to an operation procedure creation support technique for supporting creation of operation / operation procedures for devices such as servers in a data center or the like.

  With the rapid development and spread of communication networks, cloud computing that realizes the use of information systems via networks is rapidly spreading. As a result, the cost of operation management is becoming a major problem due to the expansion of the scale of data centers storing information systems and the development of global bases. For example, in data center operation management, device operation status check, restart, batch processing, disk backup, response in case of abnormalities, customer reports for those operations, etc. for a large number of servers and network devices The contents of operations are wide, and not only IT equipment such as servers but also air conditioning and power supply management, security monitoring and entry / exit management are indispensable.

  Therefore, with the aim of reducing operational management costs, centralized system operational management using operational management middleware, standardization of operational management processes using ITIL (Information Technology Library), and automation of operational procedures through runbook automation (Run Book Automation) In addition, efforts have been made to improve operational management efficiency such as collective management of configuration information using CMDB (Configuration Management Database). Although these tools and management methods realize labor saving of device operation and device management in the operation phase, it is necessary to design the operation content and management content of the device as an operation procedure before the operation phase. Up to now, the design of the operation procedure can be made manually using spreadsheet software or CAD software as the operation procedure manual, understanding the target system configuration and operating the system. It was mainstream.

  However, manual creation of operation procedure manuals is very laborious, and as a method for improving the efficiency of creation of such operation procedure manuals, in the process of creating device manuals, a common procedure from past product manuals is used. There has been proposed a method of creating a manual by combining the parts into parts.

  For example, Patent Document 1 is a device that supports creation of a manual based on device specifications, and defines a method for defining a manual portion from a past manual and extracting the manual portion from a keyword corresponding to the device specification. Disclosure. Further, in Patent Document 2, a method for determining item-specific index data determined according to items such as chapters, paragraphs, parts, etc. according to the specifications of a product in order to create a product manual. Disclosure.

JP 2006-277460 A JP 2007-26391 A

  As described above, in the process of designing the operation procedure of the information system, it is required to facilitate the creation thereof. In addition, it is a big problem that the effort to maintain the created operation procedure is large. In general, the functions of an information system are frequently changed due to the upgrade of the device configuration, tools, and application software, and it is necessary to reflect them in the operation procedure each time. This is because it is difficult to know which part of the operation procedure manual will be changed in response to the change, and it is necessary to check the operation procedure manual on the desk or to use the search function of a general-purpose tool to search for corrections sequentially. Because it takes. However, in the prior art, it has not been studied how to efficiently modify and change the current manual when the specification is changed.

  An object of the present invention is to solve the above-described problems and provide an operation procedure creation support system and method that efficiently supports creation of an operation procedure associated with a configuration change of an information system.

In order to achieve the above object, according to the present invention, there is provided an operation procedure creation support system using an information processing device that supports creation of an operation procedure for an information system. The procedure parts that are converted into parts, and the configuration requirements that make up the information system that are to be operated by the procedure parts are stored, and the configuration that the procedure parts become the operation target when a change occurs in the configuration of the information system Provided is an operation procedure creation support system that evaluates the necessity of modification to a requirement and outputs a correction range to the operation procedure for a change occurring in the configuration of the information system based on the evaluation result.

  Further, in order to achieve the above purpose, an operation procedure creation method in an operation procedure creation support system for supporting creation of an operation procedure for an information system, wherein a common procedure of the operation procedure is a procedure component, and the procedure component and , Memorize the configuration requirements that constitute the information system that the procedure component is the operation target, create a new operation procedure by combining the procedure components, and change the configuration of the information system, the procedure component Provides an operation procedure creation method that evaluates the necessity of correction of a configuration requirement to be operated and outputs a correction range to the operation procedure for a change that has occurred in the configuration of the information system based on the evaluation result.

  When supporting the creation of an information system operation procedure, by evaluating the necessity of changing the procedure parts used in the operation procedure, the affected part of the change in the operation procedure and the contents of correction corresponding to the configuration change are presented. be able to. As a result, not only the creation of the operation procedure manual, but also the efficiency of the modification of the operation procedure manual at the time of configuration change can be improved, and the maintenance of the operation procedure manual can be facilitated.

It is a figure explaining the whole structure of the operation procedure preparation assistance system based on a 1st Example. It is a figure explaining the typical structural example of the server based on a 1st Example. It is a figure explaining the processing flow of the component preparation function based on a 1st Example. It is a figure explaining the component requirement tree based on a 1st Example. It is a figure explaining the component requirement tree based on a 1st Example. It is a figure explaining the component requirement tree based on a 1st Example. It is a figure explaining an example of the information of a procedure component based on a 1st Example. It is a figure explaining an example of composition requirements concerning the 1st example. It is a figure explaining the other example of the information of a procedure component based on a 1st Example. It is a figure explaining other examples of composition requirements concerning the 1st example. It is a figure explaining the other example of the information of a procedure component based on a 1st Example. It is a figure explaining other examples of composition requirements concerning the 1st example. It is a figure explaining the other example of the information of a procedure component based on a 1st Example. It is a figure explaining other examples of composition requirements concerning the 1st example. It is a figure explaining the order relevance definition of a procedure component based on a 1st Example. It is a figure explaining the processing flow of the components search function based on a 1st Example. It is a figure explaining the operation content inputted at the time of procedure creation concerning the 1st example. It is a figure explaining the system configuration information input at the time of procedure creation based on a 1st Example. It is a figure explaining the operation information inputted at the time of procedure creation concerning the 1st example. It is a figure explaining the created operation procedure based on a 1st Example. It is the figure which showed the processing flow of the procedure verification function based on 1st Example. It is the figure which showed the result of having extracted the procedure flow from the produced operation procedure based on a 1st Example. It is a figure explaining an example of the processing flow of the procedure correction function based on 1st Example. It is a figure explaining the screen which inputs system configuration information based on a 1st Example. It is a figure explaining the screen which edits an operation procedure manual based on a 1st Example. It is a figure explaining the screen which selects a procedure component based on a 1st Example. It is a figure explaining the screen of the correction evaluation function which shows the influence range with respect to the operation procedure manual accompanying a structure change based on a 1st Example.

  Embodiments of the present invention will be described below with reference to the drawings. In this specification, the procedure part means a part obtained by dividing / extracting the operation procedure in a certain unit from the operation procedure manual, and the parameter element means various parameters determined when the procedure part is used. Indicates an item. The configuration requirement means a requirement related to a configuration of a server device, a disk device, a software tool, and the like constituting the information system. The component in the configuration requirement indicates a processing unit, memory, operating system, interface, software tool version information, etc. constituting the server device, disk device, software tool, etc. The configuration information in the configuration requirement is a procedure It corresponds to a parameter element in a part, and indicates an identification name, a tool name, a drive name, a management number, etc. of a server device, a disk device, a software tool, etc. constituting the information system.

  As a first embodiment, an embodiment relating to an operation procedure creation support system will be described.

<Overall configuration>
FIG. 1 is a diagram illustrating an overall configuration example of the operation procedure creation support system according to the first embodiment. This system includes an operation procedure design server 101 that executes various functions 110 to 115 for supporting design of operation procedures, and a storage 102 that holds various databases 120 to 124 that are used / output by various functions that support design. Is done. The operation procedure design server 101 and the storage 102 are connected via a network 104. A user who designs an operation procedure performs various operations on the operation terminal 103 connected to the operation procedure design server 101.

  The configuration of this system is not limited to the configuration shown in this figure. For example, some functions are executed by another server connected via a network, or some database information May be stored in another storage connected via a network. Each function 110-116 and various databases (DB) 120-126 of the procedure design server are hosted in the data center, and the operation terminal 103 is connected to the data center via the network, so that it can be used remotely as a cloud service. Also good.

  The various functions that support the operation of this system include a part creation function 110 that creates an operation procedure as a part, a configuration management function 111 that manages configuration information of an operation target device, a procedure creation function 112 that creates and edits an operation procedure, A procedure verification function 113 that verifies the created operation procedure, a modification evaluation function 114 that evaluates the influence of the change on the operation procedure created when the configuration and operation contents of the operation target device are modified, and creates an operation procedure In this case, the part search function 115 for searching for a procedure part candidate corresponding to the contents of the operation procedure and the configuration of the operation target device from the procedure parts created by the part creation function 110, the created procedure is determined for a paper or an electronic terminal by default. A procedure output function 116 for converting and outputting the format. Details of each function will be described later.

  In addition, various databases used by various functions that support operation design include a procedure component DB 120 that stores procedure components created by the component creation function, and standard components for managing the configuration requirements of the operation target device. A configuration requirement tree DB 121 to be stored, an order definition DB 122 for defining an order relationship among a plurality of procedure parts, a procedure DB 123 for storing operation procedures created using parts, and configuration information corresponding to parameter elements when using the parts are stored. The component parameter DB 124 to be configured, the component requirement DB 125 for storing the prerequisite components for the defined component, and the output format DB for defining the output format and layout at the time of procedure output. Details of each database will be described later.

  FIG. 2 shows a typical configuration example of the operation procedure design server 101 in the operation procedure creation support system of the present embodiment. The server includes a central processing unit (CPU) 151 that executes arithmetic processing, a memory 152 that temporarily stores program data, a controller 153 that controls various interfaces, and a hard disk that holds various data programs. A storage device 154 such as a drive (Hard Disk Drive: HDD), a network interface 155 connected to an external network, and a peripheral device interface 156 connecting peripheral devices such as a display and a keyboard are configured. As an example, the peripheral interface 156 is connected to a display device 157 which is a display. The above-described CPU 151 implements the functions described in sequence below by executing programs corresponding to the various functions 110 to 116 stored in the memory 152.

<Part creation function>
The component creation function 110 of the operation procedure creation support system according to the present embodiment is a function for newly defining an operation procedure as a procedure component after blocking the operation procedure in a certain unit and extracting a parameter element.

  FIG. 3 shows an example of the processing flow of the component creation function. First, an operation procedure is divided and extracted in a certain unit from an existing operation procedure manual or an operation procedure manual in the middle of creation, thereby obtaining a procedure component (201). The unit of procedural parts is determined arbitrarily, but for example, a unit that appears repeatedly in common in one operation procedure manual or between multiple operation procedure manuals, a unit that can give meaning to operation procedures, A common operation unit or the like can be considered for OS (Operation System) tools / middleware / application software.

  Subsequently, the configuration requirement tree of the operation target device on which the extracted procedure component is assumed is selected (202). The configuration requirement tree represents components such as servers, disk devices, and the like, OS, middleware, and various software that are the operation targets when executing the operations defined in the procedure parts. Details and specific examples of the configuration requirement tree will be described later. Next, a specific premise configuration of the operation target device is set for the component defined in the selected configuration requirement tree. For example, if a procedure component “Connect a USB (Universal Serial Bus) disk to the server” is created by an operation for the server, the server needs to have a USB terminal and the disk device has a USB terminal as a connection interface. As a configuration requirement, USB is set for an interface that is a component of the server, and USB is set for an interface that is a component of the disk device.

  Next, the extraction of parameter elements in the procedure parts is associated with the configuration information in the configuration requirements (204). A parameter element refers to a matter determined when using a procedure part. For example, if the procedure component has the contents “prepare disk device”, items such as the location of the disk device and the management number determined when the procedure component is used are parameter elements. Further, since configuration information corresponding to the parameter element can be provided in the configuration requirement, if there is configuration information corresponding to the parameter element in the configuration requirement, it is associated with it.

  Finally, the order relation with the existing operation parts is defined (205). Depending on the procedural parts, procedural parts having an order relationship before and after the relevant parts are often used. For example, when an operation procedure manual is created, when using a procedure component “connect a USB disk to a server”, it can be estimated that a procedure component “preparation of a disk device” needs to be called before that. Therefore, when using procedure parts, the procedure parts having order relations are presented to the user at the same time for the purpose of reducing the trouble of selecting parts. If there is something related to the order, specify it.

<Configuration requirement tree>
Next, an example of the configuration requirement tree 121 of the operation procedure creation support system according to the present embodiment will be described. 4A, 4B, and 4C show examples of configuration requirement trees. These configuration requirement trees are formed and managed in the storage 102 as the configuration requirement tree 121 by the configuration management function 111 that manages the configuration information described above.

  FIG. 4A is an example of a configuration requirement tree for a server. The constituent elements on the tree are represented by a tree, and the root node 251 at the vertex indicated by a rectangle represents the type (SRV) of the constituent requirements of the tree. A node 252 represented by a hexagon represents configuration information and corresponds to a parameter element such as a server identification name in the procedure component. Ellipse nodes 253 to 256 are constituent elements. For example, the node 253 indicates that an OS type is included as a constituent element. In other words, the configuration requirement for the server has the type of OS installed in the server as a component. Similarly, the node 254 represents an interface (I / F) possessed by the server, the node 255 represents the type of CPU possessed by the server, and the node 256 represents the memory capacity possessed by the server.

  FIG. 4B is an example of a configuration requirement tree for a software tool. Similarly, the root node 261 indicates a tree type, that is, a software tool (TL), the node 262 is a tool name as configuration information, the node 263 is a version as a component, a node 264 is an item set when using the tool, and a node 265 is It represents the type of OS that is assumed when the tool is executed.

  FIG. 4C is an example of a configuration requirement tree for a disk device. Similarly, the root node 271 indicates the type of tree, that is, the disk device (DK), the node 272 indicates a drive name as configuration information, the node 273 indicates the type of interface used by the component disk, and the node 274 indicates configuration information. Represents a management number.

<Example of procedure parts>
Next, an example of procedure parts created by the part creation function 110 will be described. FIG. 5A and FIG. 5B have the part name “preparation of disk device” and the contents of the procedure for preparing the disk device.

  FIG. 5A shows the procedure component information stored in the procedure component DB 120 (300). The items of information to be stored are a part name representing the name of the part, a configuration requirement targeted by the part, configuration information corresponding to the parameter element, and procedure contents. In the configuration requirement, an identifier of the configuration requirement corresponding to the part held in the configuration requirement DB 125 is designated. In the configuration information, when the configuration information corresponding to the parameter element is specified in the configuration requirement, the configuration requirement corresponding to the part held in the configuration requirement DB 125 and the identifier of the configuration information are specified.

  FIG. 5B shows DK01 (311), which is a configuration requirement corresponding to the component 300, held in the configuration requirement DB 125. Information corresponding to each component is added to the configuration requirement tree (DK) 271 of the disk device shown in FIG. 4C. For example, although the node 313 is a component related to the interface, the lower node 315 specifies USB, and the lower node 316 specifies eSATA (External Serial ATA). A dotted arc 317 is drawn at the edge connecting the two nodes, which represents an OR condition. That is, it indicates that either USB or eSATA is a component as an interface.

  The node 312 as the configuration information defines the drive name of the disk device, but “DC” (Do n’t Care) is added because the drive name is not used in the component. Similarly, the node 314, which is configuration information, defines the management number of the disk device. Since this is used as a parameter element in this part, the configuration information identifier “P01” is added.

  Next, another example of procedure parts will be described with reference to FIGS. 6A and 6B. FIG. 6A and FIG. 6B show the procedure for confirming that the part name is “USB disk device connection”, a disk device having a USB interface is connected to the server, and the connection device is recognized on the OS. FIG. 6A shows the procedure component information stored in the procedure component DB 120 (320). As the configuration requirements, SRV01, which is a server requirement, and DK02, which is a disk device requirement, are designated by an AND condition (&). In the configuration information, the server name (P01) and the port number (P02) are specified in the server requirements, and the drive name (P03) is specified in the disk device requirements, as corresponding to the parameter elements of the procedure parts.

  FIG. 6B shows the configuration requirements corresponding to the part 320 held in the configuration requirement DB 125. The user adds information corresponding to each component to the server requirement (SRV) 251 shown in FIG. 4A and the disk device requirement (DK) 271 shown in FIG. 4C. For example, the node 334 as a constituent element defines an OS, but the lower node 314 defines Windows (registered trademark) Server 2003, and the lower node 342 defines Windows Server 2007 with an OR condition. That is, it shows that these two types of OS are supported. The node 336 defines the CPU type, but the node 344 indicates “DC”, which means that the CPU type does not matter.

  The node 335 of the server requirement SRV01 (331) and the node 339 of the disk device requirement DK02 (332) represent the interface types, and indicate common components in both the server requirement and the disk device. When creating a configuration requirement, a search is made for a common configuration element in each requirement. If the configuration component is the same and the configuration content is also common, information indicating that there is a common relationship is stored (347). ). If there is a common component but the configuration content is not common, the user is notified, and if it is necessary to share as a configuration requirement corresponding to the part, the configuration content to be manually shared Is specified. For example, “USB disk device connection” in this example needs to have USBs 343 and 348 which are interfaces common to the server device and the disk device. The node 346, which is configuration information, defines a port number, but adds a configuration information identifier “P02”.

  Next, still another example of components will be described with reference to FIGS. 7A and 7B. FIG. 7A and FIG. 7B show the procedure for confirming that the part name is “eSATA disk device connection”, a disk device having an eSATA interface is connected to the server, and the connection device is recognized on the OS. The only difference from the “USB disk device connection” described with reference to FIGS. 6A and 6B is that the interface is not USB but eSATA, and the others are the same. FIG. 7A shows the procedure component information 350 stored in the procedure component DB 120. As configuration requirements, SRV02 (361) which is a server requirement and DK03 which is a disk device requirement are designated by an AND condition (&). FIG. 7B shows the configuration requirements and connection requirements corresponding to the component 350 held in the configuration requirement DB 125. The difference from the USB disk device connection 330 is that the interface 363 that is a component in the server requirement SRV02 (361) is eSATA365, and the interface 364 of the disk device requirement DK03 (362) is also eSATA366. It is a point.

  Next, still another component example will be described with reference to FIGS. 8A and 8B. FIGS. 8A and 8B show the procedure contents in which the part name is “backup execution”, the backup source / backup destination / backup option is specified, the backup is executed, the normal end is confirmed, and the backup size and time are recorded.

  FIG. 8A shows the procedure component information 370 stored in the procedure component DB 120. As the configuration requirements, SRV02 which is a server requirement and TL01 which is a tool requirement are specified by an AND condition (&). Next, as the configuration information, the backup source (P01), the backup destination (P02), and the option (P03) are specified corresponding to the tool requirement TL01.

  FIG. 8B shows configuration requirements and connection requirements corresponding to the component 370 held in the configuration requirement DB 125. The user adds information corresponding to various components to the server requirement (SRV) 251 shown in FIG. 4A and the tool requirement (TL) 261 shown in FIG. 4B. For example, “Win backup” is designated as the tool type for the node 383 of the tool requirement TL01 (377), the version is designated at the lower node 385, and the setting item when the tool is used is designated at the node 386. The setting item corresponds to the parameter element of the component as configuration information.

  For example, the node 394 as configuration information represents a backup source, the node 395 represents a backup destination, and the node 396 represents an option. In addition, as an option option, the node 397 and the node 398 are defined in an OR condition as a lower node of the node 396, and “Back up all lower layers” (397) or “Back up only the corresponding layer” (398) can be selected as an option. . Since the OS 384 type in the tool requirement TL01 is compatible only with Windows Server 2003 (387), the OS 379 type in the server requirement SRV02 (376) is designated in the same manner (389).

<Definition of part relevance>
As shown in the flow chart of the part creation function in FIG. 3, after setting the configuration requirement for the part (203), specifying the parameter element from the procedure part, and correspondence (204) with the configuration information, An order relationship is defined (205).

  FIG. 9 shows an example of the order relationship definition of procedure parts. As described above, the relationship between the four procedure parts 300, 320, 350, and 370 is defined as a directed graph as an example of part creation. The order relationship of these procedure parts will be explained. First, “prepare disk device” 400 of procedure component 300 is executed, and then “USB disk device connection” 401 of procedure component 320 or “eSATA disk device connection” 402 of procedure component 350. And “backup execution” 403 of the procedure component 370 is executed. Therefore, although the edge with an arrow extends toward the node 401 and the node 402 with respect to the node 400, since a dotted-line arc is written on both edges to represent the OR condition, it is sufficient to take either one of the nodes.

<Procedure creation function and parts search function>
Next, the procedure creation function 112 for creating the operation procedure document of FIG. 1 will be described. The operation procedure manual defines the operation procedure for the operation target device in order for each operation unit. Define the flow of the procedure for the entire operation for the operation target device, and if using the procedure parts, search for and select the corresponding procedure parts for the detailed contents of each operation item. If no part is used, the details of the operation item are manually input.

Next, the component search function 115 when using the procedure component of FIG. 1 will be described.
FIG. 10 shows an example of the processing flow of the component search function. In searching for procedure parts, first, operation contents, system configuration information, and operation information are input.

  FIG. 11A, FIG. 11B, and FIG. 11C show examples of operation contents, system configuration information, and operation information, respectively. The operation content 461 includes expressions representing the operation content such as “disk preparation”, “disk connection”, and “backup”. The system configuration information 462 illustrated in FIG. 11B represents components such as a server name, an OS type, an interface, a tool type, and a tool version in the configuration requirements defined in FIGS. 4A, 4B, and 4C. The operation information 463 illustrated in FIG. 11C represents information such as device identifiers, management numbers, tool setting items, and the like determined at the time of operation.

  The component search function 115 in FIG. 10 extracts the corresponding component from the input information from the procedure component DB 120 and the component requirement DB 125 (452). First, regarding the operation content 461, a keyword representing the operation content is extracted by analyzing the expression, and a corresponding procedure component is extracted as a candidate on a keyword basis. The extraction method of operation component candidates corresponding to the database from the operation content 461 is not limited to this, and can be realized by utilizing various language processing techniques.

  The configuration information is defined as the configuration requirement corresponding to the procedural component at the time of component creation, and stored in the configuration requirement DB 125. The configuration information is the same as the configuration requirement for the system configuration information input in the process 451. A part that is further searched from the DB 125 and further associated with the extracted configuration requirements is extracted from the procedure part DB 120 as a candidate. Various means can be considered as means for realizing a match search between the input system configuration information and the configuration requirements on the configuration requirement DB. For example, from the input system configuration information, the constituent elements and the contents corresponding thereto, for example, The component is “OS”, and the corresponding content is extracted “Windows Server 2003”.

  Next, the component requirement stored in the component requirement DB 125 is searched using the component element as a key, and if there is a matching component and the corresponding contents match, it is determined that the component is matched. . Similarly, other component elements are also searched for matching, and if all the component elements match the defined requirement, it can be extracted as a completely matched component requirement. Although all the components corresponding to the input system configuration information match, there are other components depending on the configuration requirements, and the input system configuration information matches the other component. Since it is not possible to determine the requirement, it may be determined that the requirement is not a perfect match. In that case, it may be presented to the user as a partial match, and the user may determine whether to include it as a constituent requirement candidate.

  Thus, the presence / absence of the extracted part candidate is determined (453). If there is a part candidate, an appropriate part is selected from the candidates (454). If there is no part candidate, the search is terminated (459). In this case, a new part is created by the part creation function 110 or the detailed contents of the operation procedure are manually input by the procedure creation function 112.

  Next, if there is a value corresponding to the parameter element from the input operation information for the parameter element of the procedure part, a candidate value for the parameter element is automatically set (455). If there is no value corresponding to the parameter element or the relationship between the operation information and the parameter element cannot be extracted, the parameter element is set manually (455). In addition, as a method for searching for the association between the operation information and the parameter element, the association between the configuration information and the parameter element defined by the configuration requirement may be used. For example, FIG. 5A shows a part example of “preparation of disk device”, but the management number of the disk, which is the configuration information, corresponds to the parameter element of the part. In the configuration requirement of FIG. It defines that it corresponds. When searching for a configuration requirement, for example, a management number is associated with the input operation information item, and can be used as a parameter element candidate value at the time of component generation.

  Subsequently, the part selected in step 454 in FIG. 10 is searched for a part having order relation in the order definition DB 122 (456). The order relation is shown as shown in FIG. 9. For example, if “preparation of disk device” 400 of the procedure part 300 is selected, “USB disk device connection” 401 and “eSATA disk device connection” 402 related thereto are selected. , “Procedure parts” 403 “procedure parts” are presented as candidates for order related parts. If there is an order-related part candidate (Yes in 457), a part candidate is selected (458), and parameter element settings are repeated for the selected part (455). If there is no related candidate (No in 457), the search ends (end).

<Example of created operation procedure>
FIG. 12 shows an example 464 of an operation procedure created based on the operation contents, system configuration information, and operation information shown in FIGS. 11A, 11B, and 11C. The parts using the procedure parts are parts 466, 467, and 469 surrounded by wavy lines. The portions other than the wavy frame are portions 465 and 468 in which detailed operation procedures are individually input without using parts. In addition, the parameter element at the time of component use is underlined. The created operation procedure is converted into a format corresponding to the output destination paper or electronic terminal according to the output format DB, and is generated as a final operation procedure manual.

<Procedure verification function>
Next, the procedure verification function 113 using the order relation of components for the operation procedure document created by the system of this embodiment will be described. In the procedure creation process, use the order relation information of the procedure parts for mistakes such as changing the order of the parts or not selecting the part to be originally input (for example, login but not logout). Can be detected.

FIG. 13 shows an example of the processing flow of the procedure verification function. First, a procedure flow is extracted from the created operation procedure manual (471).
FIG. 14 shows an example of a procedure flow extracted from the operation procedure manual shown in FIG. A square indicates a procedure item (481, 484) that defines the detailed contents of the operation procedure without using a part, and a circle indicates a procedure item (482, 483, 485) using the part. There are cases where the procedure flow has branches such as executing different procedure items depending on the result of executing a certain procedure item. For the procedure flow extracted as described above, the sequence relevance information related to the procedure component is extracted from the sequence component used in the sequence definition DB 122 (472).

  In addition, there is a possibility that a plurality of order relations are extracted. In this case, candidates are narrowed down by extracting only the order relations corresponding to the configuration requirements defined from the system configuration information. For example, FIG. 9 shows the order relation extracted from the procedure parts used in the created operation procedure when the operation contents, system configuration information, and operation information shown in FIGS. 11A, 11B, and 11C are input. 9, in the definition of relevance in FIG. 9, the order of the order differs depending on the interface (401 and 402) of the disk device connection parts, but the USB disk device connection is determined from the component configuration requirements and the input system configuration information. Can be extracted.

  Next, the created operation procedure flow is compared with the order definition extracted from the order relationship of the procedure parts, and matching is determined (473). Various determination methods are conceivable, and an appropriate method may be adopted. For example, by applying DP (Dynamic Programming) matching which is one of the expansion and contraction matching methods, it can be determined whether or not the relevance flows match. If it is determined that there is no match as a result of the matching determination (474), the part usage portion that does not match in the created procedure is presented (475) to prompt correction. If they match, the procedure verification ends.

<Correction evaluation function>
Next, when the system configuration or operation information of the operation target device is changed for the operation procedure document created in the system of this embodiment, the revision evaluation that evaluates which part of the operation procedure document is to be modified The function 114 will be described.

  FIG. 15 shows an example of the processing flow of the correction evaluation function. First, system configuration information and operation information reflecting correction contents are input (500). Next, a change point (difference) with respect to the pre-correction is detected, and it is detected which component has been changed in the configuration requirement assumed in the current operation procedure manual (501). Next, the component and the contents of the component corresponding to the procedure component used in the current operation procedure manual are extracted from the component requirement DB 125, and the parameter component of the procedure component and its content are extracted from the component parameter DB 124 (502) ).

  Then, it is determined whether the content of the change corresponds to a component in the configuration requirement (a node represented by a circle in FIGS. 4A, 4B, and 4C) (503). The case where the component does not correspond to the component in the configuration requirement corresponds to the configuration information of the parameter element or the configuration requirement (the node represented by a hexagon in the configuration requirement tree in FIGS. 4A, 4B, and 4C). Therefore, in this case, since it is not a change in the configuration requirement that is a prerequisite for using the procedure component, there is no change in the procedure component itself, and it is then determined whether the change corresponds to the configuration information of the parameter element or the configuration requirement (512). .

  If the result is true, the item corresponding to the configuration information of the parameter element or the structural requirement is rewritten, the change content is presented to the user (504), and the correction evaluation is finished. If not, the part is not corrected. This is notified to the user (513), and the correction evaluation is terminated. Further, if the change contents correspond to the constituent elements in the configuration requirements, the preconditions for using the procedure components change, and therefore it is necessary to change the procedure components corresponding to the changed configuration requirements. First, it is determined whether the current procedure component satisfies the configuration requirements even if the system configuration information / operation information is changed (505, 506).

  For example, in the system configuration information / operation information in FIG. 11B and FIG. 11C, the connection interface of the used disk device is changed from USB to eSATA. First, configuration requirements are extracted from the configuration requirement DB 125 for the generated operation procedure 500 in FIG. 12, and changes in the configuration requirements with respect to interface changes are evaluated. As a result, “preparation of disk device” 300 and “connect USB disk device” 320 are extracted as procedural parts that affect the interface change as configuration requirements.

  First, looking at the configuration requirement 310 of “disk device preparation”, the interface (node 313) can be either USB (node 315) or eSATA (node 316), so even if the interface is changed from USB to eSATA, the configuration requirement You can see that Therefore, in this case, it is only necessary to indicate to the user that the component can be used as it is (510).

  If the component cannot be satisfied as it is, the procedure component corresponding to the changed component is searched with the same operation contents (507, 508). As a means for determining the same operation content, having the same operation keyword is considered as an example. If there is a candidate, that is, if there is a component satisfying the configuration requirement with another part having the same operation content with respect to the changed content, it is presented as a correction candidate (509). For example, in the above example, “USB disk device connection” is extracted as a procedural component that is affected by the change from USB to eSATA, but there is a procedural component “eSATA disk device connection” in the same disk device connection. By searching the configuration requirement DB, when the interface is changed to eSATA, “eSATA disk device connection” can be extracted as a corresponding part, and this can be presented to the user as a change candidate (509). If there is no part candidate corresponding to the changed configuration requirement, the user is notified of the necessity of correcting the part itself (511). As a result, the user manually corrects the part or creates a new part. As described above, it is possible to evaluate the correction effect on the operation procedure when the system configuration information or the operation information is changed.

<Screen example>
An example of a user interface for realizing each function of the system of the present embodiment described above will be described. This user interface is displayed on the display device 157 and the like of the operation procedure design server 101 constituting the system of the present embodiment described above, but it is not limited thereto as described above. Yes, it can be displayed on the display unit in various system configurations.

  First, FIG. 16 shows an example of a screen for inputting configuration information of a system to be operated. Each item of the configuration information 601 of the target system can be defined using the configuration requirement tree shown in FIGS. 4A, 4B, and 4C. For example, the server 1 (602) is introduced by selecting the server configuration requirement tree SRV (251) in FIG. 4A with the “insert tree” button (603). For each item in the introduced configuration requirement tree, information is input by selecting a target item and pressing an “edit” button (604). When defining the items of the configuration information individually without using the configuration requirement tree, they are defined by the “Add” button (605).

  Next, FIG. 17 shows an example of a screen for editing the operation procedure manual of the system of this embodiment. The contents of the procedure manual are displayed as a flow diagram, and an overview of the procedure flow is displayed as a procedure flow 621. An operation procedure manual can be created by adding / editing / deleting items in the flow diagram. At this time, the procedure parts held on the procedure part DB 120 can be introduced for each item in the flowchart. For example, when a component is introduced to the flow item “USB disk device connection” 622, the flow item 622 is selected and the “component introduction” button 623 is pressed. As a result, a screen for selecting a part is called.

  FIG. 18 shows an example of a component selection screen of the system of this embodiment. The component selection screen displays a component list 651, a procedure flow diagram 652 of the selected component, and component requirement information 653 of the selected component. In accordance with the flowchart of the part search function shown in FIG. 10, corresponding parts are presented from the operation contents, system configuration information, and operation information input in advance. In this screen example, the display of the component list 651 displays the corresponding component (corresponding to the search result in 454) in bold. For example, in this example, a parts list organized by operation is shown, and “partition disk preparation”, “USB disk device connection”, “eSATA disk device connection”, etc. are registered as parts belonging to the “disk preparation / connection” operation. Has been. For example, “USB disk device connection” (654) is searched as a usable part from the system configuration information input in advance in the screen example of FIG. 16 with the contents shown in FIG. It is displayed. On the other hand, “eSATA disk device connection” (655) does not correspond to the system configuration information (that is, the server interface has only USB), so it is not searched as a usable part and is displayed in fine italics. Is done.

  Next, in FIG. 19, when the system configuration or operation information of the operation target device is changed with respect to the created operation procedure manual, it is evaluated which part of the operation procedure manual is to be corrected, and the correction target is determined. An example of the screen to be displayed is shown. Corresponding to the configuration change example (the disk connection interface is changed from USB to eSATA) exemplified when explaining the processing flow of the correction evaluation function in FIG. “Preparation” and “USB disk device connection” are extracted. Looking at the configuration requirement 310 of “preparation of disk device”, the interface (node 313) can take either USB (node 315) or eSATA (node 316), so the configuration requirement is not changed even if the interface is changed from USB to eSATA. You can see that it meets.

  Therefore, in this case, on the item of the procedure flow 670 of the operation procedure manual, “the configuration change item matches the configuration requirement, but the condition is satisfied even after the configuration change, so it is communicated without modification” 671 and the user Presented (corresponding to 510 in FIG. 15). In “USB disk device connection”, there is a procedure part “eSATA disk device connection” for the same disk device connection. By searching the configuration requirement DB, when the interface is changed to eSATA, “eSATA disk device connection” can be extracted as the corresponding part, and “The configuration change does not match the configuration requirement. There are parts. → Candidate: “eSATA disk device connection” 672 is presented to the user (corresponding to 509 in FIG. 15).

  In addition, this invention is not limited to an above-described Example, Various modifications are included. For example, the above-described embodiments have been described in detail in order to explain the present invention in an easy-to-understand manner, and are not necessarily limited to those having all the configurations described. Further, it is possible to add, delete, and replace other configurations for a part of the configuration of each embodiment.

  Each of the above-described configurations, functions, processing units, processing means, and the like may be realized by hardware by designing a part or all of them with, for example, an integrated circuit. In addition, each configuration, function, and the like have been described by exemplifying a case where they are realized by software by executing a program that realizes each function. However, information on programs, tables, files, and the like that realize each function It can be stored not only in memory, but also in recording devices such as hard disks and SSDs (Solid State Drives), or recording media such as IC cards, SD cards, and DVDs. It is also possible to do.

101 operation procedure design server,
102 storage,
103 operation terminal,
104 network,
110-116 Various functions of operation procedure design,
120-126 Various databases used in operation procedure design,
151 CPU (Central Processing Unit),
152 memory,
153 controller,
154 storage device,
155 network interface,
156 peripheral interface,
157 display devices 201-205 processing steps;
251 Server configuration requirement tree,
261 Tool requirements tree,
271 Disk device configuration requirement tree,
252, 262, 272, 274 configuration information,
253-256, 263-265, 273 components,
300, 320, 2350, 370 procedural parts,
310, 330, 360, 375 Configuration requirements corresponding to procedural parts,
311, 332, 362 Configuration requirements of the disk device,
331, 361, 376 Server configuration requirements,
312, 314, 333, 338, 340, 346, 388, 394-396 configuration information,
313, 334-337, 339, 363, 364, 379-382, 384-386 components,
315, 316, 341 to 345, 348, 365, 366, 383, 387, 389 to 393, 397, 398 Content of components,
400-403 procedure parts,
451-458, 471-475, 500-513 processing step 461 operation content,
462 system configuration information,
463 operational information,
464 created operational procedures,
465-469 operation procedures,
481-485 procedural steps,
601 configuration information,
621, 670 Procedure flow,
651 parts list,
671, 672 Presentation information.

Claims (15)

An operation procedure creation support system using an information processing device that supports creation of an operation procedure for an information system, wherein the information processing device includes:
A procedure component having a common procedure of the operation procedure as a component, and a configuration requirement constituting the information system, which is the operation target of the procedure component, are stored,
When a change occurs in the configuration of the information system, the procedural component evaluates the necessity for correction of the configuration requirement to be operated,
An operational procedure creation support system that presents a correction range for the operational procedure for a change that has occurred in the configuration of the information system based on the evaluation result. The operation procedure creation support system according to claim 1,
The information processing apparatus includes:
Comparing the configuration requirements of the information system modified based on the evaluation result with the existing configuration requirements targeted for operation by the procedure component, and presenting a new procedure component that is a candidate for modification based on the comparison result Operation procedure creation support system characterized by doing. The operation procedure creation support system according to claim 1,
The configuration requirement of the information system includes a configuration element and configuration information used when using the procedural part,
The information processing apparatus includes:
An operation procedure creation support system that presents a new operation procedure corresponding to the change when it is determined from the evaluation result that there is a change in the configuration requirement to be operated by the procedure component. The operation procedure creation support system according to claim 1,
The configuration requirement of the information system includes configuration information corresponding to a configuration element and a parameter element determined when using the procedural part,
The information processing apparatus includes:
Based on the evaluation result, when it is determined that there is no change in the configuration requirement that the procedure component is an operation target, and the change that has occurred in the configuration of the information system is a change to the parameter element, the parameter after the change An operation procedure creation support system that reflects elements in the configuration information and presents a new operation procedure corresponding to the change. The operation procedure creation support system according to claim 1,
The information processing apparatus includes:
Create a new operation procedure by combining the procedure parts,
At the time of creation of the procedure part, an order relationship with the existing procedure part is defined, and the procedure part having the order relation is presented as a candidate when the procedure part is selected at the time of creating the operation procedure. An operational procedure creation support system characterized by this. The operation procedure creation support system according to claim 5,
The information processing apparatus includes:
By extracting the sequence flow of the created operational procedure and comparing it with the sequence relationship between the procedure components,
An operation procedure creation support system that extracts and presents a portion of the created operation procedure that does not match the order relation between the procedure components. The operation procedure creation support system according to claim 1,
The information processing apparatus includes a display device,
An operation procedure creation support system, wherein a correction range for the operation procedure is presented on the display device. The operation procedure creation support system according to claim 7,
The information processing apparatus includes:
The operation procedure creation support system, wherein the procedure component and the correction contents of the procedure component are displayed on the display device as the operation procedure editing screen. An operation procedure creation method in an operation procedure creation support system for supporting creation of an operation procedure for an information system, wherein a common procedure of the operation procedure is a procedure component,
The procedural component and the component that constitutes the information system to be operated by the procedural component are stored,
Create a new operation procedure by combining the procedure parts,
When a change occurs in the configuration of the information system, the procedural component evaluates the necessity for correction of the configuration requirement to be operated,
An operation procedure creation method, comprising: outputting a correction range to the operation procedure for a change that has occurred in the configuration of the information system based on the evaluation result. The operation procedure creation method according to claim 9,
Comparing the configuration requirements of the information system to be corrected based on the evaluation result with the existing configuration requirements to be operated by the procedure components, and outputting a new procedure component as a correction candidate. Operation procedure creation method. The operation procedure creation method according to claim 9,
The configuration requirement of the information system includes a configuration element and configuration information used when using the procedural part,
An operation procedure creation method, comprising: outputting a new operation procedure corresponding to the change when it is determined that there is a change in the configuration requirement to be operated by the procedure component based on the evaluation result. The operation procedure creation method according to claim 9,
The configuration requirement of the information system includes configuration information corresponding to a configuration element and a parameter element determined when using the procedural part,
Based on the evaluation result, when it is determined that there is no change in the configuration requirement that the procedure component is an operation target, and the change that has occurred in the configuration of the information system is a change to the parameter element, the parameter after the change An operation procedure creation method characterized in that an element is reflected in the configuration information, a procedure part corresponding to the changed configuration information is searched, and if the procedure part is present, the procedure part is output. The operation procedure creation method according to claim 9,
The configuration requirement of the information system includes configuration information corresponding to a configuration element and a parameter element determined when using the procedural part,
Based on the evaluation result, when it is determined that there is no change in the configuration requirement that the procedure component is an operation target, and the change that has occurred in the configuration of the information system is a change to the parameter element, the parameter after the change Creating an operation procedure characterized in that an element is reflected in the configuration information, a procedure part corresponding to the changed configuration information is searched, and if the procedure part does not exist, the necessity for correction of the procedure part is output. Method. The operation procedure creation method according to claim 9,
The order relation with the existing procedure parts is defined when the procedure parts are created, and the procedure parts having the order relation are output as candidates when the procedure parts are selected when the operation procedure is created. An operational procedure creation method characterized by this. The operation procedure creation method according to claim 14,
By extracting the sequence flow of the created operational procedure and comparing it with the sequence relationship between the procedure components,
An operation procedure creation method, wherein a portion of the created operation procedure that does not match the order relation between the procedure components is extracted and output.

Images