User interface for a customized personalization document printer of an instant issuance system

A remote user interface (RUI) for a personalization document printer of an instant issuance system is provided. The RUI includes a printer functionality component and a server functionality component. The server functionality component is configured to allow, for example a user to control user authentication to use the printer, control print queues of the printer, control print workflows of the printer, control RUI configuration, control remote access to printer user functions and a print preview displaying an image of the customized personalization document with image data and personalization account data, control storage and rendering of data to be placed on a customized personalization document, lock and unlock access to supplies and/or personalization documents in the personalization document printer, access administrative functions, and provide quality assurance functions.

FIELD

This disclosure relates generally to instant issuance systems for the issuance of customizable personalization documents. More particularly, this description relates to a user interface for a personalization document printer of an instant issuance system.

BACKGROUND

Presently, a user can only access and interact with server functionality of an instant issuance system for issuing customized personalization documents via a terminal that may or may not be near a customized personalization document printer of the instant issuance system. Thus, when a user, such as a banker, would like to interact with server functionality, including controlling user authentication, print queues, access to printer user functions, etc., the user must find a terminal connected to the server that may or may not be close to the customized personalization document printer. Also, security concerns may arise as it is difficult for the instant issuance system to determine whether the user providing the print request via the terminal is the same person retrieving the customized personalization document from the customized personalization document printer.

Also, present instant issuance systems require that a server of the instant issuance system transmit both personalized account data and actual rendering data to the customized personalization document printer to initiate a print request. However, actual rendering data can be large as it may contain image data. Sending actual rendering data from the server to the customized personal document printer may require additional network bandwidth for the transmission to be processed and centralizes much of the data used for issuing a customized personalization document at the server of the instant issuance system.

SUMMARY

This application is directed to a user interface for a personalization document printer of an instant issuance system. The user interface allows a user to interact with printer functionality of the personalization document printer and to interact with server functionality associated with a server of the instant issuance system.

That is, the embodiments described herein provide a user interface that allows a user, among other features, to control printer functionality such as, for example, (displaying customized personalization document supply information, printer option settings, progress information for a current or pending print job, a print preview that can display, for example, a front and/or back image of the customized personalization document with image data and personalization account data, etc.) and to control server functionality associated with a server connected to the printer (i.e. controlling: user authentication; print queues; print workflows; remote user interface configuration; remote access to printer user functions and front and back print preview of personalized information on a personalization document, storage and rendering of data to be placed on a personalization document; locking and unlocking access to supplies and/or personalization documents in the personalization document printer; access to administrative functions (e.g., access to sensitive print logs; activity logs; ability to assign the number of authentications per function; ability to reprint personalization documents; quality assurance (QA) functions such as, for example, rejecting a card once it has been printed, reprinting a personalization document, and informing the central server; etc.); etc). All these actions then update the central server in order to track activities, inventory and central reports.

An advantage of these features is additional security within the instant issuance system as users may now be required to authenticate themselves at the customized personalization document printer before the printer will print the customized personalization document. Also, the customized personalization document printer can provide dual authentication to allow a user to control and interact with certain server functionality, as well as any function that is configured to only be accessible by an administrator.

Another advantage of these features is speed and convenience, as the user can control and interact with printer functionality and system functionality, such as unlocking hoppers, gaining access to administration functions, QA functions, etc., directly from the customized personalization document without having to return to the terminal of the instant issuance system that may or may not be close to the printer. Also, these advantages allow print requests to be driven from any workstation (i.e., any terminal or customized personalization document printer).

A further advantage of these features is that an instant issuance system may be implemented at a lower cost, as a terminal of the instant issuance system does not need to be close to the customized personalization document printer.

The embodiments described herein also provide a personalization document printer of an instant issuance system that is capable of storing actual rendering data including image data such as, for example, card templates, logos, fonts, etc. and that is capable of merging the actual rendering data with personalized account data received to render images on a display of the customized personalization document printer of a customized personalization document to be printed. In these embodiments, resources, such as the driver for printing the customized personalization document, are accessed and interacted with directly from the customized personalization document printer as opposed to a terminal that connects to a server that in turn connects to the customized personalization document printer. This allows for greater system scalability (i.e. distributed processing of images) and lower network bandwidth requirements for the instant issuance system, as only personalized account data and rendering instruction data is sent to the customized personalization document printer.

In one embodiment, a remote user interface (RUI) for a customized personalization document printer of an instant issuance system is provided. The RUI includes a printer functionality component that is configured to allow a user to control a display of customized personalization document supply information, control printer option settings, control progress information for a current or pending print job, and control a print preview for displaying an image of the customized personalization document with image data and personalization account data. The RUI also includes a server functionality component that is configured to allow a user to control user authentication to use the printer, control print queues of the printer, control print workflows of the printer, control RUI configuration, control remote access to printer user functions and a print preview displaying an image of the customized personalization document with image data and personalization account data, control storage and rendering of data to be placed on a customized personalization document, lock and unlock access to supplies and/or personalization documents in the personalization document printer, access administrative functions, and provide quality assurance functions.

In another embodiment, a customized personalization document printer for an instant issuance system that allows a customized personalization document for a document holder to be issued while the document holder is present is provided. The printer includes a personalization component that is configured to perform a printing function on a customized personalization document. The printer also includes a network component that is configured to be connected to a server computer of the instant issuance system. Also, the printer includes a memory component that is configured to store a RUI. Further, the printer includes a processor that is configured to run the RUI. Moreover, the printer includes a display and an input device that are configured to allow a user to view and interact with the RUI. The RUI is configured to allow a user to interact with and control printer functionality of the printer and is configured to allow a user to interact with and control server functionality of the server computer.

In yet another embodiment, a system for issuing a customized personalization document for a document holder, while the document holder is present is provided. The system includes a server computer configured to receive a request to issue the customized personalization document for the document holder, wherein the request includes at least one of the document holder's name and background information indicating a background to be placed onto the personalization document, configured to generate personalized account data and rendering instruction data based on information provided in the request, and configured to transmit the personalized account data and the rendering instruction data. The system also includes a customized personalization document printer connected to the server computer via a network, the printer configured to receive the personalized account data and the rendering instruction data, configured to retrieve actual rendering data based on the rendering instruction data, and configured to merge the actual rendering data and the personalized account data into printing data. The printer includes a personalization component that is configured to perform a printing function on a customized personalization document. The printer also includes a network component that is configured to be connected to a server computer of the instant issuance system. Also, the printer includes a memory component that is configured to store a RUI. Further, the printer includes a processor that is configured to run the RUI. Moreover, the printer includes a display and an input device that are configured to allow a user to view and interact with the RUI. The RUI is configured to allow a user to interact with and control printer functionality of the printer and is configured to allow a user to interact with and control server functionality of the server computer.

In yet another embodiment, a method for issuing a customized personalization document for a document holder, while the document holder is present is provided. The method includes receiving, at a customized personalization document printer, personalized account data and rendering instruction data regarding a print request. Also, the method includes retrieving, at the customized personalization document printer, actual rendering data from a memory component of the customized personalization document printer based on the rendering instruction data received from the server computer. The method also includes merging, at the customized personalization document printer, the actual rendering data and the personalized account data to generate printing data. Further, the method includes printing, at the customized personalization document printer, the printing data onto a personalization document to create the customized personalization document while the document holder is present.

DETAILED DESCRIPTION

The embodiments provided herein are directed to instant issuance systems for the issuance of customizable personalization documents. Particularly, the embodiments herein provide a user interface for a personalization document printer of an instant issuance system.

One aspect of the invention enables a document holder to receive a customized personalization document from a financial institution while the document holder is present. The document holder may be initializing a new account, or may already have an existing account. The personalization instrument may be customized with a variety of background images. The images may be chosen from an image database, or may be a personal image provided by the document holder.

The personalization document may be printed while the document holder is at, for example, a bank branch location. The document holder or a user on behalf of the document holder enters his/her identification information and background selection into a terminal provided at the branch location. The information is processed and transmitted to a personalization document printer where the document holder receives his/her new customized personalization document.

The personalization document printer may be configured to perform a variety of print functions onto a customized personalization document including, for example, one or more of magnetic encoding, embossing, smart card programming, laser printing, cleaning, and laminating of a customized personalized document. Accordingly, one skilled in the art will understand that the term “print” or “printing” as described herein refers to performing one or more of the above mentioned print functions on a customized personalization document.

Customized personalization documents may include, but are not limited to, cards such as credit cards, debit cards, licenses, personal identification cards, calling cards, etc. and booklets such as passports, among other types of documents.

Turning now toFIG. 1, a block diagram of a system100for issuing a customized personalization card while a document holder is present is provided. WhileFIG. 1is directed to issuing a customized personalization card, in other embodiments, other customized personalization documents may be issued such as, for example, passports.

FIG. 1may be divided into three locations (i.e. a branch location110, a card customization center115and a financial institution data center120). The locations are for representative purposes only, and may be physically located together and/or remotely located from each other. Furthermore, there may be more or less than the three representative locations. For example, the server122and a financial institution card management system (FICMS)124may be at the same location.

The branch location110may include a terminal112and a plurality of personalization card printers116. WhileFIG. 1shows two card printers116, in other embodiments, the branch location110may include only one card printer116or three or more card printers116as required. The terminal112may display a terminal user interface (TUI) that prompts the document holder to select information that will be placed on the personalization card. In some embodiments, one or more of the personalization card printers116may display a remote user interface (RUI) that prompts a user, such as a banker, on behalf of the document holder to select which personalization document in the print queue to be printed and to confirm that the proper image and personalization account data is printed on the personalization card. The information may include the document holder's name and account information (e.g. account number) and the image for the personalization card background. The document holder's name entered in the TUI or RUI may be the name that appears on the personalization instrument. The background image may be selected from a database of approved background images. Images used as a background on a personalization instrument may be required to be approved by the issuing financial institution or an association (e.g. VISA™, MasterCard™, etc.).

In one embodiment, the document holder is able to upload a personal image at the terminal112or the card printer116. The image may be uploaded in a variety of ways (e.g. flash memory, CD ROM, DVD ROM, floppy disk, secure digital (SD) memory, network connection, etc.). The personal image may be required to be approved by the financial institution and/or a bank representative. The personal image may be scenery, a family member's picture, favorite sports team logo, etc. In some embodiments, the image can come from a server122.

Once the information from the card holder is input into the terminal112or one of the printers116, the information is transmitted to the server122. The information may be transmitted over the bank network of the branch location, or over some other network. The network may be a local area network (LAN), a wide area network (WAN), the Internet, etc. The server122processes the received information. In one embodiment, the server122may be, for example, a CardWizard™ eServer. The processing may include checking the received information for mistakes and inaccuracies. The processing may also include checking the document holder's name and account information against a database to verify the existence of the account. Once the server122completes processing the received information, the server122transmits the process information to FICMS124.

In one embodiment, the FICMS124generates a personal account number (PAN) and an expiration date of the personalization card. The FICMS124may also determine whether a personal image provided by the document holder is approved by the financial institution. The FICMS124then transmits the PAN and the expiration date back to the server122.

Based on the received PAN and expiration date, the server122may calculate a card verification value (CVV), a card verification value 2 (CVV2), and a personal identification number (PIN) offset value. The CVV and the PIN offset value may be encoded, for example, on a magnetic stripe of the personalization card. The CVV, the PIN offset value and the CVV2 may be used to verify the authenticity of the personalization instrument. Specifically, the CVV2 may be used by merchants to verify personalization instrument authenticity when the merchant does not have physical access to the personalization instrument (e.g. a purchase made over a telephone, a mail catalog order, the Internet, etc.).

The server122transmits personalized account data (i.e., the customer name, the CVV, the CVV2, the PIN offset value, the PAN, the expiration date, etc.) and rendering instruction data to the personalization card printer116. Rendering instruction data is data that instructs the personalization card printer116as to the type of rendering to be performed onto a customized personalization card114(i.e., the type of card template, the background image, the type of logos, the type of fonts, etc.). That is, the server122does not need to send the actual rendering data (i.e. the card template, the background image, the types of logos, the types of fonts, etc.) to the personalization card printer116, as the personalization card printer116has a memory component (not shown) that stores the actual rendering data.

An advantage of one or more of the personalization card printers116storing the actual rendering data is that it allows the system100to have greater scalability as the actual rendering data can be distributed amongst other customized printers (not shown) and does not have to be stored in the server122. Another advantage of having one or more personalization card printer116store the actual rendering data is that the network bandwidth requirements for transferring data between the server122and the particular personalization card printer116is reduced as large actual rendering data, such as image data, does not need to be transferred every time a print request is sent from the server122to the personalization card printer116. In some embodiments, each of the card printers116can store different actual rendering data so that different customized cards114can be issued by each of the card printers116. Furthermore, in these embodiments the server122is not required to store the different actual rendering data for all of the different renderings that can be printed onto the customized cards114.

The output from the personalization card printer116may be the customized personalization card114. The customized personalization card114may be instantly accessed by the document holder. This enables the document holder to leave the branch location110with the customized personalization card114, as opposed to waiting to receive a customized personalization card in the mail, or returning to the branch location110at a future date.

FIG. 2provides a block diagram of one embodiment of a personalization document printer200. The personalization document printer200can be used, for example, as the personalization card printer116shown inFIG. 1. The personalization document printer200includes a processor205electrically coupled to a memory storage component210, a personalization component215, a personalization document hopper220, a display225, an input device230and a network component235. As shown inFIG. 2, in some embodiments the personalization document printer200may include additional personalization document hoppers220B-220nand also may include a manual exception slot222. In some embodiments, a plurality of manual exception slots (not shown) is provided in the printer200. In some embodiments, the personalization document printer200may also include additional personalization components215B-215n. The additional document hoppers220B-220nand the additional personalization components215B-215nare also electrically coupled to the processor205. In one embodiment, the customized personalization printer200may be a high definition customized personalization document printer.

Each of the hoppers220and220B-220nis configured to allow multiple types of personalization documents to be loaded into the printer200and printed on by one or more of the personalization components215and215B-215n. In some embodiments, a user can manually feed a personalization document, that may not be stored in the hoppers220and220B-220n, into the manual exception slot222in order to be customized by the printer200. Each of the personalization components215and215B-215nprovide one or more of the following printing operations on a customized personalization document: magnetic encoding; embossing; smart card programming; cleaning; laminating; etc.

The network component235is configured to connect to a server in an instant issuance system such as the server122in the system100shown inFIG. 1. The network component can be configured to connect to the server via a LAN, WAN, the Internet, etc.

The memory storage component210is configured to store, among other data, actual rendering data and personalized account data that may be rendered and stored onto a customized personalization document. The memory component210is also configured to store cryptographic keys to authenticate communication between the printer200and a server, such as the server122in the system100shown inFIG. 1. In some embodiments, the memory component210is a flash memory storage component.

The display225and the input device230are configured to allow a user to interact with printer functionality and with server functionality associated with a server connected to the printer200via a remote user interface (RUI)201that is stored in the memory component210and run by the processor205. Also, in some embodiments, the display225and the input device230are combined into a touch screen display. This touch screen display may use a liquid crystal display (LCD); however, other types of displays may also be used. Embodiments of the RUI201are described in more detail below with respect toFIGS. 4-25.

The user interface allows a user to interact with printer functionality such as, for example, displaying customized personalization document supply information, printer option settings, progress information for a current or pending print job, a print preview that can display, for example, a front and/or back image of the customized personalization document with image data and personalization account data, etc. The user interface also allows a user to interact with server functionality associated with a server connected to the printer200which allows a user to, for example, control: user authentication; print queues; print workflows; RUI configuration; remote access to printer user functions and front and back print preview of personalized information on a personalization document; storage and rendering of data to be placed on a customized personalization document; locking and unlocking of hoppers within the printer200; access to administrative functions; and quality assurance (QA) functions (e.g., rejecting a card once it has been printed, reprinting a personalization document, and informing the central server, etc.); etc. All these actions then update a server (such as the server122in the system100shown inFIG. 1) in order to track activities, inventory and central reports.

FIG. 3provides a flow chart of a process300for instantly issuing a customized personalization document using the customized personalization document printer200according to one embodiment. The process300begins at step305, where the network component235receives personalized account data and rendering instruction data from a server of an instant issuance system (not shown). The process300then proceeds to step310.

At step310, the processor retrieves actual rendering data from the memory storage component210based on the rendering instruction data received by the network component235. The process then proceeds to step315.

At step315, the processor205merges the actual rendering data with the personalized account data to generate printing data in the form of a print request that is added to a print queue screen of the RUI (such as print queue screen500shown inFIG. 5and discussed in more detail below) that is displayed to the user on the display225. The process300then proceeds to step320.

At step320, the RUI waits for the user to select, via the input device230, the print request from the print queue screen of the RUI which instructs the printer200to begin the process of printing a customized personalization document based on the print request. Once the print request is selected by the user the process320proceeds to step325.

At step325, the processor205determines whether the print request selected by the user at step320requires authentication. If the processor205determines that the print request does not require authentication the process proceeds to step330. If the processor205determines that the print request selected by the user at step320does require authentication, the process proceeds to step335.

At step330, the RUI displays a print preview screen (such as print preview screen600shown inFIG. 6and discussed in more detail below) of the RUI and waits for the user to instruct the printer200to initiate printing of the customized personalization document. The process300then proceeds to step335.

At step335, the processor205determines whether the print request selected by the user at step320requires the user to manually insert a personalization document to be customized into the manual exception slot222. If the processor205determines that the print request requires the user to manually insert a personalization document to be customized into the manual exception slot222, the process proceeds to step340. If the processor205determines that the print request does not require the user to manually insert a personalization document to be customized into the manual exception slot222of the printer200, the process proceeds to step345.

At step340, the RUI displays an insert document screen (such as manual personalization document insertion800shown inFIG. 8and discussed in more detail below) the process205waits for a user to insert a personalization document to be customized into the manual exception slot222of the printer200. When the processor205determines that the user has inserted a personalization document to be customized into the manual exception slot222of the printer200, the process proceeds to step345.

At step345, the processor205instructs the one or more personalization components215,215B-215nto initiate printing of a customized document personalization document.

At step350, the process300, the RUI displays a print preview authentication screen (such as print preview authentication screen700shown inFIG. 7and discussed in more detail below) of the RUI and waits for the user to instruct the processor205to begin an authentication process. Once the user has instructed the processor205to initiate the authentication process, the process proceeds to step355.

At step355, the processor205begins the authentication process whereby the user enters an authentication user enters an authentication code into the RUI. In some embodiments, the authentication code is an alpha-numeric authentication code. Once authentication has been successfully accomplished, the process300proceeds to step335.

FIGS. 4-25provide screenshots of an exemplary RUI400presented to a user via the display225and interacted with via the input device230. In the embodiment described below, the display225and the input device230are combined into a touch screen display for a user to interact with the RUI400. WhileFIGS. 4-25provide one embodiment of the RUI400, in other embodiments, a user can configure the RUI as needed by, for example, including additional functionality, updating screens of the RUI, reconfiguring what options are displayed on a particular screen, reconfiguring how the RUI responds to different user input, etc.

As shown inFIGS. 4-25, each screen of the RUI400includes a header bar410, a menu bar415and a window420. In some screens of the RUI400, a footer bar425is also included that indicates to the user the printing status of the printer200and the number of print requests in the print request queue. The header bar410indicates to the user the screen of the RUI400being displayed. The menu bar415includes a home navigation button430, a previous screen button435and two screen specific buttons440. The home navigation button430allows the user to return to the home screen405from any screen of the RUI400. The previous screen button435allows a user to return to the previous screen displayed by the RUI400. The screen specific buttons440A and440B can be configured to perform different functions based on the requirements of the screen being displayed. The window420is configured to provide screen specific information and buttons based on the screen being displayed. WhileFIGS. 4-25specifically refer to cards, it would be obvious to one skilled in the art that other types of customized personalization documents (e.g., passports) can be controlled and configured using the RUI400.

FIG. 4provides a screenshot of a home screen405of the RUI400. The home screen405appears upon powering of the printer200and when the home navigation button430is selected by the user. The window420of the home screen405includes a print queue button450, an administration button455, a supplies status indicator button460, a document status indicator button465, and an authentication indicator button470. The window420also displays the status of the printer and the language being used by the RUI400. The two screen specific buttons440in the home screen405are not used.

FIG. 5provides a screenshot of a print request queue screen500of the RUI400. The print request queue screen500appears, for example, when the user selects the print queue button450at the home screen405. The window420displays unique print request buttons505. The number of unique print request buttons505that are displayed in the window420depends on the number of pending print requests. As shown inFIG. 5, when there are multiple pending print requests a plurality of unique print request buttons505are displayed. However, if the printer200has one print request only a single unique print request button505will be displayed and if the printer200has zero print requests no print request buttons505are displayed. At the print request queue screen500, the screen specific button440A displays an upward arrow icon and when selected allows a user to scroll upward through the print request buttons505. Similarly, the screen specific button440B displays a downward arrow icon and when selected allows a user to scroll downward through the print request buttons505.

Each of the unique print request buttons505identifies a unique print request generated by the processor205. Each print request button505includes print request information including the account number and the account name to be printed onto the personalization document, hopper information indicating the specific type of personalization document to be customized, the user requesting the specific print request, an authentication indicator indicating whether the user undergo the authentication process in order to initiate printing, and the printing status of the specific print request.

FIG. 6provides a screenshot of a print preview screen600of the RUI400. The print preview screen600appears, for example, when the user selects one of the unique print request buttons505that does not require authentication at the print request queue screen500. The window420displays a fully rendered image610of how one side of the customized personalization document will appear when the print request is completed. The fully rendered image610is generated by the processor205by combining personalized account data received from an instant issuance server with actual rendering data retrieved from the memory storage component210based on rendering instruction data received by the instant issuance server. At the print preview screen600, the screen specific button440A displays a printer icon and when selected instructs the printer200to initiate printing of the customized personalization document. The screen specific button440B displays a refresh/rotate icon and when selected instructs the RUI400to display a fully rendered image of how an opposite side of the customized personalization document will appear when the print request is completed (not shown).

FIG. 7provides a screenshot of a print preview authentication screen700of the RUI400. The print preview authentication screen700appears, for example, when the user selects one of the unique print request buttons505that requires authentication at the print request queue screen500. The window420displays a fully rendered image710of how one side of the customized personalization document will appear when the print request is completed. The fully rendered image710is generated by the processor205by combining personalized account data received from an instant issuance server with actual rendering data retrieved from the memory storage component210based on rendering instruction data received by the instant issuance server. At the print preview screen700, the screen specific button440A displays an authentication icon and when selected instructs the processor205to initiate the authentication process. The screen specific button440B displays a refresh/rotate icon and when selected instructs the RUI400to display a fully rendered image of how an opposite side of the customized personalization document will appear when the print request is completed (not shown).

FIG. 8provides a screenshot of a manual personalization document insertion screen800of the RUI400. The manual personalization document insertion authentication screen800appears, for example, when the user selects initiation of a print request that requires manual insertion of a personalization document to be customized into the printer200. The window420displays the personalization document stock name of the specific type of personalization document necessary to be inserted by the user and displays a stock image810of the specific type of personalization document necessary, if the stock image810is stored in the memory storage component210. If a particular stock image is not stored in the memory storage component210, a text box815that states “no stock image” is displayed. At the manual personalization document insertion screen800, the screen specific button440A displays checkmark icon and when selected instructs the processor205to initiate the printing process. The screen specific button440B is not used in the manual personalization document insertion screen800.

FIG. 9provides a screenshot of a hopper status screen900of the RUI400. The hopper status screen900appears, for example, when the user selects the document status indicator button465at the home screen405. The hopper status screen900provides one example of the printer functionality that can be interacted with and controlled via the RUI400. The window420displays details of the personalization document stock supplies loaded into each of the hoppers220,220B-220n. For each hopper in the printer200, the hopper status screen900displays a hopper identifier905for the particular hopper, a supply indicator910indicating whether there are personalization documents available to be customized in the particular hopper, a supply amount indicator915indicating the exact amount of personalization documents available to be customized in the particular hopper, and an image button920that displays a stock image of the personalized document stored in the particular hopper.

InFIG. 9, the hopper identifier905uses a numbering system to identify each of the hoppers220,220B-220nwithin the printer200. If personalization document stock quantities are not tracked/managed by the user, the supply indicator910displays a green light if there are one or more personalization documents available in the particular hopper and a red light if there are no personalization documents available in the particular hopper. If personalization document stock quantities are being tracked/managed by the user, the supply indicator910displays a green light if there are more than a threshold number of personalization documents available in the particular hopper, a yellow light if there are less than a threshold number of personalization documents available in the particular hopper and a red light if there are no personalization documents available in the particular hopper. In one embodiment, the threshold number of personalization documents is ten. However, the threshold number can be set by the user. For example, in other embodiments, the threshold number of personalization documents can be any integer greater than 1 such as, for example, 2, 5, 20, 100, etc.

If a stock image for a personalization document supplied by a particular hopper is stored in the memory storage component210, the stock image is displayed in the image button920. If a stock image for a personalization document supplied by a particular hopper is not stored in the memory storage component210, a text box that states “no stock image” is displayed in the image button920.

The screen specific button440A is not used in the hopper status screen900. The screen specific button440B displays an authentication icon and when selected instructs the RUI400to send the user to the administration identification (ID) select screen1200.

FIG. 10provides a screenshot of an adjust personalization document count screen1000of the RUI400. The adjust personalization document count screen1000appears, for example, when the user selects one of the image buttons at the hopper status screen900. The menu bar410provides information known about the particular hopper including the hopper identifier, a stock image of personalized documents stored in the particular hopper if available and the amount of personalized documents stored in the particular hopper. The window420provides a numeric keypad1010for the user to enter the amount of additional personalized documents to be loaded into the particular hopper. The window420also displays the current amount of personalized documents stored in the particular hopper and displays the number of personalized documents selected by the user using the numeric keypad1010or the screen specific button440B (described below). The screen specific button440A displays a checkmark icon and when selected instructs the RUI400to the print request queue screen500. The screen specific button440B displays a “Fill Up” icon and when selected instructs the processor205that the particular hopper should be filled to the maximum capacity of the particular hopper.

FIG. 11provides a supplies status screen1100of the RUI400. The supplies status screen1100appears, for example, when the user selects the supplies status indicator button460at the home screen405. The supplies status screen1100provides another example of the printer functionality that can be interacted with and controlled via the RUI400. The window420displays a graphics ribbon supply indicator1110, a topping supply indicator1120and an indent supply indicator1130. The graphics ribbon supply indicator1110displays a percentage of the remaining graphic ribbon supply that can be determined, for example, by a radio frequency identification (RFID) tag on the graphic ribbon supply. The topping supply indicator1120and the indent supply indicator1130each display a green light if the topping supply amount or the indent supply amount are more than a threshold amount, a yellow light if the topping supply amount or the indent supply amount are less than a threshold amount and a red light if the topping supply amount or the indent supply amount is zero. The threshold amount for the topping supply amount and the threshold amount for the indent supply amount can be set by the user. The screen specific buttons440A, B are not used in the supplies status screen1100.

FIG. 12provides an administration identification (ID) select screen1200of the RUI400. The administration ID select screen1200appears, for example, when the user selects the authentication indicator button470at the home screen405. The window420displays unique administration ID buttons1210. The number of unique administration ID buttons1210that are displayed in the window420depends on the number of unique administration IDs registered with the printer200. As shown inFIG. 12, when there are multiple unique administration IDs a plurality of unique administration ID buttons1210are displayed. However, if the printer200has only one registered unique administration ID only a single unique administration ID button1210will be displayed and if the printer200has zero registered unique administration IDs no unique administration buttons505are displayed. The window420also includes a scroll bar1220that allows a user to scroll through the unique administration ID buttons1210. The screen specific buttons440A,440B are not used in the administration ID select screen1200.

FIG. 13provides an administration authentication screen1300of the RUI400. The administration authentication screen1300appears, for example, when the user selects one of the unique administration ID buttons1210at the administration ID select screen1200. The window420provides a numeric keypad1310that allows the user to enter an authentication password corresponding to the particular unique administration ID selected, for example, at the administration ID select screen1200. While the window420shows a numeric keypad1310, in other embodiments, the numeric keypad1310can be replaced with other types of keypads or authentication inputs such as, for example, an alpha-numeric keypad (not shown). The screen specific button440A displays a checkmark icon and can be selected by the user to instruct the processor205to verify the entered password to authenticate the unique administration ID. The screen specific button440B is not used in the administration authentication screen1300.

FIG. 14provides an administration screen1400of the RUI400. The administration screen1400appears, for example, after the processor205authenticates the unique administration ID at the administration authentication screen1400. The administration screen1400can also appear, for example, when the user selects the administration button455at the home screen400. The window420provides a settings button1405, an activity log button1410, a role setup button1415and a print request log button1420. The screen specific buttons440A, B are not used in the administration screen1400.

FIG. 15provides a settings screen1500of the RUI400. The settings screen1500appears, for example, after the user selects the settings button1405at the administration screen1400. The window420provides document stock level buttons1505a, bthat allow the user to choose whether the banker can manage the document stock level in the printer200. The window420also provides a low hopper level threshold supply setting1510that allows the user to enter a low hopper level threshold for a low hopper level threshold supply indicator supply indicator910such as the low hopper level threshold supply indicator supply indicator910. The screen specific buttons440A, B are not used in the settings screen1500.

FIG. 16provides a role setup screen1600of the RUI400. The role setup screen1600appears, for example, after the user selects the role setup button1415at the administration screen1400. The window420provides an administration setting1605that allows the user to choose the number of unique authentications required to access privileged administrative functions (e.g., access to a print log, access to activity logs; access to reprint functions; access to an unlock function, etc.) in the printer200. The window420also provides an unlock setting1610that allows the user to choose the number of unique authentications required unlock the printer200to allow the user access to load and unload supplies such as ribbons, personalization documents, etc. The screen specific buttons440A, B are not used in the role setup screen1600.

FIG. 17provides an activity log screen1700of the RUI400. The activity log screen1700appears, for example, after the user selects the activity log button1410at the administration screen1400. The window420displays unique activity log items1705. The number of unique activity log items1705that are displayed in the window420depends on the number of activity log items. As shown inFIG. 17, when there are multiple unique activity log items a plurality of unique activity log items1705are displayed. However, if the printer200has one activity log item only a single unique activity log item1705will be displayed and if the printer200has zero activity log items no activity log items1705are displayed. Each unique activity log item includes: a date and time of the action; a description of the action; the role of the action (i.e. administrator, unlock, etc.); the users who caused the action; and the amount of time the action took place. The window420also includes a scroll bar1710that allows a user to scroll through the unique activity log items17050. The screen specific buttons440A, B are not used in the activity log screen1700.

FIG. 18provides a print request log screen1800of the RUI400. The print request log screen1800appears, for example, after the user selects the print request log button1420at the administration screen1400. The window420displays unique print request log items1805. The number of print request log items1805that are displayed in the window420depends on the number of print request log items. As shown inFIG. 18, when there are multiple unique print request log items a plurality of unique print request log items1805are displayed. However, if the printer200has one print request log item only a single unique print request log item1805will be displayed and if the printer200has zero print request log items no print request log items1805are displayed. Each unique print request log item includes information regarding: the date and time a print request was received; a date and time a last state change occurred; a request ID; a state of the print request; and the user controlling the print request. The window420also includes a scroll bar1810that allows a user to scroll through the unique print request log items1805. The screen specific buttons440A, B are not used in the print request log screen1700.

FIG. 19provides a print workflow options screen1900of the RUI400. The window420provides reprint buttons1910a, bthat allow the user to choose whether the user can request a reprint of a customized personalization document at the printer200using the RUI400. If the reprint button1910ais selected, the user can request a reprint of a customized personalization document using the RUI400. In some embodiments, the RUI400may require a second user, such as a supervisor, to authenticate the reprint request. If the reprint button1910bis selected, the user may be required to perform a new print request process for a customized personalization document at a terminal, such as the terminal112in the system100shown inFIG. 1. The screen specific buttons440A, B are not used in the print workflow options screen1900.

FIG. 20provides a print queue options screen2000of the RUI400. The window420provides print queue option buttons2010a, b, cthat allow the user to choose the print queue process of the printer200using the RUI400. If the print queue option button2010ais selected, the user can request that the printer200performs print requests on a first in first out basis without requiring user authentication at the printer200using the RUI400. If the print queue option button2010bis selected, the user can request that the printer200performs print requests only after a user performs an authentication process at the printer200using the RUI400. If the print queue option button2010cis selected, the user can request that the printer200performs print requests of high priority print requests before performing print requests of low priority print requests. The screen specific buttons440A, B are not used in the print queue options screen2000.

FIG. 21provides a printer information screen2100of the RUI400. The window420provides specific printer information of the printer200including: model number; serial number; printer revision number; software name; software revision number; IP address; printer state; number of hoppers; printer option settings; number of good personalization documents; number of rejected personalization documents; and the amount of time the printer200has been on. The screen specific button440adisplays a settings icon and when selected by the user sends the user to the settings screen1500of the RUI400. The screen specific button440bdisplays a logs icon and when selected by the user the RUI400sends the user to the activity log screen1700. In another embodiment, when the user selects the screen specific button440b, the RUI sends the user to the print request log screen1800.

FIG. 22provides a view settings screen2200of the RUI400. The window420includes a design button2205, a personalization document type button2210and an images button2215. When a user selects the design button2205, the RUI400sends the user to a personalization document design screen (such as personalization document design screen2400shown inFIG. 24). When a user selects the personalization document type button2210, the RUI400sends the user to, for example, registered personalization document stock screen2500shown inFIG. 25. When a user selects the images button2215, the RUI400sends the user to an images screen (such as images screen2300shown inFIG. 23). The screen specific buttons440A, B are not used in the print queue options screen2000.

FIG. 23provides an images screen2300of the RUI400. The window420includes a plurality of unique image buttons2305. The number of unique image buttons2305that are displayed in the window420depends on the number of unique images stored in the printer200. Each unique image button2305displays the name of the image file stored in the printer200and displays a picture of the image for the user. As shown inFIG. 23, when there are multiple unique images stored in the printer200a plurality of unique image buttons2305are displayed. However, if only one image is stored in the printer200only a single unique print image button2305will be displayed and if no images are stored in the printer200no unique image buttons2305are displayed. At the images screen2300, the screen specific button440A displays an upward arrow icon and when selected allows a user to scroll upward through the unique image buttons2305. Similarly, the screen specific button440B displays a downward arrow icon and when selected allows a user to scroll downward through the unique image buttons2305.

FIG. 24provides a personalization document design screen2400of the RUI400. The window420provides file information regarding a particular personalization document design of personalization documents stored in the printer200. The screen specific buttons440A, B are not used in the print queue options screen2000.

FIG. 25provides a registered personalization document stock screen2500of the RUI400. The window420includes a plurality of unique personalization document stock buttons2505. The number of unique personalization document stock buttons2505that are displayed in the window420depends on the number of unique personalization document stocks stored in a hopper or a manual exception slot the printer200. Each unique personalization document stock button2505displays the name of the unique personalization document stock, the hopper storing the stock of the unique personalization document in the printer200and, if available, displays a picture of the front and/or back image of the unique personalization document for the user. As shown inFIG. 25, when there are multiple unique personalization document stocks stored in the printer200a plurality of unique personalization document stock buttons2505are displayed. However, if only one unique personalization document stock is stored in the printer200only a single unique personalization document stock button2505will be displayed and if no unique personalization document stocks are stored in the printer200no unique personalization document stock buttons2505are displayed. At the images screen2300, the screen specific button440A displays an upward arrow icon and when selected allows a user to scroll upward through the unique personalization document stock buttons2505. Similarly, the screen specific button440B displays a downward arrow icon and when selected allows a user to scroll downward through the unique personalization document stock buttons2505.