System and method for tracking production line productivity with industrial printing press

Abstract

Systems and methods for tracking production line productivity with industrial printers are provided. Methods and systems for operating an industrial printer include obtaining initial data indicative of an industrial printer used on a production line at a facility and a product to be output. Target data indicative of a target startup time and a target number of products and a target duration is obtained. An industrial printer is operated to report printing operation counts for a product at regular time intervals. Actual data indicative of the count and the time interval is stored. Under a condition, a line report is determined based on the count and the target data. The line report is presented on a display device. The condition is one or more of: an elapse of a target duration after a target start-up time; an elapse of a target duration after the first printing operation; changing shift workers on the production line; the time of one day; and a predetermined event.

Description

Background Art

[0001] Industrial printers such as continuous inkjet printers are used in production line printing to mark products or product packaging with information related to the product. These printers are complex devices with many components. For example, some components are filled with an ink mixture called a replenishing fluid, and other components apply an electric field to control the movement of droplets of the replenishing fluid to form a desired pattern on the product or product packaging.

[0002] As described in WO 2016 / 057465 published by the World Intellectual Property Organization (WIPO) for a specific intelligent industrial printer system, these printers may include various sensors to monitor sensor values ​​associated with one or more components of the printer. For example, a sensor at the print head may be used to monitor the temperature at the print head or monitor the temperature of the print head assembly. Temperature exceeding the desired print head temperature may cause excessive consumption of solvent, which directly affects the viscosity of the ink. To this end, a sensor may be provided at the ink supply of the printer to monitor the viscosity of the ink. In addition, an ink level sensing member may be provided to monitor the ink level remaining in the ink supply tank or ink replenishment tank. Additionally, the printer controller may be configured to generate an alarm or warning based on the sensor value generated by the sensor. In addition, user interface data or event data are generated for some printers. For example, the user interface data may include printing enable / print disable data, which may include the date and time when the printer is enabled by the operator and then subsequently disabled, or the date and time of one or more print head cleaning operations. Other data used by some industrial printers include the values ​​of user set parameters such as line speed, image height and width, substrate distance from the printhead, and actual printhead temperature. Summary of the invention

[0003] It is noted here that smart industrial printers such as those described in WIPO publication WO 2016 / 057465 can act as indicators of production line productivity. As used herein, a production line means any series of activities during the manufacture, packaging or transportation of an item, including assembly lines and fast-moving packaged consumer goods (FMCPG) environments in a manufacturing process. For example, such a printer can be operated so that data from such a printer can be used to determine the overall equipment efficiency (OEE) of a production line. OEE takes into account the various subcomponents of the manufacturing process-availability, performance, and quality. After taking various factors into account, the result is expressed as a percentage. Therefore, a technology for tracking production line productivity using an industrial printer is provided. The method utilizes equipment that the user has installed without challenging configuration and settings to obtain transparency into production line operations, which enables increased production throughput and reduced operating costs.

[0004] In a first group of embodiments, a method includes obtaining initialization data indicating a representative industrial printer used on a production line at a facility and products to be output by the production line. The method also includes obtaining target data indicating a target start time and a target number of products and a target duration for producing the target number of products. The method further includes operating the representative industrial printer to report (e.g., send a report message, which includes) a printing operation count of the product at regular time intervals. Still further, the method includes storing production line data, the production line data indicating the printing operation count and the time interval. Still further, the method includes, under a prerequisite, determining a production line report indicating production line productivity based on the printing operation count and the target data, and presenting the line report on a display device. The prerequisite is one or more of the group including: the passage of a target duration after the target start time; the passage of a target duration after the first printing operation of the product; a change of shift workers on the production line; the time of day; and the occurrence of a predetermined event.

[0005] In some embodiments of the first group, the method still further includes presenting a user interface configured to receive an event code indicating at least one of: a filler downtime; a press downtime; waiting for product; waiting for raw materials; planning maintenance; and a quality assurance hold. In these embodiments, the occurrence of the predetermined event includes receiving a report of the event code.

[0006] In some embodiments of the first group, event codes are automatically generated based on one or more sensors in an industrial printing press that are distinct from generating printing operation counts, wherein the event codes indicate a printing press condition or event associated with a production downtime of at least one of a representative printing press or different printing presses on a production line, and storing the production line data includes storing the automatically generated event codes.

[0007] In some embodiments of the first group, the method still further includes presenting a user interface configured to receive annotation input data indicating a change in annotation of observed downtime between planned downtime annotation and unplanned downtime annotation.

[0008] In some embodiments of the first group, the method still further includes presenting an inspection user interface configured to receive inspection data based on manual input provided by an inspector, and storing the inspection data on a computer-readable medium.

[0009] In some embodiments of the first group, the method further includes receiving separate data indicating a count of products on the production line from a separate sensor that is not part of the industrial printer via a communication link. Storing the production line data further includes storing supplemental data based on the separate data from the separate sensor.

[0010] In some embodiments of the first group, the processor includes one or more of a group of processors including: a processor on a representative industrial printer; a processor on a network confined to the facility; and a processor on a remote server outside the facility.

[0011] In a second set of embodiments, a system includes a production line at a facility; a processor; a display device; and an industrial printer configured to label packages on the production line. The industrial printer is in communication with the processor. The system also includes at least one memory, the at least one memory including one or more instruction sequences, the at least one memory and the one or more instruction sequences configured to cause the system to perform at least the following using the at least one processor. The system operates a representative industrial printer to report a print operation count for a product at multiple time intervals. Under prerequisites, the system determines a line report indicating a production line productivity based at least in part on the print operation count. The system presents the line report on a display device.

[0012] In other sets of embodiments, a computer readable medium or device is configured to perform one or more steps of the above method.

[0013] Still other aspects, features and advantages of the present invention will be readily apparent from the following detailed description, simply by describing a number of specific embodiments and implementations, including the best mode contemplated for carrying out the invention. The present invention is capable of other and different embodiments, and its several details may be modified in various obvious respects, all without departing from the spirit and scope of the present invention. Accordingly, the drawings and description are to be regarded as illustrative rather than restrictive in nature. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The present invention is illustrated by way of example and not by way of limitation in the figures of the accompanying drawings and in which like reference numerals refer to similar elements, and in which:

[0015] Figure 1A is a block diagram illustrating an example production line having an industrial printing press according to an embodiment;

[0016] Figure 1B is a block diagram illustrating example components and sensors in an industrial printer according to an embodiment;

[0017] Figure 1Cis a block diagram illustrating an example system for remote servicing of an industrial printing press according to an embodiment;

[0018] Figure 2 is a block diagram illustrating an example data structure for storing data from an industrial printing press for use in determining production line productivity according to an embodiment;

[0019] Figure 3 is a flow chart illustrating an example method in a processor for determining production line productivity based on an industrial printing press according to an embodiment;

[0020] Figure 4A and Figure 4B is a block diagram illustrating an example user interface for configuring an industrial printer on a production line according to an embodiment;

[0021] Figure 5 is a block diagram illustrating an example user interface (referred to as a dashboard) for reporting production line productivity according to an embodiment;

[0022] FIG. 6A to FIG. 6C is a chart illustrating example contents of a panel for reporting production line productivity according to an embodiment;

[0023] FIG. 7A to FIG. 7B is a block diagram illustrating an example screen for reporting production line productivity according to an embodiment;

[0024] Figure 8 is a chart illustrating example contents of a panel for reporting the productivity of a production line over an extended period of time according to an embodiment;

[0025] 9A to 9C is a block diagram illustrating an example screen for reporting downtime of a production line according to an embodiment;

[0026] Fig.10 is a block diagram illustrating a computer system upon which embodiments of the present invention may be implemented;

[0027] Fig.11 A chip set on which embodiments of the present invention may be implemented is illustrated;

[0028] Fig.12 is a diagram illustrating example components of a mobile terminal (eg, a cell phone) for communication according to an embodiment, the mobile terminal being capable of Figure 1A operating in a system that

[0029] Fig.13A and Fig. 13B is a block diagram illustrating example screens for reporting product inspections according to an embodiment. DETAILED DESCRIPTION

[0030] Methods and apparatus for remote operation of an industrial printing press for production line production measurement are described. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the invention. However, it will be clear to one skilled in the art that the invention can be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form so as not to unnecessarily obscure the invention.

[0031] Although the numerical range and parameter of the wide range are approximate, the numerical value set forth in the specific non-limiting example is reported as accurately as possible. However, at the time of this writing, any numerical value inherently contains a certain error, which is necessarily caused by the standard deviation present in its corresponding test measurement. In addition, unless otherwise clearly stated from the context, the numerical value presented herein has the intended accuracy given by the least significant digit. Therefore, the value 1.1 means a value from 1.05 to 1.15. The term "approximately" is used to indicate a wider range centered on a given value, and unless otherwise clearly stated from the context, it means a wider range around the least significant digit, such as "about 1.1" means a range from 1.0 to 1.2. If the least significant digit is unclear, the term "approximately" means a factor of two, for example, "about X" means a value in the range of from 0.5X to 2X, for example, about 100 means a value in the range of from 50 to 200. In addition, all ranges disclosed herein are to be understood as covering any and all sub-ranges included therein. For example, a range of "less than 10" for only positive parameters may include any and all sub-ranges between (and including) a minimum value of zero and a maximum value of 10, i.e., any and all sub-ranges having a minimum value equal to or greater than zero and a maximum value equal to or less than 10, e.g., 1 to 4.

[0032] Some embodiments of the present invention are described below in the context of services provided by one entity (e.g., a manufacturer, reseller, or retailer of an industrial printer) to many other entities (e.g., different companies), each of which is a customer and user of an industrial printer and is remote from the service provider. However, the present invention is not limited to this context. For example, in some embodiments, one entity owns many printers at one or more facilities, and services are provided by the same entity that uses the printers from a service center within one facility with many printers; or, services are provided by the same entity that uses the printers across several separate facilities, each of which has one or more industrial printers. In some embodiments, one entity provides a service center for many other entities, each of which has its own service center, which, for example, has spare parts or spare printers, or one or more knowledgeable technicians, or some combination. In various embodiments, an inkjet printer is illustrated; but the method is not limited to an inkjet printer. In other embodiments, other intelligent industrial printing or marking equipment is used, such as equipment for laser etching, laser ink filling.

[0033] 1. Overview

[0034] Figure 1A 1 is a block diagram illustrating an example production line 190 with an industrial printer according to an embodiment. The industrial printer includes an inkjet printer 110a and other printers or marking equipment indicated by item 110b and ellipses, collectively referred to as industrial printers 110. Unlabeled packages 192 enter the production line and receive content 194. When sealing, the industrial printer 110a directs inkjet 118 onto the packages, which leave the production line as a stack or canvas or other collection of dynamically labeled sealed packages 198. In other embodiments, the steps are performed in a different order, for example, before loading the content 194, the package 192 is labeled by the printer 110; or, the content 194 is directly labeled and the package 192 is omitted. In other embodiments, the printer 110a labels the package, and a different printer 110b labels the content, or other printers indicated by ellipses mark other components of the content 194, or canvases of multiple packages, or some combination. If the printer 110 fails, or the labeling applied is incorrect, the production line 190 is stopped until repairs are made, which reduces the productivity of the production line 190. In addition, if the labeling is incorrect, one or more of the labeled packages 198 must be discarded, which adds to the loss and further impairs the productivity of the facility where the production line 190 is located. If the production line or a component thereof is stopped, sensors on the printer 110 detect a lack of substrate for printing; and the printer 110 does not perform a printing operation.

[0035] like Figure 1A10a, the print head cylinder 114 is directed toward the package; and is fed by supply line 112 from the body of the printer 110, which contains one or more ink or supply reservoirs. The printer has a control panel (such as a graphical user interface, GUI, control panel 116) to receive commands from the user. In some embodiments, all or part of the GUI 116 is implemented on a separate mobile terminal (such as a tablet computer or smart phone), such as Fig.12 Some printers (such as the Model 1510 Continuous Ink Supply Printer from Videojet Technologies, Inc., Wood Dale, Illinois) include one or more processors that are configured to execute one or more software or firmware controlled processes. Such processors are typically part of a chipset, as described below with reference to Fig.11 Described in more detail.

[0036] In the illustrated embodiment, the printer 110a is configured to execute a printer service client process 120 that allows the printer 110 to be controlled based on data exchanged with a remote processor on a processing system 170 via a wired or wireless communication link 171, as described in more detail with reference to some of the following figures. In general, the remote processor is a processor such as described with reference to FIG. Fig.11 Another chipset as described, or as referenced below Fig.10 The remote processing system 170 includes a production line productivity module 172, which is configured to perform the following reference Figure 3 One or more steps of the production line productivity method are described in more detail. This module includes the following reference Figure 2 The production line data structure 173 is described in more detail.

[0037] In some embodiments, a separate sensor 178, also in communication with the processing system 170 via line 171, also makes measurements indicative of a count of items produced by the production line 190, whether on the same production line as the printer 110a or on a different production line.

[0038] Figure 1B1 is a block diagram illustrating example components and sensors in an industrial printer 110 according to an embodiment. The printer 110 includes a printer component 161, a printer component 162, and other components indicated by ellipses (hereinafter collectively referred to as printer components 160). Each printer component 160 has associated zero or more sensors (hereinafter collectively referred to as sensors 165), each of which is configured to measure a physical phenomenon associated with the printer component. As illustrated, in addition to other things indicated by ellipses, the printer component 161 also has associated sensors 163a, 163b; and, in addition to other things indicated by ellipses, the printer component 162 also has associated sensors 164a, 164b. 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 printer components and associated sensors for continuous ink supply printers are possible.

[0039] For example, there may be various sensors for various components in the print head, ink system, consumables, and electronics. These sensors provide information about parameters associated with the corresponding components. The combined information derived from the various sensors from the various components provides an unprecedented amount of information about the status of various systems in the printing press to allow a remote user to diagnose and predict potential problems with the printing press, such as faults, warnings, or malfunctions. Sensors (such as photocells or robotic arms or rollers, or some combination) are included to detect the distance of the substrate or along the substrate (for example, for stretched products such as cables or pipes) on which the marking is applied. In the event that the substrate or the distance along the substrate is not detected, the printing press will not perform a printing operation.

[0040] The printhead may include a nozzle having: 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, phase change rate, profile, and phase threshold; EHT parameters such as voltage, current, trip value, and percentage 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 open or closed time); nozzle parameters such as nozzle size, target velocity, serial number, manufacturing date, drop frequency, print count, run time, and deflected droplets. Of these, print count is used in various embodiments to at least partially monitor production line productivity.

[0041] The ink system may include: sensor parameters, such as ink pump parameters (such as pressure, speed, current, and pump run time); ink reservoir parameters, such as ink type, ink expiration date, fluid level (ml and / or percentage), remaining printing time, and ink tank temperature; replenishment reservoir parameters, such as replenishment type, expiration date, replenishment vacuum, fluid level (ml and / or percentage), remaining printing 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 exhaust valve (open or closed); filter / damper module parameters, such as ink filter pressure drop, serial number, date of manufacture, hours of operation, and replacement date; service module parameters such as flush pump speed, flush pump current, serial number, date of manufacture, hours of operation, replacement date, and information for various service module valves (open, closed, and open or closed times); cartridge parameters such as ink type, recommended replenishment type, serial number, date of manufacture, expiration date, cartridge size, fluid level, elapsed time in operation, cartridge replacement time, number of cartridge insertions, (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, date of manufacture, expiration date, cartridge size, fluid level, elapsed time in operation, cartridge replacement time, and number of insertions.

[0042] Other press parameters include: air filter parameters such as last replacement date, operating hours and replacement date; smoke / gas sensors within the press cabinet; humidity sensors within the press or for ambient environmental measurements; main control board parameters such as time and date, electronics temperature, HV voltage, HV current and voltages of various other power supplies within the electronics.

[0043] Failure in any of these components or sensors may result in a stop or slowdown in the production line 190. In some embodiments, such failures that result in production line downtime are recorded as downtime annotations. Data is passed from the sensor 165 to a control process 180, such as a control software program running on a processor of the industrial printing press 110, as indicated by the dashed line. The illustrated process 180 presents a graphical user interface GUI 186 for receiving user input 182, which includes the value of a user-set parameter, or the selection of a printing press operation (such as a quick clean operation), or some combination. The values ​​of the user-set parameters are stored in a user settings data structure 184.

[0044] Based on sensor data or user-selected press operations, or user settings 184, or some combination, the control process 180 is configured to issue a fault (e.g., a component is not working or not working properly), if appropriate, or a warning (e.g., a sensor indicates that a measurement is approaching a value outside the normal range of the corresponding component), if appropriate. The fault or warning is displayed in a user interface such as GUI 186. Example faults and warnings include some or all of those listed in Table 1, among other things.

[0045] Table 1. Example fault and warning events for an industrial printing press

[0046]

[0047]

[0048] Faults and warnings are two types of events determined by the control process 180. Other events determined by the control process 180 include user operations entered through user input 182, and machine operations such as print cycles, time stamps, inspections, and other operations, as listed in Table 2.

[0049] Table 2. Example other events for industrial printing presses

[0050]

[0051] The values ​​of other variables used and maintained by the control process 180 are referred to as environment variables. Example environment variables include hardware, firmware, and software versions, among other things, as listed in Table 3.

[0052] Table 3. Example environment variables for an industrial printing press

[0053]

[0054] The values ​​of the user-defined parameters are also used and maintained by the control process 180. Example user-defined parameters are listed in Table 4.

[0055] Table 4. Example user-defined parameters for an industrial printing press

[0056]

[0057] For a network including multiple industrial printing presses, which may number in the thousands, it can be seen that a large amount of data is available, including the sensor data mentioned above, parameter data, fault and warning events, other events, and environmental data. All of these data combinations can be considered historical data. Based on this historical data, a computer system or processor can determine associations between data, such as associations between environmental conditions and fault data. For example, it can be determined that for a printing press in a high temperature environment, the pump motor is more likely to overheat and have a shorter service life. These associations can be used to determine actions to be performed on the printing press.

[0058] Sensor data can be used (potentially in combination with historical data) to predict potential failures or other faults. An example is shown in Table 5 below. For example, if the speed of a pump is changing over time, it may indicate that the pump is wearing and will fail at some point. As another example, an increased pressure drop across a filter indicates that the filter may need maintenance. By compiling historical data from hundreds or thousands of printers in the field under various operating and environmental conditions, associations are made between sensor data and potential failures so that uptime can be maintained. For example, it can be known that after the pressure drop across the filter reaches a certain value, the printer will experience a failure 90% of the time within the next week. Therefore, it may be recommended to perform preventive maintenance on the filter before the failure occurs. As another example, for a smoke / gas sensor, it may be determined that if the gas content (e.g., solvent, such as MEK) in the printer cabinet exceeds a predetermined value, this indicates that there is likely to be a solvent leak in the printer and maintenance needs to be performed. It can be seen that various such associations can be derived from the sensor data and used to provide various warnings or actions to be taken. Of course, the number of missed prints can be used in some embodiments to indicate the productivity of the entire production line.

[0059] Table 5. Example predicted failures for an industrial printing press

[0060]

[0061]

[0062] The system can also be used to monitor the operation of the printing press in comparison with the best practice operating data. The best practice operating data relates to a predetermined process for operating and / or maintaining the printing press. The best practice operating data can be determined from design data, historical data from multiple printing presses, or from other sources. For example, it may be known that after a printing press has been down for more than 24 hours, it is best to provide a "clean start" that cleans parts of the print head before printing begins. If the user performs a quick start instead, the action will not comply with the best practice data. As another example, if the printing press fails due to a high voltage trip, the best practice may be to remove the print head cover, clean the deflector plate with solvent, and allow the parts to dry before returning to the operating mode. If the user does something different, it will not comply with the best practice. The processor uses the parameter data, the sensor data, and the best practice data to determine the compliance of the printing press operation with the best practice data. As another example, it is known that if too many clean starts are performed, the printing press will pass a lot of solvent into the mixing tank, which will dilute the ink, thereby changing its viscosity and potentially having a negative impact on the operation of the printing press (such as print quality). Therefore, if the user performs too many clean starts, this will not comply with the best practice data. Using historical data from various printers, it can be determined from sensor data how to operate as best practice. In some embodiments, best practice is defined in terms of a target number of items to be printed in a specific time interval, and actual performance can be compared with such target performance.

[0063] According to some embodiments, the printer 110 includes a printer service client process 120, such as a control software program running on a processor of the industrial printer 110. The client process is configured to exchange data with a server process running on a different device, such as a processing system 170, and to provide access to data received by a control process 180, and also to issue instructions to the control process 180, such as by changing values ​​in a user settings data structure 184 or by issuing commands to which the control process responds, such as commands issued by a user through a GUI 186 or commands of an application programming interface (API) for the control process 180.

[0064] The client-server model for separate process interaction is well known in the art. According to the client-server model, the client process sends a message including a request to the server process, and the server process responds by providing a service. The server process can also return a message with a response to the client process. The client process and the server process are usually executed on different computer devices (referred to as hosts) and communicate via a network using one or more protocols for network communication. The term "server" is conventionally used to refer to the process of providing a service, or the host computer on which the process operates. Similarly, the term "client" is conventionally used to refer to the process of making a request, or the host computer on which the process operates. As used herein, unless otherwise clearly stated from the context, the terms "client" and "server" refer to a process rather than a host computer. In addition, for reasons including reliability, scalability and redundancy, but not limited to those reasons, the process performed by the server can be decomposed into multiple processes running on multiple hosts (sometimes referred to as layers).

[0065] The remote service system for an industrial printer includes at least one industrial printer 110 having a printer service client process 120 and a printer service server process on a separate host computer that communicates with a client 120, such as via a local area network or a wide area network, or some combination. The server is configured to determine any of at least a set of service-related problems with the printer using at least sensor measurements and user-set parameter values, and to determine a remedial action for the service problem and initiate the remedial action, such as by dispatching a service technician with the correct replacement component, or by issuing a command to be executed by the printer, or by changing one or more user-set parameter values ​​in a data structure 184, or some combination. In various embodiments, the server is modified to include a line productivity module 172 to use information related to line productivity, as described below with reference to Figure 2 and Figure 3 Described in more detail.

[0066] If the server process is at a different location from the industrial printing press, one or more significant advantages arise. For example, a printing press service provider can reduce downtime of a customer's production line facility using a printing press by automatically notifying the service provider's maintenance team or technical support of abnormal conditions and supplying relevant information to resolve the problem. Service provider personnel can connect to the printing press and monitor the printing press to assess the problem and provide corrective actions remotely, or dispatch a notified service technician with the correct parts to fix it the first time. A real-time performance display presentation (also referred to as a "dashboard" below) provides key data about the printing press, which can help the service provider pinpoint areas for improvement in user-set parameter values ​​(the process of setting the values ​​of these parameters is also referred to as the "encoding process" herein).

[0067] Thus, in some embodiments, a system includes a plurality of processors, an industrial printer configured to apply ink to or otherwise mark packages on a production line, a communications network configured to support data communications between the plurality of processors, and at least one memory including one or more instruction sequences configured to cause the system, using the at least one processor, to obtain sensor data indicative of values ​​output by corresponding sensors configured to measure physical phenomena associated with one or more components of the industrial printer.

[0068] In some embodiments, the plurality of processors are located at a plurality of facilities at a corresponding plurality of different locations; and the industrial printer is at a particular facility among the plurality of facilities. Figure 1C1 is a block diagram illustrating an example system 100 for remote service of industrial printers according to an embodiment. The system 100 includes at least one industrial printer 110a at a site 105a (such as one facility of a particular company), and at least one printer service server (e.g., a printer service site server 122 on a site host 132, or a printer service central server 126 on a provider host 142 at a remote service center 108 at a different facility), and at least one communication network (e.g., a site network 134, or a wide area network 180, or a service center network 144, or some combination). In some embodiments, the system includes one or more separate sensors 178 at one or more sites, such as digital optical sensors or digital cameras that are not part of the printer 110. In some embodiments, the service operator or assembly shift operator interacts with and controls the server using input devices on a host, such as site host 132 or provider host 142, or input devices on a separate terminal, such as site terminal 136 connected to site host 132 via site network 134, or central terminal 146 connected to provider host 142 via service center network 144. In some embodiments, the terminal used by the service operator is the one described below with reference to Fig.12 A mobile terminal 150 , such as a smart phone, is depicted as being connected to a server host via the wide area network 18 or in combination with one or more other networks, such as the site network 134 or the service center network 144 .

[0069] According to the illustrated embodiment, the system is implemented in one or more networks, such as Figure 1C 134, service center network 144, and wide area network 180 as depicted in FIG. The network includes the Internet, which is configured to exchange data packets between terminals using the Internet Protocol (IP) and any of a variety of application layer protocols, including the Hypertext Transfer Protocol (HTTP) for sending World Wide Web pages between World Wide Web clients (referred to as Web browsers, or simply browsers) and World Wide Web servers. Connected to the network are several processes operating on host computers, including a printer service client 120 on the printer 110a and a printer service site server 122 on the host 132 and a printer service central server 126 on the host 142. In some embodiments, the terminals 136, 146, and 150 use a Web browser to connect to the server 122 or 126 by exchanging HTTP data packets to communicate the GUI of the dashboard and other web page screens, and to communicate operator responses (if any) to the GUI of the dashboard and other screens. In various embodiments, the printer service site server 122 or the printer service central server 126 or both include a production line productivity module 172.

[0070] In some embodiments, site 105a includes zero or more other industrial printers 110b, and a printer service server (e.g., server 122 or server 126) uses one or more databases (e.g., printer service site database 124, or printer service central database 128, either individually or in some combination) to store data received from printers 110a and 110b and zero or more individual sensors 178. In various embodiments, none, some, or all of production line data structures 173 are included in either or both of individual databases 124 and 128. In some embodiments, system 100 includes zero or more other facilities at other sites 105b, and printer service central server 126 is configured to service printers from all sites 105a and 105b.

[0071] Although for illustrative purposes, the processes, equipment, and data structures are shown in FIGS. Figure 1C , but in other embodiments, one or more processes or data structures, or portions thereof, are arranged differently on the same or different hosts, in one or more databases, or are omitted, or one or more different processes or data structures are included on the same or different hosts.

[0072] Figure 2 is a block diagram illustrating an example data structure 200 for storing data from an industrial printer and zero or more individual sensors 178 for use in determining production line productivity in accordance with an embodiment. Production line data structure 200 is an embodiment of a production line data structure 173 populated, maintained, and used by production line productivity module 172. Production line data structure 200 includes one or more production line records, such as production line record 210a and record 210b (hereinafter collectively referred to as production line records 210), in addition to other things indicated by ellipses. Each production line record 210 includes one or more fields that hold data indicating one product produced by one production line for one production run, as indicated by the fields depicted in record 210a. Although for purposes of illustration, the fields in record 210a are not shown in FIG. Figure 2 The data structure of the data structure may be depicted as a whole block in a particular order, but in other embodiments, one or more fields or portions thereof are arranged in a different order in a flat file or list or table, in zero or more databases, in one or more different memories, on one or more different computer hosts, or are combined, or omitted, or one or more additional fields are added, or the data structure is changed in some combination.

[0073] A line identifier (ID) field 211 holds data indicating a unique identifier for a particular production line, which includes one or more conveyor belts or other moving platforms, and one or more other production line components. A line description field 213 holds data describing the line, such as a location in the facility, a nickname, a list of components on the line (including one or more product part dispensers, one or more part assembly stations operated by human or robotic assemblers, one or more container dispensers, one or more fluid dispensing ports, one or more packaging components, zero or more collation machines, fillers, sealers, case packers, palletizers, reject grippers, labelers, vison systems, conveyors, buffers, accumulation stations, shrink wrappers, and one or more industrial printers for labeling parts or packages), or other descriptive information.

[0074] The printer ID field 215 holds data indicating an industrial printer among one or more printers on the production line, which is used to represent the operation of the entire production line. Such an industrial printer is called a representative printer. Any industrial printer or marking equipment (also referred to herein as an intelligent industrial printer, or simply referred to as a "smart printer" for convenience) that can be programmed to report (e.g., send a report message including) a count of printing operations in a time interval can be used as a representative printer, which includes, among other things, an inkjet printer, a laser ink-filled roller and toner printer, or a laser etched marker, a thermal inkjet printer, a thermal transfer coating printer, a drop-on-demand printer, a direct thermal labeling machine, or some combination. In some embodiments (wherein one or more individual sensors 178 that are not part of a printer assembly still report a production line count or other productivity data), field 215 includes data that uniquely indicates one or more individual sensors 178.

[0075] Fields 221 to 229 define a production run on the production line indicated in field 211. A stock keeping unit (SKU) is a number assigned to a product by a company for inventory purposes and internal operations. SKU field 221 holds data indicating a SKU number or other number indicating a specific product to be produced by the production line in a production run. Target quantity field 223 holds data indicating the number of products to be produced during a production run. Target duration field 225 holds data indicating the duration of a production run in which the production line is to output a target number of products. In some embodiments, target duration field 225 holds data indicating a target start time or a target end time, with or without a duration. Product image field 227 holds data indicating a product image associated with the number in SKU field 221. Including such an image is advantageous because such an image is more easily understood by a human operator than the abstract identifier in field 221, making it easier to ensure that the production line is operating properly. Switch time field 228 holds data indicating the amount of time during which the production line was not in operation, so that components could be modified to change from a different product previously produced on the production line identified in field 211 to the product identified in field 221. Other planned downtime field 229 holds data indicating any planned maintenance on one or more production line components (including one or more industrial printing presses) during the production run. For example, the production line may be stopped until the tank feeding the fluid dispenser is swapped out to get more of the same fluid, or the printing press ink supply is restored. This event and the associated duration for which it occurs are indicated by the data in field 229. Start time field 231 holds data indicating the time when the production run was started, if that time is not included in field 225.

[0076] Fields 233 to 253b hold data indicating actual performance of the production line during a production run as determined at least in part by the smart printer, in addition to other things indicated by ellipses. Time interval field 233 holds data indicating time intervals at which the number of items printed by the representative printer during a production run is reported to the processor, which stores the data in data structure 200. In addition to other things indicated by ellipses, interval number fields 241a, 241b (hereinafter collectively referred to as interval number fields 241) hold data indicating the number of time intervals since the time in start time field 231 (duration given by time interval fields 233). In addition to other things indicated by ellipses, associated with each interval number field 241a, 241b are product count fields 243a, 243b, respectively, in addition to other things indicated by ellipses. In addition to other things indicated by ellipses, product count fields 243a, 243b (hereinafter collectively referred to as product count fields 243) hold data indicating the number of products printed or detected by individual sensors 178. In some embodiments, the count is the number of products printed or detected since the time in the start time field 231, and the number printed in the most recent interval is the difference from the count in the immediately preceding product count field. In some embodiments, the count indicates only the increment in the number of products printed or detected during the time interval associated with the associated interval number in field 241.

[0077] In some embodiments, a smart printer or other production line component is operated to report one or more events (e.g., send an event report message of one or more events). When such an event occurs during a production run, event timestamp fields 251a, 251b (collectively referred to as event timestamp fields 251) are stored in the production line record 210 in addition to other things indicated by ellipses. Also associated with each event timestamp field 251a, 251b is an event field 253a, 2453b, respectively, in addition to other things indicated by ellipses. In addition to other things indicated by ellipses, product event fields 253a, 253b (hereinafter collectively referred to as event fields 253) also hold data indicating events at the printer or other comments of the production line.

[0078] Figure 3 1 is a flow chart illustrating an example method 300 in a processor for determining production line productivity based on an industrial printing press according to an embodiment. The production line productivity method 300 is executed by the production line productivity module 172. Although for illustrative purposes, the steps are described in detail in the following manner. Figure 3Although the overall steps are depicted in a particular order, in other embodiments, one or more steps or parts thereof are performed in a different order, or overlap in time, serially or in parallel, or are omitted, or one or more additional steps are added, or the method is changed in some combination.

[0079] In step 301, one smart industrial printer on a particular production line is designated as the representative printer for the current production run on that production line. In some embodiments, if the representative printer fails during a production run, additional printers are designated and ordered as backup representative printers. Which printer is so designated and which printers serve as backups may be determined using any method, either proactively or in response to a query message, or based on an algorithm, including receiving manual input, retrieving from a local or remote data file or database, or receiving information in a message in which the printers are ordered by advanced features or by furthest upstream or downstream location on the production line. Once selected, the production line identifier and description are stored along with the representative printer in fields 211, 213, and 215 of record 210 in the production line data structure 200. For example, in some embodiments, the representative printer is selected by the production line operator using a graphical user interface (such as Figure 4A ) to select.

[0080] Figure 4A and Figure 4B is a block diagram illustrating an example user interface for configuring an industrial printer on a production line according to an embodiment. Figure 4A 1 is a diagram illustrating an example screen on a display device of a terminal (such as a station terminal 136, a central terminal 142, and a mobile terminal 150) in a system 100 according to an embodiment. The screen includes one or more active areas that allow a user to input data to operate the system. As is well known, an active area is a portion of a display to which a user can point using a pointing device (such as a cursor and cursor moving device or a touch screen) to cause the device including the display to initiate an action. Among other things, well-known forms of active areas are stand-alone buttons with or without an associated keyboard, radio buttons, check lists, drop-down menus, scroll lists, and text boxes. Although for illustrative purposes, areas, active areas, windows, and toolbars are referred to herein. Figure 4A and 4B The user interface may be depicted as a whole block in a particular arrangement on a particular screen, but in other embodiments, one or more screens, windows, or active areas, or portions thereof, are arranged in a different order, have a different type, or one or more of them are omitted, or include additional areas, or are combined in some way to change the user interface.

[0081] Figure 4AAn example input screen 401 for selecting a representative printing press is depicted. Input screen 401 includes a screen navigation area 410 that includes several active areas, one for each input screen to which an operator can navigate, including an active area 411 for selecting a production line setup input screen. When the active area is selected, panel 420 is displayed. Panel 420 includes a site selection active area 421 (such as a drop-down menu) to select one of one or more sites in which the operator can determine replenishment for each production line. Once a site is selected, panel 420 provides subareas indicating each of the one or more production lines at the site, and an active area 423 for adding a new production line for the site. Each production line subarea includes a line name active area 431, 441 in which a line identifier, such as a line name, can be entered. Each line identifier is unique to the site indicated in area 421. Each production line subarea also includes an edit line active area 433, 443 to allow an operator to add, move, or remove components of a production line. Each production line sub-area also includes a row of production line activity areas for components 435a, 435b, 435c, 435d (collectively referred to as line components 435) in the order in which they appear along the line (as indicated by the middle arrows of the lines named in area 431); and line components 445a, 445b, 445c (collectively referred to as line components 445) in the order in which they appear along the line (as indicated by the middle arrows of the lines named in area 441). Line components 435, 445 have sensors that can be used to determine production line productivity, and include such components 435c and 445b as cameras to act as individual sensors 178, and such components 435a, 435b, 435d, 445a and 445c as smart printers. By selecting an activity area representing a component, the component can be designated as a representative component for the production line. Unlike previous methods, a smart printer can be designated as a representative component, referred to herein as a representative printer.

[0082] Return to Figure 3 In the method 300, in step 303, data about a production run is received and stored in a record 210 of the production run for the production line data structure 200. In various embodiments, the production run data includes data indicating production line target data such as production start time and target quantity of products, such as data of two or more fields 221 to 225 and zero or more fields 227 to 229. The data may be obtained using any method, either actively or in response to a query message, including receiving manual input, retrieving from a local or remote data file or database, or receiving information in a message.

[0083] Figure 4BAn example input screen 405 for describing a production run is depicted. The input screen 405 includes several active areas. Active area 455 allows the line operator to indicate products to be produced during the production run or to otherwise name the production run. Active areas 461 and 463 allow the line operator to specify a start time and end time, respectively, for the production run; or in other embodiments, a start time and duration for the production run. In the illustrated embodiment, active area 465 allows the line operator to select an all-day event in place of a start time and duration. In the illustrated embodiment, the screen includes an active area 471 to enter a description of the production run. In some embodiments, the active area 471 is used to indicate a target number of products to be produced during the production run. In other embodiments, an active area not shown is included to allow the line operator to specify a target number of products to be produced during the production run. Active area 473 allows the line operator to indicate which production line is to be used for the product, for example, selecting Figure 4A 420 of the production line. In the illustrated embodiment, screen 405 includes an active area 475 for indicating the number or names of personnel working one or more shifts during a production run. Active area 481 allows the operator to save data for a production run during which at least some information is stored in records 210 of data structure 200. Active area 483 allows the operator to exit the screen without saving any changes. Active area 485 allows the operator to delete a production run from the stored data, such as deleting record 210 in production line data structure 200.

[0084] Return to Figure 3 In method 300, in step 311, a representative printing press is operated to accumulate and report (e.g., send a message report, which includes) a print operation count for a production run (also referred to herein as a "print count"). For example, a series of commands are sent to the printing press having: a message to be printed (associated with a product of the production run); a time to initiate printing with a new annotation (e.g., based on data entered in active area 461); an instruction to zero the print count; an instruction to set a print count reporting interval. In some embodiments, the print count reporting interval defaults to a value, such as a value in the range from about 5 minutes to about 30 minutes, and preferably a value of about 15 minutes. In some embodiments, the print count is not zeroed, but is left to accumulate from any starting value. Because the print count can be recorded at time zero, the print count relative to the print count at time zero provides the number of print operations during the current production run.

[0085] In step 313, it is determined whether the current time is before the start time of the production run, and if so, control is transferred to step 345 to determine whether there is another unstarted production line. If there are no remaining production lines that have not yet started the production run, a report (e.g., a report document) is generated for all production lines at the site and presented in step 251. The process then ends. If there are any production lines that have not yet started the production run, control is transferred back to steps 301 to 311, and then the next production line is prepared for startup or a production line that has been set but not yet started is revisited. Finally, during step 313, the production line for which the production run start time is reached is found, and control is transferred to step 315.

[0086] In step 315, a determination is made as to whether a time increment report message has been received from a representative printer configured as described in step 311. If so, control passes to step 317 to store production line data including increment numbers and print counts based on the report in the next pair of fields 241 and 243 in the record 210 for the current production run. If the printer does not reset its print count, the first report represents the startup time (increment number=0), and the count represents the initial count before the production run was started. If the printer does reset its print count at the start of the production run, in some embodiments, the first report represents the increment after the startup time (increment number=1), and the count represents the count during that first time increment. If the printer does not reset its print count after each time increment, the count represents the cumulative count, and the count during the increment is the difference from the cumulative count of the previous time increment.

[0087] In some embodiments, step 317 includes receiving separate data indicating a count of products on the production line from a separate sensor 178 that is not part of the industrial printer 110 via a communication link. Storing the production line data then includes storing supplemental data based on the separate data from the separate sensor. In addition, the separate sensor acts as a reject counter for automatic reject tracking. In some embodiments, the separate sensor is a photo eye connected to a local wireless network.

[0088] In step 321, it is determined whether an event report message is received from a representative printing press configured as described in step 311 or from any other production line component configured to send event report messages. If so, control passes to step 323 to store a timestamp of the time the report message was received (or a timestamp included in the event report message) and a code for the event or a description of the event in the next pair of fields 251 and 253 in the record 210 for the current production run. In some embodiments, the event is insignificant to production line productivity, and the timestamp and event code or description are not recorded for this particular event.

[0089] In some embodiments, the event is associated with a production line stop or slowdown (collectively referred to herein as a production line downtime). For example, in some embodiments, an event is issued when a print count or individual sensor 178 indicates a significant decrease in the rate at which the product moves along the production line 190. In some of these embodiments, a downtime is associated with, for example, a period of time as recorded in a Figure 2 323. If the event is associated with the planned downtime in field 228 or field 229 of the line data structure depicted in FIG. 324, the event is recorded as a planned downtime. If the event is not associated with the data in field 228 or 229, the event is noted as an unplanned downtime during step 323.

[0090] In some embodiments, when an event is marked as planned or unplanned downtime, a user is allowed to re-mark the downtime during step 323. Thus, in some embodiments, step 33 includes presenting a user interface configured to receive marking input data indicating changes in the marking of the downtime observed between the planned downtime marking and the unplanned downtime marking.

[0091] In some embodiments, when the event is detected as a downtime, step 323 includes having the user provide a reason for the downtime, referred to as an event code, such as the following reference code: Fig.9A In these embodiments, step 323 includes presenting a user interface configured to receive a reason for the downtime.

[0092] In some embodiments, when the event is detected as a downtime, step 323 includes having the smart printer provide a reason for the downtime. In such an embodiment, an event code is automatically generated based on one or more sensors in the industrial printer 110 that are different from generating a print operation count. The event code indicates a printer condition or event associated with a production downtime of at least one of the representative printer or different printers on the production line. Storing the production line data includes storing the event code automatically generated during step 323.

[0093] In some embodiments, when the inspector is ready to inspect the product on the production line, an event report message is sent by a device such as a tablet computer or a smart phone in the inspector's hand. In some embodiments, the event is an inspection and need not be directly related to the production line production data. In some embodiments, the inspection data is received and the results are recorded through a GUI. Therefore, in some embodiments, step 323 includes presenting an inspection user interface configured to receive inspection data based on manual input provided by the inspector, and storing the inspection data on a computer readable medium.

[0094] In step 331, a determination is made as to whether the event report message is to be reported to a line operator, or whether the current time is time to update a line status report (such as a dashboard screen visible to the line operator, and described in more detail below). If so, then in step 333, the event is reported to the line operator (e.g., in a message to a local or remote terminal owned by the line operator), or the line status report is updated, or both. In either case, the requested report is prepared and presented on a display device accessible to the line operator.

[0095] In step 335, a determination is made as to whether a request has been received from an operator at a local or remote terminal for some kind of report on production line productivity, such as a report on total output, a report on production rate, a report on deviation from target, or a report on production rate predicted to the end of the production run, or some combination thereof. If so, control passes to step 337 to prepare the requested report and present it on a display device accessible to the production line operator. Figure 5 A format for displaying such a report is provided; and additional examples are provided in the Examples section.

[0096] In step 341, it is determined whether the summary reporting condition is met. Any summary reporting condition may be used, such as, among other things, the end of the shift, the elapse of time equal to the target duration after the target start time (e.g., the target end time entered in field 463), the elapse of time equal to the target duration after the first product was printed, or the print count equal to the target number of products, or any combination. If not, control passes back to step 315, and then continues to accumulate interval counts and events.

[0097] If it is determined in step 341 that the summary conditions are met, then control passes to step 343. In step 343, a summary report is generated and presented on a display device accessible to the line operator. In various embodiments, the values ​​of various parameters are presented, such as performance relative to a target, or performance in relation to various factors, such as, among other things, the unused capacity of a line, shift, product, package, line component, or line, or the total and constituent elements of downtime, or some combination. Control then passes to step 345 to configure or monitor any lines that have not yet been started.

[0098] Figure 5is a block diagram illustrating an example user interface 500 (referred to as a dashboard) for reporting production line productivity according to an embodiment. Such reporting can be performed per production line as in step 343, or for multiple production lines or multiple facilities as in step 251. The dashboard 500 includes a date range active area 503, which can be used to enter a data range for verifying production line productivity. The dashboard 500 also includes a site ID active area 501, which can be used to select any one or more sites for which production line productivity data can be consolidated. The dashboard 500 includes one or more summary panels 510, in addition to other things indicated by ellipses, and one or more graphical panels 520, in addition to other things indicated by ellipses.

[0099] Each summary panel 510 gives the current value or average of one or more productivity metrics. For example, each panel 510 includes, in addition to zero or more other things indicated by ellipses, a line ID area 511, a line status area 513, a plot type area 515, and more information areas 517. The line ID area 511 provides data indicating a production line or production run, or some combination. The status area 513 presents the value of one or more parameters summarizing the current or most recent status of the production run. The plot type area 515 is an active area that allows the user to select the type of graph to be presented in the graph panel 520. 6A to 9C Example graphics are described in the Examples section.

[0100] More information area 517 is the active area. When selected by the user, panel 510 is replaced with a list, or a graphic, or some combination of relevant information (such as a production run description, representative press, line components, among other information) for one or more production runs falling within the date range and site indicated in active areas 503 and 501, respectively.

[0101] Thus, the dashboard provides a means for a user at a terminal remote from the printer to determine the relative status of each of one or more production lines and production runs. In some embodiments, the dashboard also provides an activity area so that a user at a terminal remote from the printer can issue commands or suggest actions to be performed at the printer. The dashboard 500 allows the user to view the actual performance of the production line over a user-defined time period; understand whether the target is appropriate, positive or negative; and track the OEE performance on one or more production lines over time against the target. The grouping of production lines and time frames is user-selectable. The user can use the activity area to drill down to a specific time period for more details. The system provides access to the following types of data: throughput versus target; OEE; equipment status; downtime events; upcoming plans; and configurable alarms. The user can choose to view information at multiple levels, including: factory; production line (e.g., packaging line); product; and individual equipment. Data can be provided in different time frames: real-time performance; shift forecast; and historical trends.

[0102] therefore, Figure 3 An example method 300 is illustrated that includes obtaining initialization data indicating a representative industrial printer used on a production line at a facility and products to be output by the production line. The method 300 also includes obtaining target data indicating a target start time and a target number of products and a target duration for producing the target number of products. The method further includes operating the representative industrial printer to report a printing operation count for the product at regular time intervals. Still further, the method includes storing production line data indicating the printing operation count and the time interval. Still further, the method includes, under a prerequisite, determining a production line report indicating production line productivity based on the printing operation count and the target data, and presenting the production line report on a display device. The prerequisite is one or more of the group including: the passage of a target duration after the target start time; the passage of a target duration after the first printing operation of the product; a change of shift workers on the production line; the time of day; and a predetermined event.

[0103] 2. Example Embodiments

[0104] FIG. 6A to FIG. 6C is a chart illustrating example contents of a panel 520 for reporting production line productivity, according to an embodiment. Fig. 6Ais a bar chart depicting example totals of products produced on a production line by day of the week for the time intervals and stations specified in areas 503 and 501, respectively, of dashboard 500. The horizontal axis indicates the day of the week, and the vertical axis indicates the number of products produced. The chart indicates the number of items packaged each day versus the target for the line. The bars indicate the cumulative counts of production runs for those days based on the start time in field 231, the number of intervals in field 241, and the product count in field 243. Horizontal line 615 indicates the target quantity for the product based on the data in field 223.

[0105] Figure 6B is a bar graph depicting example OEE for the time intervals and sites specified in the dashboard 500 regions 503 and 501, respectively. The horizontal axis indicates hour numbers starting with hour zero for the time intervals and sites specified in the dashboard 500 regions 503 and 501, respectively. The vertical axis indicates overall equipment effectiveness (OEE). Hour number 2 shows good performance with an OEE level at or above 95% indicated by line 625 and shaded diagonally. Hour number 1 shows an average OEE level at or above 90% but less than 95% indicated by line 626 and shaded with dots. Hour numbers 0, 3, and 4 show marginal OEE levels at or above 85% but less than 90% indicated by line 626 and shaded with dashed lines.

[0106] Figure 6C is a bar chart depicting example actual throughput and gap to target by category for time intervals and stations specified in dashboard 500 regions 503 and 501, respectively. The horizontal axis indicates hour numbers starting with zero. The vertical axis indicates the difference from the target production rate of 1000 units per hour. The lowest segment 635 of each bar 635 indicates the number of units actually produced during that hour. The next segment 636 of each bar indicates the number of units that may have been produced in addition to the planned downtime. When the product count is not incrementing, the planned downtime can be inferred from fields 228 and 229 in the record 210 of the line data structure, together with the events indicated in one or more event fields 253 and the associated timestamps in field 251. The next segment 637 of each bar indicates the number of units that may have been produced in addition to the unplanned downtime. When the product count is not incrementing, the unplanned downtime can be inferred from the events indicated in one or more event fields 253 and the associated timestamps in field 251. The top section 638 of each bar indicates the number of units that could have been produced (but were not produced) if the line had not been stopped. These units represent lost opportunities to make the line more productive.

[0107] FIG. 7A to FIG. 7Bis a block diagram illustrating an example screen for reporting production line productivity according to an embodiment. Fig. 7A is a plant overview diagram for the time intervals and sites specified in areas 503 and 501 of the dashboard 500, respectively. The sites are indicated in area 421. The diagram provides several production lines, the status of the lines, the SKUs they are currently running, and all relevant progress towards the target data. For each production line at the site, the diagram provides a production line area 710. Each production line area 710 includes: a product image in area 711 for production runs; an area 712, which presents text indicating the identifier of the production line; an area 713, which presents text indicating the current status (e.g., operating at target efficiency for 3 hours, or operating at marginal efficiency for 15 minutes, or downtime for 25 minutes, etc.); an area 714, which annotates the time axis with the following intervals, the intervals being based on (e.g., equal to) the start time and time interval in fields 231 and 233 in records 210 in the line data structure 200, respectively; bars extending parallel to the time axis, which have different colors representing different status intervals (e.g., color 725 extending at or near target efficiency, color 726 at marginal efficiency, color 727 at or near target efficiency, color 728 at marginal efficiency, etc.); area 715 presenting text indicating the count in the last hour, the total count since the start time, and the target count since the start time; area 716 presenting text indicating the OEE efficiency, the time after the target time for the target count during the current shift, and the count after the target count during the current shift; area 717 presenting a graph indicating the trend relative to the target with arrows pointing downward, horizontally, or upward; and area 718 presenting a pie chart indicating the portion of product produced relative to the target rate and the portion of product missed due to planned downtime and the portion of product missed due to unplanned downtime.

[0108] Figure 7Bis a graph that tracks actual production versus planned production as a function of time for the time interval and site specified in areas 503 and 501, respectively, of dashboard 500. Independent axis 732 indicates time, and dependent axis 734 indicates the products that remain to be produced to reach target production. Trace 737 indicates actual counts as a function of time; and, trace 736 indicates target counts as a function of time. Planned downtime is evident at times just prior to current time 733, indicated by the dashed line. After the current time, the trace indicates the projected counts if the line continues at the target rate, which is given by the target quantity divided by the target duration, which are in fields 223 and 225, respectively, in record 210 for the current production run in line data structure 200. This projection can be used to determine the count at the target end time, at which trace 736 hits the independent axis, or the end time of the target count, at which trace 737 hits the independent axis.

[0109] Figure 8 is a chart illustrating example contents of a dashboard for reporting the productivity of a production line over an extended period of time, according to an embodiment. Figure 8 is a bar graph that depicts the ratios specified in the dashboard 500 areas 503 and 501, respectively. Figure 6B Example OEE for longer time intervals and sites in . The horizontal axis indicates the week number for each of the 5 weeks and the vertical axis indicates the OEE in percent. Weeks 1, 3, and 5 are indicated by diagonal shading with OEE over 85%. Week 2 is indicated by dotted shading with OEE over 80%. Week 4 is indicated by dotted shading with OEE below 70%.

[0110] In some embodiments, the user configures the downtime code based on any event recorded in the production run log, as described below, for example with reference to Fig.9A The code can then be accessed by any device that can connect to the system and the duration entered on the line or derived from the timestamp and the number of intervals with zero or minimum counts. As a result, the user can view downtime as an amount per time period or cumulatively by code. 9A to 9C is a block diagram illustrating an example screen for reporting downtime of a production line according to an embodiment.

[0111] Fig.9Ais an example user interface for defining different codes for different events or combinations of events. The downtime code is entered by the user, for example, during step 323, for example, via a phone, tablet computer, or PC using a web page or other GUI. The system allows this entry when the machine has been determined to be stopped (no count during a certain configurable time period). This allows the user to classify the data; therefore, gain deeper insights into how to improve operations on the production line. OEE does not change based on this classification; because OEE depends only on the total of unplanned downtime. Thus, for example, when a filler (which places the product into the package) stops, the smart printer subsequently stops printing, detects that there is no printing, and presents a request to the user, for example, via a web page, for the code to be entered. The user enters or creates a code for the filler downtime. If the user fails to enter the code, the downtime is captured as an unclassified unplanned downtime. In this example, code 1 indicates a filler downtime; code 2 indicates a press downtime as a result of any smart press event that results in a press downtime; code 3 indicates a conveyor downtime, as inferred by the absence of product appearing in front of a representative press or motion detector directed toward a conveying member; code 4 indicates waiting for raw material, such as liquid to fill a tank; code 5 indicates a downtime for planned maintenance as inferred from the data in fields 228 and 229; and, code 6 indicates a quality assurance hold as determined by the event recorded in field 253.

[0112] In some embodiments, the interface is provided during step 323 and includes a relabeling active area 912 or an auto-populated active area 914, or both. The user may use the relabeling active area 912 to change a downtime from scheduled to unscheduled, or vice versa. In the auto-populated active area 914, data is presented, for example using an icon, indicating that the event code for the particular downtime that is the subject of the display has been automatically populated based on an error code or condition automatically generated by the smart printer 110 at the event time associated with the current downtime event.

[0113] In various embodiments, one or more codes are determined in other automated or automation-assisted ways. An advantage of these automated or automation-assisted embodiments is that the downtime code is obtained in the following situation: in this situation, because the operator is focused on returning the production line to operation, the operator may otherwise skip providing a manual response to the prompt. For example, in some embodiments, the production line productivity module 172 is bound to a programmable logic controller (PLC) on each of the main controller or one or more components of the production line, and the binding is performed, for example, by monitoring the communication bus on which such PLCs place their current status. In some embodiments, a communication device (not shown) is co-located with a component of the production line. When the operator pays attention to the component, the operator can also operate the communication device, for example, using one or more buttons or active areas, in response to which a predetermined downtime code is transmitted to the production line productivity module 172.

[0114] Fig. 9B is a bar graph indicating the codes contributing to downtime for the time interval and site specified in the dashboard 500 areas 503 and 501, respectively. In the illustrated embodiment, the time interval is one week, and the horizontal axis indicates the day of the week. The vertical axis indicates the number of hours attributed to each code. The top of the bar indicates the total downtime, and the portion attributed to each code is represented by a color. The lowest segment of each bar having the first color indicates code 1, and the successively higher segments of each bar having colors 2 to 6 indicate codes 2 to 6.

[0115] Fig. 9C is a pie chart with the center removed, forming a ring or circular chart, which indicates the codes contributing to the total downtime for the time interval and station specified in areas 503 and 501, respectively, of the dashboard 500. Codes 1 through 6 contribute to the ring in a clockwise direction, accounting for 17%, 7%, 19%, 27%, 20%, and 10% of the total downtime, respectively. This type of information indicates that remedial actions are best targeted to the largest contributors, such as code 4 for waiting for raw materials.

[0116] Fig.13A and Fig. 13B is a block diagram illustrating example screens for reporting product inspections according to an embodiment. Fig.13A is a block diagram illustrating an example screenshot for configuring an unrestricted set of checks. Fig. 13B It is a block diagram illustrating example screen shots for receiving reminders and completing inspections on an Internet-enabled device (such as a desktop or smart phone). Inputs received at these screens are stored as electronic records that can be searched later and inspection summary reports generated.

[0117] Fig.13AA screen is illustrated that allows the creation of an inspection form that will replace the paper forms that may currently be used. The system provides a name for this particular "Inspection Group" form and provides the categories that will be inspected on that form. In addition to instantiating the electronic form, the user can also do one or more of the following from this screen: 1) assign the inspection group to a specific line or product (even a line that does have a smart press); 2) create a cadence for performing the inspection with associated notifications; or, 3) enter reference data, such as "16oz.+0.5oz" (not depicted).

[0118] Fig. 13B A screen is illustrated that presents a completion form that the user will review and use to complete the inspection. The inspector will review each item on the form and provide any input that will indicate a value or a "pass / fail" judgment. Additionally, the inspector can do one or more of the following: 1) review the configured reference data, which can be a value (see above) or an image (e.g., correct annotation placement); 2) provide comments that will most often be used to provide more information about a failed inspection; or, 3) attach an image, for example to capture incorrect annotation placement.

[0119] Therefore, as illustrated in these examples, the system enables people to automate packaging line settings, extract data based on key performance, and convert the data into actionable insights. Therefore, the system provides a means for increasing production line productivity, such as by identifying downtime causes, and remedial actions are optimally targeted at the causes. This is possible through the following: (a) seamless network and remote server connectivity (e.g., cloud connectivity), which enables visibility of the entire packaging and other production line operations on a single screen; (b) data visualization promotes management insights, which enables data-driven actions; and (c) equipping front-line team members with real-time data, thereby unlocking ownership, pride, and engagement around daily performance. The system enables knowing where people are, where they will go, and how they get there (so it won't happen again or be repeated). The system provides real-time visualization of packaging line and other production line performance, forward-looking predictions of productivity, and historical trend analysis of improved ID areas and best practices.

[0120] 3. Overview of computing hardware

[0121] Fig.101 is a block diagram illustrating a computer system 1000 on which an embodiment of the present invention can be implemented. The computer system 1000 includes a communication mechanism such as a bus 1010 for transferring information between other internal and external components of the computer system 1000. Information is represented as a physical signal of a measurable phenomenon, usually a voltage, but in other embodiments includes phenomena such as magnetic, electromagnetic, pressure, chemical, molecular atoms and quantum interactions. For example, a north magnetic field and a south magnetic field, or a zero voltage and a non-zero voltage represent two states (0, 1) of a binary digit (bit). Other phenomena can represent digits of a higher cardinality. The superposition of multiple simultaneous quantum states before measurement represents a quantum bit (qubit). A sequence of one or more digits constitutes digital data, which is used to represent a code for a number or a character. In some embodiments, information referred to as analog data is represented by a near continuum of measurable values ​​within a specific range. The computer system 1000 or a portion thereof constitutes a component for performing one or more steps of one or more methods described herein.

[0122] The sequence of binary digits constitutes digital data, which is used to represent a code for a number or character. The bus 1010 includes many parallel information conductors so that information can be quickly transferred between devices coupled to the bus 1010. One or more processors 1002 for processing information are coupled to the bus 1010. The processor 1002 performs a set of operations on the information. The set of operations includes bringing information from the bus 1010 and placing information on the bus 1010. The set of operations also typically includes comparing two or more information units, shifting the position of information units, and combining two or more information units such as by addition or multiplication. The sequence of operations to be performed by the processor 1002 constitutes a computer instruction.

[0123] The computer system 1000 also includes a memory 1004 coupled to the bus 1010. The memory 1004, such as a random access memory (RAM) or other dynamic storage device, stores information including computer instructions. Dynamic memory allows the computer system 1000 to change the information stored therein. RAM allows a unit of information stored at a location called a memory address to be stored and retrieved independently of information at neighboring addresses. The processor 1002 also uses the memory 1004 to store temporary values ​​during the execution of computer instructions. The computer system 1000 also includes a read-only memory (ROM) 1006 or other static storage device coupled to the bus 1010 for storing static information, including instructions that are not changed by the computer system 1000. Also coupled to the bus 1010 is a non-volatile (persistent) storage device 1008, such as a magnetic or optical disk, for storing information including instructions that persists even when the computer system 1000 is shut down or otherwise powered off.

[0124] Information including instructions is provided to the bus 1010 for use by the processor from an external input device 1012, such as a keyboard containing alphanumeric keys operated by a human user, or a sensor. The sensor detects conditions in its vicinity and transforms those detections into signals compatible with signals used to represent information in the computer system 1000. Other external devices coupled to the bus 1010, primarily for interaction with humans, include a display device 1014 for presenting images, such as a cathode ray tube (CRT) or liquid crystal display (LCD); and a pointing device 1016, such as a mouse or trackball or cursor direction keys, for controlling the position of a small cursor image presented on the display 1014 and issuing commands associated with graphical elements presented on the display 1014.

[0125] In the illustrated embodiment, special purpose hardware, such as an application specific integrated circuit (IC) 1020, is coupled to bus 1010. Special purpose hardware is configured to perform operations that are not performed quickly enough by processor 1002 for the special purpose. Examples of special purpose ICs include graphics accelerator cards for generating images for display 1014, cryptographic boards for encrypting and decrypting messages sent over a network, voice recognition, and interfaces to special external devices, such as robotic arms and medical scanning equipment that repeatedly perform some complex sequence of operations that are more efficiently implemented in hardware.

[0126] The computer system 1000 also includes one or more instances of a communication interface 1070 coupled to the bus 1010. The communication interface 1070 provides a two-way communication coupling with various external devices that operate with their own processors, such as printers, scanners, and external disks. Generally speaking, the coupling is made using a network link 1078 that is connected to a local network 1080 to which various external devices having their own processors are connected. For example, the communication interface 1070 may 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 1070 is an integrated services digital network (ISDN) card or a digital subscriber line (DSL) card, or a telephone modem that provides an information communication connection to a corresponding type of telephone line. In some embodiments, the communication interface 1070 is a cable modem that converts signals on the bus 1010 into signals for communication connection via a coaxial cable, or into optical signals for communication connection via a fiber optic cable. As another example, the communication interface 1070 may be a local area network (LAN) card to provide a data communication connection to a compatible LAN such as Ethernet. Wireless links can also be implemented. Carrier waves (such as acoustic and electromagnetic waves, including radio, optical, and infrared waves) travel through space without wires or cables. Signals include artificial changes in the amplitude, frequency, phase, polarization, or other physical properties of carrier waves. For wireless links, the communication interface 1070 sends and receives electrical, acoustic, or electromagnetic signals, including infrared and optical signals that carry information streams (such as digital data).

[0127] The term computer-readable medium is used herein to refer to any medium that participates in providing information to the processor 1002, including instructions for execution. Such media can take many 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 device 1008. Volatile media include, for example, dynamic memory 1004. Transmission media include, for example, coaxial cables, copper wire, fiber optic cables, and waves (such as sound waves and electromagnetic waves, including radio, optical and infrared waves) that travel through space without wires or cables. The term computer-readable storage medium is used herein to refer to any medium that participates in providing information to the processor 1002, except for transmission media.

[0128] 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, RAMs, 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 1002, other than carrier waves and other signals.

[0129] Logic encoded in one or more tangible media includes one or both of computer-readable storage media and processor instructions on dedicated hardware (such as ASIC 1020).

[0130] The network link 1078 typically provides information communication through one or more networks to other devices that use or process the information. For example, the network link 1078 may provide a connection through a local network 1080 to a host computer 1082 or to equipment 1084 operated by an Internet Service Provider (ISP). The ISP equipment 1084 in turn provides data communication services through the public global packet-switched communications network of networks now commonly referred to as the Internet 1090. Computers called servers 1092 connected to the Internet provide services in response to information received through the Internet. For example, the server 1092 provides information representing video data for presentation at the display 1014.

[0131] The present invention relates to the use of computer system 1000 for implementing the techniques described herein. According to one embodiment of the present invention, those techniques are performed by computer system 1000 in response to processor 1002 executing one or more sequences of one or more instructions contained in memory 1004. Such instructions (also referred to as software and program code) can be read into memory 1004 from another computer-readable medium (such as storage device 1008). The execution of the sequence of instructions contained in memory 1004 causes processor 1002 to perform the method steps described herein. In alternative embodiments, hardware such as application specific integrated circuit 1020 can replace software or be used 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.

[0132] Signals transmitted over network link 1078 and other networks through communication interface 1070 carry information to and from computer system 1000. Computer system 1000 can send and receive information including program code through networks 1080, 1090, through network link 1078 and communication interface 1070, among other things. In the example using Internet 1090, server 1092 transmits program code for a particular application requested by a message sent from computer 1000 through Internet 1090, ISP equipment 1084, local network 1080 and communication interface 1070. The received code can be executed by processor 1002 as it is received, or can be stored in storage device 1008 or other non-volatile storage for later execution, or both. In this way, computer system 1000 can obtain application program code in the form of a signal on a carrier wave.

[0133] In the process of delivering one or more sequences of instructions or data or both to the processor 1002 for execution, various forms of computer-readable media may be involved. For example, instructions and data may initially be carried on a disk of a remote computer such as a host 1082. 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 1000 receives the instructions and data on the telephone line and uses an infrared transmitter to convert the instructions and data into signals on an infrared carrier that acts as a network link 1078. An infrared detector that acts as a communication interface 1070 receives the instructions and data carried in the infrared signal and places information representing the instructions and data on a bus 1010. The bus 1010 delivers the information to the memory 1004, and the processor 1002 retrieves and executes the instructions from the memory 1004 using some data sent with the instructions. Before or after the processor 1002 executes, the instructions and data received in the memory 1004 may be optionally stored on a storage device 1008.

[0134] Fig.11 A chip set 1100 is shown on which an embodiment of the present invention may be implemented. The chip set 1100 is programmed to perform one or more steps of the method described herein and includes, for example, reference Fig.10 The chipset 1100 is a chip set that is incorporated into one or more physical packages (e.g., chips). By way of example, a physical package includes an arrangement of one or more materials, components, and / or wires on a structural assembly (e.g., a substrate) to provide one or more properties, such as physical strength, conservation of size, and / or limitation of electrical interactions. It is contemplated that in certain embodiments, the chipset may be implemented in a single chip. Chipset 1100 or a portion thereof constitutes a means for performing one or more steps of the methods described herein.

[0135] In one embodiment, the chipset 1100 includes a communication mechanism such as a bus 1101 for transferring information between components of the chipset 1100. The processor 1103 has connectivity to the bus 1101 to execute instructions and process information stored in, for example, a memory 1105. The processor 1103 may include one or more processing cores, each of which is configured to execute independently. A multi-core processor enables multiple processing within a single physical package. Examples of multi-core processors include two, four, eight or more processing cores. Alternatively or additionally, the processor 1103 may include one or more microprocessors configured in series via the bus 1101 to enable independent execution, pipelining and multithreading of instructions. The processor 1103 may also be accompanied by one or more specialized components to perform certain processing functions and tasks, such as one or more digital signal processors (DSPs) 1107, or one or more application specific integrated circuits (ASICs) 1109. The DSP 1107 is typically configured to process real-world signals (e.g., sound) in real time independently of the processor 1103. Similarly, ASIC 1109 can be configured to perform specialized functions that are not easily performed by a general purpose processor. Other specialized components that assist in performing the inventive functions described herein include one or more field programmable gate arrays (FPGAs) (not shown), one or more controllers (not shown), or one or more other special-purpose computer chips.

[0136] The processor 1103 and accompanying components have connectivity to the memory 1105 via the bus 1101. The memory 1105 includes both dynamic memory (e.g., RAM, magnetic disk, writable optical disk, etc.) and static memory (e.g., ROM, CD-ROM, etc.) for storing executable instructions that, when executed, perform one or more steps of the methods described herein. The memory 1105 also stores data associated with or generated by the execution of one or more steps of the methods described herein.

[0137] Fig.121 is a diagram of exemplary components of a mobile terminal (e.g., a cell phone) for communication according to an embodiment, the mobile terminal being capable of operating in the system of FIG. 1 . In some embodiments, the mobile terminal 1201 or a portion thereof constitutes a means for performing one or more steps described herein. In general, a radio receiver is often defined in terms of front-end and back-end characteristics. The front-end of a receiver encompasses all radio frequency (RF) circuitry, while the back-end encompasses all baseband processing circuitry. As used in this application, the term "circuitry" refers to both: (1) a pure hardware implementation (such as an implementation in analog and / or digital circuitry only), and (2) a combination of circuitry and software (and / or firmware) (such as, if applicable to a particular context, a combination of (one or more) processors, including (one or more) digital signal processors, software, and (one or more) memories, which work together to cause a device such as a mobile phone or server to perform various functions). This "circuitry" definition applies to all uses of the term in this application, including in any claims. As a further example, as used in this application, and if applicable to a particular context, the term "circuitry" will also cover an implementation of only a processor (or multiple processors) and its (or their) accompanying software / or firmware. The term "circuitry" would also cover, if applicable to the particular context, for example, a baseband integrated circuit or an applications processor integrated circuit in a mobile phone, or a similar integrated circuit in a cellular network device or other network equipment.

[0138] The relevant internal components of the phone include a main control unit (MCU) 1203, a digital signal processor (DSP) 1205, and a receiver / transmitter unit including a microphone gain control unit and a speaker gain control unit. The main display unit 1207 provides a display to the user to support various applications and mobile terminal functions that perform or support the steps described herein. The display 1207 includes a display circuit configured to display at least part of a user interface of a mobile terminal (e.g., a mobile phone). Additionally, the display 1207 and the display circuit are configured to facilitate user control of at least some functions of the mobile terminal. The audio function circuit 1209 includes a microphone 1211 and a microphone amplifier that amplifies the voice signal output from the microphone 1211. The amplified voice signal output from the microphone 1211 is fed to a coder / decoder (codec) 1213.

[0139] The radio section 1215 amplifies power and converts frequency to communicate with a base station included in a mobile communication system via an antenna 1217. A power amplifier (PA) 1219 and a transmitter / modulation circuit are operatively responsive to the MCU 1203, wherein the output from the PA 1219 is coupled to a duplexer 1221 or circulator or antenna switch, as known in the art. The PA 1219 is also coupled to a battery interface and a power control unit 1220.

[0140] In use, the user of the mobile terminal 1201 speaks to the microphone 1211, and his or her voice is converted into an analog voltage together with any detected background noise. The analog voltage is then converted into a digital signal by an analog-to-digital converter (ADC) 1223. The control unit 1203 routes the digital signal to the DSP 1205 for processing therein, such as speech coding, channel coding, encryption and interleaving. In one embodiment, the unit not shown separately encodes the processed sound signal using a cellular transmission protocol, such as Enhanced Data Rate for Global Evolution (EDGE), General Packet Radio Service (GPRS), Global System for Mobile Communications (GSM), Internet Protocol Multimedia Subsystem (IMS), Universal Mobile Telecommunications System (UMTS), etc., and any other suitable wireless medium, such as microwave access (WiMAX), long term evolution (LTE) network, code division multiple access (CDMA), wideband code division multiple access (WCDMA), wireless fidelity (WiFi), satellite, etc., or any combination thereof.

[0141] The coded signal is then routed to an equalizer 1225, which is used to compensate for any frequency-related impairments (such as phase and amplitude distortion) that occur during transmission over the air. After equalizing the bit stream, the modulator 1227 combines the signal with the RF signal generated in the RF interface 1229. The modulator 1227 generates a sine wave by means of frequency or phase modulation. In order to prepare the signal for transmission, the up-converter 1231 combines the sine wave output from the modulator 1227 with another sine wave generated by the synthesizer 1233 to achieve the desired transmission frequency. The signal is then sent through the PA 1219 to increase the signal to the appropriate power level. In a practical system, the PA 1219 acts as a variable gain amplifier, whose gain is controlled by the DSP 1205 according to information received from the network base station. The signal is then filtered in the duplexer 1221 and optionally sent to the antenna coupler 1235 to match the impedance, thereby providing maximum power transfer. Finally, the signal is transmitted to the local base station via the antenna 1217. An automatic gain control (AGC) may be supplied to control the gain of the final stage of the receiver. From there the signal may be forwarded to a remote telephone which may be another cellular telephone, any other mobile phone or landline connected to the Public Switched Telephone Network (PSTN) or other telephone network.

[0142] The sound signal transmitted to the mobile terminal 1201 is received via the antenna 1217 and immediately amplified by the low noise amplifier (LNA) 1237. The down converter 1239 reduces the carrier frequency, and the demodulator 1241 strips off the RF, leaving only a digital bit stream. The signal then passes through the equalizer 1225 and is processed by the DSP 1205. The digital-to-analog converter (DAC) 1243 converts the signal, and the resulting output is transmitted to the user through the speaker 1245, all under the control of the main control unit (MCU) 1203, which can be implemented as a central processing unit (CPU) (not shown).

[0143] MCU 1203 receives various signals including input signals from keyboard 1247. Keyboard 1247 and / or MCU 1203 combined with other user input components (e.g., microphone 1211) include a user interface circuit for managing user input. MCU 1203 runs user interface software to facilitate user control of at least some functions of mobile terminal 1201 as described herein. MCU 1203 also delivers display commands and switching commands to display 1207 and voice output switching controller respectively. In addition, MCU 1203 exchanges information with DSP 1205, and can access SIM card 1249 and memory 1251 that are optionally incorporated. In addition, MCU 1203 performs various control functions required by the terminal. Depending on the implementation, DSP 1205 can perform any of a variety of conventional digital processing functions on the sound signal. Additionally, DSP 1205 determines the background noise level of the local environment according to the signal detected by microphone 1211, and sets the gain of microphone 1211 to the level selected to compensate for the natural tendency of the user of mobile terminal 1201.

[0144] Codec 1213 includes ADC 1223 and DAC 1243. Memory 1251 stores various data including call incoming tone data, and can store other data including music data received via, for example, the global Internet. The software module may reside in RAM memory, flash memory, registers, or any other form of writable storage medium known in the art. Memory device 1251 may be, but is not limited to, a single memory, CD, DVD, ROM, RAM, EEPROM, optical storage, disk storage, flash memory storage, or any other non-volatile storage medium capable of storing digital data.

[0145] The optionally incorporated SIM card 1249 carries, for example, important information such as cellular phone number, carrier provisioning services, subscription details, and security information. The SIM card 1249 is primarily used to identify the mobile terminal 1201 on a radio network. The card 1249 also contains memory for storing a personal phone number registry, text messages, and user-specific mobile terminal settings.

[0146] In some embodiments, the mobile terminal 1201 includes a digital camera that includes an optical detector array, such as a charge coupled device (CCD) array 1265. The output of the array is image data, which is passed to the MCU for further processing or storage in the memory 1351, or both. In the illustrated embodiment, light impinges on the optical array through a lens 1263, such as a pinhole lens or a material lens made of optical grade glass or plastic material. In the illustrated embodiment, the mobile terminal 1201 includes a light source 1261, such as an LED, to illuminate the subject for capture by the optical array, such as CCD1265. The light source is powered by the battery interface and the power control module 1220 and is controlled by the MCU 1203 based on instructions stored or loaded into the MCU 1203.

[0147] 4. Extensions, Modifications and Alternatives

[0148] In the foregoing description, the present invention has been described with reference to specific embodiments of the present invention. However, it will be clear that, without departing from the broader spirit and scope of the present invention, various modifications and changes may be made thereto. Therefore, the description and the accompanying drawings are viewed in an illustrative, but not restrictive, sense. Throughout this specification and claims, unless the context otherwise requires, the words "comprise" and variations thereof, such as "comprises" and "comprising" will be understood to imply the inclusion of stated items, elements or steps, or groups of items, elements or steps, but do not exclude any other items, elements or steps, or groups of items, elements or steps. In addition, the indefinite article "one" or "an" is intended to indicate one or more items, elements or steps modified by the article.

Claims

1. A method comprising: Retrieve the identity of the printing press used on the production line that outputs the product; Use a printing press to mark products as part of a production line; Tracking the duration of time a printing press is used to mark a product as part of a production line, wherein said duration is reduced by any planned or unplanned interruption in the output of the product from the production line; incrementing a count of the printing operation of the printing press each time a product is marked by the printing press as part of a production line; as well as The productivity of the production line is determined based on a count of printing operations and the duration that the printing press is used to mark products as part of the production line.

2. The method according to claim 1, further comprising: determining target data, the target data comprising a target start time, a target number of products to be output from the production line, and a target duration for outputting the products from the production line, Determining the productivity of the production line includes determining the productivity of the production line based on the target data.

3. The method of claim 1 , wherein determining the production rate of the production line comprises: The overall equipment efficiency of the production line is determined based on a count of printing operations and the duration of time the printing press is used to mark products as part of the production line.

4. The method according to claim 1, further comprising: Determine actual usage of the press versus target usage to mark products as part of a production line, Wherein determining the productivity of the production line includes determining the productivity of the production line based on actual usage of a printing press used to mark products as part of the production line compared to a target usage.

5. The method according to claim 1, wherein: After the prerequisites are met, determine the production rate of the production line.

6. The method of claim 5, wherein the precondition comprises at least one of: the passage of a target duration after a target start time, the passage of a target duration after a first printing operation for marking a product, a change of shift workers on a production line, a time of day, or a predetermined event.

7. The method according to claim 1, further comprising: receiving an event code from a sensor, the event code indicating a printing press condition or event associated with a production downtime of the printing press; Based at least in part on the event code, usage of the printing press during output of product by the production line is determined.

8. The method of claim 7, wherein determining the production rate of the production line comprises: The productivity of the production line is determined based on usage of the printing press based at least in part on the event code.

9. A non-transitory computer-readable medium having stored thereon instructions executable by a processor to perform operations comprising: Retrieve the identity of the printing press used on the production line that outputs the product; Use a printing press to mark products as part of a production line; Tracking the duration of time a printing press is used to mark a product as part of a production line, wherein said duration is reduced by any planned or unplanned interruption in the output of the product from the production line; incrementing a count of the printing operation of the printing press each time a product is marked by the printing press as part of a production line; as well as The productivity of the production line is determined based on a count of printing operations and the duration that the printing press is used to mark products as part of the production line.

10. The non-transitory computer-readable medium of claim 9, wherein the operations comprise: determining target data, the target data comprising a target start time, a target number of products to be output from the production line, and a target duration for outputting the products from the production line, Determining the productivity of the production line includes determining the productivity of the production line based on the target data.

11. The non-transitory computer readable medium of claim 9, wherein determining a production rate of a production line comprises: The overall equipment efficiency of the production line is determined based on a count of printing operations and the duration of time the printing press is used to mark products as part of the production line.

12. The non-transitory computer-readable medium of claim 9, wherein the operations comprise: Determine actual usage of the press versus target usage to mark products as part of a production line, Wherein determining the productivity of the production line includes determining the productivity of the production line based on actual usage of a printing press used to mark products as part of the production line compared to a target usage.

13. The non-transitory computer readable medium of claim 9, wherein after the prerequisite is satisfied, a production rate of the production line is determined.

14. The non-transitory computer-readable medium of claim 13, wherein the prerequisite comprises at least one of: the passage of a target duration after a target start time, the passage of a target duration after a first printing operation for marking a product, a change of shift workers on a production line, a time of day, or a predetermined event.

15. The non-transitory computer-readable medium of claim 9, wherein the operations comprise: receiving an event code from a sensor, the event code indicating a printing press condition or event associated with a production downtime of the printing press; determining usage of a printing press during output of a product by a production line based at least in part on the event code, Wherein determining the productivity of the production line includes determining the productivity of the production line based at least in part on usage of the printing press based on the event code.

16. A system comprising: a printing press configured to mark products on the production line to be output from the production line; a processor communicatively coupled to the printing press; as well as A computer readable medium having stored thereon instructions executable by a processor to cause the processor to: Retrieve the identity of the printing press used on the production line that outputs the product; Tracking the duration of time a printing press is used to mark a product as part of a production line, wherein said duration is reduced by any planned or unplanned interruption in the output of the product from the production line; incrementing a count of the printing operation of the printing press each time a product is marked by the printing press as part of a production line; as well as The productivity of the production line is determined based on a count of printing operations and the duration that the printing press is used to mark products as part of the production line.

17. The system of claim 16, wherein the instructions include instructions executable by a processor to cause the processor to: determining target data, the target data comprising a target start time, a target number of products to be output from the production line, and a target duration for outputting the products from the production line, The instructions executable by the processor to cause the processor to determine the productivity of the production line include instructions executable by the processor to cause the processor to perform the following operations: determining the productivity of the production line based on the target data.

18. A system according to claim 16, wherein the instructions executable by the processor to cause the processor to determine the productivity of the production line include instructions executable by the processor to cause the processor to perform the following operations: determine the overall equipment efficiency of the production line based on the count of printing operations and the duration of using the printer to mark products as part of the production line.

19. The system of claim 16, wherein the instructions include instructions executable by a processor to cause the processor to: Determine actual usage of the press versus target usage to mark products as part of a production line, Wherein the instructions executable by the processor to cause the processor to determine the productivity of the production line include instructions executable by the processor to cause the processor to perform the following operations: determine the productivity of the production line based on actual usage of a printer used to mark products as part of the production line compared to a target usage.

20. A system according to claim 16, wherein the instructions are executable by the processor to cause the processor to determine the productivity of the production line after a prerequisite is met, wherein the prerequisite includes at least one of the following: the passage of a target duration after a target start time, the passage of a target duration after a first printing operation for marking a product, a change in shift workers on the production line, a time of day, or a predetermined event.

21. The system of claim 16, further comprising: a sensor communicatively coupled to the processor, The instructions include instructions executable by the processor to cause the processor to perform the following operations: receiving an event code from a sensor, the event code indicating a printing press condition or event associated with a production downtime of the printing press; determining usage of a printing press during output of a product by a production line based at least in part on the event code, The instructions include instructions executable by the processor to enable the processor to determine the productivity of the production line, and the instructions executable by the processor to enable the processor to determine the productivity of the production line include instructions executable by the processor to enable the processor to perform the following operations: determine the productivity of the production line based on the use of the printing press at least in part based on the event code.

Images