Control device, program and method

Abstract

To improve the usability when managing tasks. [Solution] The management device includes a management means for managing information on multiple tasks, including tasks scheduled to be executed and tasks currently being executed, and a providing means for displaying information for managing network devices on a display. The providing means provides a dashboard including a panel showing the usage status of the management device, and one of the panels on the dashboard is a panel that displays a list of tasks based on the information of the managed multiple tasks and at least one first user interface associated with each task, and when the first user interface is operated on the panel, it provides a display of the details of the task associated with the first user interface.

Description

Technical Field

[0001] The present invention relates to a management device, a program, and a method.

Background Art

[0002] There is a technology for managing devices connected to a network. This technology can define various services, functions, etc. for one or more devices as tasks, and execute the tasks at specified dates and times, cycles, etc. Patent Document 1 discloses a method for controlling tasks when a plurality of tasks are executed in combination. In the technology disclosed in Patent Document 1, by opening a screen for editing tasks from a list of created tasks, it is possible to confirm detailed settings including the plan for executing each task.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, the technology disclosed in Patent Document 1 concerns the control of task execution and does not provide a function to present users with information about tasks that are scheduled to be executed or are currently being executed. In practice, it is desirable to be able to check the status of tasks by displaying the scheduled date and time of execution and a list of tasks that are currently being executed on a dashboard or similar. However, with this technology, if multiple tasks have been created, it is not possible to know the status of each task (executed, in progress, scheduled for execution, etc.) from the list of created tasks. Furthermore, even if it were possible to grasp the status of task execution, when editing a task, it is necessary to manually reopen the screen showing the list of created tasks, specify the task to edit, and open the task editing screen, leaving room for improvement in usability.

[0005] Therefore, the present invention aims to provide a management device, program, and method that can improve the operability when managing tasks. [Means for solving the problem]

[0006] To solve the above-mentioned problems, the management device of the present invention comprises a management means for managing information on a plurality of tasks, including tasks scheduled to be executed and tasks currently being executed, and a providing means for displaying information for managing network devices on a display. The providing means provides a dashboard including a panel showing the usage status of the management device, and one of the panels provides a panel in the dashboard that displays a list of tasks based on the information of the plurality of managed tasks and at least one first user interface associated with each task, and when the first user interface is operated on the panel, it provides a display of the details of the task associated with the first user interface. [Effects of the Invention]

[0007] According to the present invention, it is possible to provide a management device, program, and method that can improve the operability when managing tasks. [Brief explanation of the drawing]

[0008] [Figure 1] This is an overall configuration diagram of the network device management system. [Figure 2] A block diagram showing an example of a host computer's hardware configuration. [Figure 3] This diagram shows the software configuration for the manager and agent. [Figure 4] This diagram shows an example of a screen that displays a list of tasks created by a user, and an example of a screen for creating a new task. [Figure 5] This diagram shows examples of screens for creating or editing tasks and for scheduling tasks. [Figure 6] This figure shows an example of a dashboard screen. [Figure 7] This figure shows an example of a dialog box displaying information that shows the details of a task. [Figure 8] This flowchart shows the processing flow when displaying information that shows the details of a task. [Modes for carrying out the invention]

[0009] The embodiments for carrying out the present invention will be described below with reference to the drawings. Figure 1 is an overall configuration diagram of a network device management system. In a device management system, a manager that manages network devices (hereinafter referred to as "devices") provides services to devices connected to the network via agents. When there are many devices to manage, the device management system is configured on a large scale with a manager that manages the whole system and multiple agents that perform processing on devices according to the manager's instructions. On the other hand, when there are few devices to manage, the device management system is configured on a small scale on the same host with a manager and agents.

[0010] In the example shown in Figure 1, the device management system includes manager 101, directory server 105, agent 121, agent 107, router 109, and multiple devices to be managed. Specifically, the multiple devices to be managed include device 102, device 103, device 110, and device 111. Agent 121 runs on PC 120, which is the same host computer (hereinafter referred to as "host") as manager 101. PC 120 is an example of a management device described later. On the other hand, agent 107 runs on a different host than manager 101.

[0011] Devices 102, 103, 110, and 111 are network devices managed by manager 101. Of these four devices, devices 102 and 103 are connected to the same network 104 as agent 121. Communication between manager 101, devices 102, and 103 takes place via agent 121. Devices 110 and 111 are connected to the same network 108 as agent 107. Communication between manager 101 and device 110 or device 111 takes place via router 109 and agent 107.

[0012] Manager 101, directory server 105, agent 121, device 102, and device 103 are interconnected by network 104. Network 104 is, for example, a WAN (Wide Area Network). Agent 107, device 110, and device 111 are interconnected by network 108. Network 108 is, for example, a LAN (Local Area Network). Networks 104 and 108 only need to be configured to enable data transmission and reception, and any communication method can be used. For example, networks 104 and 108 can be composed of any of the following, or a combination thereof: LAN, WAN, LTE (Long Term Evolution), 5G or other cellular network, wireless network, telephone line, dedicated digital line, etc.

[0013] Network 104 and network 108 are connected by router 109. Router 109 may be configured to, for example, allow communication between manager 101 and agent 107 on network 108, but block communication between manager 101 and device 110 or device 111. In this embodiment, a large-scale configuration with two agents and four devices is used as an example for explanation. However, even when managing tens of thousands of devices through a dozen or so agents, the configuration and operation are the same as described in this embodiment.

[0014] The example shown in Figure 1 illustrates a case where the manager 101 and agents are running on the same host and a case where they are running on different hosts, but it is not limited to this. For example, if there are many devices to be managed and the device management system has a large-scale configuration, multiple agents will be configured on hosts other than the manager 101. On the other hand, if there are few devices to be managed and the device management system has a small-scale configuration, the manager 101 and agents will be configured on the same host, and there will be no agents running on hosts other than the manager 101. The configuration of the device management system in this embodiment may be a configuration in which agents run on the same host as the manager 101, a configuration in which agents run on hosts other than the manager 101, or a configuration in which these configurations are mixed.

[0015] Manager 101 provides various services and functions for managing the network devices that are the target of management. Manager 101 has a device management application. When providing services to devices, Manager 101 uses agents to communicate with the devices. Manager 101 has a built-in web service server related to the functions it provides. Manager 101 may be implemented by one or more information processing devices, a virtual machine utilizing resources provided by a data center including information processing devices, or a combination of these. Virtual machines are a fundamental technology for cloud computing.

[0016] Agent 107 and Agent 121 execute device management processing based on the instructions of Manager 101. Agent 107 and Agent 121 have agent applications. Agent 107 and Agent 121 incorporate a web service server regarding the functions provided by the manager. Also, Agent 107 and Agent 121 are respectively associated with devices according to the addresses of the devices, etc. Agent 107 is associated with Device 110 and Device 111.

[0017] Directory Server 105 is an information processing device that manages user information such as user accounts. Manager 101 and Directory Server 105 are interconnected by Network 104. Manager 101 can also be set so that users of Directory Server 105 can log in as users of Manager 101. Directory Server 105 may be realized by a virtual machine or a combination thereof that utilizes resources provided by a data center including one or more information processing devices in addition to the information processing devices.

[0018] Device 102, Device 103, Device 110, and Device 111 are network devices that are the targets of management by Manager 101 and can communicate with Manager 101 via the corresponding agents. The network device is, for example, a multifunction printer (MFP) in which a plurality of functions such as a printing function, a reading function, and a FAX function are integrated. Note that the network device may be a printer, a scanner device, an information processing device such as a 3D printer or a PC (Personal Computer), an image processing device such as a camera, or smart home appliances.

[0019] Here, the processing flow in which the network device management system executes the provision of services to the network device will be described by taking Agent 121 and Device 102 as examples.

[0020] Manager 101 instructs Agent 121 to perform operations on Device 102. Agent 121 communicates with Device 102 according to the instructions of Manager 101 and performs operations such as sending requests to Device 102. Then, Agent 121 sends the results of the operations on Device 102 to Manager 101. Examples of operations of Agent 121 on Device 102 include obtaining information from Device 102, changing the set values of Device 102, instructing the installation of applications on Device 102, instructing the update of the firmware of Device 102, etc. In this way, communication is executed between Manager 101 and Agent 121, and between Agent 121 and Device 102. Therefore, Device 102 and Manager 101 do not communicate directly.

[0021] In this embodiment, the configuration can support such a large-scale configuration. However, the application may be configured such that a single network device management application having both the functions of the manager and the agent manages the network device.

[0022] FIG. 2 is a block diagram showing an example of the hardware configuration of a host computer. Specifically, FIG. 2 shows the hardware configuration of an information processing device in which the manager and the agent operate. Here, Manager 101 is taken as an example for explanation, but the host computer and PC 120 in which Agent 121, Agent 107 or Directory Server 105 operates also have the same hardware configuration as Manager 101.

[0023] Manager 101 includes a CPU (Central Processing Unit) 201, RAM (Random Access Memory) 202, ROM (Read Only Memory) 203, and KBDC 204. Manager 101 also includes a VC (Video Controller) 205, DC (Disk Controller) 206, HDD (Hard Disk Drive) 207, and NIC (Network Interface Controller) 208. These components are connected to the system bus 209.

[0024] The CPU 201 controls the entire manager 101. The CPU 201 loads programs stored in memory such as ROM 203 and HDD 207 into RAM 202 as needed and executes them, thereby comprehensively controlling each unit connected to the system bus 209. The CPU 201 may also comprehensively control each unit connected to the system bus 209 by loading software, programs, etc. downloaded via the network into RAM 202 as needed and executing them.

[0025] RAM202 is memory that can read and write data and functions as the main memory and work area of ​​the CPU201. ROM203 is memory dedicated to data reading and stores, for example, the basic control program of the manager101. HDD207 stores various applications including the boot program, operating system (OS), authentication client, certificates, data, etc. External storage device 210 is memory such as an HDD or SSD. External storage device 210 stores various applications, database data, user files, etc.

[0026] KBDC204 controls input to manager 101. KBDC204 sends input information from input devices such as keyboards and pointing devices (not shown), virtual keyboards, and voice input to CPU201 to control input to manager 101. VC205 controls display on a display device (not shown). The display device may be, for example, a liquid crystal display (LCD) or a head-mounted display (HMD) capable of displaying virtual reality (VR).

[0027] DC206 controls access to the external storage device 210. NIC208 is a communication controller. Manager 101 is connected to network 104 via NIC208. CPU201 is connected to network 104 via NIC208 and enables data communication with each device on the network.

[0028] Figure 3 shows the software configuration of the manager and agent. Specifically, Figure 3 is a diagram illustrating the software configuration of the device management server and agent. Figure 3(A) is a diagram illustrating the software configuration of manager 101.

[0029] The manager 101 shown in Figure 3(A) is responsible for the main functions of a management device that manages network devices, and comprises management means and provisioning means.

[0030] The management means manages information on multiple tasks, including tasks scheduled to be executed and tasks currently being executed. The providing means provides a display for information for managing network devices. The providing means provides a dashboard that includes a panel showing the usage status of the management device. The providing means also provides a panel within the dashboard, as one of the panels, that displays a list of tasks based on information on the multiple managed tasks, and at least one primary user interface associated with each task. Furthermore, when a primary user interface is operated on the panel, the providing means provides a display of the details of the task associated with the primary user interface.

[0031] The service provider may provide, as task details, a display of settings and scheduling settings specific to the type of task associated with the first user interface being operated among the tasks displayed on the panel.

[0032] The first user interface may be the section on the panel that displays the task name. The providing means may then provide a display of the task details corresponding to the first user interface, which is the task name display section, when the section is manipulated.

[0033] A second user interface may be displayed within the screen for displaying task details. Furthermore, if the second user interface is operated, the provider may further provide an editing screen for editing the content of the task whose details were being displayed.

[0034] The second user interface may be the section displaying the task name on the screen for displaying task details. The providing means may then provide the display of the task editing screen corresponding to the task when the task name display section, which is the second user interface, is manipulated.

[0035] Note that the first user interface and the second user interface may be the same user interface.

[0036] Manager 101 calls a device management application program from memory, which is then executed by CPU 201, thereby enabling the processing performed by the functional module shown in Figure 3(A). The functional module shown in Figure 3(A) is provided, for example, as a device management application.

[0037] Manager 101 includes an agent management unit 301, a device management unit 302, a task management unit 303, an HTTPS server 304, and a display unit 305. The agent management unit 301 manages information about agents in the system, namely agents 121 and 107. The device management unit 302 manages information about devices that are the target of management, such as devices 102, 103, 110, and 111. The device information includes information indicating the agents associated with the devices. The task management unit 303 performs task management. For example, the task management unit 303 manages the content and results of operations on devices. The task management unit 303 also instructs agents to perform operations on devices by executing tasks. The management information managed by the task management unit 303 is stored in a database (not shown).

[0038] The HTTP / HTTPS server 304 is a web service server built into the manager 101 that handles services provided by the manager 101. The HTTP / HTTPS server 304 receives requests from external devices such as agents and devices, and returns responses to those requests. The HTTP / HTTPS server 304 also provides a web user interface for users to operate the manager 101.

[0039] The display unit 305 controls the display of screens provided by the manager 101. In this embodiment, the display unit 305 displays a dashboard screen, a screen showing a list of created tasks, and a screen for creating or editing tasks. The display unit 305 may display the screen on a display device (not shown) by controlling the VC205, or it may display the screen on a web browser.

[0040] Figure 3(B) is a diagram illustrating the software configuration of the agent. Here, agent 107 is used as an example, but other agents 121 have a similar configuration. Agent 107 implements the processing by the functional modules shown in Figure 3(B) by having the CPU 201 execute an application program for the device management agent that has been called from memory. The functional modules shown in Figure 3(B) are functional modules related to services provided by manager 101, and are provided, for example, as agent applications provided by manager 101.

[0041] Agent 107 includes a task execution unit 310, an HTTPS server 311, and a cache control unit 312. The task execution unit 310 executes tasks instructed by the manager 101. After performing operations on the device according to the instructions of the manager 101, the task execution unit 310 sends the results to the manager 101.

[0042] The HTTP / HTTPS server 311 is a web service server built into the agent 107 that handles services provided by the manager 101. The HTTP / HTTPS server 311 receives requests from the manager 101 and external devices such as other devices. The manager 101 and the agent 107 communicate with each other mainly using HTTPS, via the manager 101's HTTPS server 304 and the agent 107's HTTPS server 311. The cache control unit 312 provides a content caching function for the manager 101. Static content, such as data for firmware updates, can be stored as a cache in the agent 107 for a certain period of time. Therefore, if the same static content is requested from different devices, the agent 107 can send the temporarily stored cache to the device and provide the content at a faster speed. In addition, by using the cache, communication between the manager 101 and the agent 107 is reduced, and the load on the manager 101 is alleviated.

[0043] Figure 4 shows an example of a screen that displays a list of tasks created by the user and a screen for creating a new task. These screens are provided by Manager 101.

[0044] Figure 4(A) shows an example of a screen display of a list of tasks created by a user. The task list display screen 401 is provided by the task management unit 303 of the manager 101, and its display is controlled by the display unit 305. The task list display screen 401 displays the task list 401 created by the user and a button 403 for creating a new task. The task list 401 includes the task name, the task's enabled / disabled status, a button 403 for duplicating the task, the task type, and the task's execution schedule. When the manager 101 detects that the user has pressed the duplicate button 403, it creates a duplicate of the task for which the duplicate button 403 was pressed and sets the status of the created task to "disabled". Also, when the manager 101 detects that the user has pressed the duplicate button 403, it adds an indication that it is a duplicate to the name. For example, the manager 101 might set it to "Duplicate of Send Counter Report". Then, the manager 101 adds the created task to the task list 401.

[0045] Manager 101 displays the schedule in the task list 401 according to the task's scheduling settings. If a task is executed regularly, such as daily or on the third Monday of each month, Manager 101 displays the schedule frequency, such as "daily" or "monthly." If a task is executed only once at a specified date and time, Manager 101 displays that date and time. Task list 401 also includes tasks that are not scheduled to be executed in the future, such as tasks with a status of "invalid" or tasks that have already been completed at a previously specified date and time.

[0046] When the manager 101 detects that the user has clicked the name field of each task in the task list, it displays a screen for editing the task, as described later. This screen is an example of the editing user interface described above. The name fields of each task are examples of the first and second user interfaces described above. In this embodiment, both the first and second user interfaces are the names of tasks displayed on the panel. Clicking is an example of an operation on the first and second user interfaces described above. When the manager 101 detects that the user has pressed the New Create button 404, it displays the New Task Creation screen 410 shown in Figure 4(B).

[0047] Figure 4(B) is an example of the task creation screen displayed by Manager 101 when Manager 101 detects that the New Task button 404 shown in Figure 4(A) has been pressed. The New Task creation screen 410 displays a list of task types that can be added. The user moves the cursor over the task type to be added and clicks. Alternatively, the user moves the cursor over the task type to be added and presses the Enter key. When Manager 101 detects these actions performed by the user, it displays a screen for creating a new task of the selected type, as described later.

[0048] Figure 5 shows examples of the screens for creating or editing tasks and for scheduling tasks. These screens are provided by Manager 101. Figure 5(A) is displayed when the user selects "Add Certificate" on the task creation screen shown in Figure 4(B) or when the user clicks the name of an existing task of type "Add Certificate" on the task list screen shown in Figure 4(A).

[0049] The Task Type field 501 displays the task type. The Text Box 502 is for entering the task name. The Radio Button 503 is a user interface for enabling / disabling the task. If the task is disabled, the Manager 101 will not execute the task. If the task is enabled, the Manager 101 will execute the task according to the schedule set by the dropdown 504, date and time input component 505, interval setting component 511, day of the week specification component 512, time input component 513, etc.

[0050] The dropdown 504 is a user interface for specifying schedule settings. In this embodiment, the dropdown 504 provides three options: "Run immediately," "Run at a specified date and time," and "Run periodically." The date and time input component 505 is a user interface for entering the date and time on which the task will be executed. The date and time input component 505 is displayed by the manager 101 when the option "Run at a specified date and time" is selected via the dropdown 504. The date and time input component 505 is not displayed by the manager 101 when the option "Run immediately" is selected via the dropdown 504.

[0051] Figure 5(B) shows an example of the schedule setting screen when the option "Run periodically" is selected via dropdown 504. The interval setting component 511 is for setting the cycle and interval for "day," "week," and "month." The interval here is, for example, every other week. The day of the week specification component 512 is for specifying the day of the week on which the task will run when the task execution cycle is "week." If "month" is specified by the interval setting component 511, the manager 101 displays components for setting the month date to the 25th, etc., and components for setting the day of the week to the third Monday, etc. If "day" is specified by the interval setting component 511, the manager 101 does not display the day of the week specification component 512. The time input component 513 is for setting the task execution time. For example, in the example shown in Figure 5(B), it is shown that the task will run every week on Monday, Wednesday, and Friday at 2:30.

[0052] The certificate list 506 is a component for selecting certificates to distribute to printers. The certificates displayed in the certificate list 506 are pre-registered in the manager 101 by users using a certificate registration screen (not shown). The printer selection component 507 is a component for selecting printers to which certificates will be added. The manager 101 displays printers with certificate addition functionality among the printers managed by device management 302 in the printer list 506.

[0053] The save button 508 is used to save the content entered by the user on the task editing screen. The manager 101 detects when the user presses the save button 508 and, if a task was being edited, overwrites and saves it to the task management unit 303 shown in Figure 3(A). The manager 101 also detects when the user presses the save button 508 and, if a new task was being created, adds it to the task management unit 303 shown in Figure 3(A). The manager 101 controls the system so that the save button 508 cannot be pressed if there are any deficiencies in the task editing screen, for example, if the task name input 502 is not entered, or if there is no day of the week selected in the execution date specification 511.

[0054] The delete button 509 is used to delete a task. Manager 101 displays the delete button 509 only when editing an existing task. When Manager 101 detects that a user has pressed the delete button 509, it displays a confirmation dialog (not shown). If the user agrees to delete the task via the confirmation dialog, Manager 101 deletes the task to be edited from the task management unit 303 and transitions to the task list screen shown in Figure 4(A). On the other hand, if the user does not agree to delete the task via the confirmation dialog, Manager 101 closes the dialog and returns to the task editing screen shown in Figure 5(A).

[0055] The cancel button 510 is used to interrupt task editing. When the manager 101 detects that the user has pressed the cancel button 510, it discards the information the user has entered on the task editing screen and transitions the user to the task list screen shown in Figure 5(A).

[0056] Figure 6 shows an example of a dashboard screen. A dashboard is a screen that allows users to view multiple graphs, tables, etc., in a list, and is intended for visually reviewing diverse data in one place. Because the dashboard allows users to visually review data using graphs, tables, etc., it enables users to quickly analyze and make decisions. Dashboard 601 includes a pull-down menu 602 for adding panels, and panels 605, 606, and 607. Panels 605, 606, and 607 each consist of a title 603, a menu 604, and a main body whose content differs depending on the type of panel. In addition, some of these panels have a fixed width, while others allow the panel width to be switched between full width and half width.

[0057] The pull-down menu 602 is used to add panels. When a user clicks, the manager 101 displays a list of panel types that can be added and adds the type of panel selected by the user to the end of the displayed panel list. The title menu 603 allows the user to change the order in which the panels are displayed by dragging and dropping them using a pointing device such as a mouse.

[0058] When Manager 101 detects that Menu 604 has been clicked, it displays a menu for changing panel settings, changing the display order, and deleting panels, as shown in Figure 6(B). Panel settings consist of settings common to all panels, such as changing the panel name and changing the panel width, and settings specific to the panel type. These are not shown in the illustration. Panel type specific settings include, for example, the unit of aggregation for Panel 607 shown in Figure 6(A), and the specification of the details of the graph to be displayed. In the example shown in Figure 6(A), the unit of aggregation is "month". The details of the graph include, for example, whether it is color or monochrome, and whether it is double-sided or single-sided printing.

[0059] Panel 605 displays the task list. Manager 101 retrieves a list of ongoing and pending tasks from the task management unit 303 and displays it. In the example shown in Figure 6(A), Panel 605 displays the name, status, and start date and time for each task. Panel 605 allows users to easily determine the status and plan of task execution by comparing it with the created task list display screen 401. When Manager 101 detects a click on the name of a task in the task list displayed on Panel 605, it displays a dialog box to show detailed task information, which will be described later.

[0060] Figure 7 shows an example of a dialog box displaying information about a task. The dialog box shown in Figure 7 displays detailed task information and is displayed by clicking on the name of the task included in the task list on panel 605. Figure 7(A) is an example of the display of task details for adding a certificate when the setting in dropdown 504 shown in Figure 5(A) is set to "Run at a specified date and time". Figure 7(B) is an example of the display of task details for retrieving setting values ​​when the setting in dropdown 504 shown in Figure 5(A) is set to "Run periodically".

[0061] The title bar 702 displays the task name. Button 703 is pressed to close the dialog. When the button 703 is detected to have been pressed by the user, the manager 101 clears the dialog and displays the dashboard 601. The task type field 704 displays the type of the selected task. The status field 705 displays the execution status of the selected task. The start date and time field 706 displays the date and time when the selected task will start. If the setting in the dropdown 504 shown in Figure 5(A) is set to "Run periodically", the manager 101 displays the periodic execution setting in the execution cycle field 711. The task settings display 707 displays the task settings which differ for each task type.

[0062] When the manager 101 detects that the user has pressed the edit button 708, it transitions the screen display from the task details dialog shown in Figure 7 to the task editing screen for the selected task. For example, if the edit button 708 is pressed in Figure 7(A), the settings screen shown in Figure 5(A) will be displayed for editing the settings of the task for adding an internal-only certificate. In addition, if the user selects the task name displayed in the title bar 702 of the task details dialog screen shown in Figures 7(A) and (B), the display may also transition to the task editing screen shown in Figure 5(A).

[0063] Figure 8 is a flowchart illustrating the processing flow when displaying information showing the details of a task. Specifically, Figure 8 shows the processing flow when Manager 101 displays dialogs 701 and 710, which display the detailed information of the task shown in Figure 7.

[0064] In step S801, the manager 101 obtains task information for the selected task from the task management unit 303. The task information consists of basic information including the task name, task type, status, start date and time, and schedule information, and task-specific settings, which are serialized in a format such as JSON (JavaScript Object Notation). By serializing and storing the task-specific information, it becomes possible to save the task-specific settings as a single task data in a database, etc., just like the basic information. Furthermore, this makes it easy to duplicate tasks by pressing the duplicate button 403 shown in Figure 4(A).

[0065] In step S802, the manager 101 displays the task name, task type, task execution status, the date and time the task will start, and the periodic execution cycle as basic information. In step S803, the manager 101 loads a different task settings display module for each task type. In step S804, the manager 101 passes the task-specific information contained in the task information obtained in step S801 to the loaded display module. In step S805, the task settings display module deserializes the passed task-specific information, creates task-specific display information that reflects the task-specific information, and returns it to the caller. The task details display process receives this task-specific display information, and terminates after it is displayed on the task settings display 707. Note that if the user operation is performed in a web browser, the above-mentioned task-specific display information is written in HTML.

[0066] Furthermore, the present invention includes the following inventions, which appropriately combine the above-mentioned features.

[0067] (Composition 1) A management device comprising: management means for managing information on a plurality of tasks, including tasks scheduled to be executed and tasks currently being executed; and providing means for providing information for managing network devices on a display, wherein the providing means provides a dashboard including a panel showing the usage status of the management device, and one of the panels provided on the dashboard is a panel that displays a list of tasks based on the information of the plurality of managed tasks and at least one first user interface associated with each task, and when the first user interface is operated on the panel, the panel provides a display of the details of the task associated with the first user interface.

[0068] (Configuration 2) The management device according to Configuration 1, characterized in that the providing means provides, as details of the task, a display of settings and schedule settings specific to the type of task among the tasks displayed on the panel that is associated with the operated first user interface.

[0069] (Composition 3) The management device according to configuration 1 or configuration 2, characterized in that the first user interface is a display portion of the task name shown on the panel, and the providing means provides a display of the details of the task corresponding to the name when the display portion of the task name which is the first user interface is operated.

[0070] (Composition 4) A management device according to any one of configurations 1 to 3, characterized in that a second user interface is further displayed within the screen for displaying the details of the task, and when the second user interface is operated, the providing means further provides the display of an editing screen for editing the content of the task that was the subject of the details display.

[0071] (Composition 5) The management device according to configuration 4, characterized in that the second user interface is a display portion of the task name shown on the screen for displaying the details of the task, and the providing means provides a display of the editing screen for the task corresponding to the name when the display portion of the task name, which is the second user interface, is operated.

[0072] (Program 1) A program for causing a computer as a management device to function as a management means for managing information on multiple tasks, including tasks scheduled to be executed and tasks currently being executed, and a providing means for displaying information for managing network devices on a display, wherein the providing means provides a dashboard including a panel showing the usage status of the management device, and one of the panels provided in the dashboard is a panel that displays a list of tasks based on the information of the managed multiple tasks and at least one first user interface associated with each task, and when the first user interface is operated on the panel, the program provides a display of the details of the task associated with the first user interface.

[0073] (Method 1) A method in a management device, comprising: a management step of managing information on a plurality of tasks, including tasks scheduled to be performed and tasks currently being performed; and a provision step of providing information for the management of a network device on a display, wherein the provision step provides a dashboard including a panel showing the usage status of the management device, and one of the panels provided on the dashboard is a panel that displays a list of tasks based on the information of the plurality of managed tasks and at least one first user interface associated with each task, and when the first user interface is operated on the panel, a display of the details of the task associated with the first user interface is provided.

[0074] <Other Embodiments> The present invention can also be realized by supplying a program that implements one or more of the functions of the embodiments described above to a system or device via a network or recording medium, and by having one or more processors in the computer of that system or device read and execute the program. It can also be realized by a circuit that implements one or more functions, for example, an ASIC (Application Specific Integrated Circuit).

[0075] Preferred embodiments of the present invention have been described above. However, the present invention is not limited to the embodiments described above, and various modifications or changes may be made without departing from the spirit of the invention. For example, in the embodiments described above, the device management system 120 is composed of a manager 101 and an agent 121, but it is not limited thereto. The device management system may be configured as a single system that combines the functions of a manager and an agent without arranging multiple agents. Also, in the embodiments described above, operation by a web browser is assumed, but the device management system 120 can also provide an operation screen that utilizes a graphical user interface provided by the operating system on which it is running. [Explanation of Symbols]

[0076] 601...Dashboard, 602...Dropdown, 603...Title, 604...Menu, 605, 606, 607...Panel, 701, 710...Dialog, 702...Title bar, 703...Button, 704...Task type field, 705...Status field, 706...Start date and time field, 707...Task settings display, 708...Edit button, 711...Execution cycle field

Claims

1. A control device, A management means for managing information on multiple tasks, including tasks that are scheduled to be executed and tasks that are currently being executed, It has a means for providing information for managing network devices to be displayed on a screen, The aforementioned means of providing is A dashboard is provided that includes a panel showing the usage status of the aforementioned management device. As one of the aforementioned panels, the dashboard provides a panel that displays a list of tasks based on the information of the managed multiple tasks, and at least one first user interface associated with each task. When the first user interface is operated on the panel, the panel provides a display of the details of the task associated with the first user interface. A management device characterized by the following features.

2. The providing means provides, as details of the task, a display of settings and schedule settings specific to the type of task among the tasks displayed on the panel that is associated with the operated first user interface. The control device according to feature 1.

3. The first user interface is the part of the panel that displays the name of the task, The aforementioned providing means provides the display of the details of the task corresponding to the first user interface, when the task name display portion is operated. The control device according to feature 1.

4. A second user interface is further displayed within the screen for displaying the details of the aforementioned task. When the second user interface is operated, the providing means further provides the display of an editing screen for editing the content of the task that was the subject of the display of details. The control device according to feature 1.

5. The second user interface is the part that displays the name of the task shown on the screen for displaying the details of the task, The aforementioned providing means, when the task name display portion of the second user interface is manipulated, provides the display of the editing screen for the task corresponding to that name. The control device according to feature 4.

6. A computer as a management device, A management means for managing information on multiple tasks, including tasks that are scheduled to be executed and tasks that are currently being executed, A program that functions as a means for providing information for the management of network devices to a display, The aforementioned means of providing is A dashboard is provided that includes a panel showing the usage status of the aforementioned management device. As one of the aforementioned panels, the dashboard provides a panel that displays a list of tasks based on the information of the managed multiple tasks, and at least one first user interface associated with each task. When the first user interface is operated on the panel, the panel provides a display of the details of the task associated with the first user interface. A program characterized by the following features.

7. A method in a control device, A management process that manages information on multiple tasks, including tasks that are scheduled to be executed and tasks that are currently being executed, The process includes providing information for managing network devices to be displayed on a screen, In the aforementioned supply process, A dashboard is provided that includes a panel showing the usage status of the aforementioned management device. One of the panels provided in the dashboard is a panel that displays a list of tasks based on the information of the managed multiple tasks, and at least one first user interface associated with each task. When the first user interface is operated on the panel, a display of the task details associated with the first user interface is provided. A method characterized by the following:

Images