Information processing system, method and device
The method predicts events in printing factories to ensure stable print request processing by assigning tasks based on worker skills and resources, addressing the limitations of existing systems that rely solely on device monitoring.
Patent Information
- Application Number
- JP2022012775
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2022-01-31
- Publication Date
- 2024-11-19
- Estimated Expiration
- 2042-01-31
AI Technical Summary
Existing systems for predicting equipment malfunctions in printing devices focus solely on device behavior, failing to ensure stable processing of print requests that meet quality and delivery requirements, relying heavily on worker capability, which can lead to delays or quality issues.
An information processing method that extracts data related to potential events from print requests and historical data to predict events in specific factories, assigning tasks to workers or maintenance based on skill levels and scheduling to ensure stable processing.
Ensures stable processing of print requests by anticipating and preparing for potential events, ensuring quality and delivery deadlines are met by matching tasks with appropriate worker skills and resources.
Smart Images

Figure 0007586505000001 
Figure 0007586505000002 
Figure 0007586505000003
Abstract
Description
[Technical field]
[0001] The present invention relates to an information processing technique related to printing. [Background technology]
[0002] When printing and various post-printing processes are actually performed, various events such as adjustments, malfunctions, breakdowns, and maintenance of devices such as printing devices occur, and human support is required for these events. Conventionally, devices such as printing devices have been mainly monitored to predict the need for human support. For example, Patent Document 1 discloses a technology for determining the planned time for maintenance work to deal with a detected symptom without interfering with the execution schedule of each process in a printer as much as possible. Specifically, the symptom detection system detects a symptom of a malfunction event in each printer, and notifies the maintenance management device of the identification information of the printer in which the symptom was detected, the type of the malfunction event, and the predicted occurrence timing. Based on the notified information, the schedule information acquisition unit of the maintenance management device acquires the job schedule of the printer in which the symptom was detected from the job schedule management system. The maintenance plan processing unit sets the planned time for maintenance work for the malfunction event related to the symptom within the free time frame of the job schedule.
[0003] This system of predicting the occurrence of malfunctions by monitoring the equipment and scheduling maintenance work accordingly is useful for equipment maintenance companies, but it is not sufficient preparation from the perspective of the party placing the print request (also called a print order). Specifically, a print request requires that all processes be carried out so that the final product that meets the quality requirements included in the print request can be received by the delivery deadline, but only a portion of malfunctions can be predicted by monitoring the equipment, and even if only such a portion of malfunctions can be dealt with, whether or not the final product can be delivered while meeting the quality and delivery requirements is likely to depend on the ability of the workers in the printing factory. In other words, if there are highly skilled workers, they can deal with various events and meet the requirements specified in the print request, such as quality and delivery date, but if there are only workers with low ability, if an event occurs that the worker cannot deal with, the print job will be delayed or quality problems cannot be corrected immediately. In such a situation, the only way to stably ensure that the requirements specified in the print request, such as quality and delivery date, are met is to allow some leeway in the scheduling of the print job. This makes it difficult to increase the operating rate of the printing factory, which also affects the profits of the printing factory.
[0004] As such, focusing only on the behavior of the device is not sufficient in terms of satisfying the various requirements contained in the print request and processing the print request stably, and there is a need to consider other aspects as well. [Prior art documents] [Patent documents]
[0005] [Patent Document 1] JP 2015-215690 A Summary of the Invention [Problem to be solved by the invention]
[0006] According to one aspect, an object of the present invention is to provide a technique for preparing a print request so as to stably process the print request by satisfying various requirements contained in the print request. [Means for solving the problem]
[0007] The information processing method of the present invention includes the steps of: (A) extracting, from data included in a first print request, first data relating to specific items related to events that may occur when processing the print request; and (B) predicting, from the first data and second data relating to the specific items extracted from data included in a second print request that is processed by a specific device in a specific factory prior to the first print request, an event that may occur in the specific device in the specific factory when processing the first print request. Effect of the Invention
[0008] According to one aspect, it is possible to prepare for stably processing a print request by satisfying various requirements contained in the print request. [Brief description of the drawings]
[0009] [Figure 1] FIG. 1 is a diagram conceptually illustrating an example of a network printing system. [Diagram 2] FIG. 2 is a diagram for explaining an example of the structural relationship within a factory and the relationship between the factory and a print order receiving and placing server, etc. [Diagram 3] FIG. 3 is a diagram illustrating an example of a functional configuration of the print order server. [Figure 4] FIG. 4 is a diagram showing the relationship between skill levels and executable work types. [Diagram 5] FIG. 5 is a diagram illustrating a processing flow in the first embodiment. [Figure 6] FIG. 6 is a diagram illustrating a processing flow in the first embodiment. [Figure 7] FIG. 7 is a diagram illustrating a processing flow in the second embodiment. [Figure 8]FIG. 8 is a diagram illustrating a processing flow in the second embodiment. [Figure 9] FIG. 9 is a functional block diagram of a computer. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] [Embodiment 1] The overall configuration of the system according to this embodiment will be described with reference to Fig. 1 and Fig. 2. Fig. 1 is a diagram conceptually explaining an example of an internet printing system 1. Fig. 2 is a diagram explaining an example of the configuration within a factory 400 and an example of the relationship between the factory 400 and a print order server 300, etc. Note that Figs. 1 and 2 are conceptual diagrams, and the actual configuration and relationships are not limited to those shown in Figs. 1 and 2.
[0011] The online printing system 1 includes a user terminal 200 operated by a user who requests printing via a network 100, for example the Internet, a print ordering server 300 that accepts print requests from the user terminal 200, a maintenance company server 350 used by a maintenance company P, and a factory 400 that processes print requests received from the print ordering server 300.
[0012] The user terminal 200 is a terminal operated by a user who requests printing. However, the reception of the print request by the print ordering server 300 is not limited to via the network 100. For example, an employee of a front office business that provides the online printing service provided through the online printing system 1 may input a print request to the print ordering server 300 by operating a terminal (not shown) connected to the print ordering server 300.
[0013] In this embodiment, the factories 400 included in the network printing system 1 may not be concentrated in one country or region, but may be distributed across multiple countries or regions. In the case of Fig. 1, the six factories 400 are distributed across Japan and the United States.
[0014] In this embodiment, the factory 400 is used to mean a place where devices used for producing printed matter (hereinafter also referred to as "production devices") are installed. Therefore, the factory 400 also includes a printing shop or business establishment where only one production device is installed.
[0015] Furthermore, the factory 400 does not have to be a place dedicated to printing, and may be a place where production equipment is located in part of a section. For example, facilities and offices of delivery companies, postal businesses, electricity businesses, gas businesses, public interest corporations, medical businesses, etc. are also included in the factory 400 in this embodiment as long as they have production equipment for printed materials located in part of a section. In other words, the type of business is not important as long as they have production equipment for printed materials. In this sense, delivery companies, postal businesses, electricity businesses, gas businesses, public interest corporations, medical businesses, etc. are also included in printing businesses.
[0016] In this embodiment, six factories 400 are managed by multiple printing businesses. In the case of FIG. 1, there are four printing businesses W, X, Y, and Z. This is due to space limitations, and in reality, there is no limit to the number. Note that the printing businesses W, X, Y, and Z are different corporations. Furthermore, the printing businesses W, X, Y, and Z do not need to have a business relationship, such as a capital relationship or an affiliation relationship. Rather, in this embodiment, it is assumed that the printing businesses W, X, Y, and Z do not have a business relationship, such as a capital relationship or an affiliation relationship.
[0017] It should be noted that the printing business operator does not need to own the factory 400, and does not need to own production equipment for producing printed matter. In addition, in this embodiment, the number of factories 400 connected to the print ordering server 300 may differ for each printing business operator.
[0018] 1, the number of factories 400 connected to the print providers W, X, and Z is one, but the number of factories 400 connected to the print provider Y is three. In other words, the number of factories 400 that each print provider connects to the print order server 300 is arbitrary.
[0019] In this embodiment, the factory 400 is equipped with a data collection server 500 that collects printing-related information and registers it in the print order server 300, a printing device 600 that produces printed matter, a processing device 700 that processes the printed matter, a workflow management device 800 that manages printing schedules, an inventory management device 900 that manages the inventory of consumables, and a sensor 1000 that detects the quality of the printed matter, the environment in the factory, the movement of people in the factory, etc. Note that the factory 400 may also be equipped with a device that manages the attendance of personnel who operate the production devices.
[0020] Here, the printing device 600 and the processing device 700 are both examples of production devices. In the example of Fig. 1, both the printing device 600 and the processing device 700 are arranged in a factory, but only one of them may be arranged in the factory 400. In other words, the factory 400 may be a factory dedicated to printing or a factory dedicated to processing.
[0021] The workflow management device 800 is an example of a production management device, and the inventory management device 900 is an example of an inventory management device.
[0022] 1, only one maintenance company server 350 is shown, but this is due to drawing constraints, and any number of servers may be arranged. Note that the maintenance company server 350 may be any type of computer.
[0023] 1, the maintenance company server 350 is managed by the maintenance company P, but of course there may be multiple maintenance companies. When there are multiple maintenance companies, there are also multiple maintenance company servers 350. Even if there is only one maintenance company, there may be cases where a maintenance company server 350 is provided for each region, for example.
[0024] In this embodiment, the data collection server 500 is installed in each factory 400 by a front office operator who operates the print order server 300, for example.
[0025] In the case of Fig. 1, only one printing device 600 is drawn in the factory 400, but this is due to drawing constraints, and the number of devices to be arranged is arbitrary. Therefore, the number of printing devices 600 arranged in the factory 400 may be one or more. The manufacturer of the printing device 600 may be different for each factory 400. Furthermore, printing devices 600 from multiple manufacturers may be mixed in the factory 400. Each printing device 600 is assigned a dedicated device ID (IDentifier), and information related to the execution of print jobs and information related to the operation of each device are managed for each device.
[0026] The processing device 700 is similar to the printing device 600. That is, the number of processing devices 700 in the factory 400 does not need to be limited to one, and multiple devices may be used. Furthermore, the manufacturer of the processing device 700 may be different for each factory 400. Furthermore, processing devices 700 from multiple manufacturers may be mixed in the factory 400.
[0027] The workflow management device 800 is a device that collectively manages production in a factory. For example, the workflow management device 800 performs processes such as order processing for print jobs, imposition processing for grouping print jobs with the same specifications, management of print schedules and processing schedules, progress management of printing and processing, and management of the amount of paper used in the factory.
[0028] The workflow management device 800 is connected to the printing device 600 and the processing device 700 through the network in the factory, and transfers various data. For example, received print data (including manuscript data and plate data) is transmitted from the workflow management device 800 to the printing device 600 according to a print schedule.
[0029] Workflow management device 800 in this embodiment also manages (i) output data from sensor 1000 that is placed on the path along which paper or the like is transported during the printing process and detects printing defects or abnormalities, (ii) output data from sensor 1000 that is placed on the path along which printed matter is transported during processing and detects processing defects or abnormalities, and (iii) output data from sensor 1000 that manages the quality of printed matter as a finished product, such as stains and defects.
[0030] The sensor 1000 may be disposed inside the housing of the printing device 600 or the processing device 700, or may be disposed separately from the printing device 600 or the processing device 700. The sensor 1000 may also be attached to equipment used by an operator in his or her work.
[0031] Furthermore, the workflow management device 800 in this embodiment also manages information on delivery service companies to be used for delivery of manufactured products (printed materials before processing, in case processing is performed at another factory). The information on the delivery service company also manages the name of the business providing the delivery service, the name of the service, details of the delivery service, shipping date, shipping number, billing amount per order, total billing amount per orderer, information specifying information prohibited from being used outside the factory, etc.
[0032] The workflow management device 800 realizes the management of this information and the provision of functions through application programs that run on a computer.
[0033] Inventory management device 900 in this embodiment manages information related to inventory of materials such as paper, ink, and toner consumed by printing device 600, and film consumed by processing device 700. The information related to inventory may include a code for identifying the inventory (i.e., inventory ID), the name of the material, the category of the material, the number of items in stock, a code for identifying the business that supplies the material (i.e., supplier ID), the name of the business, the type of material supplied by the business, and the like.
[0034] Information about inventory is updated, for example, by reading a code that identifies the inventory when the material is consumed, or by reading information recorded on an IC tag attached to the inventory or its packaging.
[0035] The data collection server 500 communicates with the printing device 600, the processing device 700, the workflow management device 800, the inventory management device 900, and the sensor 1000, and collects various information related to printing from each device. The communication here may be wired or wireless.
[0036] The data collection server 500 collects information such as a code for identifying the device (i.e., device ID), device name, device specification information, device status, status details, printing type, printing speed, speed unit, maximum and minimum paper sizes that can be handled, color space and color standard information, daily production capacity, type of paper used for each received print order or print job, and amount of paper used for each received print order or print job from, for example, the printing device 600. The amount of paper used, etc. is automatically calculated based on data acquired from, for example, a sensor 1000 provided in the printing device 600, etc.
[0037] The status here is specified by, for example, idle, broken, in use, under maintenance, etc. The format of describing this information varies depending on the manufacturer of the printing device 600, and may also vary depending on the model even for the same manufacturer.
[0038] In addition, the data collection server 500 collects information, for example, from the processing equipment 700, such as a code for identifying the equipment (i.e., equipment ID), equipment name, equipment specification information, equipment status, status details, processing type, processing speed, speed unit, daily production capacity, etc.
[0039] The status here is the same as that of the printer 600. The types of processing include, for example, folding, rounding corners, punching, sewing, scoring, surface processing, foil stamping, panel processing, die-cutting, etc. The format of describing this information varies depending on the manufacturer of the printer 600, and may also vary depending on the model even for the same manufacturer.
[0040] In addition, the data collection server 500 acquires information such as order information, printing schedules, processing schedules, progress information of each schedule, the operating status of each production device, the operating rate of each production device, and maintenance records of each production device, for example, from the workflow management device 800.
[0041] Furthermore, the data collection server 500 collects information on the inventory of consumables consumed by the production equipment from the inventory management device 900. In this embodiment, the information on the inventory of consumables includes inventory information for each type of paper by paper manufacturer.
[0042] The data collection server 500 acquires information as soon as it is generated in each device and sensor 1000. That is, the data collection server 500 in this embodiment automatically collects information that is generated in conjunction with production in a factory and that changes over time.
[0043] The data collection server 500 in this embodiment also has a function of cleaning up the collected information into a format that is compatible with model differences, and transmits the cleansed (cleansed) information to the print order server 300. Model differences here include differences in manufacturers.
[0044] In this embodiment, the data collection server 500 also transmits information obtained by analyzing the cleansed (maintenance) information to the print order server 300 through a secure line. The information obtained by analyzing the cleansed (maintenance) information is also an example of information in a format that does not matter depending on the model. The information obtained by analyzing the cleansed (maintenance) information may include, for example, the current operating availability of the production device, a prediction of the operating availability of the production device in the future, and a prediction of the inventory amount. The calculation of the operating availability also reflects maintenance schedules, holidays, and the like. In this embodiment, the cleansing (maintenance) function is provided in the data collection server 500, but the cleansing may be performed on the print order server 300 side. In this case, the print order server 300 receives a part of the raw data after the filter process through a secure path.
[0045] Although the print data is directly transmitted from the print ordering server 300 to the workflow management device 800 , it is also possible to provide the print data to the workflow management device 800 via the data collection server 500 .
[0046] Next, an example of the functional configuration of the print order server 300, which is the main part of this embodiment, will be described with reference to FIG.
[0047] The printing order server 300 has a data collection unit 310, a basic data DB 311, an order processing unit 312, a pre-processing unit 313, an analysis unit 314, an analysis result DB 315, an actual response DB 317, an actual event DB 316, a first learning processing unit 318, a prediction unit 319, a prediction result DB 321, an event processing unit 322, a second learning processing unit 323, an instruction response DB 324, and an output processing unit 325.
[0048] The data collection unit 310 mainly stores data received from the data collection server 500 in a basic data DB 311. However, in this embodiment, when an event occurs such as adjustment, malfunction, breakdown, or maintenance of a device such as the printing device 600 or the processing device 700, data related to the event is also accumulated in an actual event DB 316 for use by the first learning processing unit 318. Furthermore, data related to measures actually taken against the above events is accumulated in an actual measure DB 317 for use by the second learning processing unit 323.
[0049] Data related to an event includes, for example, an identifier of the print request or print job being processed when the event occurred, an identifier of the event, the content of the event, the time the event occurred, an identifier of the device on which the event occurred, etc. Data related to the actual action taken against the event includes, for example, an identifier of the print request or print job being processed when the event occurred, an identifier of the event, the time the action was taken, an identifier of the device on which the action was taken, etc.
[0050] The basic data DB 311 includes a requester DB, a request DB, a factory DB, etc. The requester DB stores information about the requester. The information about the requester includes, for example, a requester identifier (i.e., a customer ID), the requester's name, the requester's place of residence or location, information about the requester's person in charge, the requester's contact information, the requester's type of business, a service management number prepared for each customer, billing information, etc.
[0051] The request DB stores data related to print requests, such as an order ID, conditions specified at the time of the request, information related to the print data, a billing ID, information related to the billing, and the progress of the ordered print.
[0052] The conditions specified at the time of the request include, for example, the desired delivery date, the desired printing business, the desired factory, the country or region where printing will be performed, the desired application, the desired price, the desired delivery method, the desired paper type, the paper weight, the desired color profile, the desired production quantity, the finished size, designation of single-sided or double-sided printing, the type of processing, designation of the document layout section, the product form, single item or multiple items, etc. The application here is used to designate the type of printed matter, for example, direct mail, a book, etc.
[0053] The product form includes, for example, books, postcards, flyers, business cards, tickets, catalogs, slips, envelopes, stickers, labels, bags, boxes (packages), and the like.
[0054] The information on the print data includes the print data, which is provided by the customer as, for example, a PDF (Portable Document Format) file.
[0055] The factory DB is automatically updated with new information uploaded from the data collection server 500. The factory DB also records information calculated by the print order server 300 based on the information uploaded from the data collection server 500.
[0056] The information derived based on the information uploaded from the data collection server 500 includes, for example, information evaluating the quality of each factory, the past and current conditions of each factory, production capacity calculated from past results, predicted schedules, etc. In this embodiment, it is assumed that a production schedule can be specified for each device in each factory.
[0057] The factory DB also records registration information such as the location and business days of the factory 400. The registered information here is so-called static information that does not change over time.
[0058] The factory DB also records evaluations of the factory 400 by users who request printing, evaluations of the factory 400 by businesses who order printing received via the Internet or the like from factories 400 participating in the service, records of delays in past delivery dates, records of quality defects confirmed in past deliveries, etc.
[0059] The factory DB also stores information about the paper used in print orders and print jobs.
[0060] Furthermore, the factory DB may also store work schedule data for workers working in each factory. In this case, data on the skill level of each worker is also stored. Furthermore, the work schedule data may include data on which worker is assigned to which device.
[0061] The order processing unit 312 receives a customer's print request from the user terminal 200, and executes a process of assigning a specific factory and a specific device installed in the specific factory to process the print request based on the conditions specified at the time of the request (i.e., the ordering conditions) and the information about the factory stored in the factory DB. The order processing unit 312 stores data about the print request in the request DB, and also stores data about the placed print request in the factory DB in association with the factory to which the print request is placed.
[0062] How the order processing unit 312 allocates factories and equipment to print requests is not the main focus of this embodiment, so a detailed explanation will be omitted, but the order processing unit 312 identifies factories and equipment that can meet the conditions specified at the time of the request, and if multiple combinations of factories and equipment are identified as candidates, the factory with the highest rating is given priority. Since there is a delivery deadline, the production schedule is naturally taken into consideration, and the time period in which the current print request should be processed, i.e., the scheduled processing time period, is also identified by the order processing unit 312.
[0063] The pre-processing unit 313 performs, for example, a pre-flight check of the print data included in the print request. The pre-flight check checks for issues such as color, font, use of transparency, image resolution, total ink amount, file version compatibility, etc. Using data extracted in the pre-flight check, the order processing unit 312 may also select the model of printing device 600 that should process the print data.
[0064] The analysis unit 314 extracts data on predetermined items related to events that may occur when processing a print request from the data related to the print request. The predetermined items include items included in the conditions specified at the time of the request, items included in the print data, etc. Items included in the print data also include items extracted from the print data by the preprocessing unit 313.
[0065] The predetermined items include, for example, the following data: · File format of print data (may include version, editing software of original data and OS (Operating System)) Color or monochrome Page orientation and size Objects and their metadata (if the object is text, the font used, data about the text (such as whether it is written vertically or horizontally), etc.; if it is an image, the number of images on the page, their size, resolution, etc.) Total amount of ink -Type and quantity of paper used By combining this data with the factory and equipment, it will also be possible to predict problems with compatibility between paper and equipment (color development, fixing, etc.).
[0066] The above-mentioned predetermined items are mainly items related to events that may occur in the printing device 600, but may also include items related to events that may occur in the processing device 700. For example, items such as the type of processing and the form of the product may also be included. In addition, events that may occur in the printing device 600 and events that may occur in the processing device 700 may be distinguished and processed separately by the prediction unit 319.
[0067] The analysis result DB 315 stores data (i.e., analysis results) extracted by the analysis unit 314. At this time, the analysis result DB 315 holds the extracted data so that the order in which print requests are processed can be determined for each device in each factory.
[0068] The prediction unit 319 predicts events that may occur while the current print request is being processed at the assigned factory and device, based on extracted data (corresponding to the first data) related to the current print request and extracted data (corresponding to the second data) about a print request (a preceding print request) that is to be processed before the current print request at the assigned factory and device of the current print request.
[0069] Events include breakdowns, malfunctions, maintenance, etc. that should be handled by an equipment maintenance company, and adjustments, malfunctions, maintenance that should be handled by workers in the factory. For example, the former includes replacement of supplies (toner, belts, transfer conveyor devices, etc.) and the occurrence of dirt. The latter includes self-maintenance matters other than events that should be handled by a maintenance company. There are also cases where the occurrence of multiple events is predicted.
[0070] The prediction unit 319 includes a trained model trained by supervised machine learning, for example. The extent to which the extracted data is used is adjusted by experiments, but at least the extracted data for the immediately preceding print request is used. In addition, the occurrence probability of all events may be output, and an event whose occurrence probability is equal to or exceeds a predetermined threshold may be selected as an event to occur.
[0071] However, the prediction unit 319 may make predictions based on specific logic or rules obtained by analyzing knowledge gained to date, rather than based on a trained model trained through machine learning.
[0072] The prediction unit 319 stores the predicted event data in the prediction result DB 321 in association with the factory and device to which the print request is assigned and the data related to the print request.
[0073] The first learning processing unit 318 performs a learning process to generate a trained model for the prediction unit 319. The first learning processing unit 318 learns data related to events that occurred during processing of past print requests that is collected by the data collection unit 310 and stored in the actual event DB 316, extracted data related to past print requests that is stored in the analysis result DB 315, and data related to events predicted to occur for past print requests that is stored in the prediction result DB 321, and generates a trained model that infers events that will occur from the time-series data of the extracted data for a specific factory and a specific device.
[0074] The event processing unit 322 specifies a countermeasure for the currently predicted event, and also specifies data for specifying a person who will implement the countermeasure. For example, if the predicted event is an event that should be handled by a worker in a factory, the event processing unit 322 specifies a countermeasure for the trouble, and specifies a skill level (specified by level and rank in this embodiment) that allows the worker to implement the countermeasure for the trouble. On the other hand, if the predicted event is an event that should be handled by a maintenance company, the event processing unit 322 specifies a countermeasure for the event.
[0075] The event processing unit 322 stores the predicted event and the identified countermeasure in the instruction countermeasure DB 324 in association with the identifier of the print request.
[0076] The event processing unit 322 includes a trained model trained by, for example, supervised machine learning. Note that the event processing unit 322 may output the occurrence probability for all countermeasures, and select the countermeasures whose occurrence probability is equal to or greater than a predetermined threshold as the possible countermeasures.
[0077] However, the event processing unit 322 may be configured to identify how to deal with an event based on specific logic or rules obtained by analyzing knowledge gained up to now, a correspondence table between events and how to deal with them, etc., rather than a trained model trained by machine learning.
[0078] The second learning processing unit 323 learns data on events that have actually occurred that are collected by the data collection unit 310 and stored in the actual event DB 316, countermeasures that have actually been taken for events that have actually occurred that are stored in the actual countermeasure DB 317, and countermeasures identified for predicted events that are stored in the instruction countermeasure DB 324, and generates a learned model that infers countermeasures from events for a specific factory and a specific device.
[0079] Furthermore, the event processing unit 322 holds a table in which, for example, the level and rank of the workers in the factory are associated with the countermeasures (task types) that can be performed by workers belonging to the level and rank. An example of this table is shown in FIG. 4. For example, levels 1 to 3 are set based on the results of a predetermined qualification test, and each level is divided into three ranks according to the division of the actual working time. The number of levels and ranks is only an example, and various divisions are possible. For each combination of level and rank, the task types that can be performed by workers belonging to the level and rank are listed. Such a table is set for each type of equipment. Note that the actual working time is only an example, and the ranks may be set from other perspectives. Also, in the table as shown in FIG. 4, when a certain task type is focused on, the associated level and rank are the lowest level and rank at which the task type can be performed, and if the level and rank are higher, the task type can be performed. Also, the table as shown in FIG. 4 is only an example, and when the event type and the task type are one-to-one, the event type may also be associated.
[0080] The types of work include removing and installing the IA pump, replacing the ink pump motor and adjusting the coupling height, replacing and cleaning the gear pump (SAS), replacing the TIC board, adjusting the compressor air pressure, replacing the CS belt and motor, removing and cleaning the CS catch tray, replacing the CS pump, correcting the CS imaging oil flow rate, replacing the imaging oil pump and replacing the impeller, replacing the EBV suction blower, replacing the ITM lamp, removing and installing the main motor, cleaning and greasing the main motor gear, removing and installing the BID engage motor, removing and installing the BID motor and coupling, replacing the BID recognition sensor, replacing the BDU, cleaning the feeder head unit drawer belt, removing and installing the feeder head unit, adjusting the sheet separator height, removing and installing the VSP unit and replacing the motor and belt, replacing the AMTEK blower, replacing the vacuum valve and sensor, replacing the slave board, and replacing the power supply unit. , bridge vacuum box replacement and belt replacement, removal and installation of PSTB unit (IR sensor), removal and installation of IFR unit, removal and installation of exit conveyor unit and belt replacement, removal and installation of exit conveyor extension (ILS) unit and belt replacement, stacker transport belt replacement, stacker vacuum box replacement and belt replacement, paper transport system calibration, secondary pressure compensation wizard, simplex buckle distortion adjustment, duplex buckle distortion adjustment, suction cup margin, image placement, duplex conveyor gap adjustment, PaperLUT, front and back registration wizard, operation check of IA pump, gear pump, CS motor, etc., running the lubrication wizard, running the torque and wavelength wizard, operation check of each blower, lubrication of GDU, cleaning of ITM slip ring, replacement of PIP and ITM carbon brushes, replacement of vacuum pump blades, etc.
[0081] Using such a table, when there is an event that needs to be dealt with by workers in the factory, the event processing unit 322 identifies the level and rank of the worker who can implement a countermeasure against the event.
[0082] The output processing unit 325 transmits data about the print request to, for example, the workflow management device 800 or the data collection server 500 in the factory 400 to which the print request is placed, together with data about events that are predicted to occur, and if there is an event that needs to be dealt with by workers in the factory, data about how to deal with the event, and further data about the level and rank of the workers who can implement the action.
[0083] Furthermore, if there is an event that the maintenance company needs to deal with, the output processing unit 325 transmits to the maintenance company server 350 data on the event, data on how to deal with it, extracted data predicting the occurrence of the event (and in some cases, extracted data on an earlier print request), data on the factory and equipment to which the print request is to be placed, data on the time period during which the print request is scheduled to be processed, etc.
[0084] Next, the process of the print order server 300 according to this embodiment will be described with reference to FIGS.
[0085] First, when the order processing unit 312 receives a print request from the user terminal 200, it identifies the factory and equipment (the order recipient's factory and equipment) that will process the print request, and stores data related to the print request and data related to the order recipient's factory and equipment in the basic data DB 311 (FIG. 5: step S1). In this step, the pre-processing unit 313 may use the results of a pre-flight check performed on the print data, for example. As described above, for example, the factory and equipment that meet the conditions specified at the time of the request are prioritized based on the evaluation of the factory, and the factory and equipment with the highest priority are identified. Note that the priority may also be determined taking into account the geographical conditions of the product's delivery destination. In addition to the order recipient's factory and equipment, the scheduled processing time period is also identified.
[0086] Next, the analysis unit 314 extracts data (first data) related to predetermined items related to events that may occur when processing the print request from the data related to the print request, and stores the data in the analysis result DB 315 in association with the supplier's factory and device together with the data related to the print request (step S3). The predetermined items are as described above. As described above, the data may also include data extracted by the preprocessing unit 313.
[0087] Then, the prediction unit 319 uses the extracted data (first data) about the current print request stored in the analysis result DB 315 and the extracted data (second data) about print requests that are scheduled to be processed in advance at the supplier's factory and equipment that will process the current print request to predict one or more events that may occur while processing the current print request, and stores the prediction result in the prediction result DB 321 in association with data about the print request, including an identifier for the print request (step S5).
[0088] The reason for using the extracted data related to the print request preceding the current print request in this manner is that the processing of the preceding print request will have an impact on the client's factory and equipment, that is, depending on the preceding print request, a particular event may be more or less likely to occur during the processing of the current print request.
[0089] Furthermore, the event processing unit 322 identifies a countermeasure for each of the predicted one or more events, and stores the countermeasure in the instruction countermeasure DB 324 in association with the data related to the event and the identifier of the print request (step S7). Note that, with regard to the countermeasure (i.e., the type of work for the event), there are countermeasures that should be implemented by the maintenance company and countermeasures that should be implemented by workers in the factory, and the countermeasures that should be implemented by the maintenance company may also be listed. Note that, based on the type of event, a distinction may be made between events that should be implemented by the maintenance company and events that should be implemented by workers in the factory, and the countermeasures for the events may be distinguished based on the type of event.
[0090] Then, the event processing unit 322 judges whether the identified countermeasures include a countermeasure that should be implemented by the maintenance company (step S9). If all the identified countermeasures are implemented by workers in the factory, the process moves to the process of FIG. 6 via a terminal A. On the other hand, if the identified countermeasures include a countermeasure that should be implemented by the maintenance company, the event processing unit 322 instructs the output processing unit 325 to transmit data on the event, data on the countermeasures, extracted data (first data, including second data in some cases) in which the occurrence of the event is predicted, data on the factory and device of the order recipient of the print request, data on the schedule for processing the print request, and the like to the maintenance company server 350, and the output processing unit 325 transmits the data to the maintenance company server 350 in response to the instruction (step S11). Then, the process moves to the process of FIG. 6 via a terminal A.
[0091] 6, the event processor 322 judges whether the identified countermeasures include countermeasures that should be implemented by workers in the factory (step S13). If all the identified countermeasures are to be implemented by the maintenance company, the process proceeds to step S17.
[0092] On the other hand, if a countermeasure to be implemented by a worker in the factory is included, the event processing unit 322 identifies the skill level (e.g., level and rank) of a worker who can implement the identified countermeasure (task type) using, for example, a table such as that shown in Fig. 4 (step S15). The level and rank may be identified for each countermeasure (task type), or the skill level requiring the highest level and rank among the identified countermeasures may be identified.
[0093] The output processing unit 325 then transmits data about the print request, together with data about the predicted event, data about how to deal with an event that must be dealt with by workers in the factory if there is one, and data about the skill level of the workers who can implement the measures, to, for example, the workflow management device 800 or the data collection server 500 in the factory 400 to which the print request was placed (step S17).
[0094] By carrying out such processing, the client's factory can stably process the print request by having a worker with the specified skill level work on the current print request while the print request is being processed.
[0095] Conversely, from the perspective of the front office business operator operating the print ordering server 300 and the customer, requiring each factory 400 to assign workers with the skill level specified by the print ordering server 300 to handle the current print request ensures stable processing of print requests.
[0096] Moreover, by monitoring the equipment, the occurrence of various events is predicted earlier than predicted failures, etc., so the factory 400 side can prepare for the occurrence of events in advance. Also, data on events and countermeasures is sent to the maintenance company server 350, so the maintenance company can also prepare for the occurrence of events in advance. Furthermore, since the extracted data (although it may be only a part of it) is also notified, the maintenance company server 350 can also use it for the analysis of maintenance events and failures and for improving responses.
[0097] Furthermore, if there is a difference between a predicted event and an event that has actually occurred, the first learning processing unit 318 updates the trained model, so that events that may occur can be predicted (i.e., inferred) with greater accuracy. Similarly, if there is a difference between a countermeasure for a predicted event and a countermeasure for an event that has actually occurred, the second learning processing unit 323 updates the trained model, so that a countermeasure for the event can be identified with greater accuracy.
[0098] [Embodiment 2] In the first embodiment, factories 400 are required to provide workers with a specific skill level for each print order, with the actual allocation of workers being left to each factory 400.
[0099] On the other hand, if the print ordering server 300 stores data on the skill levels and work schedules of workers in each factory 400, for example in a factory database, print requests can be placed with factories that have workers who can handle events that may occur, ensuring more reliable processing of print requests.
[0100] The processing in such a case will be described below with reference to Figures 7 and 8. Note that although the configuration of the print ordering server 300 is almost the same as that of the first embodiment, some components have different functions, which will be explained in the process flow.
[0101] First, when the order processing unit 312 receives a print request from the user terminal 200, it identifies candidate factories and equipment capable of processing the print request (FIG. 7: step S31). For example, it identifies factories and equipment that meet the conditions specified at the time of the request, and assigns priorities based on the evaluation of the factories. In some cases, it also assigns priorities based on the geographical conditions of the product delivery destination. At this stage, it extracts factories and equipment based on other requirements, without considering the skill level and work schedule of the workers, but it identifies the planned processing time period for each candidate factory and equipment.
[0102] Next, the analysis unit 314 extracts data (first data) relating to a predetermined item related to an event that may occur when processing the print request from the data related to the print request (step S33). The analysis unit 314 outputs the extracted data (first data) about the current print request to the prediction unit 319 so that the prediction unit 319 predicts the occurrence of an event for each candidate factory and device.
[0103] The prediction unit 319 initializes a candidate counter i to 1 (step S35), and predicts one or more events that may occur while processing the current print request for the i-th candidate factory and device, using the extracted data (first data) for the current print request and the extracted data (second data) for the print request to be processed in advance (step S37). The analysis unit 314 outputs data on the predicted events to the event processing unit 322, and requests the event processing unit 322 to process the events that may occur when the current print request is placed with the i-th candidate factory and device.
[0104] The event processing unit 322 identifies how to deal with one or more events predicted to occur when the current print request is placed for the i-th candidate factory and device (step S39). As in the first embodiment, events that should be dealt with by a maintenance company and events that should be dealt with by workers in the factory may be included, so a method of dealing with each event (type of work) is identified.
[0105] Then, the event processing unit 322 judges whether the identified countermeasures include a countermeasure to be performed by an in-factory worker (step S41). If the identified countermeasures do not include a countermeasure to be performed by an in-factory worker, the process proceeds to the process of FIG. 8 via the terminal B. On the other hand, if the identified countermeasures include a countermeasure to be performed by an in-factory worker, the event processing unit 322 identifies the skill level (e.g., level and rank) of an operator who can perform the identified countermeasures (task type) using a table such as that shown in FIG. 4 (step S43). For each of the identified countermeasures (task types), the level and rank of an operator who can perform the countermeasure (task type) may be identified, or the skill level of the countermeasure that requires the highest level and rank among the identified countermeasures may be identified. The event processing unit 322 outputs data on the skill level of an operator required when the current print request is processed at the i-th candidate factory and device to the order processing unit 312.
[0106] The order processing unit 312 judges whether or not a worker with the specified skill level is available to work on the current print request based on the work schedule data for the i-th candidate factory and the skill level data for the worker (step S45). Since the planned processing time period in the case where an order is placed with the i-th candidate factory and device is also specified, it judges whether or not a worker with the specified skill level is scheduled to work during the planned processing time period. If the work schedule data includes data on the device and print request that each worker is responsible for, it may further judge whether or not the worker is available to work on the current print request. In other words, if the worker is assigned to work on another print request, it may be judged that the worker is not available to work on the current print request.
[0107] If it is determined that a worker with the identified skill level is capable of processing the current print request, the order processing unit 312 maintains the priority of the i-th candidate factory and device (step S47). This is because it is assumed that the current print request can be processed according to the evaluation so far. However, processing to raise the priority may be performed. Then, the process proceeds to step S51.
[0108] On the other hand, if it is determined that a worker with the identified skill level is not able to process the current print request, the order receiving processor 312 lowers the priority of the i-th candidate factory and device (step S49). The priority is lowered because there is a possibility that the current print request cannot be processed according to the previous evaluation. However, if the priority is raised in step S47, the priority may be maintained in step S49, but the relative priority order is lowered. It is also possible to remove the candidate from the list so that it will not be selected as a supplier. Then, the process proceeds to step S51.
[0109] The prediction unit 319 judges whether all candidates have been processed (step S51), and if there is a candidate that has not been processed, the value of the counter i is incremented by 1, and the process returns to step S37 in FIG. 7 via the terminal C. On the other hand, if all candidates have been processed, the order processing unit 312 determines the factory and device with the highest priority as the order destination for the current print request (step S55). For the factory and device determined as the order destination, the order processing unit 312 instructs the analysis unit 314, the prediction unit 319, and the event processing unit 322 to register data on the print request, extracted data (first data), data on the predicted event, data on how to deal with the event, and the like in each DB. In addition, the order processing unit 312 registers data on the print request for the factory and device determined as the order destination in the basic data DB 311.
[0110] The output processing unit 325 then transmits data on the print request, together with data on the predicted event, and data on how to deal with an event that should be dealt with by workers in the factory, to, for example, the workflow management device 800 or the data collection server 500 in the factory 400 to which the print request is placed (step S57). Note that data on the skill level of workers who can implement measures to deal with events that may occur may be transmitted, or data on the specific workers who should be engaged in the work may be transmitted.
[0111] Furthermore, the output processing unit 325 judges whether the measures identified for the event that may occur while processing the current print request at the factory and device determined as the order recipient include measures to be implemented by the maintenance company (step S59). If the workers in the factory implement all of the identified measures, the processing for the current print request ends. On the other hand, if the measures identified include measures to be implemented by the maintenance company, the event processing unit 322 instructs the output processing unit 325 to transmit data on the event, data on the measures, extracted data (first data, possibly including second data) predicting the occurrence of the event, data on the factory and device of the order recipient of the print request, data on the schedule for processing the print request, etc., to the maintenance company server 350, and the output processing unit 325 transmits the data to the maintenance company server 350 in response to the instruction (step S61). Then, the processing ends.
[0112] By performing such processing, an order is placed with a factory that is well equipped to reliably handle events that may occur during the processing of a print order.
[0113] [Other embodiments] In the above-described embodiment, in order to simplify the explanation, it is assumed that the scheduled processing time for the current print request is set after the print requests that have been placed so far. However, if there is an empty time slot between the processing of the first print request and the processing of the second print request in the production schedule, the third print request may be processed in that empty time slot. In such a case, if the third print request is scheduled in the empty time slot, the third print request will be added as a preceding print request for the second print request, so that the events that may occur for the second print request (and subsequent print requests) may change, and the skill level of the worker who can handle the event may also change.
[0114] Therefore, when a third print request is added, it is preferable to check whether the events that can occur for at least the second print request have changed and to determine whether the request can be handled by the workers already assigned.
[0115] After such confirmation, the process that predicts events that may occur with respect to the current print request and subsequent processes are performed, and if no worker capable of dealing with the event is available, the priority is lowered.
[0116] In the second embodiment, it is not assumed that the scheduled processing time slot will be changed once it has been determined, but if it is determined that no worker is available to handle a possible event, the scheduled processing time slot may be changed, for example, as long as the deadline is met. However, in such a case, there is a possibility that print requests that have been placed up to now will be affected as described above, so for print requests that are scheduled to be processed after the current print request, as described above, it is preferable to check whether the possible events will change for at least the second print request and determine whether the already assigned worker can handle it.
[0117] Furthermore, when a specific factory is specified as a condition when a print request is made, if an available time slot is selected as the scheduled processing time slot, it may be impossible to secure workers who can handle events that may occur. In such a case, it is also assumed that the processing order of the print requests will be changed. In such a case, there is no effect on print requests that are processed before the current print request is processed, but print requests that are processed after the current print request may be affected in the same way as described above, so it is preferable to check whether the events that may occur will change and determine whether they can be handled by the workers already assigned.
[0118] In cases where a specific factory is specified as a condition when a print request is made, if an available time slot for a specific device that is the most preferable is selected as the scheduled processing time slot, there may be cases where workers who can handle events that may occur cannot be secured. In such cases, an available time slot for the next most preferable device may be selected as the scheduled processing time slot, but the impact on other print requests must be considered in the same way. However, since events that may occur may differ depending on the device, there may be cases where other print requests are not affected.
[0119] Furthermore, if a large number of events are predicted to occur for a print request, or if a predetermined undesirable combination of events is predicted to occur, an order may not be placed with the factory or equipment.
[0120] Although the embodiment of the present invention has been described above, the present invention is not limited to the embodiment. For example, the order of steps in a process flow may be changed or multiple steps may be executed in parallel as long as the process result does not change.
[0121] The functional block configuration of the print order server 300 may not correspond to the program modules. The database configuration is also merely an example, and similar data may be stored in a different configuration.
[0122] Furthermore, in the first embodiment, an example is shown in which the countermeasure to an event is identified on the print order server 300 side, but a modified example is also possible in which the countermeasure to an event and the skill level of the workers who can implement the countermeasure are identified by a computer in the factory 400.
[0123] Furthermore, the print order server 300 may be implemented not by a single computer, but by multiple computers, or may be implemented on a cloud.
[0124] The print order server 300 described above is a computer device, and as shown in FIG. 9, a memory 2501, a CPU (Central Processing Unit) 2503, a hard disk drive (HDD: Hard Disk Drive) 2505, a display control unit 2507 connected to a display device 2509, a drive device 2513 for a removable disk 2511, an input device 2515, and a communication control unit 2517 for connecting to a network are connected by a bus 2519. An operating system (OS) and an application program for carrying out the processing in this embodiment are stored in the HDD 2505, and are read from the HDD 2505 to the memory 2501 when executed by the CPU 2503. The CPU 2503 controls the display control unit 2507, the communication control unit 2517, and the drive device 2513 according to the processing contents of the application program to perform a predetermined operation. Data during processing is mainly stored in the memory 2501, but may be stored in the HDD 2505. In an embodiment of the present technology, an application program for implementing the above-described processes is distributed by being stored in a computer-readable removable disk 2511, and is installed in the HDD 2505 from the drive device 2513. It may also be installed in the HDD 2505 via a network such as the Internet and a communication control unit 2517. Such a computer device realizes the various functions described above by organic cooperation between hardware such as the above-described CPU 2503 and memory 2501 and programs such as the OS and application programs.
[0125] The present embodiment described above can be summarized as follows.
[0126] The information processing method of this embodiment includes the steps of: (A) extracting, from data included in a first print request, first data relating to specific items related to events that may occur when processing the print request; and (B) predicting, from the first data and second data relating to the specific items extracted from data included in a second print request that is processed by a specific device in a specific factory prior to the first print request, an event that may occur in the specific device in the specific factory when processing the first print request.
[0127] If it is possible to predict events that may occur in a specific device in a specific factory from a print request in this way, it is possible to understand and prepare for problems that may occur when processing the print request before the print request is placed. For example, it is possible to secure appropriate workers at the factory, or to take measures such as not placing an order depending on the event.
[0128] The information processing method may further include a step of identifying a skill level of a worker capable of dealing with the predicted event or capable of executing a countermeasure against the predicted event. If the skill level of a worker capable of dealing with the predicted event can be identified, it becomes possible to manually prepare for the predicted event in advance.
[0129] Furthermore, the information processing method may further include a step of determining whether or not a worker having the specified worker's skill level is available to process the first print request while processing the first print request based on work schedule data for the specific factory, and if a worker having the specified worker's skill level is unavailable to process the first print request while processing the first print request, setting the specific factory to relatively lower its priority as an order recipient for the first print request. By relatively lowering the priority of factories and devices that may not be able to properly handle the event so that orders are not placed, it is possible to place orders with factories and devices that can reliably process the print request.
[0130] Furthermore, the information processing method may further include a step of sending a notification to a maintenance company when the predicted event or the countermeasure for the predicted event is an event that is handled by a maintenance company of a particular printing device or a countermeasure that the maintenance company will carry out, allowing the maintenance company to prepare for the occurrence of an event earlier than the occurrence of a warning sign in the device.
[0131] Furthermore, the notification to the maintenance company may include at least a part of the first data and the second data, which allows the maintenance company to analyze the event.
[0132] Furthermore, the information processing method may further include a step of outputting, to a computer in a specific factory, an output requesting that a worker having the skill level of the identified worker be assigned to the first print request, if the predicted event or the countermeasure for the predicted event is an event that is handled by a worker in a specific factory where a specific device is installed or a countermeasure that is executed by a worker in the specific factory. By mandating that the specific factory be assigned a worker having a sufficient skill level, stable processing of print requests is expected.
[0133] The output may include at least one of the contents of the predicted event and the contents of the countermeasure against the event, which allows the factory to make sufficient preparations in advance.
[0134] Furthermore, the above information processing method may further include a step of determining whether a worker having the skill level of the identified worker is available to process the first print request while processing the first print request based on work schedule data for the specific factory, and if a worker having the skill level of the identified worker is unable to process the first print request while processing the first print request, a step of determining whether it is possible to rearrange the processing order of the first print request or to process the first print request on another device in the specific factory, and a step of relatively lowering the priority ranking of the specific factory as a recipient of the first print request if it is impossible to rearrange the processing order of the first print request or to process the first print request on another device in the specific factory.
[0135] It is possible to create a program for causing a computer to execute the above-mentioned processes, and the program is stored in a computer-readable storage medium or storage device, such as a flexible disk, an optical disk such as a CD-ROM, a magneto-optical disk, a semiconductor memory (e.g., a ROM), a hard disk, etc. Data during processing is temporarily stored in a storage device such as a RAM. [Explanation of symbols]
[0136] 310 Data collection section 311 Basic data DB 312 Order processing section 313 Preprocessing section 314 Analysis section 315 Analysis result DB 316 Actual Event DB 317 Actual Response DB 318 First learning processing unit 319 Prediction unit 321 Prediction result DB 322 event processing unit 323 second learning processing unit 324 Instruction response DB 325 Output processing section
Claims
1. extracting, from data included in the first print request, first data relating to a predetermined item related to an event that may occur when processing the print request; a step of predicting an event that may occur in a specific device in a specific factory when the first print request is processed, based on the first data and second data relating to the predetermined item, the second data being extracted from data included in a second print request that is processed by a specific device in a specific factory prior to the first print request; Identifying a skill level of personnel capable of dealing with the predicted event or capable of implementing a remedy for the predicted event; determining whether an operator having the identified operator skill level is available to process the first print request while processing the first print request based on work schedule data for the particular plant; a step of setting the specific factory to have a relatively lower priority as a supplier of the first print request if a worker having the specified worker skill level is unable to engage in processing the first print request while processing the first print request; and a computer-implemented information processing method.
2. extracting, from data included in the first print request, first data relating to a predetermined item related to an event that may occur when processing the print request; a step of predicting an event that may occur in a specific device in a specific factory when the first print request is processed, based on the first data and second data relating to the predetermined item, the second data being extracted from data included in a second print request that is processed by a specific device in a specific factory prior to the first print request; Identifying a skill level of personnel capable of dealing with the predicted event or capable of implementing a remedy for the predicted event; determining whether an operator having the identified operator skill level is available to process the first print request while processing the first print request based on work schedule data for the particular factory; if an operator having the identified operator skill level is unavailable to process the first print request while the first print request is being processed, determining whether it is possible to change the processing order of the first print request or to process the first print request on another device in the specific factory; a step of relatively lowering the priority of the specific factory as a supplier of the first print request when it is impossible to change the processing order of the first print request or when it is impossible to process the first print request in another device in the specific factory; and a computer-implemented information processing method.
3. The predetermined items include metadata of objects included in the print data.
3. The information processing method according to claim 1 or 2.
4. sending a notification to a maintenance company when the predicted event or the countermeasure for the predicted event is an event that is handled by a maintenance company of the specific device or a countermeasure that the maintenance company will execute; The information processing method according to claim 1 or 2, further comprising:
5. The notification addressed to the maintenance company includes at least a part of the first data and the second data.
5. The information processing method according to claim 4.
6. outputting, to a computer in the specific factory, an output requesting that a worker having the specified skill level of the worker be assigned to the first print request, if the predicted event or the countermeasure against the predicted event is an event that is handled by a worker in the specific factory in which the specific device is installed or a countermeasure that is executed by a worker in the specific factory; The information processing method according to claim 1 , further comprising:
7. The output includes at least one of the contents of the predicted event and the contents of a method of dealing with the event.
7. The information processing method according to claim 6.
8. 8. A program for causing a computer to execute the information processing method according to claim 1.
9. means for extracting, from data included in the first print request, first data relating to a predetermined item related to an event that may occur when processing the print request; a means for predicting an event that may occur in a specific device in a specific factory when the first print request is processed, based on the first data and second data relating to the predetermined item, the second data being extracted from data included in a second print request that is processed by a specific device in a specific factory prior to the first print request; means for identifying a skill level of personnel capable of dealing with the predicted event or capable of implementing a remedy for the predicted event; means for determining whether a worker having the identified worker skill level is available to process the first print request while processing the first print request based on work schedule data for the specific factory; a means for relatively lowering the priority of the specific factory as a supplier of the first print request when a worker having the specified skill level of the worker is unable to engage in processing the first print request while processing the first print request; An information processing device having the above configuration.
10. means for extracting, from data included in the first print request, first data relating to a predetermined item related to an event that may occur when processing the print request; a means for predicting an event that may occur in a specific device in a specific factory when the first print request is processed, based on the first data and second data relating to the predetermined item, the second data being extracted from data included in a second print request that is processed by a specific device in a specific factory prior to the first print request; means for identifying a skill level of personnel capable of dealing with the predicted event or capable of implementing a remedy for the predicted event; means for determining whether a worker having the identified worker skill level is available to process the first print request while processing the first print request based on work schedule data for the specific factory; a means for determining whether or not it is possible to change the order of processing the first print request or to process the first print request in another device in the specific factory when a worker having the specified skill level of the worker is unable to engage in processing the first print request while processing the first print request; a means for changing the order of processing the first print request or, if it is impossible to process the first print request in another device in the specific factory, for relatively lowering the priority of the specific factory as a supplier of the first print request; An information processing device having the above configuration.
Citation Information
Patent Citations
Status information notification system, status information notification server, status information notification device, status information notification program, status information notification method
JP2005032231A
Image forming apparatus, image forming system, image forming job management method and program
JP2011197835A
Maintenance management apparatus and program
JP2015215690A
Image forming apparatus and program
JP2019036877A
Print order reception / placement management system, print order reception / placement server, print order reception / placement management method and program
JP2020024691A
