WO2010027091A1 - Label issuance information processing system - Google Patents

Abstract

A management system (100) for management of an issuer and a taste-appreciative period comprises a plurality of label printers (110) print food labeling information on labels and output the printed labels and a label issuance management system (130) that sets at least issuer identification information for every label printer when information to identify a person who is permitted to operate the label printer for the issuance of the label is determined to be the issuer identification information.  The label issuance management system (130) receives from the label printer (110) to which the issuer identification information is set, after the issuance of the label, label issuance history information caused by the label printer operation at the label issuance, stores the label issuance history information received from the label printer for every label printer (110) and carries out information processing.  Thus, the label issuance history information can be unitarily managed for every label printer by which the label is issued by the person who is permitted to operate the label printer for the label issuance.

Description

Label issuing information processing system

This invention relates to a label issuing information processing system that can be applied to an issuer that issues information on food labels on a label and issues the printed label, and an issue expiration date management system.

At present, food products sold at supermarkets, etc. should be printed with appropriate indications on the packaging containers so that the contents of the food products can be understood. Items such as name (product name), raw material name (impact of genetically modified food, food additive), contents, expiration date (expiration date, expiration date), storage method, manufacturer, and location of the factory are included in the food label. Desirably included. Normally, all of these display items are printed on a label sheet (roll paper), and the printed label is attached to the packaging container.

A label printer is usually used for creating and pasting labels. The label printer prints layout information directly input from the input operation unit or layout information input via a memory card after being created by a personal computer or the like on a label. A label-like roll paper is formed on a strip-shaped release paper by continuously temporarily sticking a label having a predetermined size at a predetermined pitch to form a roll paper for the label. Mounted on the body.

As described above, the label printer is provided with memory means for storing print information. Layout information including print information is read from the memory means. The layout information is stored in association with each item after changing to display items and display contents suitable for the items produced, manufactured, and processed by the user. In addition, the selling price of items often changes daily. Therefore, the label issuer reads the stored item layout (layout information) when actually printing the selling list price, corrects the price printed in the price field of the label, and then prints a predetermined number of labels. Printed.

In relation to this type of label printer, Japanese Patent Application Laid-Open No. 2004-351775 discloses a label printer system that performs pricing based on a product master for each user distributed from a management server. Japanese Laid-Open Patent Publication No. 7-205950 discloses a portable label printer system etc. in which selling price information is received from a central device via a communication line so that the selling price can be updated efficiently. Japanese Laid-Open Patent Publication No. 11-232067 discloses a label printer system in which a file storing product sales price information and the like can be accessed via a communication line.

By the way, according to the label printer as shown in Japanese Patent Application Laid-Open No. 2004-351775, Japanese Patent Application Laid-Open No. 7-205950, and Japanese Patent Application Laid-Open No. 11-232067, those other than those who are permitted to issue labels. Even a person can operate a label printer to issue a label. As described above, if anyone can issue a label without specifying the label issuer, it is difficult to confirm the label issue history. Moreover, there is a problem that if the rewriting is allowed freely without giving the authority to rewrite the expiration date, the expiration date is altered.

At present, the label issuance history is not centrally managed. An information management system that links the label issuer including the label issuer, the number of issued items, the amount of money, the expiration date, and the like with the production plan of the product to be sold and manufactured has not yet been established. Therefore, it is difficult to prevent forgery of the expiration date, missed issuance of the expiration date, and the like. By the way, when a problem such as a shelf life issuance error occurs, information for searching and verifying the label issuance history is not prepared, so it is difficult to investigate the cause early.

The present invention provides a label issuance information processing system capable of centrally managing the label issuance history information for each label printer in which a label is issued by a person who is permitted to operate the label printer for label issuance. With the goal.

A label issuance information processing system according to the present invention includes a plurality of label printers that print information on a label and output a printed label, and information that identifies a person who is permitted to operate the label printer for label issuance. When it is set as issuer identification information, it includes at least a label issue management device that sets issuer identification information for each label printer. The label issuance management apparatus receives label issuance history information generated by the operation of the label printer at the time of label issuance from each label printer in which the issuer identification information is set, and is received from the label printer. The label issuance history information is stored for each label printer and processed.

According to the label issuance information processing system according to the present invention, the label issuance management apparatus sets issuer identification information for identifying a person who is permitted to operate the label printer for label issuance for each label printer. Based on this assumption, the label issuance management apparatus receives label issuance history information generated by the operation of the label printer at the time of issuance of labels from each label printer for which issuer identification information has been set. Thereafter, the label issuance management apparatus stores the label issuance history information received from the label printer for each label printer and processes the information.

Therefore, the label issuance history information can be centrally managed for each label printer whose label is issued by a person who is permitted to operate the label printer for issuing the label. Thereby, a production plan can be made based on the label issue history information including the label issuer, the number of issued cards, the amount, the expiration date, and the like. In addition, forgery of the expiration date, missed issuance of the expiration date, and the like can be prevented. Incidentally, when a problem such as an issue error of the expiration date occurs, the cause can be investigated early by searching and verifying the label issuance history information.

It is explanatory drawing which shows the structural example of the issuer & issue expiration date management system 100 as embodiment which concerns on this invention. 3 is a block diagram illustrating a configuration example of a control system of an FTP server 135. FIG. FIG. 2 is a perspective view showing an example of the appearance of a label printer 110. 3 is a plan view illustrating a configuration example of an input operation unit 174 of the label printer 110. FIG. 3 is a block diagram illustrating a configuration example of a control system of the label printer 110. FIG. It is a table | surface figure which shows the structural example of the issuer list file F1. It is a table | surface figure which shows the structural example of the list file F2 for foodstuffs. 4 is a plan view showing a configuration example of a label 30. FIG. It is a table | surface figure which shows the layout file F3. It is a table | surface figure which shows the example of rewriting of the layout file F3. It is a table | surface figure which shows the example of a description of the issue recording file F4. It is a table | surface figure which shows the example of a description of the issue recording file F4a. 3 is an explanatory diagram showing a flow of information in an FTP server 135, a production management system 140, and a management viewer system 150. FIG. 5 is a flowchart illustrating an information processing example in a production management system 140. 5 is a flowchart illustrating an information processing example in a label issuance management system 130. 3 is an explanatory diagram showing a flow of information in the FTP server 135 and the label printer 110. FIG.

Hereinafter, a label issue information processing system as an embodiment according to the present invention will be described with reference to the drawings. The issuer & issue expiration date management system 100 shown in FIG. 1 constitutes an example of a label issue information processing system. The issuer & issue expiration date management system 100 has a plurality of label printers 110 that issue information on food labels printed on a label 30 (see FIG. 8), and manages the issuers that handle them. The issuer & issue best-by date management system 100 is a system that issues a label 30 with a time limit by the label printer 110 and is applicable to the food industry, the food manufacturing industry, and the like.

The issuer & issue expiration date management system 100 further includes a label printer 120 with a communication function, a label issue management system 130, a production management system 140, and a management viewer system 150. The label printer 110 prints and outputs information relating to food display on the label 30 (see FIG. 3). The label printer 110 is disposed in a food sales store, a food manufacturing factory (line), or the like, and is operated by employees, part-time employees, or the like who are engaged in the store, the factory line, or the like. The label printer 110 is often used under a contract between a management user and a manufacturer / seller in the same store or factory.

The label printer 110 shown in FIG. 1 is used by being connected to a modem for processing communication information (hereinafter simply referred to as modem 119). The modem 119 has one end connected to the label printer 110 and the other end connected to the communication unit 43 during information communication. As the communication means 43, a public communication line, a dedicated communication line, or the Internet is used. The public communication line includes a WAN (Wide Area Network). In this example, in addition to the label printer 110, a label printer 120 with a communication function is also used. The label printer 120 has a communication modem function inside, and is directly connected to the communication means 43 such as a public communication line.

The label issuance management system 130 includes an information management server (hereinafter simply referred to as an FTP server 135) compliant with a file transfer protocol, an information storage device 131, and a modem 136. The FTP server 135 constitutes an example of a label issue management device. The FTP server 135 has a function of mediating between the label printers 110, 120... On the client side and the production management system 140. In this example, the FTP server 135 has a function of checking the issuance of the label 30 (see FIG. 8), and at least a label that prints information on the food display on the label 30 and outputs the printed label 30 Issuer identification information is set for each of the printers 110 and 120. Here, issuer identification information refers to information for identifying a person who is permitted to issue a label, and is hereinafter referred to as an issuer ID number.

This issuer ID number is collected in a list showing a list of persons who are permitted to issue a label by the label printer 110. Information of issuer ID numbers collected in this list is referred to as issuer list information D1. The FTP server 135 sets the issuer list information D1 for each corresponding label printer 110, 120.

In addition, the FTP server 135 sets addition date information regarding the expiration date of each product in the label printers 110 and 120. The expiration date of each product is calculated by adding the number of days specified on the production date. In this example, the issuer identification information set in the label printer 110 includes information for specifying the authority for changing the expiration date.

The FTP server 135 is connected to the communication unit 43 via the modem 136 and manages one or more label printers 110 and 120. For example, the FTP server 135 monitors the presence / absence of label ordering data and registers the label ordering data and customer information in association with each other (issue label check function).

A personal computer is used for the FTP server 135. The FTP server 135 includes a label including at least an issuer ID number, an issue date, an issue number, and a shelf life of the label 30 generated by the issue operation of the label printers 110, 120,. After issuing the label, the issuance history information D4 is stored in the label printer as an issuance history file, and the label issuance history information D4 is received from the label printer 110, 120,. Further, the FTP server 135 stores the label issuance history information D4 received for each label printer 110, 120 for each label printer 110, 120, and processes the label issuance history information D4.

The FTP server 135 includes a large-capacity information storage device 131 such as a hard disk, and stores label issuance history information D4 received from the label printers 110, 120, and the like. The information storage device 131 includes an issue label database 132 and an issuer database 133. In the issue label database 132, layout data D2, issue record (history information), reservation issue update list, and the like are recorded. In the issuer database 133, a person who is permitted to perform a label issuing operation is registered.

An information terminal device 141 for production management is connected to the FTP server 135 via a communication means 40 such as a LAN (Local Area Network). A personal computer is used for the information terminal device 141. A production plan database 142 is connected to the information terminal device 141. The information terminal device 141 records and updates information relating to food display such as the amount of the product, its expiration date, issuer list information D1, layout data D2 of the label 30, and reservation issue list data D3.

In this example, the information terminal device 141 and the production plan database 142 constitute a production management system 140. The production plan database 142 is composed of a large capacity information storage device such as a hard disk. The production plan database 142 may be in either a form in which an information storage device for constructing the production plan database 142 is connected to the information terminal apparatus 141 or a form implemented in the information terminal apparatus 141.

In the issuer & issue expiration date management system 100, the issuer list information D1, the layout data D2 of the label 30, the reserved issue list data D3, etc. provided from the label issue management system 130 are included in the production plan of the production management system 140. Updated based on. The label issuance management system 130 refers to the updated issuer list information D1, the layout data D2 of the label 30, the reservation issuance list data D3, and the like, and uses these food display information for each food sales store or food manufacturing factory. Deliver to etc. As a result, the label 30 can be issued based on information relating to food display such as layout data D2 and reservation issuance list data D3 in the same store or factory line.

The information processing device 151 dedicated to the management viewer is connected to the communication means 43 via the modem 153. The information processing apparatus 151 checks whether an appropriate label 30 such as the amount of the product and its expiration date has been issued as planned by the label printer 110, 120 or the like. The information processing apparatus 151 acquires and edits the label issuance history information D4 related to the issuance record of the label 30, and checks (unified management) the issuance record of the label 30 using a dedicated application. A personal computer is used for the information processing apparatus 151.

The dedicated application includes the label issuance location (store), its issuance date, its issuer ID number, product expiration date, product price, label display quantity, software for displaying the label issuance location, label Software for making production plans such as issue date and number of labels to be issued are included. The modem 153 and the information processing apparatus 151 are provided to a management user who becomes a head office or a headquarters of a food store or a food manufacturing factory, and constitutes a management viewer system 150. In this example, the management viewer system 150 may be arranged at the production base and connected to the communication means 40 such as a LAN for connecting the label issuing management system 130 and the production management system 140 to perform information processing.

The record of the label 30 issued at each food sales store, food manufacturing factory, etc. is fed back to the production management system 140 in a timely manner, and an appropriate label such as the price of the product and its expiration date as planned by the information terminal device 141. It is checked whether 30 has been issued. Further, when an error is detected by the check in the information terminal device 141, it is possible to follow up a shipping error or the like based on the label issuance record. In this example, by verifying the contents of the production plan database 142, it is possible to trace the production state when a problem occurs. Forgery can be prevented by prohibiting the issuance of a label describing the changed expiration date by adding a change restriction to the expiration date.

Subsequently, a configuration example of the control system of the FTP server 135 will be described with reference to FIG. The FTP server 135 shown in FIG. 2 has a function of mediating between the label printers 110, 120... On the client side and the production management system 140. For example, the FTP server 135 includes a control unit 135a, communication interfaces 135b and 135c, an information storage device 131, an input operation unit 135d, and a display unit 135e.

The control unit 135a includes a ROM (Read Only Memory) 135a-1, a work RAM (Random Access Memory) 135a-2, a system bus 135a-3, a CPU (Central Processing Unit) 135a-4, and an I / O. It has an interface 135a-5. A ROM 135a-1 is connected to the CPU 135a-4 via a system bus 135a-3, and system startup program data D21 for controlling the entire FTP server is stored. The RAM 135a-2 connected to the system bus 135a-3 temporarily stores a control command and layout data D2 at the time of information accumulation, in addition to the program data D21, issuer identification information, and label issue history information D4.

When the power is turned on, the CPU 135a-4 reads the program data D21 for system activation from the ROM 135a-1 to the RAM 135a-2, activates the system, and controls the entire FTP server. An I / O interface 135a-5 is connected to the CPU 135a-4 and controls input / output of user interfaces such as the input operation unit 135d and the display unit 135e. The I / O interface 135a-5 inputs operation data D34 at the time of system startup from the input operation unit 135d.

The input operation unit 135d is operated when inputting addition date information (expiration date) of each product that is transferred from the label issuance management system 130 to the stand-alone label printer 110 and registered. The expiration date of each product is an addition date designated by the label issuing management system 130 to the label printer 110 or the like on the production date of each product, that is, the supplier of the product should consume the food by that date. This is the deadline with the number of days added. The input operation unit 135d sends operation data D34 such as addition date information to the CPU 135a-4.

The CPU 135a-4 refers to the production plan database 142 based on an instruction (operation data D34, etc.) from the input operation unit 135d or an input operation unit (not shown) of the information processing apparatus 151 (administrative user) to make a production plan. Update the label 30 and issuer list that apply to the product based.

The display unit 135e displays a layout video based on the layout data D2 and also displays input information in the input operation unit 135d. The layout data D2 is information that allows the minimum display information that must be displayed on each of the display items related to food display described above to be displayed on the label 30 of a predetermined size. The layout data D2 includes verifiable information such as the date of manufacture, the expiration date, the internal capacity and the selling price. The layout data D2 is displayed on the display unit 135e based on the display data D35.

The FTP server 135 includes a large-capacity information storage device 131 such as a hard disk, and stores label issuance history information D4 received from the label printers 110, 120, and the like. Registered in the information storage device 131 is an issue label database 132 in which layout data D2, issue record (history information), reservation issue update list, etc. are recorded, and a person who is permitted to operate the label printer to issue labels. An issuer database 133 and the like are constructed.

In this example, a data processing unit 135f is connected to the system bus 135a-3, and data writing to the information storage device 131 or data reading processing from the information storage device 131 is executed. For example, the data processing unit 135f issues an issuer list of issuer names and their ID numbers (hereinafter referred to as issuer ID numbers) in addition to the addition date information of each product transferred from the CPU 135a-4 to the label printer 110 or the like. Control is performed to transfer the information D1.

In addition, when changing the expiration date at the time of label issuance, the data processing unit 135f is controlled so that only a specific issuer can change the expiration date to the issuer list information D1 and transfer it. . For example, when the label is issued, the data processing unit 135f adds the expiration date change permission data to the issuer list information D1. Here, the expiration date change permission data refers to data that allows only a specific issuer to change the label expiration date, and specifies the authority to change the expiration date.

In this example, on the label printer side, when the label is issued and when the expiration date is changed, the operator such as the label printer 110 inputs the issuer ID number and the like, who changed the expiration date of the label 30, or who Whether the label 30 has been issued is left in the issue history file. The data processing unit 135f returns these changes to the FTP server 135, and rewrites the contents stored in the issue label database 132 and the issuer database 133.

The communication interface 135b is connected to the system bus 135a-3. The interface 135b is connected to the external terminal 135g. A communication modem 136 is connected to the external terminal 135g and is connected to a public communication line such as the Internet. The interface 135b executes communication processing between the plurality of label printers 110, 120 and the like. In this communication process, label issue history information D4 is acquired from a plurality of label printers 110, 120, and the like. For example, after issuing the label, the interface 135b receives from the label printer 110 label issuance history information D4 indicating who, when, where, how many sheets, and what expiry date the label 30 has been issued.

In addition to the communication interface 135b, a communication interface 135c is connected to the system bus 135a-3. The interface 135c is connected to the external terminal 135h. An information terminal device 141 of the production management system 140 is connected to the external terminal 135h via a communication means 40 such as a LAN. The interface 135c transmits the label issuance history information D4 stored in the FTP server 135 to the information terminal device 141 of the production management system 140.

The information terminal device 141 checks whether an appropriate label 30 (amount, expiration date, etc.) has been issued as planned in order to feed back to the production plan for the next product. Thus, the label issue management system 130 in which the FTP server 135 or the like checks the issue of the label 30 is configured. Of course, the label issue check function may be provided in the information terminal device 141 of the production management system 140, the information processing device 151 of the management viewer system 150, or the like.

Subsequently, a configuration example of the label printer 110 will be described with reference to FIG. The label printer 110 shown in FIG. 3 outputs a label 30 in which information relating to food display is printed on a roll paper for label printing. The label printer 110 has a main body 115. The main body 115 includes an upper casing 111 and a lower casing 112 that are resin-molded according to a predetermined design. The upper housing 111 and the lower housing 112 are engaged with a hinge mechanism 113 so as to be opened and closed.

In the lower housing 112, a roll paper for label printing (not shown), a printing unit 117, a control unit 118, and the like as shown in FIG. 5 are mounted. The printing unit 117, the control unit 118, and the like print information on the food display on a label and output it. An input operation unit 174 and a display unit 175 are provided on the upper surface of the upper casing 111. The input operation unit 174 is operated when inputting identification information (issuer ID number) of an issuer that issues a label 30 printed out by the printing unit 117. In this example, the label 30 is output from the vicinity of the boundary between the upper casing 111 and the lower casing 112 on the front side of the main body 115.

FIG. 4 shows a configuration example of the input operation unit 174. The input operation unit 174 shown in FIG. 4 constitutes an example of an input device. The input operation unit 174 includes numeric keys “1” to “9”, “0” K1 to K10, a blank key K11, an issue key K12, a confirmation key K13, a stop / delete key K14, a test print key K15, and a cross key K16. , Input key K17, date key K18, cancel key K19, edit key K20, shift key K21, and the like.

The numeric keys “1” to “9” and “0” K1 to K10 are used when, for example, the contents of the layout file F3 shown in FIG. 9A are extracted from the list file F2 shown in FIG. 7 of the label 30 shown in FIG. The user is operated to input a link number or the like. The numeric keys “1” to “9” and “0” K1 to K10 are also operated when inputting the issuer ID number of the issuer who issues the label 30. Further, when setting the number of labels 30 to be issued, the number keys “1” to “9” and “0” K1 to K10 are operated to input the quantity of the product.

The date key K18 is operated when inputting the expiration date (addition date) or the like. The issue key K12 is operated when the label 30 is issued. The test print key K15 is operated when the label 30 is printed out as a test. The blank key K11, the enter key K13, the stop / delete key K14, the cross key K16, the input key K17, the date key K18, the cancel key K19, the edit key K20, the shift key K21, etc. are the contents of the layout file F3 of the label 30. Used when editing and validating

A configuration example of the control system of the label printer 110 will be described with reference to FIG. The label printer 110 shown in FIG. 5 prints and outputs information relating to food display on the label 30. The printing unit 117, the control unit 118, the input operation unit 174, the display unit 175, an internal memory 178 for issuer management, A compact flash (registered trademark) memory card (hereinafter referred to as a CF card 179) for issue history management is provided.

The control unit 118 includes a CPU 118a, a ROM 118b, a work RAM 118c, a system bus 118d, and an I / O interface 118e. A ROM 118b is connected to the CPU 118a via a system bus 118d, and system startup program data D81 for controlling the entire printer is stored. The RAM 118c connected to the system bus 118d temporarily stores program data D81 and control commands for executing information processing such as rewriting, editing, and verification.

Further, the RAM 118c temporarily stores internal storage data D82. The internal storage data D82 includes issuer ID number for issuer management, issuer's name, issuer list information D1 including the authority to change the label, product name, raw material, quantity, expiration date, which is changed at the time of issue, The layout data D2 such as the amount of money, the number of labels 30 to be issued, and the reservation issue list data D3 are included.

When the power is turned on, the CPU 118a reads the program data D81 for starting the system from the ROM 118b to the RAM 118c, starts the system, and controls the entire printer. An I / O interface 118e is connected to the CPU 118a and controls input / output of user interfaces such as the input operation unit 174 and the display unit 175. The I / O interface 118e inputs operation data D74 at the time of system startup from the input operation unit 174.

In this example, the input operation unit 174 outputs the operation data D74 to the control unit 118. The operation data D74 includes the issuer ID number of the operator who issues the label 30 printed and output by the printing unit 117, the quantity of the product when setting the number of labels 30 to be issued, and the expiration date (addition date). ) Is included. The operation data D74 is input when the label 30 is issued, when the test printing is performed, and when the contents of the layout file F3 are edited or verified.

In this example, the display unit 175 displays the layout data D2 and the input information from the input operation unit 174. The layout data D2 is information that allows the minimum display information that must be displayed on each of the display items related to food display described above to be displayed on the label 30 of a predetermined size. The input information for the layout data D2 includes information that can be edited, verified, etc., such as the date of manufacture, the expiration date, the contents, and the sales price. The input operation unit 174 functions as means for correcting and inputting information that can be edited and verified. The layout data D2 is displayed on the display unit 175 based on the display data D75.

Also, the printing unit 117 is placed under the control of the CPU 118a in order to achieve the printer function. The print unit 117 includes a label transport system 117a, a print head 117b, a roll paper loading detection unit 117c, and a printer control unit 117d. The printing unit 117 prints information related to food display on the label 30 and outputs the printed label 30.

The printer control unit 117d is connected to the system bus 118d. The printer control unit 117d inputs printer control data D77 from the CPU 118a, and also inputs paper loading detection data D76 from the roll paper loading detection unit 117c, and executes output control of the label transport system 117a and the print head 117b. The printer control unit 117d shares the control of the CPU 118a and reduces the control burden.

The label transport system 117a and the print head 117b are connected to the printer control unit 117d. The label transport system 117a is controlled to input the transport control data D71 and transport the roll paper below the print head 117b. The conveyance control data D71 is output from the printer control unit 117d to the label conveyance system 117a.

The print head 117b receives the print control data D72, prints predetermined layout data D2 relating to food display on the roll paper for labels conveyed by the label conveyance system 117a, and outputs the label 30. The print control data D72 is output from the printer control unit 117d to the print head 117b. A normal thermal head is used as the print head 117b. The thermal head is a line head, but is not limited to a line head.

In this example, the label transport system 117a is provided with a roll paper loading detector 117c. When the roll paper becomes empty, the roll paper loading detection unit 117c detects that the roll paper is not loaded and outputs paper loading detection data D76 to the printer control unit 117d. The paper loading detection data D76 detects the number of times the roll paper has been replaced and prompts the replacement of the print head 117b.

The CPU 118a collates the issuer ID number input by the input operation unit 174 with the issuer identification information (issuer ID number) set from the FTP server 135, and accepts a label issuance operation based on the collation result. For example, when the expiration date is changed, the CPU 118a executes rewrite control of information relating to food display. However, when an operation input for changing the expiration date is received from the input operation unit 174 regarding the expiration date printed on the label 30, the operation is performed. Regardless of the expiration date (addition date) based on the data D74, the addition date is calculated from the addition date information designated by the FTP server 135.

The CPU 118a controls the RAM 118c and the like, and saves the content of information relating to food display changed at the time of label issuance as label issuance history information D4. The CPU 118a stores label issuance history information D4 (location (store), issuance date, issuer ID number, expiration date, amount of money, issuance number) at the time of label issuance in the RAM 118c and the like, and has the same contents as the label issuance history information D4. The information is transferred to the FTP server 135.

The internal memory 178 for storing the issue history file is connected to the system bus 118d. The internal memory 178 stores issuer list information D1, layout data D2, and reservation issue list data D3 downloaded from the label issue management system 130. The issuer list information D1 includes an issuer ID number for issuer management, the name of the issuer, and label change authority. The layout data D2 includes the product name, raw material, quantity, expiration date, and amount of money that will be changed at the time of issuance. The layout data D2 also includes the number of labels 30 issued. When the label is issued, for example, information for identifying the issuer is read from the internal memory 178 to the RAM 118c. The issuer ID number stored in the internal memory 178 is set in advance by the FTP server 135. The issuer list information D1, layout data D2, and reservation issue list data D3 constitute internal storage data D82.

Also, the issuer ID number (ID code) input by the input operation unit 174 is described in the issue history file together with its name. The ID code is, for example, a serial number assigned in the order of issuers registered in the label printer 110. The internal memory 178 is a non-volatile memory such as an EEPROM that does not lose recorded information even when the power is turned off.

In this example, a memory card interface 173 is connected to the above-described system bus 118d, and a CF card 179 for issue history management is attached to the interface 173. For the CF card 179, a portable non-volatile memory, for example, a USB memory is used. The CF card 179 stores the layout data D2 of the label 30 downloaded from the label issue management system 130.

The CF card 179 stores label issue history information D4 in addition to the layout data D2 in issue record files F4 and F4a (see FIGS. 10A and 10B). The label issue history information D4 is information collected from the internal storage data D82, and is information transferred from the RAM 118c. The label issuance history information D4 includes at least the date when the label 30 is issued, the file number of the information related to food display, the issuer ID number of the issuer who issued the label 30, and the item name of the information related to food display changed when the label is issued. , The contents (name of product, raw material, expiration date, price, etc.) and the number of labels 30 issued when the label is issued.

By storing such label issuance history information D4 in the internal memory 178 or the CF card 179, it is possible to centrally manage who exactly issued what label 30 when and when (FIG. 10A, FIG. 10). 10B). In this example, the internal memory 178 may be used as storage means for issue history management, and the label issue history information D4 may be stored (saved) together with the CF card 179 or independently of the CF card 179.

In addition to the memory card interface 173, a communication interface 184 is connected to the system bus 118d. The interface 184 is connected to the external terminal 185. A communication modem is connected to the external terminal 185 and is connected to a public communication line such as the Internet to communicate with the FTP server 135 of the label issue management system 130. Through this communication, the layout data D2 acquired from the memory card interface 173 can be directly acquired from the FTP server 135. These constitute the label printer 110.

Subsequently, a configuration example of the issuer list file F1 will be described with reference to FIG. The issuer list file F1 shown in FIG. 6 is included in the issuer database 133 of the label issue management system 130. For example, the issuer list file F1 is transferred to the internal memory 178 or the CF card 179 together with the use management contract for the label printer 110 and the like. The A column describing the issuer ID number and a column describing the name of the issuer are assigned to the issuer list file F1. In this example, the ID number 001 is described in the first line of the issuer ID number description field, and the issuer's name corresponding to the ID number 001 is displayed in the first line of the issuer name description field. Name XXX is described. Similarly, the issuer's name YYY is described corresponding to the ID number 003 in the second line of the issuer's name description column. Furthermore, in the third line of the issuer's name description column, the issuer's name ZZZ is described corresponding to the ID number 004. The issuer list file F1 is described in the internal memory 178 or the CF card 179 based on the operation data D74 indicating the issuer ID number.

Subsequently, a configuration example of the food list file F2 will be described with reference to FIG. The food list file F2 shown in FIG. 7 is transferred from the FTP server 135 of the label issue management system 130 to the CF card 179 or the internal memory 178, for example. The list file F2 for food includes columns for describing a link number, product name, raw material, expiration date (addition date), price, and product number.

In this example, the link number “1” is described in the first line of the link number column, and “cookie” is described in the first line of the item name column corresponding to the link number “1”. . In the first line of the raw material column, “flour, egg, milk, almond” is described corresponding to the link number “1”. In the first line of the expiration date (addition date) column, the addition date “10” is described corresponding to the link number “1”. In the first line of the price column, “750” (yen) is described corresponding to the link number “1”. The product number “001” is described in the first line of the product number column corresponding to the link number “1”.

Similarly, the link number “2” is described in the second line of the link number column, and “cake” is described in the second line of the product name column corresponding to the link number “2”. . In the second row of the raw material column, “flour, egg, milk, strawberry” is described corresponding to the link number “2”. In the second line of the expiration date (addition date) column, the addition date “1” is described corresponding to the link number “2”. In the second line of the price column, “350” (yen) is described corresponding to the link number “2”. The product number “002” is described in the second line of the product number column in correspondence with the link number “2”.

The list file F2 for food is developed on the display unit 175. When a link number is designated by operating the input operation unit 174, the printer 110 or the like issues a label 30 with the contents described in the link number. According to this method, a plurality of types of labels 30 can be issued with one list file F2 for food.

Subsequently, a configuration example of the label 30 will be described with reference to FIG. The label 30 shown in FIG. 8 is issued by reading (quoting) the contents of the layout file F3 from the food list file F2 and describing the contents of the layout file F3. In this case, when the link number “1” of the list file F2 for the food is input, “cookie” is printed in the item name field that is the content of the link number “1” on the label of length l × width w on the roll paper. Is done. "Flour, egg, milk, almond" is printed in the raw material column. In the column of the expiration date, “May 25, 2008” obtained by adding the addition date “10” on May 15, 2008 is printed. “750” is printed in the price column. In the bar code column, “4923100107508” is printed. The layout data D2 in the broken line frame in the figure is read from the list file F2 and printed.

Subsequently, the layout file F3 and a rewrite example thereof will be described with reference to FIGS. 9A and 9B. FIG. 9A shows the contents of the layout file F3 before rewriting. FIG. 9B shows the layout file F3a after the layout file F3 shown in FIG. 9A has been rewritten.

In the layout file F3 before rewriting, as shown in FIG. 9A, the link number “1” is described in the link number column, and “cookie assortment” is described in the product name column corresponding to the link number “1”. The In the raw material column, “flour, egg,...” Is described corresponding to the link number “1”. In the price column, “750” yen is described corresponding to the link number “1”. In the quantity, “8” is described corresponding to the link number “1”. In the column of the expiration date (addition date), when the date of production is August 10, 2008 and the addition date is “3”, the date corresponding to the link number “1” is added. August 13 (3) is described. In the manufacturer column, “XYZ Co., Ltd” is described.

In the contents of this layout file F3, the number of “cookie assortment” is rewritten from 8 to 10, and the expiration date (addition date) of “cookie assortment” is rewritten from “3” to “5”. Suppose that In this case, the “cookie assortment” quantity “8” in the layout file F3 before rewriting is updated (overwritten) to “10”. Further, the expiration date (addition date) “3” is updated (overwritten) to “5”.

In the rewritten layout file F3a, the link number “1” is described in the link number column and “cookie assortment” is described in the product name column corresponding to the link number “1” as shown in FIG. 9B. The In the raw material column, “flour, egg,...” Is described corresponding to the link number “1”. In the price column, “750” yen is described corresponding to the link number “1”. In the quantity, “10” is described corresponding to the link number “1”. In the column of the expiration date (addition date), when the production date is August 10, 2008 and the addition date is “5” corresponding to the link number “1”, 2008 is added. August 15 (5) is described. In the manufacturer column, “XYZ Co., Ltd” is described.

Subsequently, description examples of the issue record files F4 and F4a will be described with reference to FIGS. 10A and 10B. The contents of the issue record files F4 and F4a shown in FIGS. 10A and 10B are described (saved) in the issue history management internal memory 178 or the CF card 179. In this example, the issue record files F4 and F4a include description columns for an issue date, a file number, an issuer ID number, a label issue change name, a label issue change content, and a label issue number forming the label issue history information D4. . The issuance record file F4a is different from the issuance record file F4 in that the arrangement of the label issuance number column is different and the description method of the label issuance change name and the label issuance change contents # 1, # 2, and # 3 is different.

For example, in the issuance record file F4 as shown in FIG. 10A stored in the internal memory 178 or the CF card 179, the file number “00001” corresponding to the issuance date 05/01/08 and the issuer ID number = “ “001”, label issue change name = “link number”, label issue change content # 1 = “1”, and label issue number = 50.

Further, in the issuance record file F4, the file number “00001”, the issuer ID number = “001”, the label issuance change name = “link number”, and the label issuance change contents corresponding to the issuance date 05/01/08. # 1 = “2” and the number of issued labels = 50 are described. Further, the issue record file F4 has a file number “00001”, an issuer ID number = “002”, a label issue change name = “best before date”, a label issue change content corresponding to the issue date 05/01/08. "May 26, 2008", the number of issued labels = 30.

Similarly, in the issuance record file F4a as shown in FIG. 10B stored in the internal memory 178 or the CF card 179, the file number “00001” and the number of issued sheets = 10 corresponding to the issuance date 05/14/08. The issuer ID number = “003” and the name “AAA” are described. The issue record file F4a, like the issue record file F4, has a label issue change name and label issue change content # 1 column, and each label issue change name and label issue change content (for example, on the first line) Rather than describing the link number and 1) for each line, the change name at the time of label issuance (for example, the link number) and the change contents at the time of label issuance # 1 For example, the label issue change name and the label issue change contents are described in association with 2). The issue record file F4a shown in FIG. 10B can be easily and simply searched for its contents as compared to the issue record file F4.

Next, an example of information processing in the issuer & issue expiration date management system 100 will be described in four parts: a production management system 140, a label issue management system 130, a label printer 110, and a management viewer system 150.

[Examples of information processing in production management systems]
The FTP server 135, production management system 140, and management viewer system 150 will be described with reference to FIG. The management viewer system 150 shown in FIG. 11 shares editing and verification processing of the label issuance history information D4 generated by label issuance. The flowchart in the figure shows an example of information processing in the management viewer system 150 after issuing a label.

First, an example of information processing in the production management system 140 will be described with reference to FIG. In this example, the production management system 140 shares an issuance plan for the label 30 to be affixed to a product (including food) that has been manufactured and sold. The production management system 140 prepares information necessary for label issuance, for example, information related to food display, corresponding to the product planned for production and sales.

With this as an information processing condition, in the production management system 140, the information terminal device 141 supports a production plan for a product (including food) to be manufactured and sold in step ST1 of the flowchart shown in FIG. The information terminal device 141 is used to support a label issuance plan for attaching to the product. For example, the information terminal device 141 determines the amount of the product to be manufactured and sold and the expiration date thereof, issues the issuer list information D1, the layout data D2 of the label 30 to be attached to the product, and the reservation issue list data D3. Used to determine etc.

Next, in step ST2, the information terminal device 141 determines the amount of the product, its expiration date, issuer list information D1, layout data D2, reservation issuance based on the production plan of the product that has been previously determined for manufacture and sale. Information on food display such as list data D3 is created. Furthermore, in step ST3, the information terminal device 141 displays information related to food display such as the product price and the expiration date, issuer list information D1, layout data D2 of the label 30, and reservation issue list data D3. To record.

Thereafter, in step ST4, the information terminal device 141 branches the control depending on whether or not the recorded contents of the production plan database 142 are rewritten. If the recorded contents of the production plan database 142 are rewritten, the process proceeds to step ST5, and the information terminal device 141 updates the recorded contents of the production plan database 142. When the information regarding the food display before recording already exists in the production plan database 142, the information terminal device 141 updates the information regarding the food display.

The issuer list information D1, the layout data D2 of the label 30, the reservation issue list data D3, and the like are distributed from the production management system 140 to each food sales store, food manufacturing factory, and the like through the label issue management system 130. Thereafter, the process returns to step ST1. If the recorded contents of the production plan database 142 have not been rewritten, the process returns to step ST1 without updating the recorded contents. This makes it possible to prepare information relating to food display (information necessary for label issuance) corresponding to the product planned for production and sales by the production management system 140.

[Information processing example in the label issuance management system]
Next, an example of information processing in the label issue management system 130 will be described with reference to FIG. In this example, a user who manufactures or sells the product uses the label printers 110, 120, etc., and the information necessary for label issuance to the FTP server 135 when the product is manufactured or sold, for example, Request download of information about food labels.

With this as an information processing condition, in step ST11 of the flowchart shown in FIG. 13, the label issuance management system 130 accepts a download request for information necessary for label issuance corresponding to the product. At this time, the FTP server 135 receives, from the user's label printer 110, 120..., Etc., download request information for information necessary for label issuance, which is pasted when the product is sold.

In step ST12, the FTP server 135 checks whether the label printers 110, 120,. The check at this time is carried out by verifying whether or not the label printers 110, 120,... For example, whether or not a label printer has a function of identifying a person who is permitted to operate to issue a label, and whether or not the label printer can store issuer identification information, etc. You may make it discriminate | determine whether it is the label printer 110 grade | etc.,.

In response to the above request, when the label printers 110, 120,... Are managed, the FTP server 135 sets issuer identification information for each user in step ST13. The issuer identification information is set for each of the label printers 110 and 120 from the FTP server 135. This issuer identification information becomes issuer list information D1 in which a plurality of persons who are permitted to operate the label printer in order to issue a label are collected in a list. The issuer list information D1 is set for each corresponding label printer 110, 120 from the FTP server 135. In this example, the issuer identification information set in the label printer 110 or the like includes information for specifying the authority for changing the expiration date.

Thereafter, in step ST14, the FTP server 135 transmits the layout data D2 of the label 30 corresponding to the product to the management target label printer 110 and the like to be attached to the product. Further, the FTP server 135 sets addition date information regarding the expiration date of each product in the label printers 110 and 120. The expiration date of each product is calculated on the specified addition date.

In step ST15, the FTP server 135 receives the label issuance history information D4 from the label printers 110, 120,. The label issuance history information D4 is generated by the label issuance operation of the label printers 110, 120... In which the issuer identification information is set, and at least the issuer ID number, the issuance location, the number of issued pieces and the taste of the label 30. It is record information including a time limit. The label issuance history information D4 is stored as an issuance history file in the label printer 110, 120,. For example, the label issuance history information D4 up to the previous day is uploaded (transmitted) to the FTP server 135 from the label printer 110 or the like.

Thereafter, the process proceeds to step ST16, where the FTP server 135 accumulates the label issue history information D4 received for each label printer 110 in the issuer database 133 for each label printer 110 and processes the information. For example, in order to manage one or more label printers 110, the FTP server 135 monitors the presence / absence of label ordering data, associates the label ordering data with customer information, and registers them in the issuer database 133. (Issue label check function).

The FTP server 135 refers to the production plan database 142 of the production management system 140, and based on the production plan of the product to be manufactured and sold, the issuer list information D1 and the layout data D2 of the label 30 issued every day, When the reservation issue list data D3 or the like is rewritten, the recorded contents of the issue label database 132 and the issuer database 133 are rewritten. As a result, the FTP server 135 can accumulate and manage the label issue history information D4 for each user.

[Example of information processing in a label printer]
Next, the flow of information in the FTP server 135 and the label printer 110 will be described with reference to FIG. In this embodiment, a user (client) such as a label printer 110 used in each food sales store, food manufacturing factory, or the like corresponds to a product to be manufactured or sold with respect to the label issue management system 130. Request download (DL) of information necessary for label issuance, for example, information on food labeling.

Suppose that the information about the food display corresponding to the downloaded product is stored in a non-volatile memory such as the CF card 179 or the internal memory 178. In this example, the change contents at the time of label issuance are stored in the above-described nonvolatile memory as label issuance history information D4.

With these as information processing conditions, the label printer 110 is manufactured or sold in response to the user's operation input in step ST21 of the operation flowchart shown in FIG. The FTP server 135 of the label issuance management system 130 is requested to download information necessary for label issuance corresponding to the product, for example, information relating to food display.

Next, in step ST22, the label printers 110 and 120 appropriately download the issuer identification information corresponding to the product, the layout data D2 of the label 30, and the reservation issue list data D3. The issuer identification information is set for each of the label printers 110 and 120 from the FTP server 135. The issuer identification information includes issuer list information D1 in which persons who are permitted to issue labels are listed. The issuer list information D1 is set for each corresponding label printer 110, 120 from the FTP server 135.

In this example, the issuer identification information set in the label printer 110 includes information for specifying the authority for changing the expiration date. The issuer list information D1 corresponding to the product downloaded here, the layout data D2 of the label 30, and the reservation issue list data D3 are stored in a non-volatile memory such as the CF card 179 or the internal memory 178.

In step ST23, the label printer 110 executes issuer ID collation processing when issuing a label. In the issuer ID collation process, the user operates the numbers “0” to “9” of the input operation unit 174 and the character input key to input the issuer ID number and name. In this example, the user inputs “issuer ID number: 003” and “name YYY”.

Thereafter, the CPU 118a executes search processing for the issuer list file F1. In this example, it is assumed that “issuer ID number: 003” and “name YYY” are already registered in the issuer list file F1 shown in FIG. Then, the CPU 118a executes issuer ID number and name collation determination processing.

In this collation determination processing, input information relating to “issuer ID number: 003” and “name YYY” output from the input operation unit 174 and “issue” registered in the internal memory 178 or the CF card 179 from the FTP server 135 in advance. The CPU 118a compares the registration information regarding the “person ID number: 003” and “name YYY”, and the CPU 118a determines whether the input information and the registration information match or do not match.

In this example, the issuer ID numbers “003” and “name YYY” are registered in the issuer list file F1, the input “issuer ID number: 003” and “name YYY” and the FTP server in advance. Since “issuer ID number: 003” and “name YYY” registered in the internal memory 178 or the CF card 179 from 135 match, the process proceeds to step ST24.

In step ST24, the label printer 110 selects a label issued by the user. At this time, the label printer 110 has the authority to change the contents of the label, and if it is necessary to change the expiration date or the amount of money, the label expiration number or the amount of the product is changed to set the number of labels to be issued. decide. At this time, the CPU 118a executes an input process of contents to be changed when the label is issued. For example, the CPU 118a operates to rewrite the contents of the layout file F3 shown in FIG. 9A to the contents of the layout file F3a shown in FIG. 9B.

According to the layout file F3 shown in FIG. 9A and the layout file F3a shown in FIG. 9B which is a rewrite example thereof, the quantity is changed from “8” to “10” with respect to the product name “cookie assortment” of the link number “1”. Has been rewritten. Furthermore, the expiration date “3” (addition date) is rewritten to the expiration date “5” (addition date). In this example, after the label is issued, in order to describe the label issuance history information D4 in the issuance record file F4, the CPU 118a indicates the quantity “10” indicating the change contents at the time of issuance, the expiration date “5 (addition date)”, and the like. Internal storage data D52 is temporarily stored in RAM 118c.

In step ST25, the label printer 110 issues a label 30 based on information relating to food display such as layout data D2 and reservation issuance list data D3. At this time, the CPU 118a controls the printing unit 117 to execute a label issuing process. The printing unit 117 prints the label 30 based on the layout file F3a. Further, the CPU 118a increments the number of prints every time the printing unit 117 issues one label 30. After issuing the label, the CPU 118a temporarily stores in the RAM 118c internal storage data D82 indicating the number of issued labels 30 in order to describe the label issuance history information D4 in the issuance record files F4 and F4a.

In step ST26, the label printer 110 adds the label issue history information D4 and records it in a non-volatile memory such as the CF card 179 or the internal memory 178. For example, the CPU 118a controls the internal memory 178 and the CF card 179 so as to describe the label issue history information D4 in the issue record files F4 and F4a. At this time, the CPU 118a acquires the internal storage data D82 such as the quantity “10” and the expiration date “5 (addition date)” from the RAM 118c, for example, the label issuance history information in the issuance record file F4a in the CF card 179. Store D4. The issue record file F4a shown in FIG. 10B is provided with a description column for issue date, file number, number of issues, issuer ID number, issuer name, and issue change content # 1 # 2.

For example, 5/14/08 is described in the issue date. “000001” is described in the file number. “10” is described as the issued number, “001” is described as the issuer ID number, and “AAA” is described as the issuer name. A quantity “10” is described in the issue change content # 1. The expiration date 5/21/08 is described in the issue change content # 2.

In step ST27, the label printer 110 uploads the label issue history information D4 to the label issue management system 130 as appropriate. Alternatively, the label issuance history information D4 is fed back from the label printer 110 to the management viewer system 150 via the communication unit 43.

The label issuance management system 130 transfers the issuance record (label issuance history information D4) of the label 30 issued at each food sales store or food manufacturing factory to the production management system 140 in a timely manner. The label issuance history information D4 is used in the production management system 140 and the management viewer system 150 when verifying whether or not the label issuance processing has been correctly performed by the label printer 110.

In this example, when the uploading of the label issue history information D4 is completed, the label printer 110 determines the end of the label issue process in step ST28. For example, the CPU 118a monitors the operation data D74 from the input operation unit 174, and ends the label issuing process when the operation data D74 indicating printer off is detected. If the operation data D74 indicating that the printer is off is not detected, the process returns to step ST22 to continue the label issuing process.

[Information processing example in the management viewer system]
According to the information processing example in the management viewer system 150 shown in FIG. 11, in step ST31, the information processing apparatus 151 generates at least the issuer ID number of the label 30 and the issue location generated by the issue operation of the label printer 110 or the like. The label issue history information D4 including the number of issued cards and the expiration date is received.

Next, in step ST32, the information processing apparatus 151 checks the issuance record of the label 30 using a dedicated application. In step ST33, it is verified whether the label 30 has been issued as planned. In this verification process, for example, the label issuance including the issuer ID number of the label 30 at the product sales store, the product manufacturing factory, the number of sheets issued, the label issuance date, the amount of the product at the time of label issuance, the expiration date of the product, etc. The information processing apparatus 151 compares the history information D4 with production plan data including the number of labels 30 issued at the time of production planning, the label issuance date, the amount of the product, the expiration date of the product, and the like.

If the label 30 has been issued according to the production plan as a result of the comparison in step ST33, the process proceeds to step ST35, and the information processing apparatus 151 uses the dedicated application to make a production plan for the next product. . Information necessary for label issuance including the number of labels 30 issued, the label issuance date, the amount of the product, the expiry date of the product, etc. generated by the production plan of the product is managed from the information processing apparatus 151 transferred to step ST35. It is transferred to the production plan database 142 of the system 140. In the production plan database 142, the recorded contents are updated based on information necessary for label issuance generated by the production plan.

As a result of the above comparison and collation, if the label 30 has not been issued according to the production plan, for example, if a problem such as a shipping error or a forgery of the expiration date occurs, the process proceeds to step ST34 to remove the problem. The shipping error is grasped by tracking the label issuance history information D4 (issuance record). Then, the information processing apparatus 151 makes a production plan for the corresponding product again using the dedicated application.

Information necessary for label issuance including the number of labels 30 issued, the label issuance date, the amount of the product, the expiry date of the product, etc. generated by the product reproduction plan is transferred to step ST35 from the information processing apparatus 151. The data is transferred to the production plan database 142 of the production management system 140. In the production plan database 142, the recorded contents are rewritten based on information necessary for label issuance generated by the reproduction plan. Forgery can be prevented by prohibiting the issuance of a label describing the changed expiry date by adding a change restriction on the expiry date.

Thus, according to the issuer & issue expiration date management system 100 as an embodiment, the production management system 140, the label issue management system 130, the label printer 110, etc., and the management viewer system 150 are provided. The production management system 140 and the label issuance management system 130 make an issuance plan for the label 30 to be affixed to a product that has been manufactured and sold while sharing the label issuance history information D4. Label printers 110, 120, etc. issue labels 30. The management viewer system 150 executes issue history management for the label 30. In this way, label issuance can be centrally managed.

Moreover, the FTP server 135 is provided in the label issue management system 130. The FTP server 135 receives the label issuance history information D4 generated by the operation of the label printer at the time of label issuance after the label issuance from the label printer 110 or the like in which the issuer identification information is set. Thereafter, the FTP server 135 stores the label issuance history information D4 received from the label printers 110, 120, etc. for each label printer 110, 120 and processes the information.

Therefore, it becomes possible to centrally manage the label issuance history for each of the label printers 110, 120... Where the label 30 has been issued by a person who is permitted to operate the label printer for label issuance. Thereby, a production plan can be made based on the label issue history information D4 including the issuer ID number of the label 30, the number of issued cards, the amount, the expiration date, and the like. In addition, forgery of the expiration date, missed issuance of the expiration date, and the like can be prevented.

Incidentally, when a problem such as a shelf life issuance error occurs, the production management system 140 or the management viewer system 150 can search and verify (traceability) the label issuance history information D4 so that the cause can be investigated early. Become. Moreover, not only product management can be performed based on the label issuance history information D4 of the label 30 (change contents at the time of label issuance, issuer ID number, issuance date, etc.), but also expiration date management is simultaneously performed. You can also.

The present invention is extremely suitable when applied to an issuer that issues information on food labels on a label and issues a printed label, and an issue expiration date management system.

100 ... Issuing expiration date management system 110 ... Label printer 120 ... Label printer 130 ... Label issuance management system 131 ... Information storage device 135 ... FTP server 140 ... Production management system 141 ... Information terminal device 151 ... Information processing device 179 ... CF card D1 Issuer list information D2 Layout data D3 Reservation issue list data D4 Label issue history information

Claims (9)

1. A plurality of label printers that print information on labels and output printed labels;
   When the information for identifying the person who is permitted to operate the label printer for label issuance is used as the issuer identification information, at least a label issuance management device that sets the issuer identification information for each label printer,
   The label issuance management device
   The label issue history information generated by the operation of the label printer at the time of label issuance is received after the label is issued from each label printer in which the issuer identification information is set, and the label issue history information received from the label printer is A label issuance information processing system that stores and processes information for each label printer.
   
2. The label printer is
   A printing device for printing the information on a label and outputting the printed label;
   An input device for inputting issuer identification information of an issuer that issues a label printed out by the printing device;
   A control device that collates the identification information of the issuer input by the input device with the issuer identification information set from the label issuance management apparatus, and receives the label issuance based on a collation result. The label issuance information processing system according to the first item of the range.
   
3. The issuer identification information set for each label printer is:
   Including issuer list information in a list of persons who are permitted to perform label issuing operations by the label printer;
   The label issuance management device
   The label issuance information processing system according to claim 2, wherein the issuer list information is set in the corresponding label printer.
   
4. The label printer is provided with an issue history file,
   4. The label issuance information processing system according to claim 3, wherein identification information of the label issuer is input and recorded in the issuance history file when a label is issued.
   
5. The label issuance management device
   The label issuance information processing system according to claim 1, wherein the information is information relating to food display, and additional date information relating to the expiration date of each product is set in the label printer.
   
6. 6. The label issuance information processing system according to claim 5, wherein the expiration date of each product is calculated on the designated addition date.
   
7. In the issuer identification information set in the label printer,
   The label issuance information processing system according to claim 1, wherein the information is information related to food display and includes information for specifying an authority for changing the expiration date.
   
8. The label issuance management device
   Label issuance history information including at least the issuer ID number, issuance date, number of sheets to be issued, and expiration date of the label generated by the operation of the label printer is saved as an issuance history file in the label printer after label issuance. The label issuance information processing system according to claim 1, wherein the label issuance history information is received from the label printer.
   
9. 9. The label issuance information processing system according to claim 8, wherein the label issuance management device includes an information storage device for storing the label issuance history information received by the label issuance management device.

Images