US20130036125A1 - System for Analyzing Device Performance Data - Google Patents
System for Analyzing Device Performance Data Download PDFInfo
- Publication number
- US20130036125A1 US20130036125A1 US13/196,142 US201113196142A US2013036125A1 US 20130036125 A1 US20130036125 A1 US 20130036125A1 US 201113196142 A US201113196142 A US 201113196142A US 2013036125 A1 US2013036125 A1 US 2013036125A1
- Authority
- US
- United States
- Prior art keywords
- data
- mail processing
- processing device
- devices
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
- G06Q50/10—Services
- G06Q50/26—Government or public services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
Definitions
- This invention relates generally device performance and more particularly to analyzing mail processing device performance.
- Enterprises often send and receive large volumes of mail. Enterprises may utilize high volume mail processing devices to automate mail processing tasks such as opening envelopes, removing correspondence from envelopes, capturing data, folding paper, inserting correspondence into envelopes, sealing envelopes, and applying postage to envelopes. In some circumstances, enterprises may employ vendors to supply mail processing devices and/or support services for mail processing devices.
- disadvantages and problems associated with analyzing mail processing device performance may be reduced or eliminated.
- a system for analyzing performance data associated with a mail processing device includes a reporting module operable to receive, over a network, first data related to the operation of a mail processing device at one of a plurality of mail processing sites, wherein each of the plurality of mail processing sites is associated with a database accessible over the network, store the first data in a database associated with the mail processing site of the mail processing device, receive, over the network, second data identifying filter criteria for the first data, filter, using a processor, the first data with the second data, generate, using a processor, a report based on the filtered first data, and communicate the report over the network.
- a non-transitory computer readable medium includes logic for analyzing performance data associated with a mail processing device, the logic, when executed by a processor, operable to receive, over a network, first data related to the operation of a mail processing device at one of a plurality of mail processing sites, wherein each of the plurality of mail processing sites is associated with a database accessible over the network, store the first data in a database associated with the mail processing site of the mail processing device, receive, over the network, second data identifying filter criteria for the first data, filter, using a processor, the first data with the second data, generate, using a processor, a report based on the filtered first data, and communicate the report over the network.
- a method for analyzing performance data associated with a mail processing device includes receiving, over a network, first data related to the operation of a mail processing device at one of a plurality of mail processing sites, wherein each of the plurality of mail processing sites is associated with a database accessible over the network, storing the first data in a database associated with the mail processing site of the mail processing device, receiving, over the network, second data identifying filter criteria for the first data, filtering, using a processor, the first data with the second data, generating, using a processor, a report based on the filtered first data, and communicate the report over the network.
- a technical advantage of an embodiment includes providing an enterprise with the ability to automate collection of performance data from mail processing devices, or from a mail services vendor's database, to dynamically manipulate the performance data with filter criteria, to supplement the performance data with data collected from other sources, and to generate reports from the manipulated performance data. Additionally, the system may allow the enterprise to identify maintenance issues in mail processing devices, train and evaluate operators and managers, track mail processing costs, and otherwise use mail processing device performance data to improve enterprise mail processing.
- FIG. 1 illustrates a block diagram of an embodiment of a system for analyzing the performance of mail processing devices
- FIG. 2 illustrates an embodiment of a database comprising a table of data associated with the performance of mail processing devices
- FIG. 3 illustrates a flow chart of an embodiment of a method for processing data associated with the performance of mail processing devices
- FIGS. 4A-B illustrate embodiments of graphical user interfaces
- FIGS. 5A-C illustrate embodiments of reports generated by the system.
- FIGS. 1 through 5 of the drawings like numerals being used for like and corresponding parts of the various drawings.
- FIG. 1 illustrates a block diagram of an embodiment of a system 100 for analyzing the performance of mail processing devices 108 .
- system 100 includes network 102 and enterprise 104 .
- Enterprise 104 may include a number of mail processing devices 108 at one or more mail processing sites 110 , one or more clients 112 , and one or more reporting modules 114 comprising memory 116 , database 118 , processor 120 , and interface 122 .
- system 100 further includes mail services vendor module 106 .
- Mail services vendor module 106 may comprise memory 124 , database 126 , processor 128 , and interface 130 .
- mail processing devices 108 , reporting modules 114 , mail services vendor module 106 , and clients 112 are communicatively coupled to network 102 .
- Enterprise 104 includes a plurality of mail processing devices 108 at one or more mail processing sites 110 and one or more reporting modules 114 , each reporting module 114 including database 118 associated with a mail processing site 110 .
- database 118 a of reporting module 114 a may be associated with mail processing site 110 a .
- Mail processing devices 108 may record first data related to the operation of mail processing devices 108 and communicate the first data over network 102 .
- Other components of system 100 for example, mail services vendor module 106 and/or reporting modules 114 may receive and store first data.
- Clients 112 may communicate second data that identifies filtering criteria for first data over network 102 .
- reporting module 114 a receives first data related to mail processing devices 108 at mail processing site 110 a associated with database 118 a of reporting module 114 a from network 102 , and receives second data from network 102 , filters the first data with the filtering criteria identified by the second data, generates a report based on the filtered first data, and communicates the report over network 102 .
- mail services vendor module 106 receives first data from network 102 and reporting modules 114 access first data from network 102 through mail services vendor module 106 .
- reporting modules 114 receive first data from network 102 without using mail services vendor module 106 .
- system 100 provides enterprise 104 with the ability to automate collection of performance data (e.g., first data) from mail processing devices 108 , or from a mail services vendor's database 126 , to dynamically manipulate the performance data with filter criteria (e.g., second data), to supplement the performance data with data collected from other sources, and to generate reports from the manipulated performance data.
- performance data e.g., first data
- filter criteria e.g., second data
- filter criteria e.g., second data
- system 100 may allow enterprise 104 to identify maintenance issues in mail processing devices 108 , train and evaluate operators and managers, track mail processing costs, and otherwise use mail processing device 108 performance data to improve enterprise 104 mail processing.
- Network 102 represents any suitable network operable to facilitate communication between components of system 100 , such as mail processing devices 108 , mail services vendor module 106 , reporting module 114 , and clients 112 .
- Network 102 may include any interconnecting system capable of transmitting audio, video, electrical signals, optical signals, data, messages, or any combination of the preceding.
- Network 102 may include all or a portion of a public switched telephone network (PSTN), a public or private data network, a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a local, regional, or global communication or computer network, such as the Internet, a wireline or wireless network, an enterprise intranet, or any other suitable communication link, including combinations thereof, operable to facilitate communication between the components.
- PSTN public switched telephone network
- LAN local area network
- MAN metropolitan area network
- WAN wide area network
- Internet a local, regional, or global communication or computer network
- wireline or wireless network such as the Internet
- enterprise intranet or any
- Enterprise 104 represents an entity that operates mail processing devices.
- Enterprise 104 may refer to a financial institution, such as a bank, however, enterprise 104 represents any suitable type of entity in any suitable industry.
- Enterprise 104 may have different business units, or subdivisions, that handle different business activities, for example, mail processing.
- enterprise 104 includes one or more mail processing sites 110 comprising a number of mail processing devices 108 , one or more clients 112 , and one or more reporting modules 114 comprising databases 118 associated with the one or more mail processing sites 110 .
- each mail processing site 110 is associated with a database 118 of a reporting module 114 .
- mail processing site 110 a is associated with database 118 a of reporting module 114 a
- mail processing site 110 b is associated with database 118 b of reporting module 114 a
- mail processing site 110 n is associated with database 118 n of reporting module 114 n , where N represents the number of mail processing sites 110 .
- each mail processing site 110 is associated with a database 118 of one or more reporting modules 114 .
- reporting module 114 may comprise a plurality of databases 118 , each database 118 associated with one or more mail processing sites 110 .
- Mail processing device 108 represents a machine, device, or apparatus operable to perform mail processing functions.
- Mail processing functions include opening mail packaging, removing mail from mail packaging, scanning mail, imaging mail, capturing data from mail, transmitting mail within enterprise 104 , outsorting mail, inserting mail into mail packaging, packaging mail, applying postage to mail, and/or any other processing involved in transmitting or receiving mail.
- Mail represents any tangible item that may be sent through mail services such as the United States Postal Service, the United Parcel Service, Federal Express, DHL, or any other mail services provider.
- Mail processing devices 108 include mail openers, mail extractors, mail sorters, mail joggers, payment processing equipment, mail inserters, mail sealers, tabbers, paper folders, imaging devices, scanning devices, data capture devices, and/or any other device, machine, or apparatus operable to automate processing involved in transmitting or receiving mail.
- the items processed by mail processing devices 108 may be referred to as articles.
- Articles include envelopes, documents, bills, checks, payment information, or other items that may be mailed to, or mailed from, enterprise 104 .
- mail processing devices 108 are equipped to record and/or communicate data related to the operation of mail processing devices 108 .
- Mail processing devices 108 may be located at mail processing sites 110 in enterprise 104 .
- Mail processing site 110 represents a location where mail processing devices 108 operate.
- Clients 112 represent entities that communicate data, such as filtering data (e.g., second data), to system 100 . Clients 112 may further be operable to receive reports generated by system 100 . In particular embodiments, clients 112 represent general or special-purpose computers communicating with software applications capable of performing the above-described operations. Additionally, in particular embodiments, client 112 may include one or more processors operable to execute computer logic and/or software encoded on non-transitory tangible media that performs the described functionality. Clients 112 may include, but are not limited to, laptop computers, desktop computers, personal digital assistants (PDAs), mobile phones, tablets, and/or portable media players.
- PDAs personal digital assistants
- client 112 comprises one or more of a general-purpose personal computer (PC), a Macintosh, a workstation, a Unix-based computer, a server computer, or any suitable processing device.
- Client 112 may also include one or more computer input devices, such as a keyboard, trackball, or a mouse, and/or one or more Graphical User Interfaces (GUIs), through which a user may interact with the logic operating on a processor communicating with client 112 .
- GUIs Graphical User Interfaces
- client 112 includes any appropriate combination of hardware, software, and/or encoded logic suitable to perform the described functionality.
- Clients 112 may couple to network 102 through a dedicated wired or wireless connection, or may connect to network 102 only as needed to receive, transmit, or otherwise execute applications.
- clients 112 may share elements and/or functionality with other components of system 100 , for example, when a software application operates on a component of system 100 and communicates and receives data from client 112 .
- FIG. 1 illustrates, for purposes of example, a particular number and type of clients 112
- alternative embodiments of system 100 may include any appropriate number and type of clients 112 , depending on the particular configuration of system 100 .
- client 112 communicates second data over network 102 , which includes criteria for filtering first data related to the operation of mail processing devices 108 .
- Second data may identify a subset of one or more categories of first data. For example, second data may identify the subset of operators at a particular site 110 who had jam clear rates greater than 15 seconds.
- Client 112 may communicate second data through a graphical user interface (GUI), which may be part of an application running on client 112 or on reporting module 114 . Examples of GUIs for communicating second data are described in more detail below with respect to FIGS. 4A-B .
- GUI graphical user interface
- Reporting modules 114 represent any suitable component of system 100 that facilitates receiving, storing, filtering, and/or communicating data. Reporting modules 114 may also be operable to generate reports based on filtered data. In some embodiments, reporting modules 114 may execute any suitable operating system such as IBM's zSeries/Operating System (z/OS), MS-DOS, PC-DOS, MAC-OS, WINDOWS, a .NET environment, UNIX, OpenVMS, or any other appropriate operating system, including future operating systems. The functions of reporting modules 114 may be performed by any suitable combination of one or more servers or other components at one or more locations. In an embodiment where reporting modules 114 are servers, the server may be a private server, and the server may be a virtual or physical server. Additionally, reporting modules 114 may include any suitable component that functions as a server.
- z/OS IBM's zSeries/Operating System
- MS-DOS MS-DOS
- PC-DOS PC-DOS
- MAC-OS WIN
- reporting modules 114 includes memory 116 , database 118 , processor 120 , and interface 122 .
- Memory 116 represents any device operable to store, either permanently or temporarily, data, operational software, or other information for processor 128 .
- Memory 116 includes any one or a combination of volatile or non-volatile local or remote devices suitable for storing information.
- memory 116 may include random access memory (RAM), read only memory (ROM), magnetic storage devices, optical storage devices, semiconductor storage devices, or any other suitable information storage device or a combination of these devices.
- Memory 116 may include any suitable information for use in the operation of reporting module 114 .
- Memory 116 may include some or all of database 118 .
- Database 118 represents one or more databases operable to receive, store, filter, and/or communicate data associated with mail processing devices 108 .
- each database 118 is associated with a mail processing site 110 and stores data related to the performance of mail processing devices 108 at the mail processing site 110 .
- Processor 120 represents any computing device configured to control the operation of reporting modules 114 .
- Processor 120 may comprise one or more processors and may be a programmable logic device, a microcontroller, a microprocessor, any suitable processing device, or any suitable combination of the preceding.
- Processor 120 includes any hardware and/or software that operates to control and process information received by reporting module 114 .
- processor 120 communicatively couples to memory 116 , database 118 , and interface 122 and controls the operation of reporting module 114 .
- Interface 122 represents any device operable to receive input, send output, process the input and/or output and/or performs other suitable operations for reporting modules 114 .
- Interface 122 includes any port or connection, real or virtual, including any suitable hardware and/or software, including protocol conversion and data processing capabilities, to communicate through network 102 that allows reporting modules 114 to exchange information with components of system 100 over network 102 .
- interface 122 may receive data relating to the operation of mail processing devices 108 from network 102 .
- Mail services vendor module 106 represents any suitable component of system 100 that facilitates receiving, storing, filtering, and/or communicating first data.
- mail services vendor module 106 may execute any suitable operating system such as IBM's zSeries/Operating System (z/OS), MS-DOS, PC-DOS, MAC-OS, WINDOWS, a .NET environment, UNIX, OpenVMS, or any other appropriate operating system, including future operating systems.
- the functions of mail services vendor module 106 may be performed by any suitable combination of one or more servers or other components at one or more locations.
- the server may be a private server, and the server may be a virtual or physical server.
- mail services vendor module 106 may include any suitable component that functions as a server.
- mail services vendor module 106 includes memory 124 , database 126 , processor 128 , and interface 130 .
- Memory 124 represents any device operable to store, either permanently or temporarily, data, operational software, or other information for processor 128 .
- Memory 124 includes any one or a combination of volatile or non-volatile local or remote devices suitable for storing information.
- memory 124 may include RAM, ROM, magnetic storage devices, optical storage devices, semiconductor storage devices, or any other suitable information storage device or a combination of these devices.
- Memory 124 may include any suitable information for use in the operation of mail services vendor module 106 .
- Memory 124 may include some or all of database 126 .
- Database 126 represents one or more databases operable to receive, store, filter, and/or communicate data associated with mail processing devices 108 .
- Processor 128 represents any computing device configured to control the operation of mail services vendor module 106 .
- Processor 128 may comprise one or more processors and may be a programmable logic device, a microcontroller, a microprocessor, any suitable processing device, or any suitable combination of the preceding.
- Processor 128 includes any hardware and/or software that operates to control and process information received by mail services vendor module 106 .
- processor 128 communicatively couples to memory 124 , database 126 , and interface 130 and controls the operation of mail services vendor module 106 .
- Interface 130 represents any device operable to receive input, send output, process the input and/or output and/or performs other suitable operations for mail services vendor module 106 .
- Interface 130 includes any port or connection, real or virtual, including any suitable hardware and/or software, including protocol conversion and data processing capabilities, to communicate through network 102 that allows mail services vendor module 106 to exchange information with components of system 100 over network 102 .
- interface 130 may receive data relating to the operation of mail processing devices 108 from network 102 .
- Components of system 100 may include logic.
- Logic performs the operation of the component, for example, logic executes instructions to generate output from input.
- Logic may include hardware, software, and/or other logic.
- Logic may be encoded in one or more non-transitory, tangible media, such as a computer-readable medium or any other suitable tangible medium, and may perform operations when executed by a computer.
- Certain logic such as a processor, may manage the operation of a component.
- reporting modules 114 receive first data from network 102 communicated by one or more mail processing devices 108 and/or mail services vendor module 106 , receives second data from network 102 communicated by one or more clients 112 , filters the first data with the second data, generates one or more reports based on the filtered first data, and communicates the one or more reports over network 102 .
- Clients 112 may receive the reports from network 102
- enterprise 104 may use the reports to evaluate mail processing device 108 , operator, and/or manager performance.
- enterprise 104 uses reports to identify maintenance issues relating to mail processing devices 108 .
- mail services vendor module 106 receives first data from network 102 and reporting modules 114 access first data from network 102 through mail services vendor module 106 .
- reporting modules 114 receive first data from network 102 without using mail services vendor module 106 .
- System 100 may include more, fewer, or other components. Any suitable component of system 100 may include a processor, interface, logic, memory, and/or other suitable element.
- first data may originate at mail processing devices 108 and/or mail services vendor module 106 .
- FIG. 2 illustrates an embodiment of a database comprising table 200 of data associated with the operation of mail processing devices 108 .
- table 200 includes columns of data categories such as date column 202 , job name column 204 , job type column 206 , job time column 208 , operator column 210 , manager column 212 , device column 214 , customer column 216 , product column 218 , input column 220 , output column 222 , outsort column 224 , reunite column 226 , rejects column 228 , jams column 230 , jam clear rate 232 , and device idle time column 234 .
- data categories such as date column 202 , job name column 204 , job type column 206 , job time column 208 , operator column 210 , manager column 212 , device column 214 , customer column 216 , product column 218 , input column 220 , output column 222 , outsort column 224 , reunite column 226 , rejects column 228 , jams column 230
- system 100 stores first data related to the operation of mail processing devices 108 at mail processing site 110 in table 200 in database 118 associated with the mail processing site 110 .
- First data may relate to performance data of mail processing devices 108 , operators, or managers.
- Mail processing device 108 performance data includes jam rate, reunite rate, reject rate, outsort rate, and/or output rate.
- Operator performance data includes jam clear rate and/or device idle time.
- Reporting modules 114 may filter the data in table 200 , and/or generate reports based on the data in table 200 .
- System 100 may use data in table 200 to evaluate the performance of mail processing device 108 , an operator, and/or a manager.
- mail processing device 108 may record the number of articles processed by mail processing device 108 and the total number of jams during that period of time, but may not perform the calculation to determine the number of articles processed per jam (i.e., a jam rate).
- system 100 uses data from mail processing devices 108 to calculate additional data that may be useful for evaluating mail processing device 108 , operator, and/or manager performance.
- calculated data may include rates (e.g., output/unit time), performance metrics (e.g., jams/operator), or any other performance data calculated using data from mail processing devices 108 .
- the first data may include calculated data and may be filtered by second data.
- Date column 202 provides the dates that mail processing devices 108 processed particular batches of articles, referred to as jobs. Jobs may be associated with particular articles, customers, types of mail processing, or other category.
- Job name column 204 provides identification codes for particular jobs.
- Job type column 206 provides identification codes for particular categories of jobs.
- Job time column 208 provides the time mail processing device 108 operated processing a particular job.
- Operator column 210 provides identification codes for particular operators of mail processing devices 108 .
- Manager column 212 provides identification codes for particular managers that supervised operators that controlled mail processing devices 108 .
- Device column 214 provides identification codes for particular mail processing devices 108 .
- Customer column 216 provides identification codes for particular categories of products processed by mail processing devices 108 . In an embodiment, customer identification codes identify entities that sponsor the processing of particular products by mail processing devices 108 .
- Product column 218 provides identification codes for particular categories of articles processed by mail processing devices 108 . Products may be associated with particular articles, customers, types of mail processing, or other category.
- Input column 220 provides the number of articles input into mail processing devices 108 .
- Output column 222 provides the number of articles successfully processed by mail processing device 108 .
- output excludes outsorts, reunites, and rejects.
- Outsort column 224 provides the number of articles, such as envelopes or packages, that could not be opened by mail processing device 108 .
- Mail processing device 108 may receive pre-defined criteria that determine what articles mail processing device 108 should outsort. For example, criteria may include article overlap in mail processing device 108 , articles are too close together, article has incorrect dimensions, article has a change in thickness, mail processing device 108 error, metal detected in an article, damage to an article, or other suitable criteria.
- Reunite column 226 provides the number of articles, such as documents, that were not fully extracted from an envelope or package by mail processing device 108 .
- Reject column 228 provides the number of articles, such as documents, that could not be processed by mail processing device 108 because of the orientation of the article, an error in the article, an error reading the article, and/or an error imaging the article.
- Jam column 230 provides the number of obstructions that occurred in mail processing device 108 during operation.
- a jam may result from a malfunction of mail processing device 108 , an operator error, or a defect in an article being processed.
- mail processing devices 108 shut down until a jam is cleared.
- a jam may include an article getting caught in mail processing device 108 and/or a portion of mail processing device 108 that needs to be reset. For mail processing device 108 to operate efficiently, jams need to be cleared from mail processing device 108 .
- mail processing device 108 operators clear jams from mail processing device 108 .
- Jam clear rate column 232 indicates the amount of time taken to clear a jam from mail processing device 108 .
- jam clear rate represents an average time taken to clear jams from mail processing device 108 over a period of time or number of articles processed.
- Device idle time column 234 indicates the amount of time mail processing device 108 was turned on but not processing articles. In an embodiment, remaining idle time excludes the time between turning mail processing device 108 on and when mail processing device 108 is able to process articles (i.e., the startup time of mail processing device 108 ).
- Table 200 may further include data such as type of mail processing device, outsort rate, jam rate, jam time, reunite rate, reject rate, output rate, effective throughput, stops, total device time, or other type of data related to mail processing device operation useful to measure device, operator, and/or manager performance.
- Device type represents a category of mail processing devices 108 .
- Outsort rate represents a measurement of the number of outsorts occurring in mail processing device 108 .
- Outsort rate may include articles processed per outsort, a time mail processing device 108 operates per outsort, or any other suitable metric for monitoring the occurrence of outsorts in mail processing device 108 .
- outsort rate is expressed as the percentage of articles handled by mail processing device 108 that were outsorts.
- Jam rate represents a measurement of the number of jams occurring in mail processing device 108 .
- Jam rate may include articles processed per jam, time mail processing device 108 operates per jam, or any other suitable metric for monitoring the occurrence of jams in mail processing device 108 .
- Jam time represents the total amount of time a mail processing device 108 spent jammed.
- Reunite rate represents a measurement of the number of reunites occurring in mail processing device 108 .
- Reunite rate may include articles processed per reunite, time mail processing device 108 operates per reunite, or any other suitable metric for monitoring the occurrence of reunites in mail processing device 108 .
- reunite rate is expressed as the percentage of articles handled by mail processing device 108 that were reunites.
- Reject rate represents a measurement of the number of rejects occurring in mail processing device 108 .
- Reject rate may include articles processed per reject, time mail processing device 108 operates per reject, or any other suitable metric for monitoring the occurrence of rejects in mail processing device 108 .
- Output rate represents a measurement of the number of articles successfully processed by mail processing device 108 .
- Output rate may include articles processed per unit time of mail processing device operation, for example, per hour.
- Effective throughput represents a measure of the number of articles successfully processed by a mail processing device 108 . In an embodiment, effective throughput represents the number of articles successfully processed per hour. Stops represent the number of times a mail processing device 108 stopped processing articles.
- Total device time represents the total amount of time a mail processing device operated.
- Row 236 represents an embodiment of filtered first data that includes data related to a particular mail processing job.
- Row 236 includes the date the job was processed (1/1/11), the job name (0001), the job type (Job 1), the amount of time mail processing device 108 operated to process the job (02:53:58), the operator who processed the job (Oper1), the manager who supervised the operator (Manag1), the particular mail processing device 108 that processed the job (Dev1), the product involved in the mail processing job (Prod1), the number of articles input into mail processing device 108 as part of the job (27,264), the number of articles successfully processed by mail processing device 108 as part of the job (26,235), the number of articles that were outsorts (1029), the number of articles that were reunites (266), the number of articles that were rejects (612), the number of times mail processing device 108 jammed during the job (42), the average time it took the operator to clear the jams from mail processing device 108 (00:00:14), and the amount of time mail processing
- Table 200 may include more, fewer, or different column fields.
- Table 200 may include any data useful in monitoring the performance of mail processing device 108 , operator, or operator manager performance.
- Table 200 may also include any combination of column fields, any number of rows, or any number of columns.
- FIG. 3 illustrates a flow chart of an embodiment of method 300 for processing data associated with the operation of mail processing devices.
- Method 300 begins at step 302 .
- reporting module 114 receives, over network 102 , first data related to the operation of mail processing devices 108 , wherein each of the plurality of mail processing sites 110 is associated with a database 118 of reporting modules 114 accessible over network 102 .
- mail services vendor module 106 and/or mail processing device 108 communicates the first data to reporting module 114 associated with the mail processing site 110 of the mail processing device 108 that originated the data.
- First data may indicate performance metrics of mail processing devices 108 .
- reporting module 114 stores the first data in database 118 associated with the mail processing site 110 of the mail processing device 108 that originated the data.
- reporting module 114 receives, over network 102 , second data identifying filter criteria for the first data.
- reporting module 114 receives second data from one or more clients 112 .
- reporting module 114 filters, using processor 120 , the first data with the second data.
- reporting module 114 generates, using processor 120 , a report based on the filtered first data.
- reporting module 114 communicates the report over network 102 .
- Method 300 ends at step 316 .
- Method 300 may include more, fewer, or other steps. Additionally, steps may be performed in any suitable order. Any suitable component of system 100 may perform one or more steps of method 300 .
- mail services vendor 106 may perform one or more of steps described as being performed by reporting module 114
- database 126 may perform one or more of the steps described as being performed by database 118 .
- FIGS. 4A-B illustrate embodiments of graphical user interfaces (GUIs) for communicating second data.
- GUIs graphical user interfaces
- FIG. 4A illustrates an embodiment of GUI 400 .
- client 112 may select a date range, one or more manager names, and/or one or more operator names to include in a report.
- Client 112 may further select Individual Operator Reports and/or Summary Reports that include categories of data such as product, client, job type, and device.
- GUI 400 further provides client 112 other reporting options such as Product Reports by Half Hour, Output Volumes by Month, 14 Day Chart, Product Report by Date, Employee Performance Management System Reports, and an option to view More Reports.
- FIG. 4B illustrates an embodiment of GUI 402 .
- client 112 can select a date range, customer type, customer, product, job type, device type, and device to include in a report. Client 112 may further select whether to include various data such as outsort rates, jam rates, reunite rates, reject rates, and/or output rates.
- GUI 402 further provides client 112 reporting options that include Daily Report, Summary, Jam Clear Rate Report, and Remaining Idle Time Report.
- GUI 402 allows client 112 to export data used to create a report to a Microsoft Excel file.
- Interfaces 400 and 402 may include more, fewer, or other fields for receiving second data or more, fewer, or other options for reports.
- GUIs 400 and 402 may further communicate with any suitable component of system 100 .
- FIGS. 5A-C illustrate embodiments of generated reports of first data filtered by second data.
- FIG. 5A illustrates report 500 which displays data related to mail processing device 108 performance.
- Report 500 includes input, output, effective throughput, vendor effective throughput, jam rate, average remaining idle time, jam clear rate, stops, jams, run time, jam time, idle time, and total device time for a number of mail processing devices at a particular mail processing site over a particular date range.
- Enterprise 104 may use report 500 to evaluate mail processing device 108 performance, identify maintenance issues in mail processing devices 108 , or other purpose.
- FIG. 5B illustrates report 502 which displays data related to operator performance.
- Report 502 includes input, output, effective throughput, vendor effective throughput, jam rate, average remaining idle time, jam clear rate, stops, jams, run time, jam time, idle time, and total device time for a particular operator over a particular date range.
- Report 502 further includes the operator's manager, the particular devices operated by the operator, the products processed by the operator on the particular devices.
- Enterprise 104 may use report 502 to evaluate operator performance, compare operator performance, evaluate site 110 performance, or other purpose.
- FIG. 5C illustrates report 504 which displays data related to manager performance.
- Report 504 includes input, output, effective throughput, vendor effective throughput, jam rate, average remaining idle time, jam clear rate, stops, jams, run time, jam time, idle time, and total device time for a particular operator over a particular date range.
- Report 504 further includes a number of managers of a particular mail processing site 110 , the particular mail processing devices 108 operated under the supervision of the managers, and a summary of mail processing device 108 performance at site 110 .
- Enterprise 104 may use report 504 to evaluate manager performance, comparing manger performance, evaluating site 110 performance, or other purpose.
- Reports 500 , 502 , and 504 may include more, fewer, or other fields. Reports 500 , 502 , and 504 may display more, fewer, or other first data and may filter the first data with more, fewer or other second data. Reports 500 , 502 , and 504 may be generated in any suitable format and may include data tables, such as table 200 . Reports 500 , 502 , and 504 may be dynamic, allowing a user to further manipulate data in the report, or static.
Abstract
Description
- This invention relates generally device performance and more particularly to analyzing mail processing device performance.
- Enterprises often send and receive large volumes of mail. Enterprises may utilize high volume mail processing devices to automate mail processing tasks such as opening envelopes, removing correspondence from envelopes, capturing data, folding paper, inserting correspondence into envelopes, sealing envelopes, and applying postage to envelopes. In some circumstances, enterprises may employ vendors to supply mail processing devices and/or support services for mail processing devices.
- According to embodiments of the present disclosure, disadvantages and problems associated with analyzing mail processing device performance may be reduced or eliminated.
- In certain embodiments, a system for analyzing performance data associated with a mail processing device includes a reporting module operable to receive, over a network, first data related to the operation of a mail processing device at one of a plurality of mail processing sites, wherein each of the plurality of mail processing sites is associated with a database accessible over the network, store the first data in a database associated with the mail processing site of the mail processing device, receive, over the network, second data identifying filter criteria for the first data, filter, using a processor, the first data with the second data, generate, using a processor, a report based on the filtered first data, and communicate the report over the network.
- In certain embodiments, a non-transitory computer readable medium includes logic for analyzing performance data associated with a mail processing device, the logic, when executed by a processor, operable to receive, over a network, first data related to the operation of a mail processing device at one of a plurality of mail processing sites, wherein each of the plurality of mail processing sites is associated with a database accessible over the network, store the first data in a database associated with the mail processing site of the mail processing device, receive, over the network, second data identifying filter criteria for the first data, filter, using a processor, the first data with the second data, generate, using a processor, a report based on the filtered first data, and communicate the report over the network.
- In certain embodiments, a method for analyzing performance data associated with a mail processing device includes receiving, over a network, first data related to the operation of a mail processing device at one of a plurality of mail processing sites, wherein each of the plurality of mail processing sites is associated with a database accessible over the network, storing the first data in a database associated with the mail processing site of the mail processing device, receiving, over the network, second data identifying filter criteria for the first data, filtering, using a processor, the first data with the second data, generating, using a processor, a report based on the filtered first data, and communicate the report over the network.
- Certain embodiments of the present disclosure may provide one or more technical advantages. A technical advantage of an embodiment includes providing an enterprise with the ability to automate collection of performance data from mail processing devices, or from a mail services vendor's database, to dynamically manipulate the performance data with filter criteria, to supplement the performance data with data collected from other sources, and to generate reports from the manipulated performance data. Additionally, the system may allow the enterprise to identify maintenance issues in mail processing devices, train and evaluate operators and managers, track mail processing costs, and otherwise use mail processing device performance data to improve enterprise mail processing.
- Certain embodiments of the present disclosure may include some, all, or none of the above advantages. One or more other technical advantages may be readily apparent to those skilled in the art from the figures, descriptions, and claims included herein.
- To provide a more complete understanding of the present invention and the features and advantages thereof, reference is made to the following description taken in conjunction with the accompanying drawings, in which:
-
FIG. 1 illustrates a block diagram of an embodiment of a system for analyzing the performance of mail processing devices; -
FIG. 2 illustrates an embodiment of a database comprising a table of data associated with the performance of mail processing devices; -
FIG. 3 illustrates a flow chart of an embodiment of a method for processing data associated with the performance of mail processing devices; -
FIGS. 4A-B illustrate embodiments of graphical user interfaces; and -
FIGS. 5A-C illustrate embodiments of reports generated by the system. - Embodiments of the present invention and its advantages are best understood by referring to
FIGS. 1 through 5 of the drawings, like numerals being used for like and corresponding parts of the various drawings. -
FIG. 1 illustrates a block diagram of an embodiment of asystem 100 for analyzing the performance ofmail processing devices 108. According to an embodiment of the present disclosure,system 100 includesnetwork 102 andenterprise 104. Enterprise 104 may include a number ofmail processing devices 108 at one or more mail processing sites 110, one ormore clients 112, and one or more reporting modules 114 comprisingmemory 116, database 118, processor 120, and interface 122. In certain embodiments,system 100 further includes mailservices vendor module 106. Mailservices vendor module 106 may comprisememory 124,database 126,processor 128, andinterface 130. In an embodiment,mail processing devices 108, reporting modules 114, mailservices vendor module 106, andclients 112 are communicatively coupled tonetwork 102. - Enterprise 104 includes a plurality of
mail processing devices 108 at one or more mail processing sites 110 and one or more reporting modules 114, each reporting module 114 including database 118 associated with a mail processing site 110. For example,database 118 a ofreporting module 114 a may be associated withmail processing site 110 a.Mail processing devices 108 may record first data related to the operation ofmail processing devices 108 and communicate the first data overnetwork 102. Other components ofsystem 100, for example, mailservices vendor module 106 and/or reporting modules 114 may receive and store first data.Clients 112 may communicate second data that identifies filtering criteria for first data overnetwork 102. In an embodiment,reporting module 114 a receives first data related tomail processing devices 108 atmail processing site 110 a associated withdatabase 118 a ofreporting module 114 a fromnetwork 102, and receives second data fromnetwork 102, filters the first data with the filtering criteria identified by the second data, generates a report based on the filtered first data, and communicates the report overnetwork 102. In an embodiment, mailservices vendor module 106 receives first data fromnetwork 102 and reporting modules 114 access first data fromnetwork 102 through mailservices vendor module 106. In another embodiment, reporting modules 114 receive first data fromnetwork 102 without using mailservices vendor module 106. - According to certain embodiments of the present disclosure,
system 100 providesenterprise 104 with the ability to automate collection of performance data (e.g., first data) frommail processing devices 108, or from a mail services vendor'sdatabase 126, to dynamically manipulate the performance data with filter criteria (e.g., second data), to supplement the performance data with data collected from other sources, and to generate reports from the manipulated performance data. For example,enterprise 104 may develop custom reports to evaluatemail processing device 108, operator, manager, and/or maintenance performance based on data collected atmail processing devices 108. Additionally,system 100 may allowenterprise 104 to identify maintenance issues inmail processing devices 108, train and evaluate operators and managers, track mail processing costs, and otherwise usemail processing device 108 performance data to improveenterprise 104 mail processing. -
Network 102 represents any suitable network operable to facilitate communication between components ofsystem 100, such asmail processing devices 108, mailservices vendor module 106, reporting module 114, andclients 112.Network 102 may include any interconnecting system capable of transmitting audio, video, electrical signals, optical signals, data, messages, or any combination of the preceding.Network 102 may include all or a portion of a public switched telephone network (PSTN), a public or private data network, a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a local, regional, or global communication or computer network, such as the Internet, a wireline or wireless network, an enterprise intranet, or any other suitable communication link, including combinations thereof, operable to facilitate communication between the components. - Enterprise 104 represents an entity that operates mail processing devices. Enterprise 104 may refer to a financial institution, such as a bank, however,
enterprise 104 represents any suitable type of entity in any suitable industry. Enterprise 104 may have different business units, or subdivisions, that handle different business activities, for example, mail processing. In an embodiment,enterprise 104 includes one or more mail processing sites 110 comprising a number ofmail processing devices 108, one ormore clients 112, and one or more reporting modules 114 comprising databases 118 associated with the one or more mail processing sites 110. In an embodiment, each mail processing site 110 is associated with a database 118 of a reporting module 114. For example, in the illustrated embodiment,mail processing site 110 a is associated withdatabase 118 a ofreporting module 114 a,mail processing site 110 b is associated withdatabase 118 b ofreporting module 114 a, and mail processing site 110 n is associated with database 118 n of reporting module 114 n, where N represents the number of mail processing sites 110. In another embodiment, each mail processing site 110 is associated with a database 118 of one or more reporting modules 114. For example reporting module 114 may comprise a plurality of databases 118, each database 118 associated with one or more mail processing sites 110. -
Mail processing device 108 represents a machine, device, or apparatus operable to perform mail processing functions. Mail processing functions include opening mail packaging, removing mail from mail packaging, scanning mail, imaging mail, capturing data from mail, transmitting mail withinenterprise 104, outsorting mail, inserting mail into mail packaging, packaging mail, applying postage to mail, and/or any other processing involved in transmitting or receiving mail. Mail represents any tangible item that may be sent through mail services such as the United States Postal Service, the United Parcel Service, Federal Express, DHL, or any other mail services provider.Mail processing devices 108 include mail openers, mail extractors, mail sorters, mail joggers, payment processing equipment, mail inserters, mail sealers, tabbers, paper folders, imaging devices, scanning devices, data capture devices, and/or any other device, machine, or apparatus operable to automate processing involved in transmitting or receiving mail. The items processed bymail processing devices 108 may be referred to as articles. Articles include envelopes, documents, bills, checks, payment information, or other items that may be mailed to, or mailed from,enterprise 104. In an embodiment,mail processing devices 108 are equipped to record and/or communicate data related to the operation ofmail processing devices 108.Mail processing devices 108 may be located at mail processing sites 110 inenterprise 104. Mail processing site 110 represents a location wheremail processing devices 108 operate. -
Clients 112 represent entities that communicate data, such as filtering data (e.g., second data), tosystem 100.Clients 112 may further be operable to receive reports generated bysystem 100. In particular embodiments,clients 112 represent general or special-purpose computers communicating with software applications capable of performing the above-described operations. Additionally, in particular embodiments,client 112 may include one or more processors operable to execute computer logic and/or software encoded on non-transitory tangible media that performs the described functionality.Clients 112 may include, but are not limited to, laptop computers, desktop computers, personal digital assistants (PDAs), mobile phones, tablets, and/or portable media players. In some embodiments,client 112 comprises one or more of a general-purpose personal computer (PC), a Macintosh, a workstation, a Unix-based computer, a server computer, or any suitable processing device.Client 112 may also include one or more computer input devices, such as a keyboard, trackball, or a mouse, and/or one or more Graphical User Interfaces (GUIs), through which a user may interact with the logic operating on a processor communicating withclient 112. In general,client 112 includes any appropriate combination of hardware, software, and/or encoded logic suitable to perform the described functionality.Clients 112 may couple to network 102 through a dedicated wired or wireless connection, or may connect to network 102 only as needed to receive, transmit, or otherwise execute applications. In certain embodiments,clients 112 may share elements and/or functionality with other components ofsystem 100, for example, when a software application operates on a component ofsystem 100 and communicates and receives data fromclient 112. AlthoughFIG. 1 illustrates, for purposes of example, a particular number and type ofclients 112, alternative embodiments ofsystem 100 may include any appropriate number and type ofclients 112, depending on the particular configuration ofsystem 100. - In an embodiment,
client 112 communicates second data overnetwork 102, which includes criteria for filtering first data related to the operation ofmail processing devices 108. Second data may identify a subset of one or more categories of first data. For example, second data may identify the subset of operators at a particular site 110 who had jam clear rates greater than 15 seconds.Client 112 may communicate second data through a graphical user interface (GUI), which may be part of an application running onclient 112 or on reporting module 114. Examples of GUIs for communicating second data are described in more detail below with respect toFIGS. 4A-B . - Reporting modules 114 represent any suitable component of
system 100 that facilitates receiving, storing, filtering, and/or communicating data. Reporting modules 114 may also be operable to generate reports based on filtered data. In some embodiments, reporting modules 114 may execute any suitable operating system such as IBM's zSeries/Operating System (z/OS), MS-DOS, PC-DOS, MAC-OS, WINDOWS, a .NET environment, UNIX, OpenVMS, or any other appropriate operating system, including future operating systems. The functions of reporting modules 114 may be performed by any suitable combination of one or more servers or other components at one or more locations. In an embodiment where reporting modules 114 are servers, the server may be a private server, and the server may be a virtual or physical server. Additionally, reporting modules 114 may include any suitable component that functions as a server. - In the illustrated embodiment, reporting modules 114 includes
memory 116, database 118, processor 120, and interface 122.Memory 116 represents any device operable to store, either permanently or temporarily, data, operational software, or other information forprocessor 128.Memory 116 includes any one or a combination of volatile or non-volatile local or remote devices suitable for storing information. For example,memory 116 may include random access memory (RAM), read only memory (ROM), magnetic storage devices, optical storage devices, semiconductor storage devices, or any other suitable information storage device or a combination of these devices.Memory 116 may include any suitable information for use in the operation of reporting module 114.Memory 116 may include some or all of database 118. Database 118 represents one or more databases operable to receive, store, filter, and/or communicate data associated withmail processing devices 108. In certain embodiments, each database 118 is associated with a mail processing site 110 and stores data related to the performance ofmail processing devices 108 at the mail processing site 110. - Processor 120 represents any computing device configured to control the operation of reporting modules 114. Processor 120 may comprise one or more processors and may be a programmable logic device, a microcontroller, a microprocessor, any suitable processing device, or any suitable combination of the preceding. Processor 120 includes any hardware and/or software that operates to control and process information received by reporting module 114. In an embodiment, processor 120 communicatively couples to
memory 116, database 118, and interface 122 and controls the operation of reporting module 114. - Interface 122 represents any device operable to receive input, send output, process the input and/or output and/or performs other suitable operations for reporting modules 114. Interface 122 includes any port or connection, real or virtual, including any suitable hardware and/or software, including protocol conversion and data processing capabilities, to communicate through
network 102 that allows reporting modules 114 to exchange information with components ofsystem 100 overnetwork 102. In an embodiment, interface 122 may receive data relating to the operation ofmail processing devices 108 fromnetwork 102. - Mail
services vendor module 106 represents any suitable component ofsystem 100 that facilitates receiving, storing, filtering, and/or communicating first data. In some embodiments, mailservices vendor module 106 may execute any suitable operating system such as IBM's zSeries/Operating System (z/OS), MS-DOS, PC-DOS, MAC-OS, WINDOWS, a .NET environment, UNIX, OpenVMS, or any other appropriate operating system, including future operating systems. The functions of mailservices vendor module 106 may be performed by any suitable combination of one or more servers or other components at one or more locations. In an embodiment where mailservices vendor module 106 is a server, the server may be a private server, and the server may be a virtual or physical server. Additionally, mailservices vendor module 106 may include any suitable component that functions as a server. - In the illustrated embodiment, mail
services vendor module 106 includesmemory 124,database 126,processor 128, andinterface 130.Memory 124 represents any device operable to store, either permanently or temporarily, data, operational software, or other information forprocessor 128.Memory 124 includes any one or a combination of volatile or non-volatile local or remote devices suitable for storing information. For example,memory 124 may include RAM, ROM, magnetic storage devices, optical storage devices, semiconductor storage devices, or any other suitable information storage device or a combination of these devices.Memory 124 may include any suitable information for use in the operation of mailservices vendor module 106.Memory 124 may include some or all ofdatabase 126.Database 126 represents one or more databases operable to receive, store, filter, and/or communicate data associated withmail processing devices 108. -
Processor 128 represents any computing device configured to control the operation of mailservices vendor module 106.Processor 128 may comprise one or more processors and may be a programmable logic device, a microcontroller, a microprocessor, any suitable processing device, or any suitable combination of the preceding.Processor 128 includes any hardware and/or software that operates to control and process information received by mailservices vendor module 106. In an embodiment,processor 128 communicatively couples tomemory 124,database 126, andinterface 130 and controls the operation of mailservices vendor module 106. -
Interface 130 represents any device operable to receive input, send output, process the input and/or output and/or performs other suitable operations for mailservices vendor module 106.Interface 130 includes any port or connection, real or virtual, including any suitable hardware and/or software, including protocol conversion and data processing capabilities, to communicate throughnetwork 102 that allows mailservices vendor module 106 to exchange information with components ofsystem 100 overnetwork 102. In an embodiment,interface 130 may receive data relating to the operation ofmail processing devices 108 fromnetwork 102. - Components of
system 100 may include logic. Logic performs the operation of the component, for example, logic executes instructions to generate output from input. Logic may include hardware, software, and/or other logic. Logic may be encoded in one or more non-transitory, tangible media, such as a computer-readable medium or any other suitable tangible medium, and may perform operations when executed by a computer. Certain logic, such as a processor, may manage the operation of a component. - In an embodiment of operation, reporting modules 114 receive first data from
network 102 communicated by one or moremail processing devices 108 and/or mailservices vendor module 106, receives second data fromnetwork 102 communicated by one ormore clients 112, filters the first data with the second data, generates one or more reports based on the filtered first data, and communicates the one or more reports overnetwork 102.Clients 112 may receive the reports fromnetwork 102, andenterprise 104 may use the reports to evaluatemail processing device 108, operator, and/or manager performance. In certain embodiments,enterprise 104 uses reports to identify maintenance issues relating tomail processing devices 108. In an embodiment, mailservices vendor module 106 receives first data fromnetwork 102 and reporting modules 114 access first data fromnetwork 102 through mailservices vendor module 106. In another embodiment, reporting modules 114 receive first data fromnetwork 102 without using mailservices vendor module 106. - Modifications, additions, or omissions may be made to
system 100.System 100 may include more, fewer, or other components. Any suitable component ofsystem 100 may include a processor, interface, logic, memory, and/or other suitable element. In certain embodiments, first data may originate atmail processing devices 108 and/or mailservices vendor module 106. -
FIG. 2 illustrates an embodiment of a database comprising table 200 of data associated with the operation ofmail processing devices 108. In the illustrated embodiment, table 200 includes columns of data categories such asdate column 202,job name column 204,job type column 206,job time column 208,operator column 210,manager column 212,device column 214,customer column 216,product column 218,input column 220,output column 222,outsort column 224, reunitecolumn 226, rejectscolumn 228,jams column 230, jamclear rate 232, and deviceidle time column 234. - In an embodiment of operation,
system 100 stores first data related to the operation ofmail processing devices 108 at mail processing site 110 in table 200 in database 118 associated with the mail processing site 110. First data may relate to performance data ofmail processing devices 108, operators, or managers.Mail processing device 108 performance data includes jam rate, reunite rate, reject rate, outsort rate, and/or output rate. Operator performance data includes jam clear rate and/or device idle time. Reporting modules 114 may filter the data in table 200, and/or generate reports based on the data in table 200.System 100 may use data in table 200 to evaluate the performance ofmail processing device 108, an operator, and/or a manager. For example,mail processing device 108 may record the number of articles processed bymail processing device 108 and the total number of jams during that period of time, but may not perform the calculation to determine the number of articles processed per jam (i.e., a jam rate). In certain embodiments,system 100 uses data frommail processing devices 108 to calculate additional data that may be useful for evaluatingmail processing device 108, operator, and/or manager performance. For example, calculated data may include rates (e.g., output/unit time), performance metrics (e.g., jams/operator), or any other performance data calculated using data frommail processing devices 108. The first data may include calculated data and may be filtered by second data. -
Date column 202 provides the dates that mailprocessing devices 108 processed particular batches of articles, referred to as jobs. Jobs may be associated with particular articles, customers, types of mail processing, or other category.Job name column 204 provides identification codes for particular jobs.Job type column 206 provides identification codes for particular categories of jobs.Job time column 208 provides the timemail processing device 108 operated processing a particular job.Operator column 210 provides identification codes for particular operators ofmail processing devices 108.Manager column 212 provides identification codes for particular managers that supervised operators that controlledmail processing devices 108.Device column 214 provides identification codes for particularmail processing devices 108.Customer column 216 provides identification codes for particular categories of products processed bymail processing devices 108. In an embodiment, customer identification codes identify entities that sponsor the processing of particular products bymail processing devices 108.Product column 218 provides identification codes for particular categories of articles processed bymail processing devices 108. Products may be associated with particular articles, customers, types of mail processing, or other category. -
Input column 220 provides the number of articles input intomail processing devices 108.Output column 222 provides the number of articles successfully processed bymail processing device 108. In an embodiment, output excludes outsorts, reunites, and rejects.Outsort column 224 provides the number of articles, such as envelopes or packages, that could not be opened bymail processing device 108.Mail processing device 108 may receive pre-defined criteria that determine what articles mailprocessing device 108 should outsort. For example, criteria may include article overlap inmail processing device 108, articles are too close together, article has incorrect dimensions, article has a change in thickness,mail processing device 108 error, metal detected in an article, damage to an article, or other suitable criteria. Reunitecolumn 226 provides the number of articles, such as documents, that were not fully extracted from an envelope or package bymail processing device 108.Reject column 228 provides the number of articles, such as documents, that could not be processed bymail processing device 108 because of the orientation of the article, an error in the article, an error reading the article, and/or an error imaging the article. -
Jam column 230 provides the number of obstructions that occurred inmail processing device 108 during operation. A jam may result from a malfunction ofmail processing device 108, an operator error, or a defect in an article being processed. In certain embodiments,mail processing devices 108 shut down until a jam is cleared. A jam may include an article getting caught inmail processing device 108 and/or a portion ofmail processing device 108 that needs to be reset. Formail processing device 108 to operate efficiently, jams need to be cleared frommail processing device 108. In certain embodiments,mail processing device 108 operators clear jams frommail processing device 108. Jamclear rate column 232 indicates the amount of time taken to clear a jam frommail processing device 108. In an embodiment, jam clear rate represents an average time taken to clear jams frommail processing device 108 over a period of time or number of articles processed. Deviceidle time column 234 indicates the amount of timemail processing device 108 was turned on but not processing articles. In an embodiment, remaining idle time excludes the time between turningmail processing device 108 on and whenmail processing device 108 is able to process articles (i.e., the startup time of mail processing device 108). - Table 200 may further include data such as type of mail processing device, outsort rate, jam rate, jam time, reunite rate, reject rate, output rate, effective throughput, stops, total device time, or other type of data related to mail processing device operation useful to measure device, operator, and/or manager performance. Device type represents a category of
mail processing devices 108. Outsort rate represents a measurement of the number of outsorts occurring inmail processing device 108. Outsort rate may include articles processed per outsort, a timemail processing device 108 operates per outsort, or any other suitable metric for monitoring the occurrence of outsorts inmail processing device 108. In an embodiment, outsort rate is expressed as the percentage of articles handled bymail processing device 108 that were outsorts. Jam rate represents a measurement of the number of jams occurring inmail processing device 108. Jam rate may include articles processed per jam, timemail processing device 108 operates per jam, or any other suitable metric for monitoring the occurrence of jams inmail processing device 108. Jam time represents the total amount of time amail processing device 108 spent jammed. Reunite rate represents a measurement of the number of reunites occurring inmail processing device 108. Reunite rate may include articles processed per reunite, timemail processing device 108 operates per reunite, or any other suitable metric for monitoring the occurrence of reunites inmail processing device 108. In an embodiment, reunite rate is expressed as the percentage of articles handled bymail processing device 108 that were reunites. Reject rate represents a measurement of the number of rejects occurring inmail processing device 108. Reject rate may include articles processed per reject, timemail processing device 108 operates per reject, or any other suitable metric for monitoring the occurrence of rejects inmail processing device 108. Output rate represents a measurement of the number of articles successfully processed bymail processing device 108. Output rate may include articles processed per unit time of mail processing device operation, for example, per hour. Effective throughput represents a measure of the number of articles successfully processed by amail processing device 108. In an embodiment, effective throughput represents the number of articles successfully processed per hour. Stops represent the number of times amail processing device 108 stopped processing articles. Total device time represents the total amount of time a mail processing device operated. - Row 236 represents an embodiment of filtered first data that includes data related to a particular mail processing job. Row 236 includes the date the job was processed (1/1/11), the job name (0001), the job type (Job 1), the amount of time
mail processing device 108 operated to process the job (02:53:58), the operator who processed the job (Oper1), the manager who supervised the operator (Manag1), the particularmail processing device 108 that processed the job (Dev1), the product involved in the mail processing job (Prod1), the number of articles input intomail processing device 108 as part of the job (27,264), the number of articles successfully processed bymail processing device 108 as part of the job (26,235), the number of articles that were outsorts (1029), the number of articles that were reunites (266), the number of articles that were rejects (612), the number of times mailprocessing device 108 jammed during the job (42), the average time it took the operator to clear the jams from mail processing device 108 (00:00:14), and the amount of timemail processing device 108 was turned on, but not processing, during the job (00:06:32). Row 236 could include more, fewer, or other data columns. In certain embodiments, the data columns included inrow 236 are identified from second data received fromclients 112. - Modifications, additions, or omissions may be made to table 200. Table 200 may include more, fewer, or different column fields. Table 200 may include any data useful in monitoring the performance of
mail processing device 108, operator, or operator manager performance. Table 200 may also include any combination of column fields, any number of rows, or any number of columns. -
FIG. 3 illustrates a flow chart of an embodiment ofmethod 300 for processing data associated with the operation of mail processing devices.Method 300 begins atstep 302. Atstep 304, reporting module 114, receives, overnetwork 102, first data related to the operation ofmail processing devices 108, wherein each of the plurality of mail processing sites 110 is associated with a database 118 of reporting modules 114 accessible overnetwork 102. In an embodiment, mailservices vendor module 106 and/ormail processing device 108 communicates the first data to reporting module 114 associated with the mail processing site 110 of themail processing device 108 that originated the data. First data may indicate performance metrics ofmail processing devices 108. Atstep 306, reporting module 114 stores the first data in database 118 associated with the mail processing site 110 of themail processing device 108 that originated the data. - At
step 308, reporting module 114 receives, overnetwork 102, second data identifying filter criteria for the first data. In an embodiment, reporting module 114 receives second data from one ormore clients 112. Atstep 310, reporting module 114 filters, using processor 120, the first data with the second data. Atstep 312, reporting module 114 generates, using processor 120, a report based on the filtered first data. Atstep 314, reporting module 114 communicates the report overnetwork 102.Method 300 ends atstep 316. - Modifications, additions, or omissions may be made to
method 300. The method may include more, fewer, or other steps. Additionally, steps may be performed in any suitable order. Any suitable component ofsystem 100 may perform one or more steps ofmethod 300. For example, in an embodiment,mail services vendor 106 may perform one or more of steps described as being performed by reporting module 114, anddatabase 126 may perform one or more of the steps described as being performed by database 118. -
FIGS. 4A-B illustrate embodiments of graphical user interfaces (GUIs) for communicating second data.FIG. 4A illustrates an embodiment ofGUI 400. In the embodiment,client 112 may select a date range, one or more manager names, and/or one or more operator names to include in a report.Client 112 may further select Individual Operator Reports and/or Summary Reports that include categories of data such as product, client, job type, and device.GUI 400 further providesclient 112 other reporting options such as Product Reports by Half Hour, Output Volumes by Month, 14 Day Chart, Product Report by Date, Employee Performance Management System Reports, and an option to view More Reports. -
FIG. 4B illustrates an embodiment ofGUI 402. In the embodiment,client 112 can select a date range, customer type, customer, product, job type, device type, and device to include in a report.Client 112 may further select whether to include various data such as outsort rates, jam rates, reunite rates, reject rates, and/or output rates.GUI 402 further providesclient 112 reporting options that include Daily Report, Summary, Jam Clear Rate Report, and Remaining Idle Time Report. In an embodiment,GUI 402 allowsclient 112 to export data used to create a report to a Microsoft Excel file. - Modifications, additions, or omissions may be made to
interfaces Interfaces GUIs system 100. -
FIGS. 5A-C illustrate embodiments of generated reports of first data filtered by second data.FIG. 5A illustratesreport 500 which displays data related tomail processing device 108 performance.Report 500 includes input, output, effective throughput, vendor effective throughput, jam rate, average remaining idle time, jam clear rate, stops, jams, run time, jam time, idle time, and total device time for a number of mail processing devices at a particular mail processing site over a particular date range.Enterprise 104 may usereport 500 to evaluatemail processing device 108 performance, identify maintenance issues inmail processing devices 108, or other purpose. -
FIG. 5B illustratesreport 502 which displays data related to operator performance.Report 502 includes input, output, effective throughput, vendor effective throughput, jam rate, average remaining idle time, jam clear rate, stops, jams, run time, jam time, idle time, and total device time for a particular operator over a particular date range.Report 502 further includes the operator's manager, the particular devices operated by the operator, the products processed by the operator on the particular devices.Enterprise 104 may usereport 502 to evaluate operator performance, compare operator performance, evaluate site 110 performance, or other purpose. -
FIG. 5C illustratesreport 504 which displays data related to manager performance.Report 504 includes input, output, effective throughput, vendor effective throughput, jam rate, average remaining idle time, jam clear rate, stops, jams, run time, jam time, idle time, and total device time for a particular operator over a particular date range.Report 504 further includes a number of managers of a particular mail processing site 110, the particularmail processing devices 108 operated under the supervision of the managers, and a summary ofmail processing device 108 performance at site 110.Enterprise 104 may usereport 504 to evaluate manager performance, comparing manger performance, evaluating site 110 performance, or other purpose. - Modifications, additions, or omissions may be made to
reports Reports Reports Reports Reports - Although the present disclosure has been described with several embodiments, diverse changes, substitutions, variations, alterations, and modifications may be suggested to one skilled in the art, and it is intended that the disclosure encompass all such changes, substitutions, variations, alterations, and modifications as fall within the spirit and scope of the appended claims.
Claims (21)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/196,142 US9317821B2 (en) | 2011-08-02 | 2011-08-02 | System for analyzing device performance data |
US15/000,345 US9613385B2 (en) | 2011-08-02 | 2016-01-19 | System for analyzing device performance data |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/196,142 US9317821B2 (en) | 2011-08-02 | 2011-08-02 | System for analyzing device performance data |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/000,345 Continuation US9613385B2 (en) | 2011-08-02 | 2016-01-19 | System for analyzing device performance data |
Publications (2)
Publication Number | Publication Date |
---|---|
US20130036125A1 true US20130036125A1 (en) | 2013-02-07 |
US9317821B2 US9317821B2 (en) | 2016-04-19 |
Family
ID=47627627
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/196,142 Active 2033-01-04 US9317821B2 (en) | 2011-08-02 | 2011-08-02 | System for analyzing device performance data |
US15/000,345 Active US9613385B2 (en) | 2011-08-02 | 2016-01-19 | System for analyzing device performance data |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/000,345 Active US9613385B2 (en) | 2011-08-02 | 2016-01-19 | System for analyzing device performance data |
Country Status (1)
Country | Link |
---|---|
US (2) | US9317821B2 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160155008A1 (en) * | 2012-01-17 | 2016-06-02 | Lockheed Martin Corporation | Remote recognition processing system and method |
Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4863037A (en) * | 1986-09-05 | 1989-09-05 | Opex Corporation | Apparatus for the automated processing of bulk mail and the like |
US5077694A (en) * | 1988-12-16 | 1991-12-31 | Pitney Bowes Inc. | Distribution mailing system having a control database for storing mail handling categories common to the databases of selected mailer stations |
US5651445A (en) * | 1986-09-05 | 1997-07-29 | Opex Corporation | Apparatus for the automated processing of bulk mail having varied characteristics |
US20020169519A1 (en) * | 2000-07-27 | 2002-11-14 | Pitney Bowes Incorporated | Reply mail processing system |
US6697500B2 (en) * | 2002-03-11 | 2004-02-24 | Bowe Bell + Howell Postal Systems Company | Method and system for mail detection and tracking of categorized mail pieces |
US20060260989A1 (en) * | 2003-09-26 | 2006-11-23 | First Data Corporation | Mail processing system and method |
US20070204007A1 (en) * | 2006-02-16 | 2007-08-30 | Shahpour Ashaari | Centralized processing and management system |
US20110046775A1 (en) * | 2007-09-13 | 2011-02-24 | Lockheed Martin Corporation | Facility Wide Mixed Mail Sorting and/or Sequencing System and Components and Methods Thereof |
US20130031183A1 (en) * | 2011-07-26 | 2013-01-31 | Socialmail LLC | Electronic mail processing and publication for shared environments |
US20140096477A1 (en) * | 2012-10-05 | 2014-04-10 | Pitney Bowes Inc. | Method and system for identifying/outsorting improperly wrapped envelopes in a mailpiece fabrication system |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080291486A1 (en) * | 2007-05-22 | 2008-11-27 | Bowe Bell + Howell Company | Intelligent document composition for mail processing |
US20090070338A1 (en) * | 2007-09-07 | 2009-03-12 | Bowe Bell + Howell Company | Centralized production management for measuring mail industry processing performance |
US8311668B2 (en) * | 2009-10-19 | 2012-11-13 | Bell And Howell, Llc | Automatic feeder control setup based on client mailstream |
US20130036130A1 (en) | 2011-08-02 | 2013-02-07 | Bank Of America Corporation | System for Analyzing Device Performance Data |
-
2011
- 2011-08-02 US US13/196,142 patent/US9317821B2/en active Active
-
2016
- 2016-01-19 US US15/000,345 patent/US9613385B2/en active Active
Patent Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4863037A (en) * | 1986-09-05 | 1989-09-05 | Opex Corporation | Apparatus for the automated processing of bulk mail and the like |
US5651445A (en) * | 1986-09-05 | 1997-07-29 | Opex Corporation | Apparatus for the automated processing of bulk mail having varied characteristics |
US5077694A (en) * | 1988-12-16 | 1991-12-31 | Pitney Bowes Inc. | Distribution mailing system having a control database for storing mail handling categories common to the databases of selected mailer stations |
US20020169519A1 (en) * | 2000-07-27 | 2002-11-14 | Pitney Bowes Incorporated | Reply mail processing system |
US6697500B2 (en) * | 2002-03-11 | 2004-02-24 | Bowe Bell + Howell Postal Systems Company | Method and system for mail detection and tracking of categorized mail pieces |
US20060260989A1 (en) * | 2003-09-26 | 2006-11-23 | First Data Corporation | Mail processing system and method |
US20070204007A1 (en) * | 2006-02-16 | 2007-08-30 | Shahpour Ashaari | Centralized processing and management system |
US20110046775A1 (en) * | 2007-09-13 | 2011-02-24 | Lockheed Martin Corporation | Facility Wide Mixed Mail Sorting and/or Sequencing System and Components and Methods Thereof |
US20130031183A1 (en) * | 2011-07-26 | 2013-01-31 | Socialmail LLC | Electronic mail processing and publication for shared environments |
US20140096477A1 (en) * | 2012-10-05 | 2014-04-10 | Pitney Bowes Inc. | Method and system for identifying/outsorting improperly wrapped envelopes in a mailpiece fabrication system |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160155008A1 (en) * | 2012-01-17 | 2016-06-02 | Lockheed Martin Corporation | Remote recognition processing system and method |
US9690999B2 (en) * | 2012-01-17 | 2017-06-27 | Lockheed Martin Corporation | Remote recognition processing system and method |
US10147011B2 (en) * | 2012-01-17 | 2018-12-04 | Lockheed Martin Corporation | Remote recognition processing system and method |
Also Published As
Publication number | Publication date |
---|---|
US9613385B2 (en) | 2017-04-04 |
US9317821B2 (en) | 2016-04-19 |
US20160140680A1 (en) | 2016-05-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11403696B2 (en) | Client centric viewer | |
US8078518B2 (en) | ATM exception balancing system | |
EP2034430A1 (en) | Centralized production management for measuring mail industry processing performance | |
KR20150113036A (en) | Automated teller machine transaction blocking | |
US11803809B1 (en) | Fulfillment management implementing physical task interaction | |
US20140006060A1 (en) | System and method for processing data related to worksite analyses | |
CA2711935A1 (en) | Method and system for auditing internal controls | |
US20140330718A1 (en) | Paper payment receipt, processing and payment failure analytics | |
US9613385B2 (en) | System for analyzing device performance data | |
US10157091B2 (en) | Evaluating and servicing problematic cash-handling machines | |
US20140095379A1 (en) | Payments Perfection And Processing System | |
US20130036130A1 (en) | System for Analyzing Device Performance Data | |
US20140330708A1 (en) | Paper check processing in connection with bill pay requests | |
US20140330715A1 (en) | Granular, user-accesible paper payment processing indicators | |
US8719048B1 (en) | Method and apparatus for accurate estimation and disbursement in a reverse distribution environment | |
US20140046857A1 (en) | System, Method, and Software for Enterprise-Wide Complaint Aggregation | |
Mustika et al. | Analysis of Accounting Information Systems in the Cash Flow Expenditure Cycle at UD | |
US20140330714A1 (en) | Paper payment receipt, processing and real time communication with payor | |
US20140330716A1 (en) | Paper payment processing analytics | |
US20140330717A1 (en) | Paper payment receipt, processing and failure remediation | |
Mangmang | Development and Implementation of Point of Sale System (POS): Profitability Measurement for Retail Business | |
CN107533686A (en) | Method and system for monitoring business operation | |
US20140278753A1 (en) | System and method for identifying mergers and acquisitions | |
TWM625235U (en) | Intelligent credit loan evaluating system | |
US20230196313A1 (en) | Systems and methods for artificial intelligence/machine learning centric lockbox document processing |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: BANK OF AMERICA CORPORATION, NORTH CAROLINA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:PINJANI, NIDHI;REEL/FRAME:026686/0324 Effective date: 20110727 |
|
AS | Assignment |
Owner name: BANK OF AMERICA CORPORATION, NORTH CAROLINA Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNEE'S ADDRESS PREVIOUSLY RECORDED ON REEL 026686 FRAME 0324. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNEE'S ADDRESS IS: HEARST TOWER, 214 N. TRYON STREET NC1-027-20-05;ASSIGNOR:PINJANI, NIDHI;REEL/FRAME:026694/0914 Effective date: 20110727 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |