Business management method and business management system

Abstract

To present information necessary for maintenance operation work in a bird' s-eye view manner regardless of the configuration of a job and a job net in an object system and the scale and complexity of cooperation.SOLUTION: An information processing device holds definition information 1052 related to a job and a job net in a system, performs determination related to a milestone job for a component of a first job net on the basis of the definition information 1052, creates each event job of event transmission and event reception associated with the milestone job when the milestone job is determined, creates a second job net for aggregating the event jobs, and arranges at least the event reception job among the event reception job and the event transmission job in the second job net.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention generally relates to business management methods and business management system technologies, and more specifically to a technology that enables information necessary for maintenance and operation work to be presented in an overview manner regardless of the scale and complexity of the configuration and collaboration of jobs and jobnets in the target system. [Background technology]

[0002] In the various systems operated by organizations of a certain size, various jobs and their aggregates, or jobnets, are often linked hierarchically and across hierarchies and jobnets depending on the type and scale of the business. Therefore, in the operation and maintenance of such systems, understanding the linkages between jobs and jobnets is important for the efficiency and accuracy of maintenance operations.

[0003] A prior art technique proposed in the field of system maintenance and operation such as the one described above is shown in Patent Document 1. Patent Document 1 discloses a technique for simplifying the display of job flows in a job operation management system by unifying the direction of relational lines on a job flow definition screen into a single direction.

[0004] The above technology is a job operations management system equipped with a computer for displaying on a job flow definition screen on a job flow definition screen the direction of relational lines indicating the predecessor-successor execution order relationships between the units of a job net so as to match the execution direction of the job flow, the computer comprising: means for storing in a database a definition file that defines detailed information about each unit included in a job net and the predecessor-successor execution relationships between the units; means for reading the definition file from the database; means for determining, based on the read definition file, whether the direction of the relational lines between the units on the job flow definition screen matches the execution direction of the job flow; means for changing position information of the units on the job flow definition screen if the direction of the relational lines between the units does not match the execution direction of the job flow so that the direction of the relational lines matches the execution direction; and means for displaying each unit of the job net and the relational lines on the job flow definition screen using the changed position information. This relates to the job operation management system. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Laid-Open No. 2016-170553 Summary of the Invention [Problem to be solved by the invention]

[0006] Prior art has disclosed functions for sending and receiving events across jobnets and displaying the status of jobnets in different colors. However, these technologies do not address the case where a single jobnet contains multiple jobs and there are multiple such jobnets, or where job execution order control is performed across systems. In other words, no technology has been proposed that provides a bird's-eye view of the overall configuration and interconnection of multiple jobnets. As a result, when maintaining and operating such systems, personnel are forced to continue as before, individually checking the configuration of each jobnet and the interconnection between jobnets and systems.

[0007] Therefore, the present invention has been made in consideration of the above-mentioned problems, and aims to provide technology that can present information necessary for maintenance and operation work at an overview level, regardless of the size and complexity of the configuration and collaboration of jobs and jobnets in the target system. [Means for solving the problem]

[0008] The present application includes multiple means for solving the above-mentioned problems, examples of which are as follows: To solve the above-mentioned problems, a business management method according to one aspect of the present invention is characterized in that an information processing device that supports system management stores definition information related to jobs and jobnets in the system in a storage device, and performs a process of determining whether a component of a first jobnet in the system is a milestone job based on the definition information, and if the component is determined to be a milestone job as a result of the determination, performs a process of creating event jobs for event transmission and event reception associated with the milestone job, a process of creating a second jobnet for aggregating the event jobs, a process of placing the event transmission job before or after execution of the milestone job, and a process of placing at least the event reception job out of the event reception job and the event transmission job in the second jobnet.

[0009] In addition, in order to solve the above-mentioned problems, a business management system according to one embodiment of the present invention is characterized by comprising a storage device that stores definition information regarding jobs and jobnets in a target system; a process for making a judgment regarding milestone jobs for components of a first jobnet in the system based on the definition information; and, if the result of the judgment indicates that the component is a milestone job, a process for creating an event sending job and an event receiving job associated with the milestone job; a process for creating a second jobnet to aggregate the event receiving jobs; a process for placing the event sending job before or after execution of the milestone job; and a calculation device that executes the processes of placing the event receiving job in the second jobnet. [Effects of the Invention]

[0010] According to the present invention, it is possible to comprehensively present information required for maintenance and operation work, regardless of the scale and complexity of the configuration and linkage of jobs and jobnets in the target system. [Brief explanation of the drawings]

[0011] [Figure 1] 1 is a network configuration diagram illustrating a business management system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a diagram illustrating an example of the hardware configuration of a job execution manager according to the present embodiment. [Figure 3] FIG. 2 is a diagram illustrating an example of the relationship between jobs and jobnets in the present embodiment. [Figure 4] FIG. 2 is a diagram illustrating an example of a job flow according to the present embodiment. [Figure 5] FIG. 4 is a diagram illustrating an example of a job definition list according to the present embodiment. [Figure 6] FIG. 1 is a diagram illustrating an example of a flow of a business management method according to the present embodiment. [Figure 7] FIG. 1 is a diagram illustrating an example of a flow of a business management method according to the present embodiment. [Figure 8]FIG. 1 is a diagram illustrating an example of a flow of a business management method according to the present embodiment. [Figure 9] FIG. 1 is a diagram illustrating an example of a flow of a business management method according to the present embodiment. [Figure 10] FIG. 2 is a diagram illustrating an example of a job flow according to the present embodiment. [Figure 11] FIG. 1 is a diagram illustrating an example of a flow of a business management method according to the present embodiment. [Figure 12] FIG. 1 is a diagram illustrating an example of a flow of a business management method according to the present embodiment. [Figure 13] FIG. 10 is a diagram illustrating an example of job placement optimization in the present embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0012] In the following description, a communication device may be one or more communication interface devices, which may be one or more homogeneous communication interface devices (e.g., one or more NICs (Network Interface Cards)) or two or more heterogeneous communication interface devices (e.g., a NIC and an HBA (Host Bus Adapter)).

[0013] In the following description, a "memory" refers to one or more memory devices, which are an example of one or more storage devices. At least one of the memory devices may be a volatile memory device or a non-volatile memory device.

[0014] In the following description, a "storage device" may refer to one or more persistent storage devices, which are an example of one or more storage devices. A persistent storage device may typically be a non-volatile storage device, specifically, for example, a hard disk drive (HDD), a solid state drive (SSD), or a non-volatile memory express (NVMe) drive.

[0015] In the following description, a "CPU" refers to a computing device and may be one or more processor devices. The at least one processor device may typically be a microprocessor device such as a CPU (Central Processing Unit), but may also be another type of processor device such as a GPU (Graphics Processing Unit). The at least one processor device may be a single-core or multi-core. The at least one processor device may also be a processor core. The at least one processor device may also be a processor device in a broader sense, such as a hardware circuit that performs part or all of the processing (e.g., an FPGA (Field-Programmable Gate Array), a CPLD (Complex Programmable Logic Device), or an ASIC (Application Specific Integrated Circuit)).

[0016] In the following description, information that provides an output in response to an input may be described using expressions such as "xxx table" or "xxx database." However, this information may be data of any structure (for example, structured data or unstructured data), or may be a learning model such as a neural network, genetic algorithm, or random forest that generates an output in response to an input. Therefore, "xxx table" or "xxx database" may be referred to as "xxx information." In the following description, the structure of each database or table is an example, and one database or table may be divided into two or more databases or tables, or all or part of two or more databases or tables may be one database or table.

[0017] In the following description, processing may be described using a "program" as the subject. However, since a program is executed by a CPU to perform a predetermined process using a storage device and / or an interface device, etc., as appropriate, the subject of the process may also be the CPU (or a device such as a controller having a processor). A program may be installed in a device such as a computer from a program source. The program source may be, for example, a program distribution server or a computer-readable (e.g., non-transitory) recording medium. In the following description, two or more programs may be realized as one program, or one program may be realized as two or more programs.

[0018] In addition, in the following description, when describing elements of the same type without distinguishing between them, common parts of the reference symbols may be used, and when describing elements of the same type with distinction between them, reference symbols or element identifiers may be used.

[0019] <Network configuration of the business management system> 1 is a diagram showing an example of the network configuration of a business management system 100 according to this embodiment. The business management system 100 according to this embodiment is a system that can provide an overview of the information required for maintenance and operation work, regardless of the size and complexity of the configuration or linkage of jobs and jobnets in the target system. It is primarily composed of a job execution manager 102, and optionally includes a client PC 101 linked to the job execution manager 102 and job execution agents 103-105 for each system. The job execution manager 102 is an information processing device that manages system maintenance and operation work for jobs and jobnets executed by the job execution agents 103-105. Specifically, a PC (Personal Computer) or a server device can be used, but there is no particular limitation.

[0020] Furthermore, among the above system configurations, the job execution agents 103 to 105 are agents installed in systems that are job execution destinations or monitoring targets, and execute jobs in response to requests from the job execution manager 102 and return the results.

[0021] The client PC 101 is a terminal that accesses the job execution manager 102 via an appropriate network and displays the execution results of the business management method of this embodiment (such as a job flow display screen) on a screen using a predetermined viewer such as a web browser. This client PC 101 is a computer that is connected to the job execution manager 102 and is used by a person in charge of or supporting system maintenance and operation work.

[0022] As shown in FIG. 2, the job execution manager 102 includes a storage device 1025 consisting of a nonvolatile storage device such as a hard disk drive or an embedded multimedia card, a memory 1022 consisting of a volatile storage device such as a RAM (Random Access Memory), a CPU 1024 that calls up a program 10251 stored in the storage device 1025 into the memory 1022 to perform overall control of the device itself and perform various judgments, calculations, and control processing, an I / O 1021 for connecting to input devices such as a keyboard and output devices such as a display, and a communication device 1023 that connects to an appropriate network and communicates with other devices.

[0023] The functions corresponding to the business management method implemented in the storage device 1025 of the job execution manager 102 are implemented by the CPU 1024 executing a program 10251. The data held in the storage device 1025 includes a job definition list 10252. The specific configuration of this job definition list 10252 will be described later.

[0024] Note that part of the processing performed by the CPU 1024 executing the program 10251 may be executed by another arithmetic device (for example, hardware such as an ASIC or FPGA). The memory 1022 may be a ROM (Read Only Memory), which is a non-volatile storage element. The ROM stores unchanging programs (for example, BIOS). The RAM is a high-speed, volatile storage element such as a DRAM (Dynamic Random Access Memory), and temporarily stores the program 10251 executed by the CPU 1024 and data used when the program 10251 is executed.

[0025] Alternatively, the client PC 101 connected to the job execution manager 102 via a network may provide an input device or an output device via the I / O 1021. The program 10251 executed by the CPU 1024 is provided to the job execution manager 102 via removable media (CD-ROM, flash memory, etc.) or the network, and is stored in a non-volatile storage device 1025, which is a non-transitory storage medium.

[0026] Therefore, the job execution manager 102 reads data from the removable media via the I / O 1021. The job execution manager 102 is a computer system configured on one physical computer or on multiple logically or physically configured computers, and may also operate on a virtual computer built on multiple physical computer resources. The job execution manager 102 may be configured on a cloud or may be on-premise configured on a specific computer (hardware).

[0027] The network connecting the job execution manager 102 with the client PC 101 and job execution agents 103-105 may be, but is not limited to, the Internet, a local area network (LAN), a wide area network (WAN), or a mobile phone network. An example of a mobile phone network is a general public line network, whether wired or wireless, such as a fifth-generation mobile communication system (5G) that enables multiple simultaneous connections and ultra-low latency. Furthermore, by utilizing the features of new mobile phone systems beyond 5G, the present invention is expected to achieve secondary benefits, such as faster and higher-resolution job flow screen displays.

[0028] The client PC 101 is a terminal for viewing the processing results, i.e., the processing results of the business management method, as well as for making settings and storing data required for processing, for the job execution manager 102. Specifically, the client PC 101 is implemented as a PC (Personal Computer), a tablet terminal, a smartphone, or the like.

[0029] Data exchange between the job execution manager 102 and the client PC 101 or job execution agents 103 to 105 may be performed according to, for example, an API (Application Programming Interface) protocol. In this case, it is assumed that each device is pre-implemented with the functions and configurations for executing API request and response processing.

[0030] On the other hand, the client PC 101 and the job execution agents 103 to 105, like the job execution manager 102, include an I / O 1021, a memory 1022, a communication device 1023, a CPU 1024, and a storage device 1025.

[0031] <About jobs and jobnets> The relationship between jobs and jobnets will be explained with reference to Figure 3. A jobnet is a collection of jobs or jobnets. With existing technology, the Viewer on client PC 101 can only view the subordinates of one jobnet. Furthermore, a jobnet is considered complete only when all jobs or jobnets at lower levels are completed. Based on this relationship between jobs and jobnets, Figure 4 shows an example of a job flow in which there are multiple jobnets with many jobs or jobnets, and job execution order control is performed across systems between "System A" and "System B."

[0032] The job flow example shown in Figure 4 shows a flow configuration in which "Jobnet 1" in "System A" and "Jobnet 2" in "System B" are linked to each other. Both jobnet 301, which is "Jobnet 1," and jobnet 302, which is "Jobnet 2," are configured to include multiple jobs or jobnets. The execution order of jobs in this job flow is expressed by relational lines or event linkages. Relational lines define the chronological relationship between jobs or jobnets within the same jobnet, and are represented by solid arrows in the figure. On the other hand, event linkages define the chronological relationship between jobs between different jobnets by establishing a pair of jobs that send and receive events, and are represented by dotted arrows in the figure.

[0033] In the example shown in the figure, the event sending job 303 in jobnet 301, which is "jobnet 1," and the event receiving job 304 in jobnet 302, which is "jobnet 2," are connected by the above-mentioned relationship line, indicating that the two are linked.

[0034] <About the job definition list> Next, the configuration of the job definition list 10252 that the job execution manager 102 stores in the storage device 1025 will be described with reference to Fig. 5. The job definition list 1052 manages, for each unit (job), the values ​​of its upper unit (jobnet) and type, location information within the upper jobnet, execution host, presence or absence of delay monitoring settings, and preceding job.

[0035] <Work management method: Flow> Next, the processing flow of the task management method of this embodiment will be described. Fig. 6 is a diagram showing an example of the flow of the task management method of this embodiment, specifically, a diagram of the main flow. Note that the following description is based on the premise that the job execution order in the job flow shown in Fig. 4 is followed.

[0036] In the execution order of the above job flow, when jobnet 301, which is "Jobnet 1," starts, its prerequisite jobs or "Job 1," "Job 2," and "Job 7," which do not belong to any jobnet, start. Of these, when "Job 2" is completed, the subsequent "Jobnet 3" starts. When "Jobnet 3" starts, "Job 3," "Job 4," and "Job 5" start, as described above. When "Job 3" is completed, "Event Sending A" 303, which is an event sending job, starts, and its paired event receiving job, "Event Receiving A" 304, is executed. Furthermore, when both "Job 4" and "Job 5" are completed, "Job 6" starts. When all jobs or jobnets in "Jobnet 3" are completed, "Jobnet 3" is completed, and the subsequent "Jobnet 4" starts.

[0037] In this case, for example, when "Job 15" has been completed in "Job Net 2" of "System B" and you want to check the progress of "Job 16," you cannot know when "Event Reception A" 304, the prerequisite job for "Job 16," will start just by checking the status of "Job Net 2" (in the prior art). Therefore, the user had to operate the client PC 101, view a confirmation screen for "Job Net 1" on a separate screen using a viewer, and check the progress of "Event Transmission A" 303, which is paired with "Event Reception A" 304.

[0038] In this way, when a user views the status of a job using the Viewer on the client PC 101, they can only check the status of one job net. Therefore, in the past, it was difficult to get a bird's-eye view of the overall progress under such circumstances. Even if multiple Viewers were launched at the same time and the status of multiple job nets, etc. could be displayed on the screen at the same time, it was not possible to check the overall progress of jobs, etc. that may be linked to each job net, or the expected completion timing, making it difficult to evaluate the maintenance and operation of the system.

[0039] Therefore, the job execution manager 102, which is the information processing apparatus of the present invention, creates a new event receiving jobnet 914 that aggregates the event receiving jobs. By applying the technology of this embodiment to the job flow of Fig. 4, the job flow configuration of Fig. 10 is obtained. In Fig. 10, a new event receiving jobnet 914 has been created. By creating the event receiving jobnet 914 and making it possible to display it in the Viewer, the user can grasp the overall progress across each jobnet.

[0040] In addition, the horizontal direction within the display area of ​​the event receiving jobnet 914 is the time axis, and it is also possible to adjust the placement position of each object corresponding to that job based on the log of the actual completion time of each job included in the event receiving jobnet 914. This makes it possible to evaluate whether the jobs are running slower or faster than normal. Note that the jobs included in the event receiving jobnet 914 are linked to milestone jobs that are determined to be important from among the jobnets "jobnet 1" 915 and "jobnet 2" 916, and are not limited to event receiving jobs.

[0041] The method for creating the event receiving job net 914 will now be described. As already mentioned, Fig. 5 shows the job definition list 10252, and Fig. 6 shows the flow for creating an event receiving job net in the business management method of this embodiment. First, the job execution manager 102 downloads the job definition list 10252 from a predetermined job management system (S401) and stores it in the storage device 1025.

[0042] Next, the job execution manager 102 determines whether a job or jobnet is a milestone job, i.e., whether it is a milestone job, based on three criteria: delay monitoring settings, processing importance, and inter-system cooperation (S402 to S404).The job execution manager 102 also allocates the jobnet location of the milestone job by system (S405).

[0043] The job execution manager 102 also optimizes the job net position according to the actual job start time each day (S406). Finally, the job execution manager 102 uploads the job definition list 10252 to a specified job management system (S407), completes the event reception job net, and ends the flow. This makes it possible to check the newly created job net using the Viewer on the client PC 101.

[0044] Here, the method for determining a milestone job in steps S402 to S404 of the above flow will be explained. First, a detailed flow of determining whether a milestone job is a job (S402) based on the presence or absence of a delay monitoring setting will be explained with reference to FIG. 7. In the network configuration shown in FIG. 1, the job execution agents 103 to 105 in each system are capable of monitoring whether each job net executed in that system starts or ends at the scheduled date and time. This setting is called a delay monitoring setting. This setting is made for job nets in which a delay in start or end will have a significant impact on the execution schedule of the subsequent job net.

[0045] Therefore, in this embodiment, a job with this delay monitoring setting is determined to be an important job and is therefore determined to be a milestone job. In this case, the job execution manager 102 reads the first line 501 of the job definition list 10252 (S601). The job execution manager 102 also checks whether the line read in S601 is a job within an event reception job net (S602). This event reception job net is generated by the job execution manager 102, which is the information processing device of this embodiment, and is the event reception job net 914 outlined in FIG. 10. It is also assumed that the job execution manager 102 stores and manages information about the jobs and job nets placed in this event reception job net 914 in the storage device 1025 or memory 1022.

[0046] If the result of the above determination is that the job in the target row is a job in the event receiving job net 914 (S602: Yes), the job execution manager 102 reads the next row in the job definition list 10252 (S606) and executes S602 again. On the other hand, if the result of the above determination is that the job in the target row is not a job in the event receiving job net 914 (S602: No), the job execution manager 102 checks the value of column 502 in the job definition list 10252 to see if there is a delay monitoring setting (S603).

[0047] If the result of the above check shows that there is no delay monitoring setting (S603: No), the job execution manager 102 reads the next line in the job definition list 10252 (S606) and re-executes the process from S602. On the other hand, if the result of the above check shows that there is a delay monitoring setting (S603: Yes), the job execution manager 102 determines that the job in that line is a milestone job and adds definition information for an event sending job and an event receiving job associated with the milestone job to the last line 504 of the job definition list 10252 (S604).

[0048] Next, the job execution manager 102 determines whether the line currently being processed is the last line in the job definition list 10252 (S605). If the result of this determination is that the line is not the last line (S605: No), the job execution manager 102 reads the next line in the job definition list 10252 (S606) and executes the flow again from S602. On the other hand, if the result of the above determination is that the line is the last line (S605: Yes), the job execution manager 102 ends the flow.

[0049] For example, in the job definition list 10252 shown in FIG. 5, the value "Yes" 503 is set in the "Delay Monitoring Setting" 502 field for "Job 7." Therefore, in the above flow, "Job 7" is determined to be a milestone job. In this case, the job execution manager 102 adds rows of definition information for an event sending job and an event receiving job associated with "Job 7" to the last row 504 of the job definition list 10252. For example, in the job flow shown in FIG. 10, an event sending job 902 and a corresponding event receiving job 903 are created for "Job 7," which is the milestone job. The event receiving job 903 is placed in an event receiving job net 914.

[0050] Next, the specific processing of S403 in the flow of Fig. 6, which determines a milestone job from the viewpoint of processing importance, will be described based on the flow of Fig. 8. In this flow, a job in which the number of preceding jobs, job nets, or succeeding jobs or job nets within each job net is equal to or exceeds a predetermined reference value is determined to be a milestone job, since the completion of that job will have a large impact on the progress of the entire job net, that is, it is a job or job net with high processing importance.

[0051] In this case, the job execution manager 102 reads the first line 501 of the job definition list 10252 (S701). The job execution manager 102 also checks whether the job in the line read above is a job in the event reception job net 914 (S702). If the result of this determination is that the job in the line is a job in the event reception job net 914 (702: Yes), the job execution manager 102 reads the next line (S711) and executes S702 again.

[0052] On the other hand, if the result of the above determination is that the job in the row is not a job in the event reception jobnet 914 (S702: No), the job execution manager 102 checks whether the preceding job column 505 in the job definition list 10252 for that row is blank (S703). If the result of this determination is that the preceding job column 505 is blank (S703: Yes), the job execution manager 102 reads the next row in the job definition list 10252 (S711) and returns the process to S702. On the other hand, if the result of the above determination is that the preceding job column 505 is not blank (S703: No), the job execution manager 102 counts the unit names in the unit name column 506 in the job definition list 10252 for each unit name (S704) and uses this as the number of preceding jobs.

[0053] For example, in the preceding job column 507 of the job definition list 10252, the job name 508 listed in the unit name column for "Job 4" is "Job 6," and the same is true for the next row. Therefore, when these two rows are read, the preceding job count for "Job 6" is 2. Since there are two, it can be confirmed that the number of preceding jobs for "Job 6" is "2."

[0054] Next, the job execution manager 102 determines whether the number of preceding jobs confirmed in S704 exceeds a predetermined reference threshold (S705). If the result of this determination is that the number of preceding jobs exceeds the reference threshold (S705: Yes), the job execution manager 102 determines that the job is a milestone job (S706). In addition, the job execution manager 102 adds definition information for an event sending job and an event receiving job associated with this milestone job to the last line 504 of the job definition list 10252 (S706).

[0055] Furthermore, once the addition in S706 above is complete, or if the number of preceding jobs in S705 is equal to or less than the reference threshold (S705: No), the job execution manager 102 counts the unit names in the preceding job column 505 for each unit name (S707) and uses this as the number of succeeding jobs. For example, the value 510 entered in the preceding job column 505 for "Job 12" in row 509 is "Job 11," and the same is true for the next and following rows. Therefore, when these three rows are read, the succeeding job count for "Job 11" is three. Since there are three, it can be confirmed that the number of succeeding jobs is "3."

[0056] Next, the job execution manager 102 determines whether the number of subsequent jobs confirmed in S707 exceeds a predetermined reference threshold (S708). If the result of this determination is that the number of subsequent jobs exceeds the reference threshold (S708: Yes), the job execution manager 102 determines that the job in that row is a milestone job (S709) and adds definition information for an event transmission job and an event reception job associated with the milestone job to the last row 504 of the job definition list 10252 (S709). Once S709 is complete, or if the number of subsequent jobs is equal to or less than the reference threshold in S705 (S708: No), the job execution manager 102 checks whether the currently read row is the last row (S710). If it is not the last row (S710: No), the job execution manager 102 reads the next row in S711. This process is repeated until the last row is reached.

[0057] 4, if "event sending job A" 303 is determined to be a milestone job, "event receiving job B" 906 corresponding to "event sending job 2" 905 is created. "Event receiving job B" 906 is placed in an event receiving job net 914.

[0058] Finally, the specific content of S404 in the flow of Fig. 6 will be explained in Fig. 8. In this flow, if there is a problem with the job net in the system that sends the event, the job that links events between systems, such as "System A" and "System B," will also affect other systems, such as the system that receives the event. For this reason, the job in question will be determined to be a milestone job.

[0059] Here, the job execution manager 102 reads the first row 501 of the job definition list 10252 (S801). The job execution manager 102 also checks whether the job is an event transmission job based on the value of the unit type column 511 of the row read in S801 (S802). If this check shows that the job in that row is not an event transmission job (S802: No), the job execution manager 102 reads the next row (S809) and restarts the flow from S802. On the other hand, if the check shows that the job in that row is an event transmission job (S802: Yes), the job execution manager 102 newly reads the first row 501 of the job definition list 10252 (S803).

[0060] The job execution manager 102 also checks whether the job in the row read in S801 or S809 above is an event reception job that pairs with the event transmission job read in S803 and whether the execution host 512 is different (S804). If the result of the above check is that the job in the row matches the above conditions (S804: Yes), the job execution manager 102 determines that the read event transmission job is a milestone job (S805). The job execution manager 102 also adds definition information for the event reception job and event transmission job associated with this milestone job to the last row 504 of the job definition list 10252. The job execution manager 102 also deletes the event transmission job that matched the conditions in S804 above.

[0061] On the other hand, if the result of the above check shows that the job of the row does not match the above condition (S804: No), the job execution manager 102 checks whether the row read in S803 is the last row in the job definition list 10252 (S806). If the result of this check shows that the row is not the last row (S806: No), the job execution manager 102 reads the next row in the job definition list 10252 (S807) and returns the process to S804. The job execution manager 102 repeats this process until it reaches the last row of the job definition list 10252.

[0062] When the job execution manager 102 has processed up to the last line of the job definition list 10252 (S806: Yes), it checks whether the line read in S801 or S809 is the last line (S808). If the result of this check shows that the line is not the last line (S808: No), the job execution manager 102 reads the next line in the job definition list 10252 (S809) and returns the process to S802. The job execution manager 102 repeats this process until it reaches the last line.

[0063] For example, the "event transmission job A" and "event reception job A" in the unit name column 513 in the job definition list 10252 have different host names 514 (values ​​in the execution host column 512) and meet the condition in S804. Therefore, the job in that row is determined to be a milestone job. In this case, the job execution manager 102 adds definition information for the event reception job and event transmission job associated with the milestone job to the job definition list 10252 and deletes the job definition for "event reception job A" from the job definition list 10252. For example, if "job 6" in FIG. 10 is determined to be a milestone job, job 917, which is "event transmission job 3," and job 912, which is "event reception job 3," are created. Job 912, which is "event reception job 3," is placed in the event reception jobnet 914. The selection of jobs to be placed in the event reception jobnet 914 based on the above three criteria is now complete.

[0064] Next, the job net position adjustment process executed in S405 and S406 in the flow of Fig. 6 will be described with reference to the flow diagram of Fig. 11. In this case, the vertical position is specified to arrange the jobs in the event reception job net 914 by system. Therefore, the job execution manager 102 reads the first line 501 of the job definition list 10252 (S1001).

[0065] Next, the job execution manager 102 determines (S1002) whether the line read in S1001 above is a job in the event reception job net 914. If the result of this determination is that the job in the line is not a job in the event reception job net 914 (S1002: No), the job execution manager 102 reads the next line in the job definition list 10252 (S1006) and executes S1002 again.

[0066] On the other hand, if the result of the above determination is that the job in the row is a job in the event receiving jobnet 914 (S1002: Yes), the job execution manager 102 checks the value of the execution host 512 in the job definition list 10252 (S1003) and determines the position (vertical) 515 in the display area of ​​the event receiving jobnet 914 according to the execution host (S1004). In this case, for example, the positions (vertical) are determined sequentially from top to bottom in the display area in a predetermined order for each host.

[0067] The job execution manager 102 also checks whether the line read in S1001 is the last line (S1005). If the result of this check is that the line is not the last line (S1005: No), the job execution manager 102 reads the next line in the job definition list 10252 (S1006). The job execution manager 102 repeats this process until it reaches the last line.

[0068] Next, the processing of S406 in the flow of Fig. 6 will be described with reference to Fig. 12 and Fig. 13. In this flow, the horizontal direction of the display area of ​​the event reception job net 914 is used as the time axis, as shown in Fig. 13, and the job position is adjusted by checking against the log of the actual end time of the job in the event reception job net 914.

[0069] In this case, the job execution manager 102 first reads the first line 501 of the job definition list 10252 (S1201). Next, the job execution manager 102 checks whether the line read in S1201 is a job in the event reception job net 914 (S1202). If this check shows that the job in that line is not a job in the event reception job net 914 (S1202: No), the job execution manager 102 reads the next line in the job definition list 10252 (S1206) and executes S1202 again.

[0070] On the other hand, if the result of the above check is that the job in the row is a job in the event reception jobnet 914 (S1202: Yes), the job execution manager 102 reads the log of the corresponding job and calculates the average end time for the last three months (S1203). This log is acquired in advance by the job execution manager 102 from the job execution agents 103 to 105 at an appropriate timing and is stored in the storage device 1025 so that it can be used.

[0071] Next, the job execution manager 102 determines the value of the position (horizontal) 516 of the job definition list 10252 based on the end time calculated in S1203 (S1204). This value of the position (horizontal) 516 determines where the object corresponding to the job is placed on the horizontal time axis in the display area of ​​the event reception jobnet 914, i.e., it can be assumed to be a coordinate value in the display area. The job execution manager 102 checks whether the line read in S1201 is the last line (S120). If this check shows that it is not the last line (S1205: No), the job execution manager 102 reads the next line (S1206) and returns the process to S1202. The job execution manager 102 repeats this process until the last line is reached.

[0072] The event receiving job net is now complete. An example is the event receiving job net 914 in FIG. 13. An event sending job and an event receiving job are created corresponding to the job determined to be a milestone job, and of these, the event receiving job is placed in the event receiving job net 914. At this time, the objects of the event receiving job and the event sending job are placed in the display area of ​​the event receiving job net 914 in the horizontal direction, i.e., along the time axis, with a shift set to the left or right of the position of the time object 9141 according to the difference between the end time and the originally scheduled end time (for example, the format defined in the job definition list 10252 or the format managed by the job execution agents 103 to 105). This shift corresponds to the difference between the end time and the originally scheduled end time 9142 (in FIG. 13, an arrow 9144 is placed with a direction and size according to the difference). This allows the user to visually get an overview of the progress of milestone jobs and grasp the overall picture by viewing the information in the event reception job net 914 on the viewer of the client PC 101. This allows the user to grasp the overall progress of each job net and job in each system on a single screen, and also enables evaluation of whether the end time of each job is later or earlier than normal.

[0073] As described above, the business management system 100 of this embodiment makes it possible to provide an overview of the information required for maintenance and operation work, regardless of the scale and complexity of the configuration and linkage of jobs and jobnets in the target system.

[0074] The present invention is not limited to the above-described embodiments, and includes various modifications and equivalent configurations within the spirit of the appended claims. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to configurations including all of the described configurations. Furthermore, part of the configuration of one embodiment may be replaced with the configuration of another embodiment. Furthermore, the configuration of another embodiment may be added to the configuration of one embodiment. Furthermore, part of the configuration of each embodiment may be added, deleted, or replaced with other configurations.

[0075] Furthermore, the above-described configurations, functions, processing units, processing means, etc. may be partially or entirely implemented in hardware, for example, by designing them as integrated circuits. The above-described configurations, functions, etc. may also be implemented in software, with a processor interpreting and executing a program that implements each function. Information such as the program, table, and file that implements each function can be stored in memory 1022, a recording device 1025 such as a hard disk or SSD (Solid State Drive), or a recording medium such as an IC card, SD card, or DVD.

[0076] In addition, the control lines and information lines shown are those that are considered necessary for explanation, and do not necessarily represent all the control lines and information lines that are necessary for implementation. In reality, it can be assumed that almost all components are interconnected.

[0077] The above various explanations can be summarized as follows: The following summary may include supplementary explanations and explanations of variations of the above explanations.

[0078] In the business management method of this embodiment, the information processing device may output a job flow display screen including at least each piece of information about the first job net and the second job net.

[0079] This allows users to visually overview numerous interconnected jobs and jobnets, and ultimately makes it possible to present information necessary for maintenance and operation work in an overview format, regardless of the scale and complexity of the configuration and interconnections of jobs and jobnets in the target system.

[0080] In addition, in the business management method of this embodiment, the information processing device may make the judgment regarding the milestone job based on whether or not delay monitoring is set in the components of the first jobnet.

[0081] This allows jobs or jobnets whose delay in the start or end of execution would have a significant impact on the execution schedule of linked jobs or jobnets to be accurately identified as milestone jobs and applied to subsequent processing.Furthermore, it makes it possible to present information necessary for maintenance and operation work at a high level, regardless of the configuration of jobs or jobnets in the target system, or the scale and complexity of the linkages.

[0082] In addition, in the business management method of this embodiment, when making the judgment regarding the milestone job, the information processing device may determine that a component of the first job network that has a number of preceding jobs or succeeding jobs equal to or greater than a predetermined threshold is a milestone job.

[0083] This makes it possible to accurately identify milestone jobs by recognizing the number of linked targets, i.e., the magnitude of the impact on the system. Ultimately, it makes it possible to provide an overview of the information needed for maintenance and operation work, regardless of the size and complexity of the job and jobnet configurations and links in the target system.

[0084] In addition, in the business management method of this embodiment, when making the judgment regarding the milestone job, the information processing device may determine that a job among the components of the first job network that has event coordination between systems is a milestone job.

[0085] This makes it possible to identify milestone jobs based on the demand for jobs or jobnets that require collaboration between different systems. This also makes it possible to provide an overview of the information required for maintenance and operation work, regardless of the size and complexity of the job or jobnet configuration or collaboration in the target system.

[0086] Furthermore, in the business management method of this embodiment, the information processing device may list objects corresponding to each execution time in the upper row of the display area corresponding to the second jobnet on the job flow display screen, and place the event receiving job or the event sending job that constitutes the second jobnet in the middle row at the position of the completion time zone of the event receiving job or the event sending job, respectively, based on the object position of each execution time in the upper row.

[0087] This makes it possible to present to the user in a visually clear manner the execution order and timing of jobs directly involved in milestone jobs (event reception jobs and event transmission jobs), taking into account the linkages with each job and jobnet. As a result, it becomes possible to present information necessary for maintenance and operation work in an overview, regardless of the size and complexity of the configuration and linkages of jobs and jobnets in the target system.

[0088] Furthermore, in the business management method of this embodiment, the information processing device may arrange objects representing the target system in a vertical direction at either the left or right end of the display area corresponding to the second jobnet on the job flow display screen, and arrange objects of the jobnet in the target system on the same level as the objects representing the target system.

[0089] This makes it possible to present to the user in a visually clear manner the execution order and execution timing of jobs or jobnets in a configuration where jobs or jobnets are linked between systems.In turn, it makes it possible to present information necessary for maintenance and operation work in an overview, regardless of the scale and complexity of the configuration and linkage of jobs and jobnets in the target systems.

[0090] The information processing device may be configured to arrange the objects of each job in the display area corresponding to the second jobnet based on actual data on the execution time of each job that constitutes the second jobnet, using the object position at each execution time as a reference.

[0091] This makes it possible to present to the user information that can be used to consider the success or failure of the linkage of each job or job net, delays, etc., based on the actual execution status of the job or job net, etc. Furthermore, it becomes possible to present information necessary for maintenance and operation work from a bird's-eye view, regardless of the size and complexity of the configuration and linkage of jobs and job nets in the target system. [Explanation of symbols]

[0092] 100 Business Management System 101 Client PC 102 Job Execution Manager 1021 I / O 1022 memory 1023 Communication Equipment 1024 CPU (computing unit) 1025 Storage device 10251 Program 10252 Job definition list 103~105 Job execution agent

Claims

1. An information processing device that supports system management definition information relating to jobs and jobnets in the system is stored in a storage device; a process of making a determination regarding a milestone job for a component of a first job net in the system based on the definition information; If the component is determined to be a milestone job as a result of the determination, a process of creating event jobs for event transmission and event reception associated with the milestone job; a process of creating a second job net for aggregating the event jobs; placing the event transmission job before or after execution of the milestone job; a process of placing at least the event receiving job out of the event receiving job and the event transmitting job in the second job net; A business management method characterized by executing the above.

2. The information processing device, outputting a job flow display screen including at least each piece of information about the first job net and the second job net; 2. The business management method according to claim 1, wherein:

3. The information processing device, When making the determination regarding the milestone job, the determination is made based on whether or not a delay monitoring setting is set for the component of the first job net.

2. The business management method according to claim 1, wherein:

4. The information processing device, In the determination regarding the milestone job, a job having a number of preceding jobs or succeeding jobs equal to or greater than a predetermined threshold among the components of the first job net is determined to be a milestone job.

4. The business management method according to claim 3, wherein:

5. The information processing device, When making the determination regarding the milestone job, a job that performs event linkage between systems among the components of the first job net is determined to be a milestone job.

2. The business management method according to claim 1, wherein:

6. The information processing device, On the display screen for the job flow, objects corresponding to each execution time are listed in the upper row of a display area corresponding to the second job net, and the event receiving job or the event sending job constituting the second job net is arranged in the middle row at a position corresponding to a completion time zone of the event receiving job or the event sending job, based on the object positions of the objects at each execution time in the upper row.

3. The business management method according to claim 2, wherein:

7. The information processing device, On the display screen for the job flow, objects representing target systems are arranged vertically at either the left or right end of a display area corresponding to the second job net, and objects of the job net in the target system are arranged in the same row as the objects representing the target systems.

7. The business management method according to claim 6, wherein:

8. The information processing device, arranging the objects of each job in the display area corresponding to the second job net based on performance data of the execution time of each job constituting the second job net, with the object positions at the execution times as a reference; 7. The business management method according to claim 6, wherein:

9. a storage device for storing definition information relating to jobs and jobnets in the target system; a computing device that executes a process of determining whether a component of a first job net in the system is a milestone job based on the definition information, and if the component is determined to be a milestone job as a result of the determination, a process of creating an event sending job and an event receiving job associated with the milestone job, a process of creating a second job net for aggregating the event receiving jobs, a process of placing the event sending job before or after execution of the milestone job, and a process of placing the event receiving job in the second job net; A business management system including an information processing device.

Images