Management system, server, and management method

Abstract

To provide a management system, a server and a management method for improving convenience by improving the efficiency of setup work.SOLUTION: The management system includes an MFP as a first device, a server, a memory, and a network I / F. The server executes a request receiving process (S25) for receiving the initial setting process request and the user ID, a data-creating process (S27) for creating a setup flow specifying the content of the initial setting process of the first devices, and a data-transmitting process (S29) for transmitting the setup flow created in the data-creating process. In the data creation processing, the server creates setup flow data for designating at least one of one or more operation items to be executed in the initial setting processing and setting values necessary for the operation items on the basis of the use history of the second device associated with the user ID received in the request reception processing.SELECTED DRAWING: Figure 4

Description

[Technical Field]

[0001] The present disclosure relates to a management system, a server, and a management method. [Background technology]

[0002] Conventionally, there is known a technique for initial setting processing (hereinafter also referred to as "setup") for transitioning an unpacked device such as a printer or scanner into a usable state, as described in Patent Document 1. Patent Document 1 discloses that the device is set up by executing a setup program read by the device's CD-ROM drive. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2004-110393 Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the technology described in Patent Document 1, the processes and tasks executed during setup are uniform regardless of the user's past usage history, and therefore processes unnecessary for the user are also executed, resulting in a problem of inconvenience for the user. For example, when a user needs to perform setup work for multiple devices, the user needs to repeatedly perform similar setup work, including processes unnecessary for the user, resulting in poor work efficiency.

[0005] In view of the above, an object of the present disclosure is to provide a management system, a server, and a management method that can improve convenience by streamlining the setup process. [Means for solving the problem]

[0006] (1) To achieve the above-mentioned object, according to one embodiment of the present disclosure, there is provided a management system including a first device, a server, a memory, and a communication interface, wherein the memory stores a user ID for identifying a user and a usage history of a second device associated with the user ID in association with each other, the server executes a request reception process to receive, via the communication interface, an initial setup process request for initial setup process to transition the first device to a usable state, and the user ID, a creation process to create designation data specifying the content of the initial setup process of the first device, the designation data specifying at least one of one or more operation items to be executed in the initial setup process and setting values ​​required for the operation items, based on the usage history of the second device associated with the user ID received in the request reception process, and a transmission process to transmit the designation data created in the creation process via the communication interface, and the first device executes an execution process to execute the initial setup process of the first device based on the designation data transmitted in the transmission process.

[0007] According to this management system, the initial settings of the first device can be performed with content corresponding to the usage history of the second device associated with the user ID, thereby improving the efficiency of the initial setting work. When a user needs to perform the initial setting work for multiple devices, the user must repeatedly perform the same initial setting work, including processes that are unnecessary for the user, which previously resulted in poor work efficiency. However, according to the above-described system, the initial setting work can be performed efficiently.

[0008] (2) In the management system of the above form, type information indicating the type of the second device is stored in the memory in correspondence with the user ID, and the server may further receive type information indicating the type of the first device in the request receiving process, and in the creation process, if the type information of the first device received in the request receiving process matches the type information of the second device, create the specified data based on the usage history of the second device.

[0009] According to this form of management system, when the type information of the first device matches the type information of the second device, designated data is created based on the usage history of the second device, so that designated data can be created according to the type of device.

[0010] (3) In the management system of the above form, in the creation process, the server may obtain the usage amount of the operation item used by the second device as the usage history, and if the usage amount is less than a predetermined threshold, create the specified data omitting initial settings for the operation item.

[0011] According to the management system of this aspect, in the initial setting of the first device, the initial setting of the operation items whose usage amount is less than the threshold can be omitted, thereby improving the efficiency of the initial setting work.

[0012] (4) In the management system of the above form, the first device and the second device have a printing mechanism, and the server, in the creation process, obtains the printing volume of the second device as the usage volume, and if the printing volume is less than the threshold, creates the specified data omitting initial settings that improve the printing accuracy of the first device.

[0013] According to this type of management system, if the amount of printing used by the second device is less than a threshold value during initial setup of the first device, the initial setup to improve printing accuracy is omitted, thereby improving the efficiency of the initial setup work.

[0014] (5) In the management system of the above form, the first device and the second device have a printing mechanism, and in the creation process, the server acquires the usage amount of the paper feed tray used for printing on the second device as the usage amount, and if the usage amount is less than the threshold, the server may create the specified data omitting the initial settings for the paper feed tray.

[0015] According to the management system of this aspect, the efficiency of the initial setting work can be improved because the initial setting of the first device is omitted for the paper feed tray in the second device whose usage amount is less than the threshold.

[0016] (6) In the management system of the above form, the server may, in the creation process, acquire the usage amount of the operation item used by the second device as the usage history, and if the usage amount is equal to or greater than a predetermined threshold, create the specified data including an initial setting for the operation item.

[0017] According to the management system of this aspect, in the initial setting of the first device, it is possible to efficiently perform the initial setting including the initial setting of the operation items whose usage amount in the second device is equal to or exceeds the threshold.

[0018] (7) In the management system of the above form, the first device and the second device have a printing mechanism, and in the creation process, the server acquires the usage amount of the paper feed tray used for printing on the second device as the usage amount, and if the usage amount is equal to or greater than the threshold, creates the specified data in which the setting value for the paper feed tray is set based on the usage history of the second device.

[0019] According to this management system, if the usage of the paper feed tray used for printing on the second device is equal to or greater than a threshold, it is possible to create designation data in which the setting values ​​for the paper feed tray are set based on the usage history of the second device. As a result, in the initial setting of the first device, the setting values ​​for the paper feed tray correspond to the user's usage history, allowing for efficient initial setting processing.

[0020] (8) In the management system of the above form, in the creation process, the server may obtain a subscription history of a service targeted at the second device as the usage history, determine whether or not a notification is necessary for subscription to a service targeted at the first device based on the subscription history, and if it determines that the notification is necessary, create the specified data including the notification as the action item.

[0021] According to the management system of this aspect, it is possible to appropriately notify a user who needs to be notified of service subscription information during initial setup of the first device.

[0022] (9) In the management system of the above aspect, if the server determines in the creation process that the announcement notice is necessary, the server may create the specified data including the announcement notice displaying the content of the service. According to this aspect of the management system, specific service content can be displayed during initial setup of the first device, thereby improving convenience for the user.

[0023] (10) According to a second aspect of the present disclosure, there is provided a server that manages an initial setting process of the first device in a management system including a first device, a memory, and a communication interface, wherein a user ID for identifying a user and a usage history of a second device associated with the user ID are stored in the memory in association with each other, and the server executes the following steps: a request receiving process for receiving, via the communication interface, an initial setting process request for initial setting process to transition the first device to a usable state and the user ID; a creation process for creating designation data that specifies the content of the initial setting process of the first device, the designation data specifying at least one of one or more operation items to be executed in the initial setting process and setting values ​​required for the operation items, based on the usage history of the second device associated with the user ID received in the request receiving process; and a transmission process for transmitting the designation data created in the creation process via the communication interface.

[0024] According to this type of server, the initial setup of the first device can be performed with content corresponding to the usage history of the second device associated with the user ID, thereby improving the efficiency of the initial setup work.

[0025] (11) According to a third aspect of the present disclosure, there is provided a management method executed by a management system including a first device, a server, a memory, and a communication interface, wherein a user ID for identifying a user and a usage history of a second device associated with the user ID are stored in the memory in association with each other, and the management method includes: a request reception process executed by the server to receive, via the communication interface, an initial setup process request for initial setup process to transition the first device to a usable state and the user ID; a process to create designation data specifying content of the initial setup process of the first device, the designation data specifying at least one operation item to be executed in the initial setup process and setting values ​​required for the operation item, based on the usage history of the second device associated with the user ID received in the request reception process; a transmission process to transmit the designation data created in the creation process via the communication interface; and an execution process executed by the first device to execute the initial setup process of the first device based on the designation data transmitted in the transmission process.

[0026] According to this type of management method, the initial setup of the first device can be performed with content corresponding to the usage history of the second device associated with the user ID, thereby improving the efficiency of the initial setup work. [Brief explanation of the drawings]

[0027] [Figure 1] 1 is a block diagram illustrating a schematic configuration of a management system according to an embodiment of the present disclosure. [Figure 2] FIG. 2 is a diagram illustrating a storage table T1 stored in a server. [Figure 3] FIG. 10 is a diagram illustrating a storage table T2 stored in the server. [Figure 4] 10 is a flowchart illustrating a procedure of an initial setting process executed by the management system. [Figure 5]FIG. 10 is a diagram illustrating the contents of an initial setting process. [Figure 6] FIG. 10 is a diagram illustrating the contents of an initial setting process. [Figure 7] 10 is a flowchart showing the procedure of a creation process. [Figure 8] FIG. 10 is a diagram illustrating an example of a display screen of a mobile terminal when correcting print accuracy. [Figure 9] FIG. 10 is a diagram illustrating an example of a display screen of a mobile terminal when correcting print accuracy. [Figure 10] FIG. 10 is a diagram illustrating an example of a display screen of a mobile terminal when correcting print accuracy. [Figure 11] FIG. 10 is a diagram illustrating an example of a display screen of a mobile terminal for setting a paper feed tray. [Figure 12] FIG. 10 is a diagram illustrating an example of a display screen of a mobile terminal for setting a paper feed tray. [Figure 13] 10A and 10B are diagrams showing examples of display screens of an MFP and a mobile terminal in the initial setting process. DETAILED DESCRIPTION OF THE INVENTION

[0028] Hereinafter, an embodiment will be described with reference to the drawings. <Embodiment> A management system 1 according to an embodiment of the present disclosure will be described with reference to FIGS.

[0029] [Overall configuration of management system 1] Fig. 1 shows a schematic configuration of a management system 1 according to an embodiment of the present disclosure. As shown in Fig. 1, the management system 1 includes a mobile terminal 10, a plurality of MFPs 50, and a service providing server 70 (hereinafter also simply referred to as "server 70"). The mobile terminal 10 is an external terminal carried by a user. MFP is an abbreviation for Multi-Function Peripheral. The management system 1 is a system that uses the server 70 to comprehensively manage services that use the MFPs 50.

[0030] Here, "service" refers to, for example, a delivery service that delivers consumables used in the MFP 50, a billing service that charges by the number of printed pages (the number of printed sheets on one side), or a rental service that rents out the MFP 50 itself. A service includes multiple plans. A "plan" specifies the scope, quality, available benefits and functions, price, etc. of the service provided.

[0031] A user uses the mobile terminal 10 owned by the user to apply for a service by selecting a plan, or to request initial setup processing to transition the MFP 50 to a usable state. A service contract is concluded between the user and the service provider based on the contents of the subscription plan. For example, after a rental service contract is concluded and the desired product is delivered to the user, the user requests initial setup processing of the product. Details of the initial setup will be described later.

[0032] The mobile terminal 10 and the MFP 50 are connected to a network 200. The network 200 may be the Internet, a local area network (LAN), or a combination of a LAN and the Internet. The network 200 may be wired, wireless, or a combination of wired and wireless. In this embodiment, the mobile terminal 10 and the MFP 50 are connected wirelessly to a router (not shown) that constitutes part of the network 200. A service providing server 70 is also connected to the network 200.

[0033] The mobile terminal 10 mainly includes a CPU 12, a memory 14, a network I / F 16, an LCD 20, and a touch panel 22. These components are capable of communicating with each other via a bus 28. The mobile terminal 10 is, for example, a mobile terminal such as a smartphone. Note that the mobile terminal 10 is not limited to a smartphone, and may be other terminal devices such as a tablet or a laptop. The configuration of the mobile terminal 10 shown in FIG. 1 is one example. For example, the mobile terminal 10 may also include a mobile terminal communication I / F for wireless communication with a mobile base station, a camera for capturing images, and the like.

[0034] The CPU 12 executes the initial setting process in accordance with the initial setting application 30 stored in the memory 14. The initial setting application 30 is not initially stored in the memory 14 of the mobile terminal 10; for example, the initial setting application 30 can be stored in the service providing server 70 and downloaded and installed by the mobile terminal 10, causing the mobile terminal 10 to execute the initial setting. The initial setting application 30 is, for example, an application program that causes the mobile terminal 10 to execute the initial setting of the MFP 50. The CPU 12 that executes the initial setting application 30 sets an administrator password for the MFP 50, sets the time on the MFP 50, and displays an initial setting guide on the LCD 20. Furthermore, the memory 14 includes a data storage area 32. The data storage area 32 is an area that stores data necessary for executing the initial setting application 30.

[0035] The network I / F 16 is a communication interface that performs wired or wireless communication with the network I / F 56 of the MFP 50 connected to the network 200, and includes chips and circuits that comply with the communication standards of the wired LAN or wireless LAN. The mobile terminal 10 and the MFP 50 transmit and receive electronic data to and from each other via a wireless LAN, such as Wi-Fi (registered trademark). The communication method between the mobile terminal 10 and the MFP 50 is not particularly limited. For example, the mobile terminal 10 and the MFP 50 may perform wireless communication via Bluetooth (registered trademark) or NFC (registered trademark).

[0036] The LCD 20 has a display screen that displays various functions of the mobile terminal 10. The touch panel 22 has a touch sensor and is arranged to cover the display screen of the LCD 20. The touch panel 22 detects approach or contact with the user's finger, a touch pen, or the like, and outputs an electrical signal in response to the detection.

[0037] The MFP 50 mainly comprises a CPU 52, memory 54, a network I / F 56, an LCD 58, an input I / F 60, a printer unit 61, a scanner unit 62, a FAX unit 63, a paper feed tray 67, and a cartridge storage unit 65. These components can communicate with each other via a bus 64.

[0038] The CPU 52 executes processing in accordance with a program 66 stored in the memory 54. The program 66 includes, for example, an application program for executing a printing process or a scan, and an application program for executing initial settings of the MFP 50 in accordance with instructions from the initial setting application 30 of the mobile terminal 10. The memory 54 also includes a data storage area 68. The data storage area 68 is an area for storing data necessary for executing the program 66, etc.

[0039] Note that the memory 54 of the MFP 50 and the memory 14 of the mobile terminal 10 are configured by combining RAM, ROM, flash memory, HDD, buffers provided in the CPUs 12 and 52, and the like. Furthermore, the memory 54 of the MFP 50 and the memory 14 of the mobile terminal 10 may be computer-readable storage media. Computer-readable storage media are non-transitory media. In addition to the above examples, non-transitory media also include recording media such as CD-ROMs and DVD-ROMs. Non-transitory media are also tangible media. Meanwhile, electrical signals carrying programs downloaded from a server on the Internet are computer-readable signal media, which are a type of computer-readable media, but are not included in non-transitory computer-readable storage media.

[0040] In addition, the network I / F 56 of the MFP 50 is a communication interface for performing wired or wireless communication with the network I / F 16 of the mobile terminal 10 and the network I / F 73 of the service providing server 70 described below, and includes chips and circuits compatible with the communication standards of wired LAN or wireless LAN.

[0041] The LCD 58 has a display screen that displays various functions of the MFP 50. The MFP 50 of this embodiment has four image processing functions, namely, copy, print, scan, and fax, as a plurality of executable functions. The input I / F 60 is, for example, a touch panel that is configured integrally with the LCD 58, and accepts user operations on icons, buttons, etc. displayed on the display screen of the LCD 58. The input I / F 60 may also have hard keys, etc., in addition to the touch panel.

[0042] The printer unit 61 forms an image on a sheet (e.g., paper, an overhead projector, etc.). The printer unit 61 may be an exposure unit, a photosensitive element, a developing roller, and a fixing unit for performing electrophotographic printing, or an inkjet head, a carriage, and a carriage drive mechanism for performing inkjet printing. When the MFP 50 receives a print instruction from the mobile terminal 10, it transports a sheet stored in the paper feed tray 67 to the printer unit 61, and the printer unit 61 prints an image based on the print image data included in the received print instruction on the sheet. The scan unit 62 has a reading sensor for reading an image from a document. When the MFP 50 receives a scan instruction from the mobile terminal 10, it generates scan data using the scan unit 62 and sends the generated scan data to the mobile terminal 10. The fax unit 63 performs fax processing according to a predetermined protocol. Sheets printed by printing, copying, or fax reception are discharged to a paper output tray of the MFP 50 (not shown). In this embodiment, the paper feed trays 67 include a first tray, a second tray, and a third tray. Hereinafter, when there is no need to distinguish between the individual trays, they will simply be referred to as "paper feed trays 67." The printer unit 61 corresponds to an example of a "printing mechanism."

[0043] The cartridge storage unit 65 is configured to allow a cartridge that stores a colorant such as ink or toner for coloring a sheet to be detachably attached. The cartridge storage unit 65 is equipped with a detection sensor that detects that a cartridge has been attached. Note that instead of the cartridge storage unit 65, a tank that stores the colorant may be provided. The tank may be equipped with an inlet, and a user can store the colorant in the tank by injecting the colorant into the inlet from a bottle containing the colorant. The tank may also be equipped with a detection sensor that detects whether the amount of colorant stored is equal to or greater than a threshold.

[0044] The multiple MFPs 50 each have the same configuration. Of the multiple MFPs 50, an MFP 50 that the user has been using previously will be referred to as the second MFP 50, and an MFP 50 that is not currently in use and that the user will use after initial setup will be referred to as the first MFP 50. When there is no particular distinction between the first MFP 50 and the second MFP 50, they will be referred to as MFPs 50. The first MFP 50 is an example of a "first device." The second MFP 50 is an example of a "second device."

[0045] The service providing server 70 mainly comprises a CPU 71, a memory 72, a network I / F 73, an LCD 74, and an input I / F 75. These components are capable of communicating with each other via a bus 78. The CPU 71 executes processing in accordance with a program 76 stored in the memory 72. The memory 72 is configured by combining RAM, ROM, flash memory, HDD, buffers provided in the CPUs 12 and 52, and the like, and includes a data storage area 77. The data storage area 77 is an area for storing data necessary for executing the storage tables T1 and T2 (described below) and the program 76. The memory 72 corresponds to an example of a "memory."

[0046] The program 76 includes, for example, an application program for creating designation data (described below) that designates the contents of the initial setting process of the mobile terminal 10, and a transmission application program for transmitting the created designation data to the mobile terminal 10. Each configuration is the same as the configuration provided in the mobile terminal 10 or the MFP 50. The service providing server 70 manages services using the MFP 50. More specifically, the service providing server 70 accepts service applications for the MFP 50 and manages the MFP 50 so as to make available functions according to the subscription plan.

[0047] As described above, in this embodiment, the server 70 stores the initial setting application 30 and also plays a role in transmitting the initial setting application 30 in response to a request from the mobile terminal 10. However, the present invention is not limited to this. The initial setting application 30 may be stored in a server separate from the server 70, and the mobile terminal 10 may access the server to download the initial setting application 30. The network I / Fs 16, 56, and 73 correspond to an example of a "communication interface." The service providing server 70 corresponds to an example of a "server."

[0048] FIG. 2 is a diagram illustrating storage table T1 stored in server 70. Storage table T1 shows information regarding the usage history of MFP 50 for each user. Here, the usage history includes the usage history of the second MFP 50 that the user has previously used. On the other hand, the first MFP 50 is in an unused state and is an MFP that the user will be initializing, so the usage history of the first MFP 50 is not included in the usage history of storage table T1 in FIG. 2. Storage table T1 is stored in memory 72 of server 70. As shown in FIG. 2, storage table T1 includes a user ID that identifies the user, a device ID of the MFP 50, a product name of the MFP 50, the number of times a function has been used on the MFP 50, the number of times a paper feed tray has been used, and a service subscription history. In storage table T1, the user ID, device ID, product name, the number of times a function has been used, the number of times a paper feed tray has been used, and the service subscription history are associated with each other.

[0049] The device ID is unique identification information for identifying the MFP 50. The product name corresponds to an example of "type information" indicating the type of the MFP 50. The function usage count and paper feed tray usage count correspond to examples of the "usage history," "usage amount related to operation items," and "print volume" of the MFP 50. Furthermore, the paper feed tray usage count corresponds to an example of the "paper feed tray usage amount." Specifically, in this embodiment, the memory 72 stores the number of jobs for each of the five functions: copy, print, scan, fax transmission, and fax reception. The storage table T1 stores the number of jobs for each of the first to third paper feed trays 67 as the paper feed tray usage count. Each of the copy, print, and fax reception functions involves a printing operation that uses the paper feed tray 67. Therefore, the total number of copy, print, and fax reception counts matches the total number of paper feed tray usages (the sum of the number of jobs for the first, second, and third trays). The service subscription history indicates the subscription history for services targeted at the MFP 50. The service subscription history includes the service name and the plan name of the service.

[0050] 2 shows an example in which a user with a user ID of "ABC" (hereinafter simply referred to as "user ABC") has used two different MFPs 50, with product names "MFP-XXX" and device IDs of "111111" and "222222," as second MFPs 50, before the initial setting process of the first MFP 50. When the same user uses multiple MFPs 50, memory 72 stores the number of times a function has been used, the number of times a paper feed tray has been used, and the service subscription history for each MFP 50.

[0051] FIG. 3 is a diagram illustrating storage table T2 stored in server 70. Storage table T2 shows, among the usage history, the paper type and the number of jobs for each paper type used in each paper feed tray 67. As shown in FIG. 3, storage table T2 also stores, as usage history, the paper type and the number of jobs for each paper type. Although FIG. 3 illustrates only the usage history of user ABC, the paper type and the number of jobs for each paper type are also stored as usage history for other users. For user ABC, for two second MFPs 50 with the product name "MFP-XXX," the total number of times the first tray has been used is 463, the total number of times the second tray has been used is 50, and the total number of times the third tray has been used is 0.

[0052] 2 and 3, storage table T1 and storage table T2 are shown as separate tables for convenience, but the information shown in storage table T1 and storage table T2 may be stored together as a single table. Furthermore, the total value of the number of times each paper feed tray 67 in the two second MFPs 50 has been used, and the total value for each paper type and paper category in storage table T2 shown in Fig. 3 do not need to be stored in advance in memory 72. For example, these values ​​may be calculated when the user ID of the user who requested the initial setting is found in storage table T1 during a data creation process by server 70, which will be described later.

[0053] Furthermore, the storage tables T1 and T2 are accumulated by periodically transmitting usage history from the MFP 50 to the server 70, for example, at predetermined intervals, while the MFP 50 and the server 70 are connected after the user signs up for a predetermined service and starts using the MFP 50. Furthermore, the usage history may be accumulated in the storage tables T1 and T2, distinguishing between predetermined periods. For example, usage history from the last few years (e.g., five years) may be accumulated.

[0054] [Initial setting process] Next, the control processing executed by the management system 1 configured as above will be described with reference to Fig. 4. Fig. 4 is a flowchart showing the procedure of the initial setting processing executed by the management system 1. Based on an initial setting request from a user, the management system 1 causes the first MFP 50 to execute the initial setting processing that reflects the usage history of the second MFP 50 by the same user.

[0055] In the following flowcharts, processes such as "request," "instruction," "receive," "send," "configure," "create," "update," "search," "determine," "notify," and "omit" executed by the mobile terminal 10, the first MFP 50, and the server 70 represent processes executed by the CPUs 12, 52, and 71 in accordance with instructions written in the initial setup application 30 or the programs 66 and 76. The processes executed by the CPUs 12, 52, and 71 also include hardware control via the OS. Note that "acquire" is used as a concept that does not necessarily require a request. In other words, the process of receiving data without an application request is also included in the concept of "the CPU acquiring data." Furthermore, "data" in this specification refers to a computer-readable format. Data with essentially the same meaning but different formats are treated as the same data. The same applies to "information" in this specification.

[0056] The "user" uses the mobile terminal 10 to apply for a service or request initial settings for the MFP 50. Specifically, the CPU 12 of the mobile terminal 10 executes various processes based on the user's operation on the touch panel 22. In FIG. 4, the processes shown in the "Mobile Terminal" column are processes executed by the CPU 12 of the mobile terminal 10. The processes shown in the "MFP" column are processes executed by the CPU 52 of the first MFP 50. The processes shown in the "Server" column are processes executed by the CPU 71 of the server 70.

[0057] In the following description, the processing of the CPUs 12, 52, 71, etc. in accordance with instructions written in the initial setting application 30 or the programs 66 and 76 may be described using abbreviated terms. For example, the statement "CPU 52 of the first MFP 50 executes A" may also be simply described as "the first MFP 50 executes A." The statement "CPU 71 of the server 70 executes A" may also be simply described as "the server 70 executes A." The statement "CPU 12 of the mobile terminal 10 executes A" may also be simply described as "the mobile terminal 10 executes A." Furthermore, data transmission and reception between the mobile terminal 10, the MFP 50, and the server 70 is performed via each network I / F 16, 56, 73. However, in the following description of the transmission and reception processing, the term "via the network I / F" may be omitted. In the following description of each processing, steps are abbreviated as "S."

[0058] 4, the user uses the mobile terminal 10 to request installation of the initial setup application 30 (S11). Specifically, the user turns on the power of the first MFP 50, and while a QR code (registered trademark) linked to an access destination (setup.xxxx.com) for downloading the initial setup application 30 is displayed on the LCD 58 of the first MFP 50, the user photographs the QR code with the camera of the mobile terminal 10. The CPU 12 of the mobile terminal 10 analyzes the photographed QR code, accesses the access destination indicated by the QR code, and displays an installation screen for the initial setup application 30. When the user inputs a request for installation of the initial setup application 30 on the installation screen, the mobile terminal 10 downloads the initial setup application 30 capable of executing initial setup of the MFP 50, and installs the initial setup application 30 (S13).

[0059] Then, the mobile terminal 10 launches the installed initial setting application 30. The following steps S15, S19, S23, S31, and S37 are processes executed by the mobile terminal 10 by the initial setting application 30. Note that if the initial setting application 30 is already installed on the mobile terminal 10, the mobile terminal 10 can omit steps S11 and S13 and simply launch the initial setting application 30 in response to a user operation.

[0060] The user inputs an initial setting request for the first MFP 50 to the operation screen of the installed initial setting application 30 (S14). The portable terminal 10 performs communication settings for the first MFP 50 in response to the initial setting request from the first MFP 50 and establishes a network connection with the first MFP 50 (S15). Then, the portable terminal 10 acquires product information from the MFP 50 (S17). The product information includes a product name indicating the type of the first MFP 50. Next, the portable terminal 10 displays an account login screen for logging in to the server 70 on the LCD 20 (S19). The user inputs login information into the account login screen (S21).

[0061] Specifically, the user inputs the login information, such as the user's email address and the login password for logging into the account, via the touch panel 22. The mobile terminal 10 transmits the login information input by the user, the product information, and information regarding the initial setup request from the user to the server 70 (S23). The server 70 then executes a request reception process (S25). In the request reception process, the server 70 receives the login information, the product name, and the initial setup process request from the user, and if the login information is authenticated, executes the process of S27.

[0062] Next, the server 70 executes a data creation process to create designation data specifying the content of the initial setup process (S27). FIGS. 5 and 6 are diagrams illustrating the content of the initial setup process. FIG. 5 shows an example of a default basic setup flow F1 and setup flow data D1. FIG. 6 shows an example of a setup flow F2 and setup flow data D2 modified from the default basic setup flow F1 based on the user's usage history in the data creation process. The setup flows F1 and F2 shown in FIGS. 5 and 6 represent operation items and the order in which the operation items are performed. The setup flow data D1 and D2 shown in FIGS. 5 and 6 correspond to the setup flows F1 and F2 and represent specific flow data executed by the program. In FIGS. 5 and 6, the symbols (i) to (vii) assigned to the operation items in the setup flows F1 and F2 correspond to the symbols (i) to (vii) assigned to the setup flow data D1 and D2, respectively, and the processing contents correspond to the symbols (i) to (vii) assigned to the setup flow data D1 and D2. The basic setup flow F1 shown in FIG. 5 is pre-stored in the memory 72 of the server 70.

[0063] As shown in the setup flows F1 and F2 in Figures 5 and 6, the contents of the initial setup process include the operation items (i) to (vii) executed in the initial setup process, the order in which these operation items are executed, and the setting values ​​required for the operation items. In this embodiment, the data transmitted and received is represented as setup flow data D1 and D2 including the operation items, the order, and the setting values. The setup flow data D1 and D2 correspond to an example of "designated data." In the following description, when there is no particular distinction between the basic setup flow data D1 and the modified setup flow data D2, they are also simply referred to as "designated data." In this embodiment, "initial setup" and "setup" have the same meaning, so in the following description, the initial setup is also referred to as setup.

[0064] The initial setting operation items include (i) cartridge installation, (ii) preparation processing, (iii) time setting, (iv) print accuracy correction, (v) tray setting, (vi) FAX setting, and (vii) service subscription information. In this embodiment, the basic setup flow data D1 includes all seven operation items (i) to (vii). "(i) Cartridge installation" is an operation item that displays a message on the LCD 74 prompting the user to install a cartridge in the cartridge storage unit 65 and determines whether the cartridge has been installed. Whether the cartridge has been installed is determined based on the results of a detection sensor provided in the cartridge storage unit 65. "(ii) Preparation processing" is an operation item related to preparation processing for printing an image on a sheet by the printer unit 61. For example, if the printer unit 61 is an electrophotographic printer, this includes a process of stirring the toner stored in the cartridge. Furthermore, if the printer unit 61 is an inkjet printer, this includes a process of filling the inkjet head with ink stored in the cartridge.

[0065] "(iii) Time setting" is an action item for setting the time. Specifically, the mobile terminal 10 reads the current time set in the mobile terminal 10 and transmits an instruction to set the time together with the current time information to the first MFP 50. In response, the CPU 52 of the first MFP 50 receives the current time information via the network I / F 56 and stores it in the data storage area 68 of the memory 54.

[0066] In this embodiment, information is exchanged between the mobile terminal 10 and the first MFP 50 using, for example, SNMP (Simple Network Management Protocol), with the mobile terminal 10 acting as an SNMP manager and the MFP 50 acting as an SNMP agent, via MIB (Management Information Base). Of course, this information exchange is just one example, and other methods may be used.

[0067] "(iv) Correction of printing accuracy" is an action item that sets the function to improve the printing accuracy of the printing function. For example, it includes processes to correct the print position and correct misalignment of ruled lines. "(v) Tray settings" is an action item that sets the settings related to each paper feed tray 67, and sets the paper size and paper type used in the paper feed tray 67. "(vi) Fax settings" is an action item that sets the settings related to the fax function. "(vii) Service subscription information" is an action item that sets the settings related to the service subscription notification. The content of the notification is set based on the user's service subscription history. Details of the data creation process will be described in more detail below.

[0068] Referring again to Figure 4, the server 70 executes a transmission process to transmit the specified data (see Figure 6) created in the data creation process to the mobile terminal 10 (S29). The mobile terminal 10 requests the first MFP 50 to update the setup flow data (S31). The first MFP 50 then executes a data reception process to receive the specified data (S33). The first MFP 50 executes a setup flow update process based on the received specified data (S35). In the setup flow update process, the basic setup flow F1 stored in advance as a default is modified based on the usage history.

[0069] Next, when the mobile terminal 10 detects that the setup flow update process of the first MFP 50 has been completed, it instructs the first MFP 50 to start setup (S37), and the first MFP 50 executes initial setup process based on the updated setup flow data (S39). By execution process (S41), the first MFP 50 executes initial setup process based on the user's usage history. Note that the data creation process (S27) corresponds to an example of a "creation process," and the data transmission process (S29) corresponds to an example of a "transmission process."

[0070] [Create Process] Next, the details of the process for creating designated data executed by the server 70 will be described with reference to FIG. 7. FIG. 7 is a flowchart showing the procedure of the creation process executed by the CPU 71 of the server 70. As shown in FIG. 7, the CPU 71 searches whether the user ID included in the login information received in the request reception process (S25) is in the storage table T1 (S51). Then, the CPU 71 determines whether the user ID is in the storage table T1 (S53). Specifically, the CPU 71 reads the storage table T1 stored in the memory 72, searches for the received user ID, and checks whether a matching ID exists.

[0071] If a matching user ID is found in the storage table T1 (S53: Yes), the CPU 71 searches the storage table T1 for a product name corresponding to the matching user ID (S55). Then, it determines whether the product name included in the product information received in the request receiving process (S25) matches the product name stored in the storage table T1 (S57). If the product names match (S57: Yes), the CPU 71 acquires the usage amount and service subscription history as the usage history associated with the product name corresponding to the user (S59). The usage amount acquired here includes the number of times the function is used, the number of times the paper feed tray is used, and the usage history for each tray, as shown in FIG. 2.

[0072] The CPU 71 determines whether the number of times the function involving printing has been used is less than a threshold value (S61). If the number of times the function involving printing has been used is less than the threshold value (S61: Yes), the CPU 71 omits the action item "correct print accuracy" from the setup flow (S63). This is because if the number of times the function involving printing has been used is low, there is little need to perform initial settings to improve print accuracy. Note that if the number of times the function involving printing has been used is not less than the threshold value (S61: No), the CPU 71 skips the processing of S63. Note that in the processing shown in FIG. 7 and the following description, the "setup flow" in the phrase "omit an action item from the setup flow" refers to the basic setup flow F1.

[0073] 8 to 10 are diagrams showing examples of the display screen of the mobile terminal 10 when correcting print accuracy. When "correct print accuracy" is executed during initial setting, the first MFP 50 first prints a quality confirmation pattern image on a sheet to check the print quality to see whether printing can be performed normally by the printer unit 61. The first MFP 50 then transmits a print confirmation screen 151 as shown in FIG. 8 to the mobile terminal 10, and the screen 151 is displayed on the LCD 20 of the mobile terminal 10. However, if the action item "correct print accuracy" is omitted in the processing of S63, the process for that action item is omitted, and therefore, during initial setting, the screen related to "correct print accuracy," including printing of the quality confirmation pattern image and print confirmation screen 151, is not displayed, and instead a screen related to the next action item is displayed.

[0074] When correction of print accuracy is to be performed, the user selects "Yes" shown in Fig. 8, and the mobile terminal 10 notifies the first MFP 50 that the selection operation has been performed. In response to receiving the notification, the first MFP 50 transmits a selection screen 152 shown in Fig. 9 or a selection screen 153 shown in Fig. 10 to the mobile terminal 10. A specific example will be described later.

[0075] Next, the CPU 71 determines whether there is a paper feed tray 67 whose usage count is less than the threshold (S65). If there is a paper feed tray 67 whose usage count is less than the threshold (S65: Yes), the CPU 71 omits the corresponding "Paper feed tray setting" action item from the setup flow (S67). This is because there is little need to perform initial settings for a paper feed tray 67 that has been used less than the threshold. Note that if there is no paper feed tray 67 whose usage count is less than the threshold (S65: No), the CPU 71 skips the processing of S67. For example, as shown in FIG. 3, according to the usage history of user ABC, the third tray has been used 0 times. Therefore, the third tray corresponds to a paper feed tray 67 whose usage count is less than the threshold, and the action item related to the setting of the third tray is omitted.

[0076] Next, the CPU 71 sets the most frequently used paper type and paper type for paper feed tray 67 as the initial values ​​(S69). In the example of user A, B, C shown in FIG. 3, different initial values ​​are set for the first tray and the second tray. For example, for the first tray, plain paper is used most frequently as the paper type, and A4 is used most frequently as the paper type. Therefore, the initial values ​​for the first tray are set to "plain paper" as the paper type and "A4" as the paper type. On the other hand, for the second tray, glossy paper is used most frequently as the paper type, and "Letter" is used most frequently as the paper type. Therefore, the initial values ​​for the second tray are set to "glossy paper" as the paper type and "Letter" as the paper type.

[0077] 11 and 12 are diagrams showing examples of setting screens 154 and 155 displayed on the mobile terminal 10 when setting the paper feed tray 67. When the first MFP 50 executes the process for the action item "tray setting," the setting screens 154 and 155 are transmitted from the first MFP 50 to the mobile terminal 10 and displayed on the LCD 20 of the mobile terminal 10. Specifically, when the initial values ​​for the first tray are set and the initial settings are executed in the above example, a setting screen 154 shown in FIG. 11 is displayed on the LCD 20 of the mobile terminal 10 as the setting screen for the first tray. Then, a setting screen 155 shown in FIG. 12 is displayed on the LCD 20 of the mobile terminal 10 as the setting screen for the second tray. As shown in FIG. 11, the setting screen 154 for the first tray displays the paper type as "plain paper" and the paper size as "A4." On the other hand, as shown in FIG. 12, the setting screen 155 for the second tray displays the paper type as "glossy paper" and the paper size as "letter."

[0078] That is, in the initial setting of paper feed tray 67, a screen that reflects the user's usage history is displayed, rather than a specification that uniformly displays "plain paper" or "A4." Therefore, when the user performs the initial setting of first MFP 50 in a format that corresponds to the usage history of second MFP 50, the user can avoid the trouble of reselecting the paper type and paper size from the default values ​​to user specifications on touch panel 22.

[0079] Furthermore, in the process of S69, the frequently used paper size is also set as the initial value when setting the paper size for printing the correction pattern image for correcting the printing accuracy described above. When the user selects "Yes" on the print confirmation screen 151 (FIG. 8) as described above, the screen transitions to a selection screen 152 for the paper size for printing the correction pattern image. FIG. 9 is a diagram showing the selection screen 152 for the paper size for printing the correction pattern image. As shown in FIG. 3, in the usage history of users ABC, the paper size used most frequently among the first to third trays is A4, so the selection tab for "A4" is displayed at the top, as shown in FIG. 9.

[0080] For example, if the most frequently used paper size in the user's usage history is "Letter," a selection screen 153 is displayed as a selection screen for the paper size on which to print the correction pattern image, with the selection tab for "US Letter" corresponding to Letter displayed at the top, as shown in Fig. 10. In this way, because a screen according to the user's usage history is displayed, if there is no need to change the paper size to be corrected, the user can avoid the trouble of reselecting another tab during initial setup.

[0081] Referring again to FIG. 7, after setting the initial value in S69, the CPU 71 determines whether the number of times the fax has been used is less than the threshold value (S71). If the number of times the fax has been used is less than the threshold value (S71: Yes), the CPU 71 omits the action item "Fax Settings" from the setup flow (S73). This is because if the number of times the fax has been used is low, there is little need for initial fax settings. Note that if the number of times the fax has been used is not less than the threshold value (S71: No), the CPU 71 skips the processing of S73.

[0082] The "threshold for the number of times a function involving printing is used," "threshold for the number of times a paper feed tray is used," and "threshold for the number of times a fax is used" are each set appropriately in advance. For example, if the average number of times a function is used by multiple users is used as a reference value, the threshold can be set to a value that is about 0% to 30% of the reference value.

[0083] Next, the CPU 71 determines whether or not there is a history of service subscription even once (S75). Specifically, the server 70 reads out the storage table T1 stored in the memory 72 and makes this determination based on the information on the user's service subscription history in the storage table T1. If there is a history of service subscription even once (S75), it determines that a service subscription notification is necessary, and determines to include a "service notification" including a plan content display in the setup flow (S77). Note that if there is no service subscription history (S75: No), the CPU 71 skips the processing of S77. In other words, it determines not to include a service notification display as an operation item.

[0084] The CPU 71 creates customized setup flow data by modifying the basic setup flow data D1 based on the operation items and setting values ​​determined by the series of processes shown in S51 to S77 in Fig. 7 (S79). The created setup flow data is, for example, the setup flow data D2 shown in Fig. 6. The CPU 71 then ends the data creation process. Note that if there is no user ID in the storage table T1 in S53 (S53: No) or if there is no match in the product name in S57 (S57: No), the CPU 71 creates basic setup flow data D1 corresponding to the basic setup flow F1 (S52) and ends the data creation process. Note that even if communication with the server 70 is not possible due to some kind of communication trouble, the MFP 50 executes the basic setup flow F1.

[0085] The creation process described above in detail will be described below in the case where user ABC newly enters into a service contract for a first MFP 50 with the product name "MFP-XXX" and executes an initial setup request. As shown in FIG. 2, user ABC has previously used two models with the product name "MFP-XXX," and has a service subscription history for each. In user ABC's usage history, it is assumed that the number of times functions involving printing have been used is greater than or equal to a threshold. Furthermore, in user ABC's usage history, it is assumed that the third tray has never been used, and therefore the third tray is the only paper feed tray 67 whose usage count is less than the threshold, and furthermore, the number of times the FAX has been used is less than the threshold.

[0086] When each step of the data creation process is executed sequentially based on the usage history of user ABC, the setting of the third tray is omitted in S65 and S67 because the number of times the tray has been used is less than the threshold. Furthermore, because the number of times the FAX has been used is low and less than the threshold, the action item (vi) FAX setting is omitted in S71 and S73. Furthermore, in S75 and S77, a service information notification including the contents of plan a of service A to which the user has subscribed is added to the action items. Note that here, if the user has subscribed to multiple plans, any of the multiple plans is selected. Note that the selection here may, for example, prioritize the plan with the longest subscription period or the most recently subscribed plan.

[0087] As shown in FIGS. 5 and 6 , the basic setup flow F1 includes all of the operation items (i) to (vii), whereas the setup flow F2 customized for user ABC omits the setting of the third paper input tray in “(v) Tray Setting” and “(vi) FAX Setting.” Furthermore, while the basic setup flow F1 only notifies the user of the service overview in “(vii) Service Subscription Information,” the setup flow F2 specifically notifies the user of the service plan (in this example, plan a for service A). This plan is a plan to which user ABC has previously subscribed. During initial setup, the first MFP 50 transmits, for example, a service subscription information screen 156 shown in FIG. 13 to the mobile terminal 10, and the mobile terminal 10 displays the service subscription information screen 156. Based on the service subscription information screen 156, the user can select a service they have previously used and easily complete the subscription procedure. For example, a service subscription information screen 120 is displayed on the LCD 58 of the first MFP 50.

[0088] As described above, since user ABC has no experience of using the third tray, it is highly likely that the setting of the third tray itself is unnecessary in user ABC's usage pattern, and therefore the setting of the third tray is omitted from the contents of the initial setting process.Similarly, since user ABC uses the FAX only infrequently, it is highly likely that the setting of the FAX itself is unnecessary in user ABC's usage pattern, and therefore the setting of the FAX is omitted from the contents of the initial setting process.

[0089] Furthermore, in the service subscription guide, the specific plan for a service previously subscribed to (in this example, plan a for service A) is notified during initial setup. Therefore, by creating setup flow data based on the user's usage history through the above-described creation process, the user's initial setup time can be reduced and the user can efficiently perform the initial setup. After the initial setup is complete, the MFP 50 transitions to a usable state, and for example, a HOME screen 130, 157 shown in FIG. 13 is displayed, allowing the user to use the MFP 50. The HOME screen 130, 157 includes icons for executing various functions provided in the MFP 50, such as fax, copy, and scan, as well as a colorant remaining gauge and setting icons.

[0090] The management system 1 of the above embodiment has the above-described configuration and thereby provides the following actions and effects.

[0091] (1) In the management system 1 of the above embodiment, the server 70 executes a request receiving process (S25), a data creating process (S27), and a data transmitting process (S29), and the first MFP 50 executes a data receiving process (S33) and an execution process (S39). In the data creating process (S27), setup flow data specifying operation items and setting values ​​to be executed in the initial setting process is created based on the usage history of the second MFP 50 associated with the user ID. Then, in the execution process (S39), the initial setting process of the first MFP 50 is executed based on the modified setup flow data D2.

[0092] That is, it is possible to execute an initial setting process corresponding to the user's past usage history, thereby improving convenience. Specifically, it is possible to omit the execution of operation items that are unnecessary for the user, and to execute the initial setting with appropriate setting values ​​specified. In particular, when a user needs to perform setup work on multiple devices, the user must repeatedly perform similar setup work, including processes that are unnecessary for the user, which has previously resulted in poor work efficiency. However, according to the above embodiment, the setup work can be executed efficiently.

[0093] (2) In the management system 1 of the above embodiment, in the data creation process (S27), if the product name of the first MFP 50 matches the product name of the second MFP 50 (S57: Yes), the server 70 creates setup flow data based on the usage history of the second MFP 50. This makes it possible to create setup flow data according to the type of device. For the same user, if the model of the second MFP 50 previously used and the model of the first MFP 50 that will be newly used match, there is a high possibility that the usage patterns are the same, and in such a case, effective setup flow data can be created.

[0094] (3) In the management system 1 of the above embodiment, the server 70 acquires the usage amount of the operation items used by the second MFP 50 as the usage history (S59), and if the usage amount is less than a predetermined threshold, creates setup flow data that omits the initial settings for the operation items (S61, S63, S65, S67, S71, S73). In other words, since setup for operation items with little usage can be omitted based on the usage amount of the second MFP 50, the efficiency of the setup work can be improved.

[0095] (4) In the management system 1 of the above embodiment, in the data creation process (S27), the server 70 acquires the number of uses of functions involving printing as the print volume of the second MFP 50 as the usage amount, and if the number of uses is less than a threshold (S61: Yes), creates setup flow data in which the action item for “correcting print accuracy” is omitted (S63). In other words, if the print volume is small in the usage history, the action item for correcting print accuracy is omitted, thereby improving the efficiency of the setup work.

[0096] (5) In the management system 1 of the above embodiment, in the data creation process (S27), the server 70 acquires the number of uses of the paper feed tray 67 used for printing by the second MFP 50 as the usage amount, and if the number of uses is less than the threshold (S65: Yes), creates setup flow data that omits the initial settings for the paper feed tray 67 (S67). In other words, because the operation items for the paper feed tray 67 that is used less frequently in the usage history are omitted, the efficiency of the setup work can be improved.

[0097] (6) In the management system 1 of the above embodiment, the server 70 acquires the usage amount for the operation items used by the second MFP 50 in the data creation process (S27), and if the usage amount is equal to or greater than a predetermined threshold, creates setup flow data including initial settings for the operation items. These operation processes correspond to the process of skipping S63 if S61: No, the process of skipping S67 if S65: No, and the process of skipping S73 if S71: No. According to this embodiment, it is possible to execute setup including initial settings for operation items with high usage amounts based on the usage amount of the second MFP 50.

[0098] (7) In the management system 1 of the above embodiment, in the data creation process (S27), the server 70 acquires the number of uses of the paper feed tray 67 used for printing by the second MFP 50 as the usage amount, and if the number of uses is equal to or greater than a threshold value, creates setup flow data (S69) in which setting values ​​for the paper feed tray 67 are set based on the usage history of the second MFP 50. According to this embodiment, for example, as described above in detail, when setting up the paper feed tray 67 to set the paper size and paper type, a screen can be displayed in which items that are used most frequently are displayed at the top according to the user's usage history (FIGS. 9 to 12), thereby saving the user the trouble of changing the setting value items.

[0099] (8) In the management system 1 of the above embodiment, in the data creation process (S27), the server 70 acquires the subscription history of the service targeted for the second MFP 50 as the usage history, determines whether or not a notification of subscription to the service targeted for the first MFP 50 is required based on the subscription history, and if it determines that a notification of subscription to the service is required (S75: Yes), creates setup flow data including the notification of subscription as an action item (S77). This makes it possible to properly notify the user who requires a notification of service subscription in the initial setting of the first MFP 50 of the service subscription notification.

[0100] (9) In the management system 1 of the above embodiment, when the server 70 determines in the data creation process (S27) that the above-mentioned guide notice is necessary, it creates setup flow data including a guide notice displaying the contents of the service. This allows the specific contents of the plan to be displayed in the initial setting of the first MFP 50 as shown in FIG. 13, thereby improving convenience for the user.

[0101] <Other embodiments> In the management system 1 of the above embodiment, the default basic setup flow shown in Figure 5 includes "(vii) Service subscription information." However, this action item does not have to be included. For example, this action item may be included in the setup flow data only if there is a history of service subscription, and a notification of the service subscription may be executed during initial setup.

[0102] In addition, the operation items and setting values ​​of the setup flows F1 and F2 can be omitted, added, or otherwise modified as appropriate. For example, scan settings can be added as an operation item. For example, the setup flows F1 and F2 can be configured to include operation items for scan settings and correction processes to improve scan reading accuracy. Scan settings include settings for resolution and document size. Correction processes are processes for correcting the position and color of scanned images. In the data creation process (S27), the above setup operations related to scanning can be determined based on the user's usage history.

[0103] In the management system 1 of the above embodiment, the device is described as a multifunction peripheral (MFP) 50, but the device may also be a copier, facsimile, or scanner. Furthermore, the device may also be a printing device such as a laser printer or LED printer. An LED printer is one in which the means for exposing the photosensitive body is an LED head. In this case, the color material is toner.

[0104] In the management system 1 of the above embodiment, the content of the initial setup process specified in the designation data includes the operation items to be executed in the initial setup process, the order of the operation items, and the setting values ​​required for the operation items. Alternatively, the content of the initial setup process may include only the operation items or only the setting values. In other words, the designation data may include at least one of the operation items, the setting values, and the order of the operation items. Furthermore, in the above embodiment, the setup flow data D1 and D2 are transmitted and received as the designation data, but the designation data may also be transmitted and received together with the execution program.

[0105] In the management system 1 of the above embodiment, in S29, the server 70 transmits the setup flow data (designated data) updated in the data creation process (S27) to the mobile terminal 10. Alternatively, the updated setup flow data may be transmitted directly to the first MFP 50. In this case, the server 70 may transmit a setup update request to the first MFP 50 together with the updated setup flow data.

[0106] In the management system 1 of the above embodiment, the updated setup flow may be executed solely by the first MFP 50. That is, the screens in Figures 8 to 13 may be displayed on the LCD 58 of the first MFP 50, rather than being transmitted from the first MFP 50 to the mobile terminal 10.

[0107] In the management system 1 of the above embodiment, the initial setup application 30 of the mobile terminal 10 may pre-store a basic setup flow F1 to be executed by the initial setup application 30. The mobile terminal 10 then updates the pre-stored basic setup flow F1 based on the setup flow data transmitted from the server 70 in S29. In this configuration, the initial setup process proceeds under the initiative of the initial setup application 30, and the mobile terminal 10 transmits instructions to execute each operation item to the first MFP 50 as needed. The first MFP 50 executes the process of the operation item in response to the instructions from the mobile terminal 10. Specifically, for example, an instruction to be executed by the first MFP 50 for the operation item (i) cartridge installation is transmitted from the mobile terminal 10, and the first MFP 50, upon receiving the instruction, displays a screen prompting the user to install a cartridge and detects the cartridge. In the management system 1 configured as described above, S31 in FIG. 4 may be deleted, and the processing of S33 and S35 may be executed by the mobile terminal 10.

[0108] In the management system 1 of the above embodiment, when the product name of the first MFP 50 and the product name of the second MFP 50 match (S57: Yes), setup flow data is created based on the usage history of the second MFP 50. In other words, the usage history of the second MFP 50 is used when the models match, but even when the models do not match, setup flow data may be created based on the usage history of the second MFP 50.

[0109] In addition, when creating the setup flow data, it is possible to delete the following settings as appropriate: settings based on the number of times functions involving printing are used (S61, S63), settings based on the number of times the paper feed tray 67 is used (S65, S67), settings for the initial values ​​of the tray paper type and paper type (S69), settings based on the number of times the FAX is used (S71, S73), and settings based on the service subscription history (S75, S77). The setup flow data can be implemented in a form that includes at least one of the above-mentioned settings, or in a form that combines any of multiple settings.

[0110] In the management system 1 of the above embodiment, the number of jobs is used as the printing amount, but other information such as the number of printed sheets, the length of the sheets used for printing, the amount of ink or toner used for printing, etc. may also be used. Also, the number of times a function is used and the number of times a paper tray is used are used as the usage amount, but the number of printed sheets, the number of scanned sheets, etc. may also be used.

[0111] The configuration of the management system 1 in the above embodiment may be modified as appropriate. For example, the server 70 may be configured with multiple physical servers. The server 70 may be configured with at least one of multiple virtual servers constructed by dividing a single physical server using virtualization software.

[0112] In the management system 1 of the above embodiment, the storage tables T1 and T2 are stored in the memory 72 of the server 70, but they may be stored in a memory different from the memory 72 of the server 70. It is sufficient that a user ID and the usage history of the second MFP 50 associated with the user ID are stored in any of the memories of the management system 1 in association with each other.

[0113] The present disclosure is not limited to the above-described embodiments and can be realized in various configurations without departing from the spirit thereof. For example, the technical features in each embodiment corresponding to the technical features in the form described in the Summary of the Invention section can be appropriately replaced or combined to solve some or all of the above-described problems or achieve some or all of the above-described effects. Furthermore, if a technical feature is not described as essential in this specification, it can be appropriately deleted.

[0114] The present disclosure can be realized in various forms, such as a non-transitory computer-readable medium such as a semiconductor memory on which a control program executed by the management system 1 is recorded, a management method, a non-transitory computer-readable medium such as a semiconductor memory on which a printing device program is recorded, etc. The management method can be realized as a method including a request receiving process, a creating process, and a sending process executed by the server 70, and an execution process executed by the MFP 50 as the first MFP 50. [Explanation of symbols]

[0115] 1...Management system, 10...Mobile terminal, 12, 52, 71...CPU, 50...MFP (first device, second device), 16, 56, 73...Network I / F (communication interface), 70...Service providing server (server), 72...Memory.

Claims

1. A management system including a first device, a server, a memory, and a communication interface, The memory stores a user ID for identifying a user and a usage history of a second device associated with the user ID, in association with each other; The server a request receiving process of receiving, via the communication interface, an initial setting process request for requesting initial setting process for transitioning the first device to a usable state, and the user ID; a process for creating designation data that specifies the content of the initial setting process of the first device, the designation data specifying at least one of one or more operation items to be executed in the initial setting process and setting values ​​required for the operation items, based on the usage history of the second device associated with the user ID received in the request receiving process; a transmission process of transmitting the designated data created in the creation process via the communication interface; The first device an execution process of executing the initial setting process of the first device based on the designation data transmitted in the transmission process; A management system characterized by executing the above.

2. The memory stores type information indicating a type of the second device in association with the user ID, The server In the request receiving process, type information indicating a type of the first device is further received; 2. The management system described in claim 1, characterized in that, in the creation process, if the type information of the first device received in the request receiving process matches the type information of the second device, the specified data is created based on the usage history of the second device.

3. The server In the creation process, 2. The management system according to claim 1, characterized in that the usage amount for the operation item used by the second device is obtained as the usage history, and if the usage amount is less than a predetermined threshold, the specified data is created omitting initial settings for the operation item.

4. the first device and the second device have a printing mechanism; The server In the creation process, 4. The management system according to claim 3, characterized in that the printing volume of the second device is obtained as the usage volume, and if the printing volume is less than the threshold, the specified data is created omitting initial settings that improve the printing accuracy of the first device.

5. the first device and the second device have a printing mechanism; The server In the creation process, 4. The management system according to claim 3, characterized in that the usage amount is obtained as the usage amount of the paper feed tray used for printing on the second device, and if the usage amount is less than the threshold value, the specified data is created in such a way that the initial settings for the paper feed tray are omitted.

6. The server In the creation process, 2. The management system of claim 1, further comprising: obtaining a usage amount for the operation item used by the second device as the usage history; and, if the usage amount is greater than or equal to a predetermined threshold, creating the specified data including an initial setting for the operation item.

7. the first device and the second device have a printing mechanism; The server In the creation process, 7. The management system of claim 6, wherein the usage amount is obtained as the usage amount of a paper feed tray used for printing on the second device, and if the usage amount is equal to or greater than the threshold value, the specified data is created with the setting value for the paper feed tray set based on the usage history of the second device.

8. The server In the creation process, The management system described in claim 1, characterized in that it obtains a subscription history of a service targeted at the second device as the usage history, determines whether or not a notification of subscription to a service targeted at the first device is necessary based on the subscription history, and if it determines that the notification is necessary, creates the specified data including the notification as the action item.

9. The server In the creation process, 9. The management system according to claim 8, wherein, when it is determined that the notice is necessary, the management system creates the specified data including the notice indicating the content of the service.

10. In a management system including a first device, a memory, and a communication interface, there is provided a server that manages an initial setting process of the first device, The memory stores a user ID for identifying a user and a usage history of a second device associated with the user ID, in association with each other; a request receiving process of receiving, via the communication interface, an initial setting process request for requesting initial setting process for transitioning the first device to a usable state, and the user ID; a process for creating designation data that specifies the content of the initial setting process of the first device, the designation data specifying at least one of one or more operation items to be executed in the initial setting process and setting values ​​required for the operation items, based on the usage history of the second device associated with the user ID received in the request receiving process; a transmission process of transmitting the designated data created in the creation process via the communication interface; A server that executes the above.

11. A management method executed in a management system including a first device, a server, a memory, and a communication interface, the method comprising: The memory stores a user ID for identifying a user and a usage history of a second device associated with the user ID, in association with each other; Executed by the server, a request receiving process of receiving, via the communication interface, an initial setting process request for requesting initial setting process for transitioning the first device to a usable state, and the user ID; a process for creating designation data that specifies the content of the initial setting process of the first device, the designation data specifying at least one of one or more operation items to be executed in the initial setting process and setting values ​​required for the operation items, based on the usage history of the second device associated with the user ID received in the request receiving process; a transmission process of transmitting the designated data created in the creation process via the communication interface; Executed by the first device, an execution process for executing the initial setting process of the first device based on the designation data transmitted in the transmission process; A management method comprising:

Images