System and method for marking substrate with improved line recovery time
By receiving and classifying printer sensor data, and determining the self-repair or backup replacement process based on the estimated repair time, the production downtime problem caused by industrial printer failure is solved and the rapid recovery of the production line is achieved.
Patent Information
- Application Number
- CN202080043186.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-06-13
- Filing Date
- 2020-06-12
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2040-06-12
AI Technical Summary
Production downtime caused by industrial printer failure has had a serious impact on medium to large customers, and it is difficult for the existing technology to effectively shorten the line recovery time.
By receiving sensor data associated with the tag and/or encoding device, the classification module uses the classification module to classify the fault conditions based on the received data, and decide whether to perform the self-repair recovery process based on the estimated repair time and line recovery time threshold. It is recommended to use self-repair recovery. Or standby replacement process.
It is realized that the self-repair or standby replacement process is automatically determined and performed without exceeding the predetermined line recovery time threshold, which significantly shortens the recovery time of the production line and reduces downtime losses.
Smart Images

Figure CN114007846B_ABST
Abstract
Description
Background Art
[0001] Embodiments are directed to a system and method for minimizing, improving and monitoring production line recovery time in response to detected failures of marking and encoding equipment.
[0002] Production downtime due to industrial printer failures (malfunctions that prevent the printer from printing) primarily affects medium to large customers due to various reasons such as limited excess capacity in 24×7 operations, regulated products such as in pharmaceuticals, and spoiled products such as in dairy products. Summary of the invention
[0003] Embodiments relate to systems and methods for improving line restoration time. A method includes receiving sensor data associated with a marking and / or encoding device. The method includes classifying, by a classification module, a fault condition based on one or more of the received sensor data, device self-test data, current operating data, and historical device condition data. The method includes autonomously determining a repair process recommendation for a non-operating, non-encoding, and / or non-marked device based on an estimated time to repair (ETR) relative to a line restoration time (LRT) threshold using a self-repair recovery process in response to the classified fault condition. The method includes recommending, by at least one processor, a self-repair recovery process in response to the ETR being less than or equal to the LRT threshold.
[0004] A system includes a plurality of devices and a computing system coupled to the devices and having at least one processor, the at least one processor being configured to: receive sensor data associated with each device. The at least one processor is configured to receive sensor data associated with each of the plurality of devices and store device metadata and batch job metadata in a backup file for each device. The at least one processor is configured to classify a fault condition of a corresponding one of the devices by a classification module based on one or more of the received sensor data, printer self-test data, current operation data, and historical device status data. The processor is configured to autonomously determine a repair process recommendation for the inoperative device using a self-repair recovery process relative to a line restoration time (LRT) threshold in response to the classified fault condition and based on an estimated time to repair (ETR). The processor is configured to recommend, by the at least one processor, a self-repair recovery process as a repair process recommendation in response to the ETR being less than or equal to the LRT threshold. BRIEF DESCRIPTION OF THE DRAWINGS
[0005] A more particular description, briefly stated above, will be rendered by reference to specific embodiments thereof illustrated in the accompanying drawings. Understanding that these drawings depict only typical embodiments and are not therefore to be considered limiting of its scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:
[0006] Figure 1 illustrates a block diagram of a system for marking a substrate with an improved line restoration time (LRT);
[0007] Figure 2A illustrates a block diagram of a Line Restoration and Time Estimator (LR&TE) engine;
[0008] Figure 2B illustrates a block diagram of a line restoration time estimator submodule;
[0009] Figure 3A illustrates a block diagram of a recovery edge server;
[0010] Figure 3B A block diagram illustrating a process flow for a classifier module is shown;
[0011] Figure 4 illustrates a flow chart of a process for backing up printer and batch job metadata based on a service level;
[0012] Figure 5 illustrates a flow chart of a process for determining whether a self-repair process or an alternate replacement process is recommended;
[0013] Figure 6 illustrates a flow chart for a process of selecting a repair option for a user;
[0014] Figure 7 A flow chart illustrating a process for installing a spare part with a printer copy is shown;
[0015] Figure 8 illustrates a flow chart of a process for reporting line restoration time statistics;
[0016] Figures 9A-9H illustrates a graphical user interface for performing a self-repair process;
[0017] Fig.10 A flow chart illustrating a process or method for self-repair;
[0018] Figures 11A-11B illustrates a graphical user interface for displaying reports; and
[0019] Fig.12 A block diagram of a computing system is illustrated. DETAILED DESCRIPTION
[0020] Embodiments are described herein with reference to the accompanying drawings, wherein the same reference numerals are used throughout the accompanying drawings to represent similar or equivalent elements. The accompanying drawings are not drawn to scale, and they are provided only to illustrate the aspects disclosed herein. Several disclosed aspects are described below with reference to non-limiting example applications for illustration. It should be understood that many specific details, relationships, and methods are set forth to provide a comprehensive understanding of the embodiments disclosed herein. However, a person of ordinary skill in the relevant art will readily recognize that the disclosed embodiments can be implemented without one or more of the specific details or using other methods. In other cases, known structures or operations are not shown in detail to avoid blurring the aspects disclosed herein. The embodiments are not limited by the order of the actions or events illustrated, because some actions can occur in different orders and / or simultaneously with other actions or events. In addition, not all illustrated actions or events are necessary to implement the method according to the embodiment.
[0021] Although the numerical ranges and parameters of the wide ranges are approximate, the numerical values set forth in the specific non-limiting examples are reported as accurately as possible. However, any numerical value inherently contains a certain error, which is necessarily caused by the standard deviation found in their corresponding test measurements. In addition, all ranges disclosed herein are to be understood to include any and all subranges contained therein. For example, a range of "less than 10" may include any and all subranges between (and including) a minimum value of zero and a maximum value of 10, that is, any and all subranges with a minimum value equal to or greater than zero and a maximum value equal to or less than 10, such as 1 to 4.
[0022] Although the present invention is described with reference to an industrial printer such as a continuous inkjet printer, the present invention is not limited thereto but includes a variety of marking and / or encoding devices such as laser marking devices, thermal transfer overprinters (TTO), thermal inkjet printers (TIJ), continuous inkjet printers (CIJ), label encoding machines, and the like.
[0023] The following terms are defined below.
[0024] Remote Monitoring Service (RMS): A cloud-based solution that enables remote monitoring through email alerts, diagnostics, repairs, and is available to both corporate technical support and customer maintenance teams.
[0025] Warning: A condition that the user should be aware of and can correct but will not stop the printer from operating.
[0026] Self-Repairable: A printer failure that can be resolved by an operator / technician with or without remote assistance in less than a predetermined Line Restoration Time (LRT) threshold, with or without parts replacement. For example, the predetermined LRT threshold may be 20 minutes. The failure / failure is resolved, where the same failure / failure will not reoccur for at least a 24-hour period.
[0027] Classifier: A cloud-based analytical tool that identifies whether a printer failure is self-repairable or whether a replacement printer needs to be deployed. The cloud-based analytical tool can use machine learning techniques to classify self-repairable failures.
[0028] Remote Edge Server (RES): A network computing device placed at a customer site that collects printer data from one or more printers and delivers it to the cloud.
[0029] Actual Line Recovery Time (LRT): The actual time to resume production from a printer failure / failure that is at or below a pre-defined LRT threshold. Actual LRT is measured from the time the customer confirms the failure until the printer is back online and printing.
[0030] Accelerated Printer Recovery (APR): A process by which the system backs up a failed printer and restores the backup to a spare printer to expedite a spare swap by an operator / technician.
[0031] Backup File: A file stored on the RES that is used to replicate the functionality of a failed printer on a backup printer. The backup file content can include printer parameters, printer settings, batch job details, batch job counters, etc., which basically replicates the current printer and current batch metadata. The backup file will be limited to 1 per printer, which has the most recent (latest) update. Not limited to other storage media on the edge server.
[0032] Printer metadata: refers to, by way of non-limiting example, data associated with one or more of printer settings, ink color, serial number, printer type, printer model, printer sensors.
[0033] Batch metadata: Represents data associated with a batch job required to perform labeling of tag(s) on a substrate.
[0034] Figure 1A block diagram of a system 100 is illustrated, which is used to mark a substrate with improved line recovery time (LRT). The system 100 may include a recovery edge server (RES) 150 and one or more printers 102, 104, 106, and 108 that communicate with the RES 150 by wire or wireless communication. As can be understood, a site can have different types of printers to apply various types of markings on a variety of substrates S02, S04, S06, S06, and S08. Substrates S02 and S08 can be the same substrate, but marked by different printers. Substrate S04 can be a bottle cap type. Substrate S06 can be a paper product type substrate. The list of substrates is not intended to be limiting in any way. The substrate can include a non-porous or porous substrate, plastic, paper, foil, cardboard, glass, metal, or other material.
[0035] As non-limiting examples, printers 102, 104, 106, and 108 may be inkjet printers, continuous inkjet (CIJ) printers, laser marking devices, thermal transfer printers. Assume that printer 102 marks batch B02; printer 104 marks batch B04; printer 106 marks batch B06; and printer 108 marks batch B08. Each batch may be different, requiring each different printer to be programmed with a different batch instruction set or data.
[0036] RES 150 may include a batch job database (BJD) 160 ( Fig.12 ). The BJD 160 may include data representing one or more of a batch number 162, batch font(s) 164, batch print direction 166, batch message flag(s) 168, and entry / batch count 169. The BJD 160 may include data representing one or more of a printer model 172, a printer type 174, printer settings 176, a printer status 178, and a printer sensor reading 179.
[0037] System 100 may include one or more fault detection monitors (FDMs) 112, 114, 116, and 118. A FDM may include a sensor in the printer, where software is distributed between the printer and RES 150 or another controller, to detect a fault condition. A fault condition as used herein is a condition that prevents the printer from printing.
[0038] The system 100 may include one or more backup printers 122, 124, and 126. During operation, the printer may be configured to be monitored by internal sensors to determine the health and status of the printer. RES 150 may be configured to receive and track sensor data (not shown), as disclosed, for example, in U.S. Patent No. 9,524,132, entitled "SYSTEM AND METHOD FOR REMOTELY SERVICING AN INDUSTIAL PRINTER," issued on December 20, 2016 and assigned to Videojet Technologies, Inc. The printer may include various sensors that monitor one or more components of the printer. Some sensors are used to track the amount of printer consumables (such as, as a non-limiting example, ink and solvent). Monitoring the health or remaining useful life (RUL) of a machine is well known in the art. Some of these repairs and / or maintenance, such as replacing exhausted consumables, are required from time to time. These repairs can be scheduled. However, such maintenance activities require the printer to be offline.
[0039] For example, in some embodiments, the nozzle assembly has a temperature sensor, a jet velocity sensor, a pressure sensor, a modulation voltage sensor, a modulation current sensor, and a modulation frequency sensor.Other example assemblies and associated sensors for a continuous ink printer are possible.
[0040] For example, there may be various sensors for various components in the printhead, ink system, consumables, and electronics for detecting or determining faults or failure conditions associated with these subsystems or their components. The sensors provide information about parameters associated with the respective components. The combined information from the various sensors from the various components provides an unprecedented amount of information about the status of the various systems in the printer to allow a remote user to diagnose, predict, and / or determine potential problems, such as faults, warnings, or malfunctions, with the printer and its subsystems. The printhead (and associated electronics) may include nozzles with sensor parameters such as modulation voltage set point, modulation current, frequency, temperature, jet velocity set point, actual velocity, target pressure, temperature compensated target pressure, and actual pressure; phase sensor parameters, including selected phase, rate of change of phase, profile, and phase threshold; EHT parameters such as voltage, current, trip value, and % of trip; gutter parameters such as accumulation, time since last cleaning, warning level setting, and presence of ink in the gutter; printhead heater parameters such as set temperature, actual temperature, and drive; printhead cap parameters such as state (open or closed) and time since last removal: state of various printhead valves (open, closed, and time open or closed); nozzle parameters such as nozzle size, target velocity, serial number, date of manufacture, drop frequency, print count, run time, and drop deflection. Again, these parameters are monitored for diagnosis and determination of potential or existing faults associated with various components.
[0041] The ink system (e.g., consumables and associated electronics) may include sensors for monitoring printing operation parameters, and the associated data may be used to detect, diagnose, or determine potential problems, such as faults, warnings, or malfunctions. The sensors may be configured to monitor, for example, ink pump parameters, such as pressure, speed, current, and pump run time; ink reservoir parameters, such as ink type, ink expiration date, level (ml and / or %), remaining print time, and ink tank temperature; replenishment reservoir parameters, such as replenishment type, expiration date, replenishment vacuum, level (ml and / or %), remaining print time, and replenishment tank temperature; viscometer parameters, such as target empty time, actual empty time, density, viscosity, and fill time; ink quality parameters, such as ink conductivity; condenser parameters, such as state (open or closed), temperature, and vent valve (open or closed); filter / damper module parameters, such as ink filter pressure drop, serial number, manufacturing date , operating hours and replacement date; service module parameters such as flush pump speed, flush pump current, serial number, manufacturing date, operating hours, replacement date and information on various service module valves (open, closed and time opened or closed); cartridge parameters such as ink type, recommended replenishment type, serial number, manufacturing date, expiration date, cartridge size, fluid level, operating time, time of cartridge replacement, number of cartridges inserted, (one or more) viscosity coefficients, fluid density, number of modulation algorithms and number of cold start algorithms; replenishment cartridge parameters such as replenishment type, serial number, manufacturing date, expiration date, cartridge size, fluid level, operating time, time of cartridge replacement and number of insertions. Other printer parameters include air filter parameters such as last replacement date, operating hours and replacement date; smoke / gas sensors in the printer cabinet; humidity sensors in the printer or for environmental measurements; main control board parameters such as time and date, electronics temperature, HV voltage, HV current and voltages of various other power supplies in the electronics.
[0042] There are other faults that may be detected by sensors due to reasons other than exhaustion of consumables. Some components of the printer may require maintenance based on time intervals or number of operations, which may require the printer to be placed offline. Especially for industrial complexes, at least one technician may be available to perform maintenance tasks. In other cases, remote repair via a remote monitoring service (RMS) platform may assist in some repairs. As a non-limiting example, U.S. Patent No. 9,524,132 also describes an example of a remote monitoring service (RMS) platform to help remotely repair and / or maintain a printer.
[0043] Applicants have found that up to 80% of faults or fault conditions are associated with ink system operating parameters, particularly with the replenishment reservoir (replenishment reservoir failure) and printhead operating parameters, and particularly with the gutter (gutter failure) and EHT (EHT failure).
[0044] Figure 2A 1 illustrates a block diagram of a line restoration and time estimator (LR&TE) engine 200A. The LR&TE engine 200A may include program code instructions that, when executed, cause the system to determine a fault condition among a plurality of fault conditions based on real-time sensor data derived from sensors of a corresponding one of the operating printers. The fault condition may be based on historical sensor data for a particular printer model / type. The fault condition may also be based on the age of the printer.
[0045] The engine 200A may include a fault condition determination module 240, which may query a database 202 of fault conditions, such as fault condition 1 F01, fault condition 2 F02, fault condition 3 F03, fault condition 4 F04, ..., fault condition X F0X. Each fault condition may have associated therewith a repair sequence (RS) and an estimated time to repair (ETR) for repairing the fault / failure. Thus, fault condition 1 F01 has a repair sequence 1 RS01 and an associated estimated time to repair 1 ETR01. Accordingly, fault condition 2 F02 has a repair sequence 2 RS02 and an associated estimated time to repair 2 ETR02. Fault condition 3 F03 has a repair sequence 3 RS03 and an associated estimated time to repair 3 ETR03. Fault condition 4 F04 has a repair sequence 4 RS04 and an associated estimated time to repair 4 ETR04. Fault condition X F0X has a repair sequence X RS0X and an associated estimated time to repair X ETR0X. The estimated time to repair may be a learned value based on historical data. The estimated time to repair (ETR) is a function of the downtime of the printer. When the printer is down, the printer cannot print. It is assumed that in some embodiments, self-repair may occur substantially immediately.
[0046] Also refer to Figure 2B , which illustrates a block diagram of the LR&TE submodule 250. The submodule 250 is Figure 2AThe row 210 in the database 202 of the engine 200A is shown. For each fault condition, such as fault condition 1 F01, the repair sequence 1 RS01 allows the printer to repair itself without having to replace the entire printer. In the illustrated example, it is assumed that the printer 102 has a display device 203, which has a screen 205. The repair sequence 1 RS01 includes a plurality of instruction sets 221A, 221B, and 221C (displayed as a graphical user interface) Figures 9A-9H ). Each instruction set 221A, 221B, and 221C is displayed separately and continuously on screen 205 to provide instructions to a technician or user and prompt the user when the instructions associated with those on the screen are completed. The term "row" is used herein to represent elements that are linked together. Although the description herein provides a single database 202, database 202 may include multiple databases. For example, each row may be a separate database. Alternatively, each column may be a separate database, each of which is appropriately linked.
[0047] The engine 200A may estimate the time to complete the instructions of the instruction set 221A, where each instruction set may have a repair screen associated with a repair screen estimated time to complete (ETOC) 1. Similarly, the engine 200A may estimate the time to complete the instructions of the instruction set 221B with a repair screen estimated time to complete (ETOC) 2. The engine 200A may estimate the time to complete the instructions of the instruction set 221C with a repair screen estimated time to complete (ETOC) 3. The instruction sets may be interactive repair instructions that require input by the technician and are displayed before the next instruction set. During the interactive repair instructions, the engine may track the actual time required for the technician to complete the repair for the particular instruction set on a particular screen. This may be used to update or train the estimated time to repair.
[0048] RES 150 may be coupled directly or indirectly to a cloud or cloud engine. The cloud may include data from database 202. Cloud 280 may be updated with actual repair time 1 (ATR01) so that estimated repair time may be trained and updated. ATR01 may be a function of the time to complete a repair sequence. ATR01 is a function of the actual time to complete (ATOC) corresponding to the completed instruction or the cumulative time of the progress time to complete each screen. In this example, ATOC is a function of the actual time to complete 1 (ATOC1) of the repair instruction for the first repair screen, the actual time to complete 2 (ATOC2) of the repair instruction for the second repair screen, and the actual time to complete 3 (ATOC3) of the repair instruction for the third repair screen. The number of screens may vary. However, for illustrative purposes, only three repair screens are shown. Cloud 280 may receive data for report maintenance, as will be described below with respect to Fig.11A and 11BThe cloud 280 may be a remote monitoring service (RMS) cloud.
[0049] Figure 3A A block diagram of a recovery edge server (RES) 150 is illustrated. The recovery server may be a network server coupled to a network having a plurality of printers coupled to the network. RES 150 may include one or more of the following: a printer fault detector module (FDM) 305; a printer fault classifier module 310; a fault self-repair ETOC training module 315; a fault self-repair feedback module 320; a printer resource management module 330; a printer backup file copy 335; a fault printer copy module 340; (one or more) batch jobs 360; a repair statistics and mean time between failures tracker module 380; and a reporting module 385. The present invention is not limited to the use of edge servers, and other data backup devices may be used to store backup data.
[0050] RES 150 may be coupled to a historical printer status data (HPCD) database(s) 302. HPCD database 302 may store data associated with the historical status of a printer, such as Figure 3B RES 150 may include a historical repair / timing data (HRTD) database 303. HRTD may include historical metrics for other operators of the same printer type and condition. HRTD may include timing data based on the success of a repair.
[0051] The RES 150 may include a repair procedure recommendation module 325 configured to autonomously determine a repair procedure recommendation in response to the classified fault condition and based on an estimated time to repair (ETR) for a non-printing (faulty) printer using a self-healing recovery process relative to a line restoration time (LRT) threshold. The recommendation may be provided to an operator or technician using a graphical user interface. The repair procedure recommendation of the self-healing recovery process may be responsive to an ETR less than or equal to the LRT threshold.
[0052] One or more of the modules may be distributed among one or more computing devices, network servers (i.e., RES 150), cloud 280, and / or printers. Printer Fault Detector Module (FDM) 305 is configured to determine a fault with the printer based on internal sensors or other status indicators within the printer. Printer Fault Classifier Module 310 may use current sensor data to determine a fault condition, such as Figure 2A This information is described below. Figure 5 The method 500 is used. The ETOC is used to recommend to the operator or technician whether to replace the failed printer with a spare part or recommend a self-repair process. The classifier module 310 can determine the current state of the printer plus the historical data from the cloud storage device.
[0053] The fault self-repair ETOC training module 315 will receive feedback from the fault self-repair feedback module 320 based on the operator's or technician's interaction during the repair process of the faulty printer. The feedback can also determine data indicating the successful completion of the repair. The ETOC training module 315 will train the repair module to improve the accuracy in the line recovery time. For example, if the repair is unsuccessful within the allocated time, the self-repair process may not be recommended in the future. Alternatively, the self-repair process can be modified to reduce the allocated time while being able to complete the self-repair using a technician.
[0054] For training purposes, the fault self-repair feedback module 320 tracks the interactions during the self-repair process. The printer resource management module 325 can track and identify all printers in the site, or those printers that are particularly coupled to RES 150 or managed by RES 150. For example, some spare printers can be tracked by RES 150 and are provided with an offline or idle state. In other cases, the spare printer may not communicate with RES 150. In other cases, the online operating printer may have an offline state. However, if a batch job is printed in use, the operating printer is not considered as a spare part. In some embodiments, a communication representing a list of compatible spare printers that may be available on site can be sent to a technician or operator. A customer site may have multiple buildings. As can be understood from the description herein, spare printers in buildings of customers in different cities, states, and countries may not be used as "spare parts" because the time to obtain the spare printer may exceed the LRT threshold.
[0055] The printer backup file copy 335 is an up-to-date file of printer settings and batch job settings and counters. The printer backup file copy 335 may be an up-to-date copy of printer metadata. The term "printer metadata" means the current settings, counters, font type, etc., used for the current batch job. In some cases, when a backup printer is brought online, the Internet Protocol (IP) address may not be copied or replicated. One reason for backing up printer metadata and batch job metadata is that it may be time consuming to enter print information and batch job information back into the backup printer. The data may include batch codes, counter expiration dates, fonts, print direction (i.e., left to right), and other instructions for applying symbols and / or alphanumeric characters representing indicia.
[0056] The faulty printer duplication module 340 can be configured to duplicate the metadata of the failed printer on the backup printer so that the backup printer can pick up exactly where the failed printer stopped. In some cases, this will eliminate waste. The backup printer can start printing the exact next batch number without having to search and find a match in the count of the backup printer. Using the faulty printer duplication module 340 can allow the operator to find a backup file in the file storage and download the backup file to the backup printer. The faulty printer duplication module 340 can be configured to configure the backup printer by downloading the stored printer metadata and batch job metadata to duplicate the failed printer by the backup printer.
[0057] The batch job(s) 360 are stored and tracked by the RES 150 and / or the cloud 280, including starting and ending the batch job according to metadata or settings. The mean time between failures tracker module 380 can determine the mean time between failures, and in particular the mean time between failures of self-repairing printers. Some repairs are patches that have an expected short time between failures. Other self-repairs can be performed based on an expected duration (meaning time between failures) within which the repair will last. Some self-repairs can be selected in a manner that can extend the expected time to the next failure before a full repair or full repair may be completed.
[0058] The reporting module 385 may allow an operator or technician to view metrics associated with using self-healing to scale batch job operations. Some batch jobs include products with expiration dates that may cause the products to spoil if there are long delays in the labeling process. An example report is shown in Figures 11A-11B Shown in.
[0059] Figure 3B A block diagram of a flow process for a printer fault self-healing classifier module 310 is illustrated. Prior to discussing the training of the classifier module, additional operations of the printers (i.e., printers 102, 104, 106, and 108) will be described. As a non-limiting example, each printer may include a condition estimator 390, which may include (one or more) operating parameter collectors 392. Some operating parameters may be determined based on certain electrical signals, differences in specific electrical signals, and / or the absence of specific electrical signals. As a non-limiting example, some components including wiring, short circuits, and accidental opens may affect the value of the electrical signals. Therefore, fluctuations in the electrical signals may be the basis of the fault condition, rather than just the sensor data.
[0060] The printer's condition estimator 390 may include a printer self-test module 394 configured to perform diagnostic self-tests on its components to determine the condition of one or more printer components. The self-test module 394 may generate self-test data for use by the classification module 310 to evaluate with other data to determine the current fault condition. The printer's condition estimator 390 may include one or more printer sensors 396 to generate sensor data. The sensor data may be transmitted to the classifier module 310 for use in classifying the current fault condition.
[0061] The condition estimator data, such as sensor data, self-test data, and / or other operating parameters, may be used by the classifier module 310 in conjunction with historical printer condition data (HPCD) (one or more) in the database 302. The data may be processed by the classifier module 310 to determine a condition of the printer, such as a failure of the printer that may have caused the printer to stop printing. The HPCD may include historical data associated with the printer, including, but not limited to, past component repairs, past failures, and past consumable replacements.
[0062] Printer components have useful lives. Thus, the HPCD may maintain or track the current age or remaining useful life of specific components of an instant printer. The HPCD may maintain and / or track the number of consumable printer components such as inks and solvents. The HPCD may maintain and / or track the time to or between the next cleaning cycle or service cycle for the current printer. The HPCD may include data associated with past fault conditions and estimated time to repair (ETR).
[0063] A repair may have a time function associated with it that is tracked. Tracking time may be used to change future recommendations. Data from the historical repair / timing data (HRTD) database 303 may be used by a classifier module to determine whether a repair can be repaired within a certain time interval. The repair time in the HRTD database 303 may be based on a time metric that includes one or more of the following: a standard for the repair task time; an amount of time for the repair task to be deterministic; and a repair task uncertainty time. Each repair task may be a function of one of these time metrics. The total repair time to complete the self-repair process may include multiple repair tasks, each of which may have a time metric selected from the following: at least a standard for the repair task time; an amount of time for the repair task to be deterministic; and a repair task uncertainty time. The self-repair process will typically include repair tasks of different time metrics, which will be tabulated to determine the estimated time to repair (ETR).
[0064] Assume that a user can be instructed to perform a first repair task using a GUI to provide instructions and interactions to determine when the task is completed. Assume that the first repair task has a time metric with a standard for the repair task time. The RES maintains the standard for the determined time for the user / operator to perform the first repair task. The system can determine whether the user / operator actually performed the function within the predetermined time standard. The GUI can be used as a user interface to log when the task is completed so that the actual repair time is tracked.
[0065] The system can track the amount of time a user / operator takes to complete a repair task. The actual time can include a standard for the time. In some cases, any excess in the standard for the time may be due to an operational delay. The RES can also track the total time used for the repair task to determine whether the standard time allocation for the time can be adjusted for future repairs. The RES can track the task completion delay time interval, such as for printer types, sites, and / or operators. As a non-limiting example, any delay in completion causes the standard for the time to be exceeded, and it can be determined whether the delay is due to the operator. For example, the delay may be based on the operator being called away from the task or other external influences. For example, the operator may stop the repair process and go to lunch. Nevertheless, there are other reasons that cause the operator to be called away from the current repair task, which may cause the actual time to exceed the expected time. Therefore, in some cases, the actual repair time may be voided or adjusted so that the training of the classifier is not trained with defective data or unresponsive data. Unresponsive data can be used to define those times when the operator may not respond within the standard of the time to complete the repair task for any reason except performing the current repair task as expected or according to the standard / rule of the operation.
[0066] Alternatively, the delay may be printer based.For reporting module 385, the RES system can track the criteria, any deviations and reasons for the time, so that if the repair task cannot be completed within a specific time, the system can stop making such recommendations if the time for the repair is outside the established criteria and thresholds.
[0067] The printer may perform operations associated with a repair task that has a deterministic time interval based on the operation of the printer. As a non-limiting example, certain printer automation actions or tasks may have a deterministic time interval for completion. Deterministic time interfaces are inherently machine-specific and may not be a function of human interaction.
[0068] The printer may perform operations associated with repairs that have non-deterministic time intervals. In other words, some repair tasks have a time metric that is a function of the non-deterministic time intervals based on the printer automation. Some repair tasks have a time metric that is a function of both deterministic time intervals and non-deterministic time intervals based on the printer automation.
[0069] The classifier module may be trained based on whether a recommended repair procedure was successful, where the classifier module is trained on which recommended repair procedures were unsuccessful. The classifier module may be trained on whether a generated recommendation was not followed and the resulting result resulted in a successful repair within an expected time to repair or LTR threshold. For example, if the recommendation is to replace the printer with a spare part, but the operator selects a self-repair, and such self-repair is performed at or below a line restoration time (LRT) threshold, the RES will track such success to train the classifier module and for consideration of future repair procedure recommendations.
[0070] The RES may use the data to adjust criteria for time, deterministic time intervals, and non-deterministic time interval estimates and / or train classifier modules.
[0071] The RES can use the data in the HRTD database 303 to generate reports to administrators or operators to show customers the fault LRT savings, operator performance, printer performance, and / or revenue impact. The revenue impact can be a function of the amount of time that the printer is in a fault condition or not printing. The revenue impact can include an estimated time required for the next repair that will require the printer to be in a non-printing state or fault condition. As a non-limiting example, the revenue impact can include an amount of money lost based on delays in printing certain surfaces associated with consumables or data-sensitive products.
[0072] The methods described herein may be performed in the order shown or in a different order. One or more of the blocks may be omitted, skipped, or performed simultaneously. Blocks may be added.
[0073] Figure 4 A flow chart of a process or method 400 for backing up printer and batch job metadata based on a level of service is illustrated. The method 400 may include, at block 402, confirming whether a valid service contract with LRT entitlement exists for the printer in order to activate the capability. The method 400 may include, at block 404, automatically generating and storing backup files in the RES 150 and / or the cloud 280 via the printer backup file copy 335 (for each printer with LRT entitlement). LRT entitlements are service contracts that provide repair services to improve line recovery time.
[0074] The method 400 may include, at block 406, updating the stored backup file each time a setting / parameter affecting print output is modified. As a non-limiting example, the RES 150 should be able to support backup files for 1 to 50 printers without any performance degradation.
[0075] Figure 5 A flow chart of a process or method 500 for determining whether to perform a self-repair process or an alternate replacement process is illustrated. The method 500 may include, at box 502, determining that a printer failure has occurred. If the determination is "no", the method 500 loops back to the beginning. If the determination is "yes", the method may proceed to box 504. A printer failure may be caused by a printer failure that prevents the printer from printing / marking and shutting down. If a failure exists, the method 500 may include, at box 504, determining whether the failure is self-repairable. At box 504, the determination may be a function of a predefined LRT threshold relative to an estimated time to repair (i.e., ETR01) for a particular failure (i.e., fault condition F01). If the determination is "no", the method 500 may recommend an alternate printer replacement at box 506. About Figure 6 The alternate printer replacement process is described. The recommendation may be delivered via a text message, a message on the printer screen, or other display screen of the electronic device. If the determination is "yes," the method 500 recommends a self-repair process at block 508. Figure 8 and 9A -9H describes the self-healing process.
[0076] Figure 6 A flow chart of a process or method 600 for a user to select a repair option is illustrated. The method 600 may include, at block 602, causing a message (such as a fault message) to be displayed on the printer screen 205 to replace the printer with an available spare printer ( Figure 1 A). In some embodiments, for example, if self-repair does not result in resumption of production in less than 20 minutes or other LRT threshold, the process may recommend a spare replacement. This may be indicated in a fault message at the printer with notification of the failure and a recommendation to deploy a spare printer (driven by the classifier module output). The operator may acknowledge the failure and may proceed with spare part deployment or choose to attempt the repair themselves. The options may be provided in the form of a message and selection means (button, key, touch screen button or label).
[0077] The method 600 may include, at block 604, determining whether the operator chooses to attempt to repair the printer. At block 606, the selection, success, or failure is recorded in the RMS cloud for reporting purposes. Success may include repair of the printer, which may now print, but may then ensue a warning state. The method 600 may include, at block 608, determining whether the operator chooses to deploy a spare part with accelerated printer recovery (APR) functionality (in the event that self-repair is unsuccessful).
[0078] The method 600 may include, at block 610, if the operator selects to deploy the spare part, triggering a technical support (TS) case by creating a TS case in the system or remote repair system, and the TS case will contain a direct link (Internet, intranet, or Ethernet) to a remote monitoring service (RMS) dashboard of the printer. The TS case is automatically created with a TS case number provided to the operator as a reference.
[0079] The method 600 may include, at block 612, automatically capturing key parameters and settings (metadata) and updating the RES backup file. The backup file may be easily identifiable by an operator.
[0080] Figure 7 A flow chart of a process or method 700 for installing a spare part with a printer copy is illustrated. The method 700 may include, at block 702, performing a backup process configured to save key meta information (metadata), such as a serial number, a friendly name, a model number, a date and time of the backup (as defined by a "backup file" content document). In some embodiments, the LRT process may be part of a level of repair service contract. As a non-limiting example, the level of repair service contract may be important for sensitive or perishable materials. Thus, block 702 may be used Figure 4 frame replacement.
[0081] The method 700 may include, at block 704, notifying the operator of the progress of the backup and upon successful completion. The progress may be displayed on a computer screen, a printer screen, a mobile computing device, or other screen of a computing device.
[0082] The method 700 may include, at block 706, installing the spare unit on the line and identifying and selecting an appropriate recovery file from a list of available files in a recovery menu. The installation may be done with the assistance of an operator or a technician.
[0083] The method 700 may include, at block 708, graying out the recovery menu with instructions to check the line or Wi-Fi connection on the printer if no network connection is sensed. The method 700 may include, at block 710, providing additional instructions to the operator to follow a standard manual replacement process if the connection problem persists.
[0084] The method 700 may include, at block 712, providing a progress message (instructions) including successful completion of the recovery when the recovery file is selected. The method 700 may include, at block 714, placing (by an operator) the standby printer in a printing mode. For example, a failed printer may be set aside for an on-site visit by a field service engineer. The printer may be shipped off-site for repair.
[0085] Each diagnostic screen may provide self-guided instructions to repair or fix a failed printer. A fault as used herein causes the printer to go offline from printer mode. When a fault occurs, the system will look up a table to determine whether the fault is determined by the classifier module 310 based on real-time sensor data for the sensed fault condition. The condition may include more than one fault, so that the fault condition is a multiple fault condition. The classifier module 310 may determine whether the fault condition is suitable for self-repair or not. Not all faults are classified. Some faults will never be self-repairable. Therefore, the need to replace the printer with a spare part can be identified early in the process. For example, the classifier module 310 may not classify faults associated with consumable failures for refilling ink or solvent.
[0086] The benefits of embodiments herein can be used to allow the voice of the customer to be heard in order to address the impact of a failed printer on daily operations. The recommendation to self-repair or not may depend on the success rate of the specific self-repair process and / or printer. Spare part replacement can be used for 24 / 7 operations and / or operations that mark perishable items. In addition to the cost of printer repair, printer downtime can be very costly. A perishable item that is not processed / marked for an hour is lost forever and can never be recovered.
[0087] Although the printer may still provide a warning signal, instructions for continuing to recover the printer can be provided so that the mean time between failures or repairs is reduced. Instead of clearing the fault, repairs can be continued. Embodiments herein can reduce line recovery time and eliminate uncertainty about what is required when a printer fails.
[0088] Self-healing process
[0089] Figure 8A flow chart of a process or method 800 for self-repair is illustrated. As an operator, when a self-repairable printer fault occurs, the method 800 may include, at box 802, being notified of the fault via a message on the printer screen and providing an instruction set to complete the repair within 20 minutes or below the LRT threshold. This will be implemented at the printer itself. The fault message will provide notification of the failure and a suggestion for self-repair (driven by the classifier module output). For example, the fault message will display "Printer Failure Self-Repairable" and will give the operator a preview of the steps required to complete the self-repair, as well as the option to perform the self-repair or deploy spare parts instead. If there are multiple faults to be repaired by the self-repair process, the operator will be aware of the multiple faults.
[0090] If the operator chooses to deploy a backup printer, they can do Figure 7 One or more blocks of method 700 in . If the operator chooses to complete the self-repair, he will have the option of following the repair instructions on the printer screen or contacting technical support via telephone for step-by-step instructions. The operator should have the option of stopping the self-repair and performing spare parts deployment throughout the process.
[0091] If the operator selects the guided option through technical support, the operator is provided with the local technical support phone number via the printer screen. A TS case is automatically generated in the system with the customer account and site information from RMS, and the standard work to repair the printer. The customer can call technical support to get guided support. The technical support engineer assists the customer in resolving the issue. The technical support engineer closes the TS case with feedback on the usefulness of the standard work to help improve the classifier module.
[0092] At box 804, if the operator chooses to perform self-repair on his own, he can access step-by-step instructions on the printer screen. The instructions can be downloaded in real time, or the screen can be pre-stored in the printer's memory. The instructions can be stored in RES 150 or cloud 280. The operator attempts self-repair. During the repair, at box 806, the system, RES 150 and / or printer captures the time to complete the (one or more) tasks or (one or more) repairs associated with the screen. The system can track whether the repair for the screen is successful before switching to the next screen. At box 808, the process will fail or succeed. Record, such as in the cloud, for reporting purposes and / or training purposes. The classifier module can be updated or trained, such as if the time to complete the repair is longer than expected. If the self-repair is successful, then at box 810, the system can end the repair / support process and resume the batch marking operation of the printer.
[0093] The operator may have the opportunity to provide feedback to the classifier module.
[0094] Figures 9A-9HGraphical user interfaces (repair screens) 900A, 900B, 900C, 900D, 900E, 900F, 900G, and 900H are illustrated for performing a self-repair process. Figures 9A-9H is a series of repair screens for a self-healing fault condition. A fault condition may be associated with one or more faults or errors.
[0095] exist Fig. 9A In the embodiment of the present invention, a graphical user interface (GUI) 900A includes a plurality of control or navigation buttons 902, 904, 906, 908, 910, and 912 on one side of a GUI screen 914A. The GUI screen 914A may display a fault message 926. The GUI screen 914A may display a message 930A indicating the handling of the fault condition, such as determining whether the fault condition is correct or not. Figure 5 The GUI screen 914A may display an indicator 932A indicating that the printer, RES, cloud, or other computing device is continuing processing.
[0096] Button 902 causes the printer to navigate to a home page. Button 904, when selected, may display information indicating a job. Button 906, when selected, may cause the printer to print; and button 908, when selected, may navigate to tools for adjusting parameters or settings of the printer. Button 910, when selected, may navigate to tools that may be used to operate the printer navigation; and button 912, when selected, may log out an operator or technician. Each of the graphical user interfaces 900A, 900B, 900C, 900D, 900E, 900F, 900G, and 900H may include a plurality of control or navigation buttons 902, 904, 906, 908, 910, and 912. Therefore, no further description will be provided.
[0097] exist Fig. 9B , GUI screen 914B may display a message 928 indicating a particular type of categorized fault condition. In this example, the fault condition is a "slot fault." In this example, GUI screen 914B may display a recommendation message 930B indicating a self-repair. Additionally, GUI screen 914B may display a message 934B indicating the skill set required for an operator or technician to perform the self-repair process. GUI screen 914B may display a message 936B indicating the tools required to perform and complete the self-repair process. GUI screen 914B may display a control button "Next" 916B, which, when selected, transitions the sequence from GUI screen 914B to GUI screen 914C. GUI screen 914B may display a "More" button 918B, which, when selected, navigates to a screen to provide and / or display additional information. Once button 916B is selected, the time the user remains on screen 914B is recorded as the actual completion time for that screen.
[0098] exist Fig. 9C , the GUI screen 914C may display a message 928 indicating a particular type of categorized fault condition. The GUI screen 914C may display a message 930C indicating a particular sequence to be performed. In this example, the sequence is for a nozzle backflush sequence. The GUI screen 914C may display sequence instructions 936C indicating a step-by-step process to be completed. The GUI screen 914C may include a button 916C indicating initiation of the backflush process. The GUI screen 914C may display a "more" button 918C that, when selected, navigates to a screen to provide and / or display additional information. The additional information may be associated with the nozzle backflush sequence.
[0099] exist Fig.9D , the GUI screen 914D may display a message 928 indicating a particular type of categorized fault condition. The GUI screen 914D may display a message 930D indicating a particular sequence (i.e., a nozzle backflush sequence). The GUI screen 914D may display an indicator 932D indicating continued processing of the backflush process. Once the repair process is associated with the GUI screen 914D, the actual completion time is recorded.
[0100] exist Fig.9E , the GUI screen 914E may display a message 928 indicating a particular type of categorized fault condition. The GUI screen 914E may display a message 930E indicating another particular sequence to be performed. In this example, the sequence is for a needle cleaning sequence. The GUI screen 914E may display sequence instructions 936E indicating a step-by-step process to be completed. The GUI screen 914E may include, for example, a button 916E indicating navigation to the next screen. The GUI screen 914E may display a "more" button 918E that, when selected, navigates to a screen to provide and / or display additional information. The additional information may be specific to the needle cleaning sequence.
[0101] exist Fig.9F , GUI screen 914F may display a message 928 indicating a particular type of classified fault condition. GUI screen 914F may display a message 930F indicating yet another particular sequence to be executed. In this example, the sequence is for starting a spray sequence. GUI screen 914F may display a sequence instruction 936F indicating at least one step to be completed. GUI screen 914F may include a button 916F that, when selected, causes the identified sequence to be started, for example. GUI screen 914F may display a "more" button 918F that, when selected, navigates to a screen to provide and / or display additional information. The additional information may be specific to the start-up spray sequence. The system may record the time of actual completion for the sequence.
[0102] exist Figure 9G In the example, the GUI screen 914G may display a message 928 indicating a specific type of classified fault condition. The GUI screen 914G may display a message 930G indicating that the start jet sequence has been initiated. However, in the GUI screen 914G, a display indicator 932G is provided, which indicates that the printer, RES, cloud or other computing device continues to process the start jet sequence.
[0103] exist Figure 9H , GUI screen 914H may display a message 948 indicating a successful self-repair. GUI screen 914H may display additional instructions 936H to complete the self-repair and bring the printer online to continue its batch printing or marking process. GUI screen 914H may display a "Finish" button 916H, which, when selected, indicates completion of instructions 936H. The time of actual completion for tracking, training, and updating the engine may also be recorded.
[0104] Performance Report
[0105] Fig.10 A flow chart of a process or method 1000 for reporting line restoration time statistics is illustrated. A fault session associated with line restoration time may record all or substantially all event data and tasks performed, and store the repair event data and tasks performed in the cloud for customers to run reports and evaluate the performance of the system. Information may include all of the choices made by the user, operator, or technician along the way and the actual time at each restoration screen to determine, for example, whether a self-repair task can be completed within 20 minutes or within the LRT threshold for a particular fault condition. A remote monitoring service (RMS) may monitor the printer for faults and current status.
[0106] Line recovery time can utilize data analysis and printer backup and recovery capabilities to reduce customer production downtime caused by printer failure. Some repairs take 50 minutes. In some cases, the embodiments herein can be reduced to 20 minutes per event. However, although the spare replacement may take longer to be put into operation, the mean time between expected failures for a specific fault may save time in overall production downtime.
[0107] Using data analytics, customer downtime due to printer failures can be reduced by identifying simple self-repairs and providing step-by-step repair instructions to customers to speed up recovery. When self-repair is not possible, the process will speed up replacement of failed printers with spare parts through local backup and recovery. When spare printers are deployed, embodiments can speed up field response to repair the downed printer(s) by proactively dispatching local field service.
[0108] The method 1000 may include, at block 1002, generating a report via the remote monitoring service dashboard detailing the performance and value created by line restoration time (LRT) for the facility. This will be implemented in the RMS dashboard and accessible by the operations manager and or designated personnel.
[0109] The method 1000 may include, at block 1004, generating in a report the number and total number of failures [failures resulting in more than 1 minute of no printing] that occurred by the printer within a specified time period.
[0110] The method 1000 may include, at block 1006, calculating and identifying in a report the number of self-repaired failures and spare parts deployed [the number of times an operator successfully self-repaired the printer based on operator feedback to the classifier module, the number of backups restored within 20 minutes, or the number of spare parts deployed based on a recovery time interface (RTI)].
[0111] The method 1000 may include, at block 1008, calculating and identifying in a report the number of minutes of downtime for a printer or site [downtime is calculated as the time from failure to completion of self-repair or spare part deployment].
[0112] Method 1000 may include, at block 1010, identifying in the report a comparison of the production downtime for each printer failure to a "theoretical would have been downtime time" for a numerical description [actual recovery time for each event vs. standard (50) minutes].
[0113] The method 1000 may include, at block 1012 , calculating and identifying in a report a number of self-repair opportunities and a number of times an operator chose to deploy a spare part rather than attempt a repair.
[0114] The method 1000 may include, at block 1014 , calculating and identifying in a report a number of spare part deployment opportunities and a number of times an operator chose to attempt a repair rather than deploy a spare part.
[0115] The administrator may be able to run a report that includes providing the number of failures that occurred during a specified period. The report may provide the administrator with the number of self-repaired failures versus spare parts deployed and services dispatched. The report may provide the administrator with the number of self-repairable events where the repair was successfully completed, the repair failed and a spare part was deployed, and the customer opted out of the repair and a spare part was deployed. The report may provide the administrator with the number of self-repair opportunities versus the number of times the operator chose to deploy a spare part rather than attempt a repair.
[0116] This report can provide managers with the number of spare part deployment opportunities and the number of times an operator chose to attempt a repair rather than deploy a spare part.
[0117] The data may represent how often customers attempt self-repair and succeed. The report may include data that breaks down customers into different entitlement groups (LRT vs. non-contract type vs. contract type, etc.) by customer account, site, region, or globally.
[0118] Figures 11A-11B Graphical user interfaces 1100A and 1100B for displaying reports such as on a computer system are illustrated. In box 1102A, the report GUI 1100A may include information associated with the total number of failures of multiple printers. In box 1104A, the report GUI 1100A may include statistics associated with the number of replacements and the number of self-repairs. In box 1106A, the report GUI 1100A may include statistics associated with the mean time to repair. In box 1108A, the report GUI 1100A may include statistics associated with the deployment time of the average spare part. In box 1110A, the report GUI 1100A may include statistics associated with the recommendation to adopt and abandon the recommendation. The operator may select an option different from the recommended option. In box 1112A, the report GUI 1100A may include statistics associated with the effectiveness of the suggestion. The effectiveness of the suggestion is a function of the number of LRT events that the actual time completed is within the LRT threshold or meets the LRT threshold. Information is tracked by site, printer or printer type, fault type, and time increment.
[0119] The report GUI 1100A may include data selection fields 1120A for selecting and / or filtering report data by site, printer or printer type, fault type, and time increment. For example, the time increment may last for 30 days. Other increments may be based on annual, semi-annual, 90 day, 60 day, or other time intervals. Statistics may be displayed using a bar graph, annular segmentation, or other statistical representation. For example, a pie chart or line graph may be used.
[0120] Fig. 11B The reporting GUI 1100B is similar to Fig.11A 110A in the report GUI. Therefore, only the differences will be described in detail. In the report GUI 1100B, statistics associated with successful completion of recommended self-repairs; repair failures with spare parts deployed; opting out and deploying spare parts; and opting out and performing self-repairs may be included.
[0121] Computing Hardware Overview
[0122] Fig.121 is a block diagram of a computer system 1200 (i.e., RES 150) on which embodiments of the present invention may be implemented or used. Computer system 1200 may be a server running a server application. The server may be a web server. RES 150 may be coupled to a printer via a network. The terms computing system, computing device, server, and computer system may be used interchangeably herein. The term engine may also include components of a computing device or computer system. Computer system 1200 includes a communication mechanism such as bus 1210 for transferring information between other internal and external components of computer system 1200. Information is represented as a physical signal of a measurable phenomenon, typically voltage, but in other embodiments, includes phenomena such as magnetic, electromagnetic, pressure, chemical, molecular atomic, and quantum interactions. For example, north and south magnetic fields, or zero and non-zero voltages, represent two states (0, 1) of a binary digit (bit). Other phenomena may represent numbers of higher bases. The superposition of multiple simultaneous quantum states before measurement represents a quantum bit (qubit). A sequence of one or more numbers constitutes digital data, which is used to represent a number or code of a character. In some embodiments, information referred to as analog data is represented by an approximate continuum of measurable values within a specific range. Computer system 1200, or a portion thereof, constitutes a device for performing one or more blocks of one or more methods described herein. Therefore, the computer system is a special purpose computer system.
[0123] A sequence of binary digits constitutes digital data, which is used to represent a number or code of a character. Bus 1210 includes many parallel wires for information, so that information is quickly transferred among devices coupled to bus 1210. One or more processors 1203 for processing information are coupled to bus 1210. Processor 1203 performs a set of operations on information. The set of operations includes introducing information from bus 1210 and placing information on bus 1210. The set of operations also typically includes comparing two or more units of information, moving the position of units of information, and combining two or more units of information, such as by addition or multiplication. The sequence of operations to be performed by processor 1203 constitutes a computer instruction.
[0124] The computer system 1200 also includes a memory 1204 coupled to the bus 1210. The memory 1204, such as a random access memory (RAM) or other dynamic storage device, stores information including computer instructions. The memory 1204 may also include dynamic memory, which allows the information stored therein to be changed by the computer system 1200. RAM allows a unit of information stored at a location called a memory address to be stored and retrieved independently of information at adjacent addresses. The memory 1204 is also used by the processor 1203 to store temporary values during the execution of computer instructions. The computer system 1200 also includes a read-only memory (ROM) 1206, a non-volatile persistent storage device or static storage device coupled to the bus 1210, for storing static information, including instructions, that is not changed by the computer system 1200. The ROM 1206 may be a secure byte-addressable memory (storage) device or a file direct access (DAX) memory device. The bus 1210 may also have other storage devices coupled to it, including non-volatile (persistent) storage devices such as magnetic disks or optical disks for storing information, including instructions, that persists even when the computer system 1200 is turned off or otherwise loses power.
[0125] Information including instructions is provided to the bus 1210 from an external input device 1213, such as a keyboard containing alphanumeric keys operated by a human user, or a sensor for use by the processor. The sensor detects conditions in its vicinity and converts those detections into signals compatible with signals used to represent information in the computer system 1200. Other external devices coupled to the bus 1210, primarily for interaction with humans, include: a display device 1214, such as a cathode ray tube (CRT) or liquid crystal display (LCD), light emitting diode (LED) display, for presenting images; and a pointing device 1216, such as a mouse or trackball or cursor direction keys, for controlling the position of a small cursor image presented on the display device 1214 and issuing commands associated with graphical elements presented on the display 1214.
[0126] In the illustrated embodiment, special purpose hardware, such as an application specific integrated circuit (IC) 1230, may be coupled to bus 1210. Special purpose hardware may be configured to perform operations that are not performed quickly enough for a special purpose by processor 1203. Examples of special purpose ICs include graphics accelerator cards for generating images for display device 1214, cryptographic boards for encrypting and decrypting messages sent over a network, voice recognition, and interfaces to special external devices.
[0127] Computer system 1200 also includes one or more instances of a communications interface 1270 coupled to bus 1210. Communications interface 1270 provides a two-way communications coupling to a variety of external devices that operate with their own processors, such as printers, scanners, and external disks.
[0128] Communication interface 1270 may receive data from a printer or other peripheral device. Pointing device 1216 , input device 1213 , and display device 1214 may be associated with host computer 1282 .
[0129] Typically, the computer system 1200 can be coupled to a network link 1278 through a communication interface 1270, and the network link 1278 is connected to a local network 1280, and a variety of external devices with their own processors are connected to the local network 1280. In some embodiments, the local network 1280 can be a dedicated network and can include wired and / or wireless communications. For example, the communication interface 1270 can be a parallel port or a serial port or a universal serial bus (USB) port on a personal computer. In some embodiments, the communication interface 1270 is an integrated services digital network (ISDN) card or a digital subscriber line (DSL) card or a telephone modem, which provides an information communication connection to a corresponding type of telephone line. In some embodiments, the communication interface 1270 can be a cable modem, which converts signals on the bus 1210 into signals for communication connections on coaxial cables, or into optical signals for communication connections on fiber optic cables. As another example, the communication interface 1270 can be a local area network (LAN) card to provide a data communication connection to a compatible LAN such as Ethernet. A wireless link can also be implemented. Carrier waves, such as acoustic and electromagnetic waves, including radio, optical and infrared waves, propagate through space without wires or cables. Signals include artificial variations in the amplitude, frequency, phase, polarization or other physical properties of carrier waves. For wireless links, the communication interface 1270 sends and receives electrical, acoustic or electromagnetic signals, including infrared and optical signals that carry information streams (such as digital data).
[0130] The term computer-readable medium is used herein to refer to any medium that participates in providing information including instructions for execution to the processor 1203. Such media can take a variety of forms, including but not limited to non-volatile media, volatile media, and transmission media. Non-volatile media include, for example, optical or magnetic disks, such as storage devices. Volatile media include, for example, dynamic memory 1204. Transmission media include, for example, coaxial cables, copper wires, fiber optic cables, and waves that propagate through space without wires or cables, such as sound waves and electromagnetic waves, including radio waves, light waves, and infrared waves. The term computer-readable storage medium is used herein to refer to any medium that participates in providing information to the processor 1203, except for transmission media.
[0131] Common forms of computer readable media include, for example, floppy disks, flexible disks, hard disks, magnetic tapes or any other magnetic media, compact disk ROMs (CD-ROMs), digital video disks (DVDs) or any other optical media, punch cards, paper tapes or any other physical media with patterns of holes, RAM, programmable ROMs (PROMs), erasable PROMs (EPROMs), FLASH-EPROMs or any other memory chips or cartridges, carrier waves or any other media from which a computer can read. The term non-transitory computer readable storage media is used herein to refer to any medium that participates in providing information to the processor 1203, other than carrier waves and other signals.
[0132] Logic encoded in one or more tangible media includes one or both of processor instructions on a computer-readable storage medium and dedicated hardware (such as ASIC 1230).
[0133] The network link 1278 typically provides information communication through one or more networks to other devices that use or process the information. For example, the network link 1278 can provide a connection to a host computer 1282 (such as a secure host computer) through a dedicated or local network 1280. For example, in some embodiments, a pilot can be located at the host computer 1282. Thus, a user interface can be located at the host computer 1282. As a non-limiting example, the host computer 1282 can also update and / or control the RES 150 from a remote location based on user responses or training session trends.
[0134] In some embodiments, the computer system 1200 may be connected to equipment 1284 operated by an Internet service provider (ISP) or an intranet service provider. The ISP equipment 1284 in turn provides data communication services through a public, global packet-switched communication network of a network now commonly referred to as the Internet 1290, or alternatively through an intranet. A computer called a server 1293 connected to the Internet or intranet provides services in response to information received through the Internet or intranet. For example, the server 1293 provides information representing video data to be presented at the display 1214, or the server may receive information representing video data. The cloud 280 may be accessible by the computer system 1200 (i.e., RES 150) via the ISP equipment 1284. The host 1282 may be part of a remote monitoring service (RMS) platform for communicating with and between the RES 150 and the printer.
[0135] The present invention relates to the use of computer system 1200 to implement the techniques described herein. According to one embodiment of the present invention, those techniques are performed by computer system 1200 in response to processor 1203 executing one or more sequences of one or more instructions contained in memory 1204 to form a computer program product. Such instructions, also referred to as software and program code, can be read into memory 1204 from another computer-readable medium (such as storage device 1208). Execution of the sequence of instructions contained in memory 1204 causes processor 1203 to perform the method blocks described herein. In alternative embodiments, hardware such as application specific integrated circuit 1230 can be used in place of software or in combination with software to implement the present invention. Therefore, embodiments of the present invention are not limited to any specific combination of hardware and software.
[0136] For development convenience, the computer program code for performing the above operations can be written in a variety of programming languages, including but not limited to high-level programming languages, such as but not limited to C or C++. In addition, the computer program code for performing the operations of the embodiments described herein can also be written in other programming languages, such as but not limited to interpreted languages. The program code may include a hardware description language (HDL) or a very high speed integrated circuit (VHSIC) hardware description language, for example, for firmware programming. Some modules or routines can be written in assembly language or even microcode to improve performance and / or memory usage. It will be further understood that any or all of the functions in the program module can also be implemented using discrete hardware components, one or more application specific integrated circuits (ASICs) or programmed digital signal processors (DSPs) or microcontrollers. The code of the program for describing the embodiments can be included in RAM, ROM, and flash memory as firmware. Otherwise, the code can be stored in a non-temporary tangible computer-readable storage medium, such as a tape, a floppy disk, a hard disk, a compressed disk, an optical disk, a digital versatile disk (DVD), or the like.
[0137] The signals transmitted over the network link 1278 and other networks through the communication interface 1270 carry information to and from the computer system 1200. Among other things, the computer system 1200 can send and receive information, including program code, through the networks 1280, 1290, through the network link 1278 and the communication interface 1270. In the example using the Internet 1290, the server 1292 transmits the program code of a specific application requested by the message sent from the computer 1200 through the Internet 1290, the ISP equipment 1284, the local network 1280 and the communication interface 1270. The received code can be executed by the processor 1203 when it is received, or can be stored in the storage device 1208 or other non-volatile storage device for later execution, or both. In this way, the computer system 1200 can obtain application program code in the form of a signal on a carrier wave.
[0138] When one or more sequences of instructions or data or both are carried to the processor 1203 for execution, various forms of computer-readable media may be involved. For example, the instructions and data may initially be carried on a disk of a remote computer such as the host computer 1282. The remote computer loads the instructions and data into its dynamic memory and sends the instructions and data over a telephone line using a modem. The modem local to the computer system 1200 receives the instructions and data on the telephone line and uses an infrared transmitter to convert the instructions and data into a signal on an infrared carrier used as a network link 1278. An infrared detector used as a communication interface 1270 receives the instructions and data carried in the infrared signal and places information representing the instructions and data on the bus 1210. The bus 1210 carries the information to the memory 1204, and the processor 1203 retrieves and executes the instructions from the memory 1204 using some of the data sent with the instructions. The instructions and data received in the memory 1204 may optionally be stored on the storage device 1208 before or after execution by the processor 1203.
[0139] The memory 1204 may have stored thereon an application implemented as software or computer instructions. When executed by the processor 1203, the application may perform one or more functions, steps or methods as described herein.
[0140] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the embodiments belong. It will be further understood that terms (such as those defined in commonly used dictionaries) should be interpreted as having a meaning consistent with their meaning in the context of the relevant art, and will not be interpreted in an idealized or overly formal sense unless explicitly defined as such herein.
[0141] In particular, unless specifically stated otherwise as apparent from the discussion, it is to be understood that throughout this description, discussions utilizing terms such as "processing" or "computing" or "calculating" or "determining" or "displaying" or the like refer to the actions and processes of a computer system or similar electronic computing device that manipulates and transforms data represented as physical (electronic) quantities in the computer system's registers and memories into other data similarly represented as physical quantities in the computer system memories or registers or other such data storage, transmission, or display devices.
[0142] The terms used herein are only for the purpose of describing specific embodiments and are not intended to be limiting. As used herein, the singular forms "one", "an" and "the" are intended to also include plural forms unless the context clearly indicates otherwise. In addition, with respect to the terms "include", "comprise", "comprising", "having", "having", "with" or their variants used in the detailed description and / or claims, such terms are intended to be inclusive in a manner similar to the term "comprising". In addition, unless otherwise specified, any use of the terms first, second, etc. does not represent any order or importance, but the terms first, second, etc. are used to distinguish one element from another element.
[0143] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the embodiments of the present invention belong. It will be further understood that terms (such as those defined in commonly used dictionaries) should be interpreted as having a meaning consistent with their meaning in the context of the relevant art, and will not be interpreted in an idealized or overly formal sense unless explicitly defined as such herein.
[0144] Although various disclosed embodiments have been described above, it should be understood that they have only been given as examples and not limitations. Without departing from the spirit or scope of the embodiments, many changes, omissions and / or additions may be made to the subject matter disclosed herein according to the embodiments disclosed herein. In addition, without departing from the spirit and scope of the embodiments, equivalents may replace its elements. In addition, although specific features may have been disclosed only about one of several implementations, such features may be combined with one or more other features of other implementations, as may be desirable and advantageous for any given or specific application. In addition, without departing from its scope, many modifications may be made to adapt specific situations or materials to the teachings of the embodiments.
[0145] Moreover, the foregoing abstract is intended to enable the U.S. Patent and Trademark Office and the public, scientists, engineers, and practitioners in general and in the related art(s) who are not familiar with patent or legal terms or phraseology to quickly ascertain the nature and essence of the technical disclosure upon cursory inspection. The abstract is not intended to limit the scope of the disclosure in any way.
[0146] Thus, the breadth and scope of the subject matter provided herein should not be limited by any of the embodiments explicitly described above. Rather, the scope of the embodiments should be defined in accordance with the following claims and their equivalents.
Claims
1. A method comprising: operate marking and coding equipment; classifying, by the classification module, the fault condition based on one or more of the received sensor data, the printer self-test data, the current operating data, and the historical device condition data; Responsive to the classified fault condition and based on an estimated time to repair (ETR) relative to a line restoration time (LRT) threshold, autonomously determining a repair process recommendation for an unmarked or uncoded device using a self-repair recovery process; as well as In response to the ETR being less than or equal to the LRT threshold, recommending, by at least one processor, a self-healing recovery process as a repair process recommendation.
2. The method according to claim 1, further comprising: storing device metadata and batch job metadata in a backup file; as well as The standby device is configured by downloading the stored device metadata and batch job metadata to replicate the failed device by the standby device.
3. The method according to claim 1, further comprising: Provides the option to override recommendations.
4. The method according to claim 1, further comprising: Replace a faulty device with a spare printer online.
5. The method according to claim 1 further comprises performing a self-repair recovery process, comprising Transmitting instructions in one or more timed repair screens; Tracks the time to complete each repair screen associated with the repair task; as well as Measure the time of the trace until the self-healing is complete.
6. The method according to claim 1 further comprises performing a self-repair recovery process, comprising Tracks the Line Restoration Time (LRT) statistics associated with each resolved fault condition.
7. The method according to claim 6, wherein: The LRT statistics include statistics associated with the mean time between failures associated with completed self-repairs.
8. The method according to claim 1, further comprising: Provides the option to override recommendations; Replace the failed equipment with a spare one online; as well as The standby device is configured by downloading the stored device and batch job metadata to replicate the failed device.
9. The method according to claim 1, further comprising: tracking actual time to complete a repair process associated with a repair process recommendation; tracking statistics associated with at least one of adoption of recommendations, average time to complete the repair process, and average time to deploy a backup device during the repair process; as well as Optionally report trace statistics.
10. The method of claim 9, further comprising tracking operator performance based on the tracked statistics and reporting the performance. The method of claim 9 , further comprising tracking performance of device types and reporting the performance.
12. The method of claim 1, wherein the fault condition comprises a fault associated with one or more of a printhead and an ink system associated with the encoding or marking device.
13. The method of claim 12, wherein the print head-related failure comprises one or both of a gutter failure and an EHT failure.
14. The method of claim 13, wherein the EHT fault is associated with one or more parameters including voltage, current, trip value, and percentage of trip.
15. The method according to claim 13, wherein: Gutter faults are associated with one or more parameters including gutter ink accumulation, time since last gutter cleaning, warning level settings, and the presence of ink in the gutter.
16. The method of claim 12, wherein the fault condition associated with the ink system comprises one or more of an ink reservoir failure and a resupply tank failure.
17. The method of claim 16, wherein an ink reservoir fault is associated with an ink reservoir parameter comprising at least one of ink type, ink expiration date, fluid level, remaining printing time, and ink tank temperature, and a refill tank fault is associated with a refill reservoir parameter comprising at least one of refill type, expiration date, refill vacuum, fluid level, remaining printing time, and refill tank temperature.
18. A system comprising: one or more marking and / or coding devices; as well as A computing system coupled to one or more devices and having at least one processor, the at least one processor configured to: classifying, by the classification module, a fault condition of a corresponding one of the devices based on one or more of the received sensor data, the printer self-test data, the current operation data, and the historical printer condition data; Responsive to the classified fault condition and based on an estimated time to repair (ETR), using a self-healing recovery process relative to a line restoration time (LRT) threshold, autonomously determining a repair process recommendation for unmarking and / or uncoding the device; as well as In response to the ETR being less than or equal to the LRT threshold, recommending, by at least one processor, a self-healing recovery process as a repair process recommendation.
19. The system of claim 18, wherein the at least one processor of the computing system is further configured to: storing device metadata and batch job metadata in a backup file for each device; and The standby device is configured by downloading the stored device and batch job metadata to replicate a corresponding one of the failed devices.
20. The system of claim 18, wherein the at least one processor of the computing system is further configured to: Provides the option to override recommendations.
21. The system of claim 18, wherein the at least one processor of the computing system is further configured to: Replace a corresponding failed device with a spare device online.
22. The system of claim 18, wherein the at least one processor of the computing system is further configured to: Perform a self-healing recovery process, including Transmitting instructions in one or more timed repair screens; Track the time to complete each repair screen for each repair task; and Measure the time of the trace until the self-healing is complete.
23. The system according to claim 18, further comprising performing a self-healing recovery process, comprising Tracks the Line Restoration Time (LRT) statistics associated with each resolved fault condition.
24. The system of claim 23, wherein: The LRT statistics include statistics associated with the mean time between failures associated with completed self-repairs.
25. The system of claim 18, wherein the at least one processor of the computing system is further configured to: Providing an option to overlay the recommendation on the device's screen; and In response to replacing the failed printer with a spare device, the spare device is configured by downloading the stored device and batch job metadata to replicate the failed device by the spare device.
26. The system of claim 18, wherein at least one processor of the computing system is further configured to: tracking actual time to complete a repair process associated with a repair process recommendation; tracking statistics associated with at least one of adoption of recommendations, average time to complete the repair process, and average time to deploy a replacement printer during the repair process; as well as Optionally report tracking statistics via a graphical user interface.
27. The system of claim 18, wherein the fault condition comprises a fault associated with one or more of a print head and an ink system associated with the encoding or marking device.
28. The system of claim 27, wherein the printhead-related fault comprises one or both of a gutter fault and an EHT fault.
29. The system of claim 28, wherein the EHT fault is associated with one or more parameters including voltage, current, trip value, and percentage of trip.
30. The system of claim 28, wherein: Gutter faults are associated with one or more parameters including gutter ink accumulation, time since last gutter cleaning, warning level settings, and the presence of ink in the gutter.
31. The system of claim 27, wherein the fault condition associated with the ink system comprises one or more of an ink reservoir failure and a resupply tank failure.
32. The system of claim 31 , wherein an ink reservoir fault is associated with an ink reservoir parameter comprising at least one of ink type, ink expiration date, fluid level, remaining printing time, and ink tank temperature, and a supply tank fault is associated with a supply reservoir parameter comprising at least one of supply type, expiration date, supply vacuum, fluid level, remaining printing time, and supply tank temperature.
