JPWO2016084212A1 - Control server and control application grouping method - Google Patents

Control server and control application grouping method Download PDF

Info

Publication number
JPWO2016084212A1
JPWO2016084212A1 JP2014081488A JP2016561176A JPWO2016084212A1 JP WO2016084212 A1 JPWO2016084212 A1 JP WO2016084212A1 JP 2014081488 A JP2014081488 A JP 2014081488A JP 2016561176 A JP2016561176 A JP 2016561176A JP WO2016084212 A1 JPWO2016084212 A1 JP WO2016084212A1
Authority
JP
Japan
Prior art keywords
application
control
priority
group
applications
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
JP2014081488A
Other languages
Japanese (ja)
Inventor
崇博 大平
崇博 大平
直之 武田
直之 武田
Original Assignee
株式会社日立製作所
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社日立製作所 filed Critical 株式会社日立製作所
Priority to PCT/JP2014/081488 priority Critical patent/WO2016084212A1/en
Publication of JPWO2016084212A1 publication Critical patent/JPWO2016084212A1/en
Application status is Pending legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/48Program initiating; Program switching, e.g. by interrupt

Abstract

An object of the present invention is to manage operations according to the characteristics of various applications in a monitoring control system in which a plurality of types of application programs operate. Means for solving this problem include a real-time control application that performs control calculation based on data collected from the field equipment and outputs control to the controller, and an equipment state of the field equipment for the external terminal. A plurality of applications are grouped into a screen application that transmits and receives control instructions from the user via the external terminal and processes them, and a planning application that receives and processes control plans from the plan server, An application operation priority is predetermined for each group, and each of the plurality of applications is executed according to the predetermined priority.

Description

  The present invention relates to a control server and a control application grouping method.

In a computer system, there is a system that divides applications into a plurality of groups and executes processing according to the priority of the group. For example, in Patent Document 1, in an application server, a plurality of types of application programs are classified into a plurality of groups according to priority, executed with priority specified for the group, and appropriate according to transaction processing time. It describes that load control is performed.

International Publication No. 2005/041038

  In a control server constituting a monitoring control system such as an industrial plant or a power system, a plurality of types of control applications are operating. This control application includes, for example, a real-time control application that performs real-time control based on sensor data of a plant and the like, and is necessary for constantly monitoring the system status in an external terminal device and controlling it by human operation as necessary. There are screen-related applications mounted on the server, planning-related applications that plan the operation of the monitoring control system, and the like. As described above, in the control server, the real-time control application, the screen system application, the planning system application, and the like operate together on the control server.

  Here, in the technique of the above-mentioned patent document 1, it is described that a plurality of types of application programs are classified into a plurality of groups according to priority, and executed with the priority specified for the group to which each application program belongs. Yes.

  However, when the technique of Patent Document 1 is applied to a control server, among the multiple types of control applications that operate on the control server, what operation is prioritized is determined according to the specific characteristics of each application. It is necessary, but this point is not taken into consideration at all.

  An object of the present invention is to provide a control server or a control application grouping method capable of managing operations in accordance with characteristics of various applications in a monitoring control system in which a plurality of types of application programs operate. That is.

One of the representative control server and control application grouping methods of the present invention for achieving the above object is to perform control calculation based on data collected from the field equipment and to output control output to the controller. A real-time control application to be performed, a screen application for transmitting the equipment state of the field equipment to an external terminal, receiving a control instruction from a user via the external terminal and processing, and a control plan from a plan server Grouping a plurality of applications into the planned application to be processed in advance, predetermining the priority of operation of each application for each group, and executing each of the plurality of applications according to the predetermined priority Features.

In a supervisory control system in which a plurality of application programs operate, it becomes possible to manage the operation according to the characteristics of various applications.

It is a block diagram of the grouping method concerning this invention. It is a figure which shows the process management table in FIG. It is a figure which shows the priority control table in FIG. It is a flowchart of the group control mechanism in FIG. It is a figure which shows the constraint management table in FIG. It is a flowchart of the group registration mechanism in FIG. It is a flowchart of the constraint check mechanism in FIG. It is a figure which shows the trace filter setting in FIG. It is a flowchart of the trace control mechanism in FIG.

  In the following, as an embodiment to which the present invention is applied, a method of managing in a group with respect to design and testing of application processing installed in a control server in a control application in the control server will be described.

  The grouping method of control applications on the control server in this embodiment has a configuration as shown in FIG.

  FIG. 1 is a diagram showing a system configuration of a monitoring control system which is an embodiment to which the present invention is applied. In the monitoring control system of the present embodiment, the control server 1, the controller 2, the external terminal 3, and the planning server 4 are connected via an external network. Further, the external network connecting the control server 1 and the controller 2 and the external network connecting the control server 1 and the external terminal 3 and the planning server 4 are different networks.

  The control server 1 includes a CPU 11, a memory 12, a disk device 13, a network I / F 14, and a display device 15 as hardware configurations, each of which is connected by a bus.

  The CPU 11 transfers a program from the disk device 13 to the memory 12 and executes this program. Examples of the program to be executed include an operating system (hereinafter referred to as “OS”) and an application program operating on the OS.

  The memory 12 is a temporary storage area for the CPU 11 to operate, and stores, for example, an OS and application programs transferred from the disk device 13.

  The disk device 13 is an information storage medium. The disk device 13 stores an OS, application programs, device drivers, and a program for operating the CPU 11, and also stores program execution results. Examples of the disk device 13 include a hard disk drive (HDD), a solid state drive (SSD), and a flash memory. The disk device 13 may be an external storage medium that can be easily removed. As such an external storage medium, for example, a flexible disk (FD), an optical disk such as a CD or a DVD, a flash memory such as a USB memory or a compact flash (registered trademark) can be used.

  The network I / F 14 has a communication function with an external network. The network I / F 14 receives a communication request from a program executed by the CPU 11 and communicates with an external network. Examples of the network I / F 14 include ICs such as an IEEE 802.3 standard MAC (Media Access Control) chip, a PHY (physical layer) chip, a combined MAC and PHY chip, an FPGA, a CPLD, an ASIC, and a gate array. The network I / F 14 may be included in the CPU 11 or a chip set that controls an information path inside the computer.

  The display screen 15 is a device that displays operations on the control server 1, monitoring data of field facilities, and the like, and can be exemplified by a CRT (Cathode Ray Tube) or an LCD (Liquid crystal display).

  Examples of the bus include a PCI bus, an ISA bus, a PCI Express bus, a system bus, and a memory bus.

  Next, functions of the control server 1 will be described. In FIG. 1, various programs executed by the CPU 11 are described as a functional block diagram on the memory 12, and various tables and filters are described on the disk device 13.

  The applications executed by the CPU 11 include at least a real time control application 125, a screen system application 126, and a planning system application 127, which are classified into a real time group, a screen system group, and a planning system group, respectively. The characteristics of each application will be described later.

  In addition, as other programs executed by the CPU 11, a group control mechanism 121, a group registration mechanism 122, a constraint check mechanism 123, and a trace control mechanism 124 are included. The disk device 132 also stores a process management table 131, a priority control table 132, a constraint management table 133, and a trace filter setting 134. Details of each mechanism and table will be described later.

  The controller 2 is a device that handles sensor data and the like installed in on-site equipment by a monitoring control system. Data from the controller 2 is collected by the control server 1, control judgment is performed according to the plan, and control output is performed as necessary. It is the real time control application 125 that handles this on the control server.

  The external terminal 3 is a terminal in which the operator refers to the on-site equipment state in the supervisory control system and gives a control instruction as necessary. The screen system application 126 processes this on the control server. .

  The plan server 4 is a server that performs a control plan of the monitoring control system, and processes information such as sensor data by the control server based on the control plan. The plan application 127 performs this processing in the control server.

  Further, the control server 1 collects OS trace information for performance analysis and failure analysis of these applications (real-time control application 125, screen application 126, and planning application 127). In the present embodiment, the group control mechanism 121 performs group management of various applications using a real-time group, a screen system group, and a planning system group, and performs operations according to the characteristics of the various applications, thereby causing the control server 1 to perform optimal operations. This characteristic is set in the priority control table 132 in advance, and the group control mechanism 121 operates using this.

  In addition, the program constituting the group is managed in the process management table 131, and the group control mechanism 121 determines the group based on this information when the process is executed, and the process based on the information in the priority control table 132. By operating, it is possible to operate according to the characteristics. The group registration mechanism 122 is a mechanism for registering programs in these groups, and the constraint check mechanism 123 is a mechanism for confirming whether a program can be registered in a group.

  The group registration mechanism 122 receives the group number to be registered, the program name, and the source code, and first calls the constraint check mechanism 123 to check whether the source code can be registered. If the check is successful in the constraint check, registration in the process management table 131 is performed.

  The constraint checking mechanism 123 confirms whether the constraints defined for each group are observed in the source code. This constraint is held in the constraint management table 133, and the constraint check mechanism 123 confirms the source code using the contents of this table. As a result, only the program in which the restrictions are observed can be executed in the group, and it can be determined whether or not the program is correctly designed at the time of registration.

The trace control mechanism 124 is a mechanism for performing control so as to collect OS traces required by various applications. Since various applications are managed in groups, trace points required in each group are managed in the trace filter settings, and tracing is controlled efficiently based on this information by controlling the OS trace. A long-time trace can be collected for a collection area of a finite capacity.

<Group control>
First, group control performed by the control server 1 of the present embodiment will be described.

  As described above, the control server 1 operates a plurality of applications such as the real-time control application 125, the screen system application 126, and the planning system application 127. In order to design these applications, it is necessary to set processor execution priority, disk access processing priority, and network processing priority for each process according to the characteristics of various applications based on the overall design of all applications. .

  FIG. 2 is a diagram showing the contents of the process management table 131. The process management table 131 stores a group number, a group name that is a name of the group, and a program name that is a specific application name in association with each other. In this embodiment, the control program A is associated with the group 1 real-time program, the screen program A is associated with the group 2 screen system, and the planning program A is associated with the group 3 planning system. It is remembered.

  FIG. 3 is a diagram showing the contents of the priority control table. The priority control table 132 stores program execution priority, disk access priority, and network transmission / reception priority in association with the group number defined in the process management table 131. These priorities are set according to the characteristics of each application group.

  The real-time control application is a highly real-time application that processes time-series data such as sensor data transmitted from the outside, makes a control decision based on the data, and controls the system. For this reason, it is necessary to operate in preference to the screen application or the planning application. The screen application is an application that is processed by an operation request from a system operator or the like at an external terminal. Therefore, although the amount of data to be transmitted / received is relatively small, the application requires a response time. On the other hand, because the planning application processes data indicating the overall plan of the monitoring and control system, it is desirable that the amount of data to be transmitted and received is relatively large and the processing time is fast, but compared with other applications. Then, real-time performance is not required.

  Therefore, in this embodiment, the execution priority “high”, the disk access priority “low”, and the network priority “high” are set to correspond to the group 1 (real time) and correspond to the group 2 (screen system). The execution priority “medium”, the disk access priority “high”, and the network priority “medium” are set, and the execution priority “low”, the disk access priority “ “High” and network priority “Low” are set. FIG. 4 shows a flowchart of the group control mechanism 121. The group control mechanism 121 reads the process management table 131 in S11. In S12, the priority control table 132 is read. In S13, the program execution start is waited. When the application starts running, this wait is released. Thereafter, in S14, the program name of the application that has started execution is received, the process management table 131 is searched from the name, and the group number is specified. In S15, the priority control table 132 is referred to the specified group number, and the set priority is set for the OS. Thereby, the process of the application in a group can operate | move according to the set priority.

In this embodiment, a plurality of applications are grouped according to their characteristics, and various priorities are defined for each group. Therefore, when designing each application, it is not necessary to set priorities individually, and application design can be easily performed.
<Group registration>
Next, a process when a new application is registered as a group in the control server 1 of this embodiment will be described.

  As described above, in this embodiment, a plurality of applications are grouped into a real-time group, a screen system group, and a planning system group, and operations are performed according to their priorities.

  Here, for example, the real-time control application 125 cannot be secured when performing low-speed disk access processing. Therefore, it is necessary to design the real-time control application 125 so as not to perform disk access, but this must also be designed for each process. For this reason, in the application design process, when the applications are combined and operated after the test of each process, defects in priority and disk access processing are often extracted. This necessitates re-designing in the design process, which increases man-hours. Therefore, it is necessary to be able to confirm that the program is tailored to the characteristics at the test execution timing of each process.

  Therefore, in this embodiment, the conditions required for each group are set in the constraint management table 133 in advance, and when the application is newly registered in the group, the constraint management table 133 is checked, so that Make sure that

  FIG. 5 is a diagram showing the contents of the constraint management table 133. In the constraint management table 133, an unusable API (Application Programming Interface), a disk access capacity upper limit, and a network transmission / reception capacity upper limit are provided as conditions required for each group in association with the group number defined in the process management table 131. And are stored.

  In this embodiment, the unusable API “read, write, etc.”, the disk access capacity upper limit “none”, and the network transmission / reception capacity condition “4 KB” are set corresponding to the group 1 (real time), and the group 2 (screen system) Corresponding to, the unusable API “none”, the disk access capacity upper limit “1 MB”, the network transmission / reception capacity condition “1 MB” are set, and the unusable API “none”, disk corresponding to group 3 (planned) The access capacity upper limit “none” and the network transmission / reception capacity condition “none” are set.

  FIG. 6 shows a flowchart of the group registration mechanism 122. The group registration mechanism 122 acquires the registration group number given to the mechanism in S21, acquires the registration program name given to the mechanism in S22, and sets the registration source given to the mechanism in S23. get. Next, in S24, a group number and a source code are specified, and the constraint check mechanism 123 is called. The result of the constraint check mechanism 123 is determined in S25, and if it is a failure indicating that the constraint is not satisfied, a failure message is output and not registered in the group. If it is a success indicating that the constraint is satisfied, it is registered in the process management table in S27. In S28, a success message is output. As a result, only programs that satisfy the restrictions are registered in the group. FIG. 7 shows a flowchart of the constraint check mechanism 123. The constraint checking mechanism 123 acquires the group number and source code passed from the group registration mechanism 122 in S31. In S32, the constraint management table 133 in which constraints to be satisfied for each group are set is read. In S33, it is searched whether or not the unusable API for the group number specified in the constraint management table 133 is used on the source code. The search result is determined in S34. If it is used, the check fails. Next, in S35, it is searched whether the disk API for accessing the disk is used in the source code. If it has been used, it is determined in S36 whether the access capacity exceeds the disk access capacity upper limit specified in the constraint management table. If the upper limit is exceeded, the check fails. Next, in S37, it is searched whether the network API that performs network transmission / reception is used in the source code. If it is used, it is determined in S38 whether the transmission / reception capacity exceeds the network transmission / reception capacity upper limit specified in the constraint management table 133. If the upper limit is exceeded, the check fails. If all constraints are satisfied, the check is successful.

As described above, in this embodiment, the conditions required for the application of each group are set in the constraint management table 133 in advance, and this constraint management table 133 is used when newly registering an application as a group. It can be confirmed that the program is tailored to the characteristics. As a result, it is possible to reduce unnecessary man-hours such as extracting defects and redesigning them for the first time when the applications are combined and operated after the test of each process.

<Trace collection>
In a control server of a supervisory control system such as an industrial plant or an electric power system as in this embodiment, it is necessary to collect an OS (Operating System) operation trace for performance analysis and failure analysis of various applications. Here, since various applications have different characteristics, data required for analysis is different. However, since the characteristics of the OS are unknown, it is necessary to acquire all trace information. However, since a storage device such as a memory used for tracing is a finite resource, the time that can be collected is limited.

  Therefore, in the present embodiment, trace points for collecting traces necessary for application analysis corresponding to each group are set in advance in the trace filter setting 134 for each group, and the necessary trace is set by using the trace filter setting 134. Select and collect information.

  FIG. 8 is a diagram showing the contents of the trace filter setting 134. In the trace filter setting 134, trace points for collecting traces necessary for analyzing the application of each group are stored as a collected trace point filter in association with the group number defined in the process management table 131.

  In the present embodiment, “all (collection)” is set in correspondence with group 1 (real time), and “execution start, Execution end, network transmission / reception, disk access "is set.

  FIG. 9 shows a flowchart of the trace control mechanism 124 and trace collection. The OS trace is collected at various trace points as shown in the trace collection flowchart. In the trace collection, the group number is specified from the information of the current process currently being executed when passing the trace collection point in S44. In S45, the group determines whether the trace point information is necessary based on the collection flag. If there is no need, the collection flag is OFF, and the process ends without performing trace collection. If necessary, since the collection flag is ON, the trace is collected and the process ends. The trace control mechanism turns off the collection flag so as not to collect a trace unnecessary for the application in the group. In S41, the trace filter setting 134 is read. The trace filter setting 134 describes trace points that need to be collected. If all traces are collected, “all” is specified. In S42 and S43, collection flags are set for all trace points. A collection flag is set in S43 based on the collection necessity definition for each group of trace points in the trace filter setting. Thereby, it is possible to collect only the necessary traces in each group, and it is possible to efficiently collect traces for a long time.

  As described above, in this embodiment, trace points for collecting traces necessary for application analysis corresponding to each group are set in advance in the trace filter setting 134 for each group. Then, when collecting traces, only necessary trace information is selected and collected using the trace filter setting 134. As a result, the OS trace information for failure analysis is not collected in the same way as all processes, but the traces collected for each group are limited to the necessary traces, enabling efficient collection and long-term trace collection. It becomes.

  As described above, in this example, the group is managed according to the characteristics of various applications, and it is possible to design and test in units of groups, not in each process, to improve development efficiency, and during testing and operation. A monitoring control system that enables long-term collection of analysis trace information necessary for the above was explained.

  Specifically, the group control mechanism that manages and executes various applications in groups manages the real-time control application, the screen system application, and the planning system application in groups. The execution program in each group is controlled according to the characteristics. The real-time control application operates with priority over other applications. Further, the screen application operates the disk access and the network access with priority over the planning application. As a result, the real-time property of the real-time control application and the response time of the screen system application are shortened.

  It also has a group registration mechanism for registering various application programs in each group. It also has a constraint check mechanism so that only programs that match the characteristics of the group can be registered. By confirming with this restriction check mechanism at the time of group registration, it is possible to pick out the above-mentioned defects that cause redesign at the timing of group registration.

  The trace collection control mechanism selects traces to be collected by various applications. This makes it possible to collect for a longer time than collecting all traces by collecting only traces that match the characteristics of various applications.

  As described above, according to the present embodiment, the control server manages the real-time control application, the screen application, and the planning application in a group, and can execute each with an appropriate priority, and checks the restrictions at the time of registration. As a result, it is possible to advance the defect extraction timing, and to efficiently collect trace information necessary for analysis during application execution.

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 for easy understanding of the present invention, and are not necessarily limited to those having all the configurations described. 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. Each of the above-described configurations, functions, and the like may be realized by software by interpreting and executing a program that realizes each function by the processor. Information such as programs, tables, and files for realizing each function can be stored in a memory, a hard disk, a recording device such as an SSD (Solid State Drive), or a recording medium such as an IC card, an SD card, or a DVD.

1 control server 11 CPU
12 memory 121 group control mechanism 122 group registration mechanism 123 constraint check mechanism 124 trace control mechanism 125 real-time control application 126 screen system application 127 planning system application 13 disk device 14 network I / F
15 Display device 2 Controller 3 External terminal 4 Planning server

Claims (8)

  1. Real-time control application that performs control calculation based on data collected from the field equipment and outputs control to the controller, and transmits the equipment state of the field equipment to the external terminal, and the user via the external terminal Multiple applications are grouped into screen applications that receive and process control instructions from and planning applications that receive and process control plans from the plan server. A storage unit for storing a defined priority control table;
    A control server comprising: an arithmetic processing unit that executes the plurality of applications in accordance with the priority set in the priority control table.
  2. In claim 1,
    The control server according to claim 1, wherein an execution priority of the application, a disk access priority, and a network transmission / reception priority are determined for each group in the priority control table.
  3. In claim 2,
    In the priority control table,
    The execution priority and network transmission / reception priority of the real-time control application are set higher than the screen application and the planning application,
    The control server, wherein the disk access priority of the screen application is set higher than that of the real-time control application and the planning application.
  4. The claim 1, further comprising:
    The storage unit stores a constraint management table that defines the constraint content required for applications belonging to each group,
    The control processing unit checks whether or not an application newly registered in the group is an application satisfying a restriction content necessary for a registration destination group by using the restriction management table.
  5. In claim 4,
    In the constraint management table,
    As the restriction content required for the real-time control application, it is determined not to perform disk access and not to use a disk access interface,
    A restriction server characterized in that it is determined that a predetermined disk access capacity is not exceeded as a restriction content of a screen system application.
  6. The claim 1, further comprising:
    The storage unit stores a trace filter setting table in which trace points for collecting trace information necessary for analysis of each application are defined for each group,
    The control server, wherein the arithmetic processing unit selects and collects trace information necessary for analyzing each of the plurality of applications using the trace filter setting table.
  7. In claim 6,
    In the trace filter setting table, trace information relating to application execution start, application execution end, network transmission / reception, and disk access is defined as trace information necessary for analysis of the screen application and the planning application. A control server characterized by that.
  8. Real-time control application that performs control calculation based on data collected from the field equipment and outputs control to the controller, and transmits the equipment state of the field equipment to the external terminal, and the user via the external terminal Multiple applications are grouped into a screen application that receives and processes control instructions from and a planning application that receives and processes control plans from the plan server, and the priority of operation of each application is grouped. Predetermined,
    A control application grouping method for executing each of the plurality of applications according to the predetermined priority.
JP2014081488A 2014-11-28 2014-11-28 Control server and control application grouping method Pending JPWO2016084212A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2014/081488 WO2016084212A1 (en) 2014-11-28 2014-11-28 Control server and grouping method for control applications

Publications (1)

Publication Number Publication Date
JPWO2016084212A1 true JPWO2016084212A1 (en) 2017-07-20

Family

ID=56073827

Family Applications (1)

Application Number Title Priority Date Filing Date
JP2014081488A Pending JPWO2016084212A1 (en) 2014-11-28 2014-11-28 Control server and control application grouping method

Country Status (2)

Country Link
JP (1) JPWO2016084212A1 (en)
WO (1) WO2016084212A1 (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003067201A (en) * 2001-08-30 2003-03-07 Hitachi Ltd Controller and operating system
JP2003303181A (en) * 2002-04-09 2003-10-24 Toshiba Corp Distributed processing system and distributed processing program
JP2006281900A (en) * 2005-03-31 2006-10-19 Xanavi Informatics Corp On-vehicle information system and application execution method

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7430741B2 (en) * 2004-01-20 2008-09-30 International Business Machines Corporation Application-aware system that dynamically partitions and allocates resources on demand
US8104039B2 (en) * 2006-08-07 2012-01-24 International Business Machines Corporation Method for balancing resource sharing and application latency within a data processing system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003067201A (en) * 2001-08-30 2003-03-07 Hitachi Ltd Controller and operating system
JP2003303181A (en) * 2002-04-09 2003-10-24 Toshiba Corp Distributed processing system and distributed processing program
JP2006281900A (en) * 2005-03-31 2006-10-19 Xanavi Informatics Corp On-vehicle information system and application execution method

Also Published As

Publication number Publication date
WO2016084212A1 (en) 2016-06-02

Similar Documents

Publication Publication Date Title
CN104679602B (en) For disposing the method and system of event in storage area network
US9225554B2 (en) Device-health-based dynamic configuration of network management systems suited for network operations
US8660995B2 (en) Flexible event data content management for relevant event and alert analysis within a distributed processing system
US8676883B2 (en) Event management in a distributed processing system
JP5324958B2 (en) Method, program and apparatus for generating an integrated display of performance trends for multiple resources in a data processing system (integrated display of resource performance trends)
JP2016522947A (en) Determine and monitor the performance capabilities of computer resource services
US8151248B1 (en) Method and system for software defect management
US8924521B2 (en) Automated deployment of software for managed hardware in a storage area network
JP4555703B2 (en) Area set setting method and network system
US8943366B2 (en) Administering checkpoints for incident analysis
US9178936B2 (en) Selected alert delivery in a distributed processing system
US9219665B2 (en) Systems and methods for managing computing systems utilizing augmented reality
US20130111502A1 (en) Selected Alert Delivery In A Distributed Processing System
US8429645B2 (en) Method for optimizing migration of software applications to address needs
US20100125715A1 (en) Storage System and Operation Method Thereof
US10248671B2 (en) Dynamic migration script management
KR20120061710A (en) Data prefetch in sas expanders
US20150019197A1 (en) Database modeling and analysis
US20110145793A1 (en) Method and apparatus to semantically connect independent build and test processes
US20150169313A1 (en) Integrated system and firmware update method
US9038030B2 (en) Methods for predicting one or more defects in a computer program and devices thereof
US20070266166A1 (en) Aggregating network activity using software provenance data
US8997086B2 (en) Fix delivery system
TW201401092A (en) Method, computer system and program product for dynamically adjusting log level of a transaction
US8867819B2 (en) Information technology asset location using visual detectors

Legal Events

Date Code Title Description
A621 Written request for application examination

Free format text: JAPANESE INTERMEDIATE CODE: A621

Effective date: 20170314

A131 Notification of reasons for refusal

Free format text: JAPANESE INTERMEDIATE CODE: A131

Effective date: 20170711

A02 Decision of refusal

Free format text: JAPANESE INTERMEDIATE CODE: A02

Effective date: 20180206