Management device, management method, and program

Abstract

To provide a technique of device management with improved operability.SOLUTION: A management device manages a device via a network. The management device generates templates used for tasks to manage the device, manages the generated plurality of different templates, designates a schedule and generates tasks on the basis of information on two or more templates selected from the plurality of managed templates, manages the generates tasks, and executes the managed tasks according to the schedule to execute processing corresponding to each of the plurality of templates. When execution means can execute processing of a combination of the plurality of templates, the management device generates the tasks.SELECTED DRAWING: Figure 8

Description

[Technical Field]

[0001] The present disclosure relates to a technique for managing devices connected to a network. [Background technology]

[0002] Device management systems have been known for some time now for acquiring and managing data such as operational information for image processing devices (hereinafter also referred to as devices) such as printers and multifunction peripherals via a network. These device management systems perform tasks using templates, such as device search, setting management for devices detected through the search, status management such as alerts, and device application management. These templates specify processing methods for devices in advance. For example, a user can create a template in which certain setting items and setting values ​​are specified in advance, thereby enabling efficient and reliable task creation and execution.

[0003] The device management server described in Patent Document 1 analyzes the range of values ​​that can be set for each setting item in advance, assuming that the range of values ​​that can be set for the same setting item may differ depending on the model to be managed.The device management server then creates templates based on the analysis results and applies the created templates to multiple image processing devices. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2013-246451 Summary of the Invention [Problem to be solved by the invention]

[0005] Task settings can be set in a variety of categories and setting items, and users create templates for each of these categories and setting items. When creating a template, users select one of the previously created templates and register a task corresponding to that template on the management server, which then executes the task. However, users cannot, for example, select two templates and register (execute) them as a single task on the management server. This means that users must either edit one of the templates or execute the task twice, which creates usability issues.

[0006] The present disclosure provides a device management technique with improved operability. [Means for solving the problem]

[0007] A management device according to one embodiment of the present disclosure manages devices via a network. The management device includes: a first generation unit that generates templates to be used in tasks for managing the devices; a first management unit that manages a plurality of different templates generated by the first generation unit; a second generation unit that generates tasks by specifying a schedule based on information on two or more selected templates from the plurality of templates managed by the first management unit; a second management unit that manages the tasks generated by the second generation unit; and an execution unit that executes the tasks managed by the second management unit according to the schedule to perform processing corresponding to each of the plurality of templates. The second generation unit generates the tasks when the execution unit is capable of executing processing for a combination of the plurality of templates. [Effects of the Invention]

[0008] According to the present disclosure, device management with improved operability can be achieved. [Brief explanation of the drawings]

[0009] [Figure 1]1 is a diagram illustrating an example of the configuration of a device management system including a management server according to a first embodiment. [Figure 2] FIG. 2 is a block diagram illustrating a hardware configuration of a management server. [Figure 3] FIG. 2 is a block diagram showing the hardware configuration of a device. [Figure 4] FIG. 2 illustrates an example of the software configuration of a management server and a device. [Figure 5] FIG. 10 is a diagram showing an example of a menu / data display screen provided by a device management unit. [Figure 6] FIG. 10 is a diagram illustrating an example of a template screen. [Figure 7] FIG. 10 is a diagram illustrating an example of a task template list screen. [Figure 8] 10 is a flowchart showing a process of registering a task corresponding to a generated template. [Figure 9] FIG. 10 is a diagram illustrating an example of a task creation screen. [Figure 10] 10 is a flowchart showing a process in which the management server executes a registered task. [Figure 11] 10 is a flowchart showing a process of a management server in the second embodiment. [Figure 12] 12 is a flowchart showing the processing of a management server in the second embodiment (continued from FIG. 11). [Figure 13] FIG. 11 is a diagram showing an example of a dialog screen in the second embodiment. [Figure 14] 12 is a flowchart showing the processing of a management server in the third embodiment (continued from FIG. 11). [Figure 15] 12 is a flowchart showing the processing of a management server in the fourth embodiment (continued from FIG. 11). [Figure 16] FIG. 13 is a diagram showing an example of a dialog screen in the fourth embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In the drawings, components having the same configuration or function are designated by the same reference numerals, and repeated description thereof will be omitted. The configurations shown in the following embodiments are merely examples, and the present disclosure is not limited to the configurations shown in the drawings.

[0011] First Embodiment FIG. 1 is a diagram showing an example of the configuration of a device management system including a management apparatus according to the first embodiment. The device management system includes one or more devices 300 and a management server 200 as a management apparatus that manages these devices 300. The management server 200 and the devices 300 are connected to a communication line 100 such as a LAN, and are capable of communicating with each other. The communication line 100 may be an intranet line or an Internet line. In the following description, when individual devices 300 are to be distinguished from one another, they may be referred to as devices DevA1, DevA1, DevA2, ..., DevAn.

[0012] The management server 200 manages the devices 300 by executing various tasks on the devices 300, for example. A task here refers to processing performed by the management server 200 to manage the devices 300. Specifically, the management server 200 performs various processing such as searching for devices 300, managing settings for the devices 300 detected by the search, managing their status, managing device applications, and managing various reports. That is, examples of tasks (task types) include a device search task, a device setting task, a device alert reception task, a status management task, an application-related task (installation and customization), and a report creation task. A report is a report on the operating status of the device 300, such as the usage time period of the device 300 and the status of consumables.

[0013] Tasks other than the device discovery task that are for managing devices are called device management tasks.

[0014] The device discovery task includes a device discovery method and its execution schedule. Discovery methods include SNMP, IP broadcast, SLP multicast, etc., which are well known to those skilled in the art. SNMP is an abbreviation for Service Location Protocol. SLP is an abbreviation for Simple Network Management Protocol.

[0015] The device setting task is a task related to device settings, and is a process of making various settings for the device 300 detected by the device discovery task. The device setting task includes a process of setting values ​​for various setting items for the device 300 selected by the user as the target for execution, and an execution schedule for the process. For example, if the device setting task includes the "installation location" of the device 300 as a setting item, the management server 200 controls the execution of the task configured with the settings of that "installation location." The "installation location" corresponds to an intranet environment. Since settings such as security vary depending on the intranet environment, the management server 200 manages devices for each "installation location." Similarly, if "power management" is present as a setting item for the device 300 in the device setting task, the management server 200 controls the execution of tasks such as power ON / OFF and sleep transition / recovery time of the device 300.

[0016] 2 is a block diagram showing the hardware configuration of the management server 200. The management server 200 has a CPU 201, a ROM 202, and a RAM 203. The management server 200 also has a video card (VC) 204, a keyboard controller (KBC) 206, a disk controller (DKC) 208, and a network interface card (NIC) 211. These elements are connected via a system bus 220. The management server also has drive devices such as an HDD (Hard Disk Drive) 209 and a Disk Drive 210.

[0017] The CPU 201 functions as a controller that controls the entire system. The CPU 201 uses the RAM 203 as a work area and executes various programs stored in the ROM 202 and / or the HDD 209. In the following description, at least one of the ROM 202 and the HDD 209 may be referred to as a storage device.

[0018] Each of the above programs for management server 200 is supplied by a storage medium such as an FD, CD-ROM, DVD, magneto-optical disk, or IC memory card that can be mounted on disk drive 210. CPU 201 installs each of the above programs into management server 200 by accessing HDD 209 and disk drive 210 via disk controller 208.

[0019] The CPU 201 displays a user interface on a display device (CRT) 205 via a video card 204. Of course, the display device 205 is not limited to a CRT, and may be a liquid crystal display or the like. Furthermore, the CPU 201 performs control via a keyboard controller 206 in response to input instructions via a user interface from a keyboard (KB) 207 or a pointing device such as a mouse. The CPU 201 also performs communication processing with the device 300 on the communication line 100 via the network interface card 211 .

[0020] 3 is a block diagram showing the hardware configuration of a device 300. The device 300 is typically an image forming apparatus such as a printer, a copier, a digital multifunction peripheral, or a 3D printer.

[0021] The device 300 has functions related to image formation such as printing, copying, and scanning, and a function for communicating with external devices such as the management server 200 via the communication line 100. The device 300 has a CPU 301, a ROM 302, a RAM 303, a disk controller (DKC) 304, and an HDD 305. The device 300 also has a UI 306, a card reader 307, a printer 308, a scanner 309, and a network interface card (NIC) 310.

[0022] The CPU 301 functions as a controller that controls the entire system. The CPU 301 uses the RAM 303 as a work area and executes a control program stored in the ROM 302 and / or the HDD 305. The control program is a program for controlling the printer 308, scanner 309, etc. connected to the system bus 320. The CPU 301 also accesses the HDD 305 via the disk controller 304 . The CPU 301 also performs communication processing with the management server 200 on the communication line 100 via the network interface card 310 . Furthermore, the CPU 301 compares user information stored in advance in the HDD 305 with information received via the card reader 307, for example, information on the user's IC card, and performs a login process for the user.

[0023] The UI 306 has an operation unit, an LED display, and the like that allow the user to operate the device 300. The operation unit is made up of a display device and switches that can be touched. The UI 306 transmits information based on the operation performed by the user on the UI 306 to the CPU 301 .

[0024] 2 and 3, instead of CPU 201, 301, a PLD (Programmable Logic Device) such as an FPGA (Field Programmable Gate Array) may be provided. Alternatively, an ASIC (Application Specific Integrated Circuit) may be used. In FIGS. 2 and 3, instead of HDD 209, 305, other devices such as a semiconductor memory such as a flash memory or an optical recording device may be used.

[0025] 4 is a diagram showing an example of the software configuration of the management server 200 and the device 300. The device management unit 40 running on the management server 200 includes, as the various programs described above, a task template management unit 41, a task generation unit 42, a task management unit 43, a task execution unit 44, and a data storage unit 45.

[0026] The device management unit 40 may also be implemented as a web-based application, in which case the user can access the device management unit 40 via a web browser.

[0027] The data storage unit 45 is a data recording medium such as a database that runs on the HDD 19 .

[0028] In the following, the terms "generation" and "creation" for templates and tasks will be used differently depending on the subject. When the subject is a computer (management server 200), "generation" is used, and when the subject is a human (user), "creation" is used. The same applies to "designation" and "selection," with "designation" being used for computers and "selection" being used for humans.

[0029] The task template management unit 41 generates task templates and stores them in the data storage unit 45. A task template (hereinafter sometimes simply referred to as a template) predefines a processing method for device discovery and device management that can constitute a part of a task for efficiently and reliably creating and executing a task. Task template management unit 41 is an example of a first generation means that generates templates used for tasks for managing devices, mainly in cooperation with CPU 201. Furthermore, task template management unit 41 and data storage unit 45 are an example of a first management means that manages a plurality of different templates generated by the first generation means, mainly in cooperation with CPU 201 and a storage device.

[0030] In the case of a device search task, the task generation unit 42 generates a task consisting of a search method and its execution schedule, and stores this in the data storage unit 45. In the case of a device management task for a device 300 detected by the search, the task generation unit 42 generates a task including a management processing method for the target device 300 and an execution schedule thereof, and stores this in the data storage unit 45 . The task generation unit 42 can specify a template generated in advance by the task template management unit 41 as a processing method for device search and device management when generating a task. The task generation unit 42 is an example of a second generation means that, mainly in cooperation with the CPU 201, generates a task by specifying a schedule based on information of two or more templates selected from the plurality of templates managed by the first management means.

[0031] The task management unit 43 has a function of managing the tasks generated by the task generation unit 42 and stored in the data storage unit 45. The task management unit 43 instructs the task execution unit 44 to execute the task according to the execution schedule set for the task. Task management unit 43 and data storage unit 45 are an example of a second management unit that manages the tasks generated by second generation unit mainly in cooperation with CPU 201 and the storage device.

[0032] The task execution unit 44 executes the task on the device 300 via the communication line 100 in accordance with the task execution instruction from the task management unit 43. At this time, if a template is used in the instructed task, the task execution unit 44 follows the settings of the template. The task execution unit 44 is an example of an execution unit that executes the tasks managed by the second management unit according to a schedule, mainly in cooperation with the CPU 201, to execute the processes corresponding to each of the plurality of templates.

[0033] The response control unit 46 of the device 300 performs processing in response to the request from the task execution unit 44 and returns the result to the task execution unit 44. The task execution unit 44 stores the result in the data storage unit 45.

[0034] Here, the task template management unit 41 can generate multiple templates applicable to various tasks. In the case of a device setting task, a user may select and set several setting items rather than setting all of the numerous device setting items in a single template. For example, a user may create separate templates, such as a template having setting items configuring device information such as the "installation location" of the device 300 and a template having setting items configuring the "power management" of the device 300. Alternatively, in a template having setting items configuring the "installation location" of the device 300, the installation locations of devices DevA1 to A10 and devices DevA11 to An may be different. In this case, when the setting items are the same but the setting values ​​are different, the task template management unit 41 generates multiple templates corresponding to those setting values. On the other hand, when the time until the devices 300 transition to sleep is the same for all devices 300, the task template management unit 41 generates a single template.

[0035] The task generation unit 42 executes a task by specifying multiple templates when generating a task based on user input. When multiple templates are specified, it is desirable to identify executable and inexecutable combinations of the templates and appropriately control each of them. Being executable for a combination of multiple templates means that there is no conflict or inconsistency in the processing of tasks corresponding to the combination of the template settings. This will be described in more detail later.

[0036] 5 is a diagram showing an example of a menu / data display screen provided by the device management unit 40. This menu / data display screen 50 includes a menu 51 and a data display / creation area 52. The device management unit 40 displays a data display and creation screen in the data display / creation area 52 on the CRT 205 according to the menu 51 selected by the user.

[0037] The menu 51 includes a "Device" 501 and a "Task" 502 as menu items. "Device" 501 includes a submenu "Device List" 511. "Device List" 511 displays a list (not shown) of devices 300 detected by a device discovery task. The "Task" 502 includes submenus "Device Setting Task" 512, "Task Template" 513, "Other Tasks" 514, and "Task List" 515. "Device setting task" 512 is a submenu for displaying a screen corresponding to a function for creating a device setting task. "Task Templates" 513 is a submenu for creating, editing and deleting various templates. "Other Tasks" 514 is a submenu for creating tasks other than device setting tasks. Other tasks refer to the creation of tasks other than device discovery tasks and device setting tasks. "Task List" 515 displays a list of the created tasks. The user can also create a new task by editing a task displayed in "Task List" 515, without creating a new task.

[0038] When the user selects "Task Template" 513, the task template management unit 41 displays a template creation / edit / deletion screen (hereinafter referred to as the template screen) on the CRT 205. An example of the template screen 600 is shown in Fig. 6. The template screen 600 shown in Fig. 6 is a template screen for a device setting task.

[0039] The template screen 600 for the device setting task includes tab sheets for creating, editing, and deleting: a create tab 601, an edit tab 602, and a delete tab 603. Each tab sheet is provided with a save button 610 for saving the created, edited, or deleted content, and a cancel button 611 for canceling the process.

[0040] The tab sheet for the Create tab 601 includes a task template name 604 and setting contents 606 for performing device settings. The setting contents 606 include a setting category 607, a setting item 608, and a setting value 609. The task template name 604 is an edit box for setting the name of the template to be created.

[0041] The tab sheet of the edit tab 602 is a sheet for editing the template created in the tab sheet of the create tab 601.

[0042] The tab sheet for the delete tab 603 is a sheet for deleting a template created on the tab sheet for the create tab 601 .

[0043] In the tab sheet of the Creation tab 601, one setting category 607 includes one or more setting items 608 for the device 300, and each setting item 608 corresponds to a setting value 609. The setting value 609 is a value that can be set by user input. In the example shown in FIG. 6, the setting category 607 of "device information" includes setting items 608 such as "device name" and "installation location." The "power management" setting category 607 includes setting items 608 such as "sleep transition time" and "shutdown time."

[0044] When the user presses the save button 610 , the task template management unit 41 saves the template in the task template list in the data storage unit 45 .

[0045] 6, "Template 1" is entered as the task template name 604. As the setting content 606, "Device Information" is selected in the setting category 607, and "Installation Location" is selected in the setting item 608 by checking the checkbox. "Office A" is set as the setting value 609 for "Installation Location." The task template management unit 41 generates a template that reflects the above settings and saves it in the task template list in the data storage unit 45.

[0046] 7 is a diagram showing an example of a task template list screen including the settings of a template. This task template list 700 is composed of the task template name 604, setting category 607, setting item 608, setting value 609, and configurable target task (task type) 705 created on the screen shown in FIG.

[0047] 7, for the task template name 604 "Template 1," "Device Information" is set as the setting category 607, "Installation Location" is set as the setting item 608, and "OfficeA" is set as the setting value 609. This indicates that the configurable target task 705 is "Device Settings" (device setting task). The setting of "Template 2" in the task template name 604 differs from the setting of "Template 1" in that "OfficeB" is set as the setting value 609. In other words, "Template 1" and "Template 2" are different. For the task template name 604 "Template 3", "Power management" is set as the category 607, "Sleep transition time" is set as the setting item 608, and "30 minutes" is set as the setting value 609. It is shown that the configurable target task 705 is "Device setting". In this way, task template management unit 41 manages a plurality of different templates.

[0048] The task template name 604 functions as identification information that uniquely identifies each template. Alternatively, the task template management unit 41 may have an ID (which may be composed of numbers, symbols, or other character strings other than the template name) corresponding to the task template name 604 as identification information.

[0049] Note that task template management unit 41 may also manage templates for other tasks using the test template list shown in FIG. 7, or may generate and manage a template list for each task type.

[0050] 8 is a flowchart showing the process of registering a task corresponding to a generated template by the task generation unit 42. In this process, the CPU 201 reads out a program corresponding to the processing content, loads it into the RAM 203, and executes it.

[0051] In S800, the task generation unit 42 acquires menu information selected by the user in the menu 51 in Fig. 5. Here, the task generation unit 42 acquires information that the "Device Setting Task" 512 in Fig. 5 has been selected.

[0052] In S801, the task generation unit 42 determines whether the selected menu is task creation (the creation tab 601 in FIG. 6), and if it is determined that it is task creation, the process proceeds to S802.

[0053] In S802, the task generation unit 42 displays a task creation screen for creating a task on the CRT 15. Then, in S803, the task generation unit 42 sets the content of the task to be created based on the user's input.

[0054] 9 is a diagram showing an example of the task creation screen. Here, a task creation screen 900 for a device setting task is taken as an example. This task creation screen 900 has four sections: "Task Information" 901, "Target Device" 902, "Setting Information" 903, and "Schedule Settings" 904. The task creation screen 900 also includes a registration button 905 for registering the content of the task to be created (processing of S812, described below), and a cancel button 906 for canceling the process.

[0055] "Task information" 901 includes "task type" 907 and "task name" 908. "Task type" 907 displays the type of the task to be created using a fixed character string. "Task name" 908 is an edit box for setting the name of the task to be created. In the example shown in Fig. 9, "Device setting" is displayed in "Task type" 907, and "Device setting 1" is set as "Task name" 908.

[0056] "Target Devices" 902 is a device list of devices 300 detected as a result of a device search executed in advance. In the example shown in FIG. 9, devices DevA1 to An have been detected, and the task generation unit 42 displays a list of devices DevA1 to An in "Target Devices" 902. The task generation unit 42 specifies devices DevA1 to DevAn as the target devices 300. The target devices 300 are selected by the user checking the check boxes in "Target Devices" 902. Note that the task generation unit 42 specifies all devices 300 detected by the search, but the user may select at least one, or may deselect at least one of the target devices 300 from the selection of all of the target devices 300.

[0057] In "Setting information" 903, the user can select whether or not to use a template. "Use task template" 909, which means using a template, is enabled when a template that matches the task to be generated is stored in the data storage unit 45. On the other hand, if the user does not want to use a template, the user can select "Do not use task template" 910. If the user selects "Do not use task template" 910, the user selects a "Setting category" 607 and a "Setting item" 608 for device settings, and sets a "Setting value" 609 for the selected "Setting item" 608. In the example shown in Fig. 9, since the data storage unit 45 contains templates 1 to n of the device setting task shown in Fig. 7, the task generation unit 42 enables the selection of "Use task template" and displays a list of the templates in Fig. 7. Then, the task generation unit 42 specifies multiple templates, for example, template 1 and template 2, based on the user's input (selection).

[0058] "Schedule settings" 904 includes "Execution schedule" 911 and "Execution cycle" (not shown). "Schedule settings" 904 is composed of, for example, a selection list and an edit box for setting schedule information for executing a registered task. "Execution schedule" 911 allows the user to select an execution schedule for the task, such as "execute periodically" or "execute immediately." "Execution cycle" sets how the task will be executed periodically when the execution schedule is set to "execute periodically." For example, the following execution cycle is meant: Monthly: Specify delivery date and time Weekly: Specify the delivery day and time Daily: Specify delivery time

[0059] The settings for "Execution Schedule" 911 and "Execution Cycle" are not limited to the above methods. For example, it may be an irregular execution schedule or cycle, such as 9:00 to 17:00 from Monday to Friday of a certain week, and all day on Saturday and Sunday. In the example shown in Figure 9, "Execute Immediately" is selected as the "Execution Schedule" 911.

[0060] Returning to the description of Fig. 8, in S804, the task generation unit 42 determines the button action input by the user, and if it determines that the registration button 905 has been pressed, the process proceeds to S805.

[0061] In S805, the task generation unit 42 determines whether to use a template as the task content set in the previous S803, and if it is determined that a template will be used, the process proceeds to S806. In the example shown in Fig. 9, since "Use task template" 909 is enabled, the task generation unit 42 determines that the setting to use a template has been made in the device setting task set in S803.

[0062] In S806, the task generation unit 42 determines whether multiple templates were selected in S803, and if multiple templates were selected, the process proceeds to S807. In the example shown in Fig. 9, two templates, template 1 and template 2, were selected in S803, so the process proceeds to S807.

[0063] In S807, the task generation unit 42 analyzes the information of the plurality of templates selected in S803.

[0064] In S808, the task generation unit 42 determines whether a conflict occurs between the selected templates, and if it determines that a conflict occurs, the process proceeds to S809. A conflict between templates means, for example, in the case of a device setting task template, that the same setting item 608 exists in multiple selected templates, but the setting value 609 is different.

[0065] 7, the task generation unit 42 determines that the setting item 608 of Template 1 and Template 2 selected in S803 is the same, "Installation location." However, the setting value 609 is different, being "OfficeA" in Template 1 and "OfficeB" in Template 2. In other words, it is determined that a conflict occurs between Template 1 and Template 2. On the other hand, in the case of a template for a device setting task, if the same setting item 608 does not exist in the selected multiple templates, or if it exists but its setting value 609 is the same, it is determined that there is no conflict.

[0066] If a conflict occurs, it means that the processing of the combination of multiple templates (the task corresponding to the processing of that combination) cannot be executed. If a conflict does not occur, it means that the processing of the combination of multiple templates (the task corresponding to the processing of that combination) can be executed.

[0067] In S809, the task generation unit 42 notifies the user of a conflict error between the selected templates, and the process proceeds to S803. In S809, the task generation unit 42 displays, for example, a message on the CRT 15 indicating that the task cannot be saved, or a message indicating that the contents of the selected templates 1 and 2 conflict, and prompts the user to reset the task contents.

[0068] On the other hand, if the task generation unit 42 determines in S808 that no conflict will occur between the templates, it registers the task in the data storage unit 45 in S812 and terminates the process. For example, assume that template 1 and template 3 are selected as templates in S803. In this case, the task generation unit 42 determines in S808 that no conflict will occur because the setting item 608 of template 1 is "installation location" and the setting item 608 of template 3 is "sleep transition time," and the process proceeds to S812.

[0069] If the task generation unit 42 determines in S805 that a template will not be used, or if it determines in S806 that there are not multiple selected templates, the process proceeds to S812.

[0070] If the task generation unit 42 determines in S801 that the selected menu is not task creation, it executes the other selected menu in S813 and ends the processing. Also, if the task generation unit 42 determines in S804 that the button action by the user is pressing the cancel button 906, it ends the processing.

[0071] 10 is a flowchart showing the process of executing a registered task by the management server 200. In this process, the CPU 201 reads out a program corresponding to the process content, loads it into the RAM 203, and executes it.

[0072] In S1400, the task management unit 43 waits until the time when the task should be executed (the time set in the execution schedule 911 shown in FIG. 9). If the setting is "execute immediately," the time is the time when the registration button 905 is pressed and the task generation unit 42 accepts the input. If the task management unit 43 determines that the current time is the time when the task should be executed, the process proceeds to S1401.

[0073] In S1401, the task management unit 42 instructs the task execution unit 44 to execute the task, and the task execution unit 44 executes the task.

[0074] As described above, according to this embodiment, a user can select multiple templates when creating a task, and if the management server 200 can execute a task corresponding to one of the templates, the user can register the task. On the other hand, if the task corresponding to one of the templates cannot be executed, the task cannot be registered. Even when multiple templates are specified, the management server 200 can generate a task appropriately and reliably, thereby improving the operability of task creation for the user.

[0075] Second Embodiment Next, a second embodiment will be described. In the second and subsequent embodiments, the description of the same configurations, functions, processes, etc. as those described in the first embodiment will be omitted or simplified.

[0076] 9, of the multiple templates selected by the user, for example, Template 1 may be a template for changing the password, SNMP community name, etc. used in the device. Template 2 may be a template that uses the password, SNMP community name, etc. used in the device 300 that is the target of the changes in Template 1. There may be multiple templates like Template 2. In such cases, it is desirable to be able to set the application order of Template 1 and Template 2, in terms of whether to change the password, SNMP community name, etc. used in the device 300 before using them, or to use them before changing them.

[0077] 11 and 12 are flowcharts showing the processing performed by management server 200 to achieve the above. Steps S800 to S809, S812, and S813 are the same as those shown in FIG. 8, and therefore a description thereof will be omitted.

[0078] Note that the task generation unit 42, for example, allows the user to set in advance whether or not to inquire about the application order of multiple templates, and stores the setting in the data storage unit 45. In the process shown in Figs. 11 and 12, this process will be described assuming that the setting is to inquire about the application order of the user.

[0079] In S1000, if the task generation unit 42 determines that no conflict occurs between the two templates (template 1 and template 2) selected in S808, it acquires the application order inquiry information stored in the data storage unit 45. The application order inquiry information is information indicating that a plurality of templates having multiple application order patterns, such as the setting contents of template 1 and template 2, have been specified.

[0080] In S1001, the task generation unit 42 determines whether it is necessary to inquire about the application order of the templates based on the application order inquiry information acquired in S1000. If Template 1 and Template 2 have been selected, the task generation unit 42 determines that it is necessary to inquire about their application order, and proceeds to S1002. In other words, if a plurality of templates having multiple application order patterns have been specified, the task generation unit 42 determines that it is necessary to inquire about their application order. The order of S1000 and S1001 may be reversed.

[0081] In S1002, the task generation unit 42 displays on the CRT 15 a dialog box inquiring the user about the application order of the templates. Fig. 13 is a diagram showing an example of the screen of this dialog box. This dialog box includes a list 1301 of templates whose application order needs to be set, and buttons "Move Up" 1302 and "Move Down" 1303 for changing the application order of the templates. This dialog box also includes a setting button 1304 for saving the application order specified by the user using "Move Up" 1302 or "Move Down" 1303 in the data storage unit 45. 13 includes only template names as list 1301, but it may also include the corresponding settings. This allows the user to set the application order while viewing the template settings, improving operability.

[0082] In S1003, the task generation unit 42 sets the application order according to the user's input instructions in the dialog, and the process proceeds to S812. In the example shown in Fig. 13, in S1003 the task generation unit 42 sets that template 1 is applied first and template 2 is applied second. As a result, in S812, task registration is performed so that the tasks corresponding to the templates are executed in that application order.

[0083] On the other hand, if the task generation unit 42 determines in S1001 that it is not necessary to inquire about the template application order, the process proceeds to S812.

[0084] As described above, according to this embodiment, it is possible to obtain the same effects as the first embodiment, and also to set the order in which multiple templates are applied, thereby further improving operability and increasing the processing efficiency of task execution by the management server 200.

[0085] <Third embodiment> In FIG. 9, among the multiple templates selected by the user, for example, template 1 may be a template for installing an application (device application) that runs on device 300. Template 2 may be a template for customizing the application installed on device 300. Customizing an application means, for example, in the case of an application that tallies the number of pages printed by device 300, setting various tallying methods, such as tallying by color / monochrome printing or by single-sided / double-sided printing. In such a case, it is desirable for management server 200 to install the application using template 1 and then customize the application using template 2.

[0086] 14 is a flowchart showing the processing performed by management server 200 to achieve the above. In this processing, steps S800 to S809 are the same as those in FIG. 11, so these steps are used and the description thereof will be omitted.

[0087] In S1200, if the task generation unit 42 determines that no conflict occurs between the templates selected in S808, it acquires application order information that has been defined in advance and stored in the data storage unit 45. In this case, the application order information is setting information that, when template 1 related to application installation and template 2 related to its customization are selected, customize them after installation.

[0088] In S1201, the task generation unit 42 determines whether or not it is necessary to set the application order acquired in S1200, and if it determines that it is necessary to set the application order, the process proceeds to S1202. The determination of whether or not it is necessary to set the application order is made by determining whether or not template 1 and template 2 to which the application order should be applied have been designated. The order of S1200 and S1201 may be reversed.

[0089] In S1202, the task generation unit 42 sets the application order of the task templates based on the application order information acquired in S1200, and the process proceeds to S812. In the example shown in Fig. 14, in S1202 the task generation unit 42 sets that template 1, which prescribes application installation, will be applied, and then template 2, which prescribes application customization. As a result, in S812, task registration is performed so that the tasks corresponding to the templates are executed in that application order.

[0090] <Fourth embodiment> The management server 200 may have a task function for generating a report (device report) on the usage status of the device 300, such as the number of printed pages totaled by color / monochrome printing or by single-sided / double-sided printing, etc. In order to generate such a report, the management server 200 must execute a task in advance to collect device data to be reported from the device 300.

[0091] For example, in a task template for collecting device data, Template 1 may have a setting to collect the number of pages printed by the device every day at 7:00 PM, while Template 2 may have a setting to collect the number of pages printed by the device every Friday at 8:00 PM. In other words, these tasks collect the same device data at different times. In such a case, it is desirable to be able to set whether or not to allow the same data to be collected at different times.

[0092] 15 is a flowchart showing the processing performed by management server 200 to achieve the above. In this processing, steps S800 to S809 are the same as those in FIG. 11, so these steps are used and the description thereof will be omitted.

[0093] In S1300, if the task generation unit 42 determines that no conflict occurs between the templates selected in S808, the task generation unit 42 determines whether the templates have settings for collecting the same device data at different times. If the task generation unit 42 determines that the templates have settings for collecting the same device data at different times, the task generation unit 42 transitions to S1301. For example, in S1300, if the task generation unit 42 determines that template 1 has a setting for collecting the number of printed pages from the device at 19:00 every day and template 2 has a setting for collecting the number of printed pages from the device at 20:00 every Friday, the task generation unit 42 transitions to S1301.

[0094] In S1301, the task generation unit 42 displays on the CRT 15 a dialog screen for asking whether or not to allow the collection of the same device data to be executed at different times. Fig. 16 is a diagram showing an example of this dialog screen. In the example shown in Fig. 16, the task generation unit 42 displays that template 1 has a setting to collect the number of printed sheets of a device, which is one of the collection data, at 19:00 every day, and that template 2 has a setting to collect this data at 20:00 every Friday.

[0095] If the "Yes" button 1601 is pressed in S1302, the task generation unit 42 sets that collection of the same device data is permitted (enabled) to be executed at different timings. If the "No" button 1602 is pressed, the task generation unit 42 sets that collection is not permitted (disabled). As a result, in S812, a task corresponding to a template of settings that reflects either of these is registered. If a task that does not permit collection of the same device data to be executed at different timings is set, the task execution unit 44 may not collect the device data in question, or may select one of two different collection timings.

[0096] If the task generating unit 42 determines in S1300 that there is no setting for executing collection of the same device data at different timings between the selected templates, the process proceeds to S812.

[0097] <Other embodiments> At least two of the second, third, and fourth embodiments may be combined. For example, the task generation unit 42 may execute both S1001 and S1201 when generating a task. Alternatively, the task generation unit 42 may execute at least one of S1001 and S1201 and S1300. In this case, the order of these processes does not matter.

[0098] In each of the above embodiments, two templates are used as an example of the multiple templates to be subjected to the determination of whether a conflict occurs in the combination process in S808. However, there are also cases where the determination is to be performed on a combination of three or more templates.

[0099] The disclosure of this embodiment includes the following configuration, method, and program. (Configuration 1) A management device that manages devices via a network, a first generating means for generating a template to be used in a task for managing the device; a first management means for managing a plurality of different templates generated by the first generation means; a second generation means for generating a task by specifying a schedule based on information of two or more templates selected from the plurality of templates managed by the first management means; second management means for managing the tasks generated by the second generation means; an execution unit that executes the tasks managed by the second management unit according to the schedule, thereby executing processes corresponding to the plurality of templates; The second generating means generates the task when the executing means can execute the process of the combination of the plurality of templates. A management device characterized by: (Configuration 2) When it is determined that no conflict occurs in the processing of a combination of the plurality of templates based on the setting contents of the plurality of templates, the second generation means generates the task by determining that the processing of the combination is executable. 2. The management device according to configuration 1. (Configuration 3) The first management means manages a template list that associates identification information for identifying the template with the setting content. 3. The management device according to configuration 2. (Configuration 4) The second generation means sets an application order of the plurality of templates when the execution means is capable of executing the process of the combination of the plurality of templates. 4. The management device according to any one of configurations 1 to 3. (Configuration 5) The second generation means inquires of a user about an application order of the plurality of templates and sets the application order based on an instruction from the user. 5. The management device according to configuration 4. (Configuration 6) The second generation means sets the application order when it is determined that it is necessary to set the application order of the plurality of templates based on the setting contents of the plurality of templates. 5. The management device according to configuration 4. (Configuration 7) When the execution means is capable of executing a process of a combination of the plurality of templates, and when the plurality of templates have settings for collecting the same device data at different times, the second generation means controls enabling and disabling of the settings based on a user instruction. 7. The management device according to any one of configurations 1 to 6, wherein: (method) 1. A method for managing devices over a network, comprising: a first generation step of generating a template to be used in a task for managing the device; a first management step of managing the plurality of different templates generated in the first generation step; a second generation step of generating a task by specifying a schedule based on information of two or more templates selected from the plurality of templates managed in the first management step; a second management step of managing the tasks generated in the second generation step; an execution step of executing the tasks managed in the second management step according to the schedule, thereby executing processes corresponding to the plurality of templates, In the second generating step, when the process of the combination of the plurality of templates in the executing step is executable, the task is generated. A management method characterized by: (program) A program to be executed by a management device that manages devices via a network, a first generation step of generating a template to be used in a task for managing the device; a first management step of managing the plurality of different templates generated in the first generation step; a second generation step of generating a task by specifying a schedule based on information of two or more templates selected from the plurality of templates managed in the first management step; a second management step of managing the tasks generated in the second generation step; an execution step of executing the tasks managed in the second management step according to the schedule, thereby executing processes corresponding to the plurality of templates, In the second generating step, when the process of the combination of the plurality of templates in the executing step is executable, the task is generated. A program that causes the management device to execute the above.

[0100] The present disclosure has been described above in detail based on preferred embodiments thereof, but the present disclosure is not limited to the above embodiments, and various modifications are possible based on the gist of the present disclosure, and these modifications are not excluded from the scope of the present disclosure.

Claims

1. A management device for managing devices via a network, a first generating means for generating a template to be used in a task for managing the device; a first management means for managing a plurality of different templates generated by the first generation means; a second generation means for generating a task by specifying a schedule based on information of two or more templates selected from the plurality of templates managed by the first management means; a second management means for managing the tasks generated by the second generation means; an execution unit that executes the tasks managed by the second management unit according to the schedule, thereby executing processes corresponding to the plurality of templates, The second generating means generates the task when the executing means is capable of executing the process of the combination of the plurality of templates. A management device comprising:

2. The second generation means, when it is determined that no conflict occurs in processing of a combination of the plurality of templates based on the setting contents of the plurality of templates, generates the task by determining that the processing of the combination is executable.

2. The management device according to claim 1.

3. The first management means manages a template list that associates identification information for identifying the template with the setting contents.

3. The management device according to claim 2.

4. The second generation means sets an application order of the plurality of templates when the execution means is capable of executing processing of a combination of the plurality of templates.

2. The management device according to claim 1.

5. The second generation means inquires of a user about an application order of the plurality of templates and sets the application order based on an instruction from the user.

5. The management device according to claim 4.

6. The second generation means sets an application order of the plurality of templates when it is determined that it is necessary to set the application order of the plurality of templates based on the setting contents of the plurality of templates.

5. The management device according to claim 4.

7. When the execution means is capable of executing a process of a combination of the plurality of templates and the plurality of templates have settings for collecting the same device data at different times, the second generation means controls enabling and disabling of the settings based on a user instruction.

2. The management device according to claim 1.

8. 1. A method for managing devices over a network, comprising: a first generation step of generating a template to be used in a task for managing the device; a first management step of managing a plurality of different templates generated in the first generation step; a second generation step of generating a task by specifying a schedule based on information of two or more templates selected from the plurality of templates managed in the first management step; a second management step of managing the tasks generated in the second generation step; an execution step of executing the tasks managed in the second management step according to the schedule, thereby executing processes corresponding to the plurality of templates, In the second generating step, when the process of the combination of the plurality of templates in the executing step is executable, the task is generated. A management method comprising:

9. A program to be executed by a management device that manages devices via a network, a first generation step of generating a template to be used in a task for managing the device; a first management step of managing a plurality of different templates generated in the first generation step; a second generation step of generating a task by specifying a schedule based on information of two or more templates selected from the plurality of templates managed in the first management step; a second management step of managing the tasks generated in the second generation step; an execution step of executing the tasks managed in the second management step according to the schedule, thereby executing processes corresponding to the plurality of templates, In the second generating step, when the process of the combination of the plurality of templates in the executing step is executable, the task is generated. A program that causes the management device to execute the above steps.

Images