JP5007741B2 - Label issuing information processing system - Google Patents

Description

  The present invention relates to an issuer that prints and issues information relating to food labeling on a label and a label issuance information processing system that can be applied to an issuance expiration date management system. Specifically, a label issuance management device that sets issuer identification information for each label printer is provided, and the label issuance operation is performed by accumulating the label issuance history information received from the label printer for each label printer for information processing. Label issuance history information including label issuer, number of issued items, amount of money, expiration date, etc., as well as enabling unifying management of label issuance information for each label printer that has been issued a label by an authorized person A production plan is made based on the above, and the forgery of the expiration date, the issuance error of the expiration date, and the like can be prevented.

  At present, food products sold at supermarkets, etc. are properly labeled so that the contents of food products etc. can be seen on their packaging containers, etc., according to the Food Sanitation Act and JAS Act (standardization and quality labeling of agricultural and forestry substances) It is required by the Act on Optimization. In this food labeling, it is necessary to satisfy the minimum labeling items stipulated in the Food Sanitation Law and JAS Law. 7 items such as name (product name), raw material name (improves that it is a genetically modified food, food additive), content, expiration date (expiration date, expiration date), storage method and manufacturer, location of the factory, etc. Display items required for Normally, all of these display items are printed on a label sheet (roll paper), and the printed label is attached to the packaging container.

  Usually, a label printer is used for creating and attaching a label. The label printer prints layout information directly input from an input operation unit or layout information input through a memory card after being created by a personal computer (hereinafter referred to as a personal computer) on a label. . The roll paper for labels is a label printer body in which a seal-like label of a predetermined size is continuously temporarily fixed to a strip-like release paper at a constant pitch and is wound in a roll shape. It is attached to.

  As described above, the label printer is provided with a memory means for storing printing information, reads out layout information (standard version) including printing information, and is a display item suitable for items produced, manufactured and processed by the user. And the display contents are changed and stored in association with each item. In addition, since the selling price of the item is often changed every day, when actually printing, after reading the saved item layout (layout information) and correcting the price printed in the price item column, A predetermined number of labels are printed.

  In relation to this type of label printer, Patent Document 1 discloses a system that performs pricing based on a product master for each user distributed from a management server. In Patent Document 2, selling price information is received from a central apparatus connected via a communication line so that the selling price can be updated efficiently. Japanese Patent Application Laid-Open No. 2004-228561 makes it possible to access a file storing product sales price information and the like via a communication line.

JP 2004-351775 A JP-A-7-205950 Japanese Patent Laid-Open No. 11-232067

  By the way, according to the label printer as shown in the conventional example and Patent Documents 1 to 3, even a person other than the person authorized to issue the label can operate the label printer to issue the label. In this way, if anyone can issue a label without specifying the label issuer, it becomes difficult to check the label issuance history if there is any problem. 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, and the label issuance plan including the label issuer, the number of issuance, amount of money, expiration date, etc. is linked to the production plan for the products that are sold and manufactured. The information management system has not been established yet. Therefore, the present situation is that the forgery of the expiration date and the issuance mistake of the expiration date cannot be prevented. By the way, when a problem such as a shelf life issuance error occurs, it is difficult to find out the cause at an early stage because information for searching and verifying the label issuance history is not prepared.

  Accordingly, the present invention solves the above-described problems, and label issuance information that enables centralized management of label issuance history information for each label printer in which a label is issued by a person who has been permitted to issue a label. An object is to provide a processing system.

In order to solve the above problems, a label issuance information processing system according to the present invention includes a plurality of label printers that print information on label issuance printed on a label and outputs the label, and issuance history information received from the label printer. A label issuance management apparatus that stores and unifies the information for each unit, and the label issuance management apparatus uses the issuance identification information for each label printer when the information for identifying the person authorized to issue the label is used as the issuer identification information. In the label issuance information management system for setting the issuer identification information, the issuer identification information set for each label printer is issuer list information that is a list of persons who are permitted to issue label issuance operations by the label printer. The label issuance management device downloads information relating to label issuance from the label printer. The label printer requesting download is checked whether the label printer is a management target label printer. If the label printer is a management target label printer as a result of the check, the issuer list information is It is characterized by being transferred to a label printer .

According to the label issuance information processing system according to the present invention, the plurality of label printers print information on label issuance on labels and output them. The label issuance management apparatus accumulates the issuance history information received from the label printer for each label printer and centrally manages it. Based on this assumption, the label issuance management apparatus sets issuer identification information for identifying a person who is permitted to perform a label issuance operation for each label printer . Also, the label issuance management apparatus receives a request for downloading information relating to label issuance from the label printer, checks whether the label printer that requests download is a label printer to be managed, and requests download as a result of the check. When the label printer is a management target label printer, the issuer list information is transferred to the label printer . Accordingly, it is possible to centrally manage the label issuance history for each label printer in which a label is issued by a person who is permitted to perform the label issuance operation.

The label issuance information processing system according to the present invention includes a label issuance management device that accumulates label issuance history information received from a label printer for each label printer and centrally manages the label issuance management information. The issuer identification information for identifying the person who is permitted to operate is set for each label printer, the label printer that receives the download request for the information about the label issuance is received from the label printer, and the label printer that requests the download is the label printer to be managed If the label printer requesting download is a label printer to be managed as a result of the check, the issuer list information is transferred to the label printer .

  With this configuration, it is possible to centrally manage the label issuance history for each label printer from which a label has been issued by a person who has been permitted to issue a 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 1 as embodiment. 3 is a block diagram illustrating a configuration example of a control system of an FTP server 20. FIG. 1 is a perspective view showing an example of the appearance of a label printer 100. FIG. 5 is a plan view showing a configuration example of an input operation unit 74. FIG. 3 is a block diagram illustrating a configuration example of a control system of the label printer 100. 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. (A) And (B) is a table | surface figure which shows the layout file F3 and its rewriting example. (A) And (B) is a table | surface figure which shows the example of description of the issue recording files F4 and F4 '. 4 is an explanatory diagram showing a flow of information in the FTP server 20, the production management system 400, and the management viewer system 500. FIG. 4 is a flowchart illustrating an information processing example in a production management system 400. 5 is a flowchart illustrating an information processing example in a label issue management system 300. 3 is an explanatory diagram showing a flow of information in the FTP server 20 and the label printer 100. FIG.

  Hereinafter, a label issuing information processing system as an embodiment according to the present invention will be described with reference to the drawings. FIG. 1 is an explanatory diagram illustrating a configuration example of an issuer & issuance expiration date management system 1 as an embodiment.

  The issuer & issuance expiration date management system 1 shown in FIG. 1 constitutes an example of a label issuance information processing system, and includes a plurality of label printers 100 that print and issue information relating to food display on a label 30 (see FIG. 8). This is a system for managing issuers that handle this, and is a system applicable to the food industry, food manufacturing factories, and the like, in which the label printer 100 issues a label 30 with a time limit.

  The issuer & issue expiration date management system 1 includes one or more label printers 100, a label printer 200 with a communication function, a label issue management system 300, a production management system 400, and a management viewer system 500. Composed.

  The label printer 100 prints and outputs information relating to food display on the label 30 (see FIGS. 2 to 4). The label printer 100 is disposed in a food sales store, a food manufacturing factory (line), or the like, and is operated by an employee who is engaged in the store, the factory line, or the like, a part-time employee, or a part-time worker. The label printer 100 is used under a contract between a management user and a manufacturer / seller of the same store or factory. The label printer 100 is used by being connected to a modem for processing communication information (hereinafter simply referred to as modem 37).

One end of the modem 37 is connected to the label printer 100 during information communication, and the other end is connected to the communication means 43. 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 100, a label printer 200 with a communication function is also used. The label printer 200 has a communication modem function inside, and is directly connected to a communication means 43 such as a public communication line.

  The label issue management system 300 includes an information management server (hereinafter simply referred to as FTP server 20) compliant with a file transfer protocol, an information storage device 31, and a modem 36.

  The FTP server 20 constitutes an example of a label issuance management apparatus, and has a function of mediating between the label printers 100, 200... On the client side and the production management system 400. In this example, the FTP server 20 has a function of checking the issuance of the label 30 and sets issuer identification information for each label printer 100 that prints and outputs information relating to food display on the label 30 at least. . 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.

  The issuer ID numbers are collected in a list showing a list of persons who are permitted to issue the label of the label printer 100, and the issuer ID number information collected in this list is called issuer list information D1. . The FTP server 20 sets the issuer list information D1 for each corresponding label printer 100, 200.

  Further, the FTP server 20 sets addition date information regarding the expiration date of each product in the label printer 100. The expiration date of each product is calculated on the specified addition date. In this example, the issuer identification information set in the label printer 100 includes information for specifying the authority for changing the expiration date.

  The FTP server 20 is connected to the communication means 43 via the modem 36 and manages one or more label printers 100. For example, the FTP server 20 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 20. The FTP server 20 generates a label issuance history including at least the issuer, the issue date, the number of issued items, and the expiration date of the label 30 caused by the issue operation of the label printers 100, 200,. After the label is issued, the information D4 is stored as an issue history file in the label printer, and the label issue history information D4 is received from the label printer 100, 200,. Further, the FTP server 20 stores the label issuance history information D4 received for each label printer 100 for each label printer 100 to process the label issuance history information D4.

  The FTP server 20 includes a large-capacity information storage device 31 such as a hard disk, and stores label issuance history information D4 received from the label printers 100, 200 and the like. An issue label database 32 and an issuer database 33 are constructed in the information storage device 31. In the issue label database 32, layout data D2, issue record (history information), reservation issue update list, and the like are recorded. In the issuer database 33, a person who is permitted the label issuing operation is registered.

  An information terminal device 41 for production management is connected to the FTP server 20 via communication means 40 such as a LAN (Local Area Network). A personal computer is used for the information terminal device 41. A production plan database 42 is connected to the information terminal device 41, and records information related 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. It is made to update.

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

  In the issuer & issue expiration date management system 1, issuer list information D 1 provided from the label issue management system 300, layout data D 2 of the label 30, reservation issue list data D 3, etc. are included in the production plan of the production management system 400. Updated based on. The label issuance management system 300 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.

  An information processing device 51 dedicated to the management viewer is connected to the communication means 43 via the modem 38. The information processing apparatus 51 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 100, 200 or the like. The information processing apparatus 51 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 51.

  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 38 and the information processing apparatus 51 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 500. In this example, the management viewer system 500 may be arranged at the production site, and information processing may be performed by connecting to the communication means 40 such as a LAN connecting the label issuing management system 300 and the production management system 400 described above.

  The record of the label 30 issued at each food sales store, food manufacturing factory, etc. is fed back to the production management system 400 in a timely manner, and an appropriate label such as the amount of the product and its expiration date as planned by the information terminal device 41. It is checked whether 30 has been issued. Further, when an error is detected in the check in the information terminal device 41, a tracking investigation such as a shipping error is performed based on the issuance record. In this example, the production state at the time of the problem can be traced by verifying the contents of the production plan database 42. In addition, forgery can be prevented by adding a change restriction to the remaining date of the issued expiration date.

  Next, a configuration example of the control system of the FTP server 20 will be described. FIG. 2 is a block diagram illustrating a configuration example of a control system of the FTP server 20. The FTP server 20 shown in FIG. 2 has a function of mediating between the label printers 100, 200... On the client side and the production management system 400. For example, the FTP server 20 includes the control unit 2, communication interfaces 24 and 27, an information storage device 31, an input operation unit 34, and a display unit 35.

  The control unit 2 includes a ROM (Read Only Memory) 21, a work RAM (Random Access Memory) 22, a system bus 23, a CPU (Central Processing Unit) 25, and an I / O interface 26. The The CPU 25 is connected to the ROM 21 via the system bus 23 and stores system activation program data D21 for controlling the entire FTP server. In addition to the program data D21, issuer identification information, and label issuance history information D4, the RAM 22 connected to the system bus 23 temporarily stores information control commands and layout data D2.

  When the power is turned on, the CPU 25 reads the program data D21 for system activation from the ROM 21 to the RAM 22, activates the system, and controls the entire FTP server. An I / O interface 26 is connected to the CPU 25 and controls input / output of user interfaces such as the input operation unit 34 and the display unit 35. The I / O interface 26 inputs operation data D34 at the time of system startup from the input operation unit 34.

  The input operation unit 34 is operated when inputting addition date information (expiration date) and the like of each product transferred from the label issuance management system 300 to the stand-alone type label printer 100 and registered. The expiration date of each product is an addition date designated by the label issue management system 300 to the label printer 100 or the like. The input operation unit 34 is configured to output operation data D34 such as addition date information to the CPU 25.

  The CPU 25 refers to the production plan database 42 based on an instruction (operation data D34 or the like) from the input operation unit 34 or an input operation unit (not shown) of the information processing device 51 (administrative user), and products based on the production plan The label 30 and the issuer list applied to the are updated.

  On the display unit 35, a layout video based on the layout data D2 is displayed, and input information in the input operation unit 34 is displayed. The layout data D2 is information that is laid out so that the minimum display information that must be displayed on each of the display items related to food display described above can 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 35 based on the display data D35.

  The FTP server 20 includes a large-capacity information storage device 31 such as a hard disk, and stores label issue history information D4 received from the label printers 100, 200, and the like. The information storage device 31 includes an issuance label database 32 in which layout data D2, issuance record (history information), a reservation issuance update list, and the like are recorded, and an issuer database 33 in which a person who is permitted to issue a label is registered. Built.

  In this example, a data processing unit 39 is connected to the system bus 23 to execute data writing to the information storage device 31 or data reading processing from the information storage device 31. For example, in addition to the addition date information of each product transferred from the CPU 25 to the label printer 100 or the like, the data processing unit 39 issues issuer list information D1 such as an issuer name and its ID number (hereinafter referred to as issuer ID number). Is controlled to transfer.

  In addition, when changing the expiration date at the time of label issuance, control is performed such that the authority that only a specific issuer can change is added to issuer list information D1 and transferred. For example, when the label is issued, the expiration date change permission data is added 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, at the time of label issuance and when the expiration date is changed, the label printer side inputs the issuer ID number, etc., and issues who changed the expiration date of the label 30 or who issued the label 30. It will be left in the history file. These changes are returned to the FTP server 20, and depending on the data processing unit 39, the contents stored in the issue label database 32 and the issuer database 33 are rewritten.

  A communication interface 24 is connected to the system bus 23 described above. The interface 24 is connected to the external terminal 28. A communication modem 36 is connected to the external terminal 28 and is connected to a public communication line such as the Internet. The interface 24 is configured to execute communication processing between a plurality of label printers 100, 200, and the like. In this communication process, the label issuance history information D4 is obtained from the plurality of label printers 100, 200, etc. For example, after the label is issued, the interface 27 receives from the label printer 100 label issuance history data indicating who, when, where, how many sheets, and what expiry date the label 30 has been issued. .

  In addition to the communication interface 24, a communication interface 27 is connected to the system bus 23. The interface 27 is connected to the external terminal 29. An information terminal device 41 of the production management system 400 is connected to the external terminal 29 via a communication means 40 such as a LAN. The interface 27 transmits the label issuance history data stored in the FTP server 20 to the information terminal device 41 of the production management system 400.

  In order to feed back to the production plan for the next product, the information terminal device 41 checks whether an appropriate label 30 (amount, expiration date, etc.) has been issued as planned. Thus, the label issue management system 300 in which the FTP server 20 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 41 of the production management system 400, the information processing device 51 of the management viewer system 500, or the like.

Next, a configuration example of the label printer 100 will be described. FIG. 3 is a perspective view showing an example of the appearance of the label printer 100. A label printer 100 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 100 has an apparatus main body 101. The apparatus main body 101 includes an upper housing 11 and a lower housing 12 that are resin-molded according to a predetermined design. The upper housing 11 and the lower housing 12 are engaged with a hinge mechanism 13 so as to be freely opened and closed.

A roll paper for label printing (not shown), a printing unit 7 as shown in FIG. 5, a control unit 8, and the like are mounted in the lower housing 12 so that information relating to food display is printed on a label and output. Made. An input operation unit 74 and a display unit 75 are provided on the upper surface of the upper casing 11, and when inputting identification information (issuer ID number) of an issuer that issues a label 30 printed out by the printing unit 7. Operated. In this example, the label 30 is output from the vicinity of the boundary between the upper casing 11 and the lower casing 12 on the front side of the apparatus main body 101.

  FIG. 4 is a plan view illustrating a configuration example of the input operation unit 74. The input operation unit 74 shown in FIG. 4 constitutes an example of an input unit. The input operation unit 74 includes numbers “1” to “9”, “0” keys K1 to K10 that constitute numeric keys, a conversion / blank key K11, An issue key K12, a confirmation key K13, a stop / delete key K14, a test print key K15, a cross key K16, an input key K17, a date key K18, a cancel key K19, an edit key K20, a shift key K21, and the like are provided.

  The numbers “1” to “9” and “0” keys K1 to K10 are used when, for example, the contents of the layout file F3 shown in FIG. 9 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 numbers “1” to “9” and “0” keys K1 to K10 are also operated when inputting the issuer ID number of the issuer who issues the label 30. Furthermore, when setting the number of labels 30 to be issued, the numbers “1” to “9” and “0” keys K1 to K10 are operated to input the quantity and the like.

  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. Other conversion / blank key K11, confirm key K13, stop / delete key K14, cross key K16, input key K17, date key K18, cancel key K19, edit key K20, shift key K21, etc. are included in layout file F3 of label 30. Used when editing and validating content.

  FIG. 5 is a block diagram illustrating a configuration example of the control system of the label printer 100. A label printer 100 shown in FIG. 5 prints information related to food display on a label 30 in order to print out the printing unit 7, a control unit 8, an input operation unit 74, a display unit 75, an internal memory 78 for issuer management, A compact flash (registered trademark) memory card (hereinafter referred to as a CF card 79) for issue history management is provided.

  The control unit 8 includes a CPU 80, a ROM 81, a work RAM 82, a system bus 83, and an I / O interface 86. A ROM 81 is connected to the CPU 80 via a system bus 83, and system start program data D81 for controlling the entire printer is stored. A RAM 82 connected to the system bus 83 temporarily stores program data D81 and control commands for executing information processing such as rewriting, editing, and verification.

  Further, the internal storage data D82 is temporarily stored in the RAM 82. 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 80 reads the program data D81 for system activation from the ROM 81 to the RAM 82, activates the system, and controls the entire printer. An I / O interface 86 is connected to the CPU 80 and controls input / output of user interfaces such as the input operation unit 74 and the display unit 75. The I / O interface 86 inputs operation data D74 at the time of system startup from the input operation unit 74.

  In this example, the input operation unit 74 sets the number of labels 30 to be issued, the expiration date (addition date), in addition to the issuer ID number of the operator who issues the label 30 printed out by the printing unit 7. ), The operation data D74 input when the label 30 is issued, the test print, the contents of the layout file F3 is edited or verified, and the like are output to the control unit 8.

  In this example, the display unit 75 displays the layout data D2 and the input information on the input operation unit 74. The layout data D2 is information that is laid out so that the minimum display information that must be displayed on each of the display items related to food display described above can be displayed on the label 30 of a predetermined size. The input information for the layout data D2 is information that can be edited and verified such as the date of manufacture, the expiration date, the content and the sales price, and the input operation unit 74 corrects the information that can be edited and verified. It functions as a means for inputting. The layout data D2 is displayed on the display unit 75 based on the display data D75.

  The printing unit 7 is placed under the control of the CPU 80 to achieve the printer function, and includes a label transport system 71, a print head 72, a roll paper loading detection unit 76, and a printer control unit 77, Information relating to the display is printed on the label 30 and output.

  The printer control unit 77 is connected to the system bus 83 and receives printer control data D77 from the CPU 80 and paper loading detection data D76 from the roll paper loading detection unit 76 to control output of the label transport system 71 and the print head 72. Execute. The printer control unit 77 shares the control of the CPU 80 and reduces the control burden.

  The label transport system 71 and the print head 72 are connected to the printer control unit 77. The label transport system 71 is controlled to input the transport control data D 71 and transport the roll paper below the print head 72. The conveyance control data D71 is output from the printer control unit 77 to the label conveyance system 71.

  The print head 72 inputs print control data D72, prints predetermined layout data D2 relating to food display on the label roll paper conveyed by the label conveyance system 71, and outputs the label 30. The print control data D72 is output from the printer control unit 77 to the print head 72. As the print head 72, a thermal head is usually used. The thermal head is a line head, but is not limited to a line head.

  In this example, the label transport system 71 is provided with a roll paper loading detection unit 76. When the roll paper becomes empty, loading of the roll paper is detected and paper loading detection data D76 is output to the printer control unit 77. . The paper loading detection data D76 detects the number of times the new roll paper has been replaced and prompts replacement of the print head 72.

  The CPU 80 collates the issuer ID number input by the input operation unit 74 with issuer identification information (issuer ID number) set from the FTP server 20, and accepts a label issuing operation based on the comparison result. To be made. For example, when the expiration date is changed, the CPU 80 executes rewriting control of information relating to food display. However, when an operation input for changing the expiration date is received from the input operation unit 74 regarding the expiration date printed on the label 30, the operation is performed. Regardless of the expiration date (addition date) based on the data D34, the addition date is calculated from the addition date information designated by the FTP server 20.

  The CPU 80 stores the content of the information related to food display changed at the time of label issuance as label issuance history information D4. The CPU 80 stores label issuance history information D4 (location (store), issuance date, issuer ID number, expiration date, amount of money, number of issuances) at the time of label issuance, and stores the label issuance history information D4 having the same contents as the FTP server 20. To be transferred.

  The above-described system bus 83 is connected to an internal memory 78 that constitutes an example of an issuance history file. The issuer ID number, issuer name, and label change authority for issuer management downloaded from the label issuance management system 300 are displayed. Including issuer list information D1, layout data D2 such as product name, raw material, quantity, expiration date, amount of money, number of labels 30 to be issued, and reservation issuance list data D3. When the label is issued, for example, information for identifying the issuer is read from the internal memory 78 to the RAM 82. The issuer ID number stored in the internal memory 78 is preset from the FTP server 20.

  Further, the issuer ID number (ID code) input by the input operation unit 74 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 100. It is. The internal memory 78 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 73 is connected to the system bus 83 described above, and a CF card 79 for issue history management is mounted. For the CF card 79, for example, a USB memory, which is a portable nonvolatile memory, is used. The CF card 79 stores the layout data D2 of the label 30 downloaded from the label issuance management system 300.

  In the CF card 79, in addition to the layout data D2, label issue history information D4 is described in issue record files F4 and F4 '(see FIG. 10). The label issuance history information D4 is information collected from the internal storage data D52 and transferred from the RAM 82. 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 78 or the CF card 79, it becomes possible to centrally manage who exactly issued what label 30 when and what (see FIG. 10). . In this example, the internal memory 78 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 79 or independently of the CF card 79.

  In addition to the memory card interface 73, a communication interface 84 is connected to the system bus 83 described above. The interface 84 is connected to the external terminal 85. A communication modem is connected to the external terminal 85 and is connected to a public communication line such as the Internet so as to execute communication processing with the FTP server 20 of the label issue management system 300. In this communication process, the layout data D2 acquired from the above-described memory card interface 73 is directly acquired from the FTP server 20. These constitute the label printer 100.

  FIG. 6 is a table showing a configuration example of the issuer list file F1. The issuer list file F1 shown in FIG. 6 is constructed in the issuer database 33 of the label issue management system 300, and is transferred to the internal memory 78 or the CF card 79 together with a usage management contract for the label printer 100, for example. 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 = No. 001 is described, and ID number = No. In 001, the name of the issuer is described. Similarly, ID number = No. 003 describes the name of the issuer ΔΔΔΔ. ID number = No. In 004, the name of the issuer is described. The issuer list file F1 is described in the internal memory 78 or the CF card 79 based on the operation data D74 indicating the issuer ID number.

  FIG. 7 is a table showing a configuration example of the food list file F2. The food list file F2 shown in FIG. 7 is transferred from the FTP server 20 of the label issue management system 300 to the CF card 79 or the internal memory 78, 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, “1” is described in the link number column, “cookie” is described in the product name column of the link number “1”, and “flour, egg, milk, almond” is described in the raw material column. “10” is described in the “Best before date (addition date)” column, “750” is described in the “Price” column, and “001” is described in the “Part number” column.

  Similarly, “cake” is described in the item name column of the link number “2”, “flour, egg, milk, strawberry” is described in the raw material column, and the expiration date (addition date) column thereof. “1” is described in “No.”, “350” is described in the price column, and “002” is described in the product number column.

  “Norayaki” is described in the product name column of the link number “3”, “Flour, red beans, milk” is described in the raw material column, and “3” is displayed in the expiration date (addition date) column. “300” is described in the price column, and “003” is described in the product number column. The list file F2 for food is developed on the display unit 75. When the link number is specified by operating the input operation unit 74, the label 30 is issued 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.

FIG. 8 is a plan view illustrating a configuration example of the label 30. According to the label 30 shown in FIG. 8, when the contents of the layout file F3 are read from the food list file F2 ( cited ) and the label 30 is issued, the link number “1” is issued in the list file F2. Is entered on the roll paper for the label of length l x width w, "cookie" is printed in the item name field that is the content of the link number "1", and "flour, egg, milk, almond""," 10 "is printed in the expiration date (addition date) field," 750 "is printed in the price field, and" 4923100107508 "is printed in the barcode field. The The layout data D2 in the broken line frame in the figure is read ( quoted ) from the list file F2 and printed.

  9A and 9B are table diagrams showing the layout file F3 and an example of rewriting thereof. The layout file F3 shown in FIG. 9A is obtained by correcting the content before rewriting. The layout file F3 shown in FIG. 9B is the contents of the rewritten layout file F3 '.

  As shown in FIG. 9A, the contents of the layout file F3 before rewriting are described with “1” in the link number column and “cookie assortment” in the product name column with the link number “1”. "Wheat flour, eggs, ..." is described in the column, "750" is described in the price column, "8" is described in the quantity, and the expiration date (addition date) "3" is described in the column of "3", and "XX Co., Ltd." is described in the column of the manufacturer.

  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”. In this case, the quantity “8” of “cookie assortment” in the layout file F3 before rewriting is updated (overwritten) to “10”. Further, the expiration date (addition date) “3” is updated (overwritten) to “5”.

  As shown in FIG. 9B, the contents of the rewritten layout file F3 ′ are described with “1” in the link number column and “cookie assortment” in the item name column with the link number “1”. “Wheat flour, eggs,...” Is described in the raw material column, “750” is described in the price column, “8” is described in the quantity, and the expiration date (addition date) ) Column describes the date of August 13, 2008 when the date of production is August 10, 2008 and the date of addition is “3”. “XXX” is described.

  10A and 10B are table diagrams showing examples of description of the issue record files F4 and F4 '. The contents of the issue record files F4 and F4 'shown in FIGS. 10A and 10B are described (saved) in the internal memory 78 or CF card 79 for issue history management. In this example, the issue record files F4 and F4 'are provided with description columns for the issue date, file number, issuer ID number, issue name change name, issue change contents, and number of issues that form the label issue history information D4. The difference between the issue record files F4 and F4 'is a modification of the description method of the issue number description position, issue name change name, and issue change contents # 1, # 2, and # 3.

  For example, in the issuance record file F4 constructed in the internal memory 78 or the CF card 79 as shown in FIG. 10A, the file number “00001” and the issuer ID number = “001” with respect to the issue date 08/05/01. ”, Change name at issue =“ link number ”, issue change content # 1 =“ 1 ”, issued number = 50.

  Further, the issue record file F4 has a file number “00001”, an issuer ID number = “001”, an issue change name = “list number”, and an issue change content # 1 = for the issue date 08/05/01. “2” and the number of issued sheets = 50 are described. The issue record file F4 has a file number “00001”, issuer ID number = “002”, change name at issue = “best before date”, issue change content “05/2008” for the issue date 08/05/01. 26th month ", number of issued sheets = 30 sheets is described.

  In the issue record file F4 ′ constructed in the same manner as shown in FIG. 10B, the file number “00001” and the number of issues = 10 are described for the issue date 08/05/14, and the issuer ID number is issued. = “003” and name “ΔΔΔΔ” are described. In the issue record file F4 ′, there is no itemization description between the issue name change name and issue change content # 1 as in the issue record file F4, and the issue change name in the issue change content # 1 in parentheses. To be described. In the case shown in FIG. 10B, the content search of the issuance record file F4 'can be made easier and simpler than the issuance record file F4.

  Next, an example of information processing in the issuer & issuance expiration date management system 1 will be described in four parts: a production management system 400, a label issuance management system 300, an operation example in the label printer 100, and a management viewer system 500.

[Examples of information processing in production management systems]
FIG. 11 is an explanatory diagram showing the flow of information in the FTP server 20, the production management system 400, and the management viewer system 500. The management viewer system 500 shown in FIG. 11 shares the 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 500 after label issuance. In this example, an information processing example in the production management system 400 will be described first.

  FIG. 12 is a flowchart showing an information processing example in the production management system 400. In this example, the production management system 400 shares an issuance plan for the label 30 to be affixed to a product (including food) that has been manufactured and sold. In the production management system 400, information relating to label issuance, for example, information relating to food display, is prepared corresponding to the product planned for manufacture and sale.

With this as an information processing condition, in the production management system 400, the information terminal device 41 supports a production plan of a product (including food) to be manufactured and sold in step ST1 of the flowchart shown in FIG. Used to assist in label issuance plans. For example, the information terminal device 41 determines the price 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 41 lays out the amount of the product, its expiration date, issuer list information D1, and issuance of the label 30 based on the production plan of the product that has been previously determined for manufacture and sale. Information related to food display such as data D2, reservation issuance list data D3, etc. is created. Furthermore, in step ST3, the information terminal device 41 displays information related 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 issuance list data D3. To record.

  Thereafter, in step ST4, the information terminal device 41 branches the control depending on whether or not the recorded contents of the production plan database 42 are updated. If the recorded contents of the production plan database 42 are rewritten, the process proceeds to step ST5, and the information terminal device 41 updates the recorded contents of the production plan database 42. When the information regarding the food display before recording already exists in the production plan database 42, the information terminal device 41 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 400 to each food sales store, food manufacturing factory, and the like through the label issue management system 300. . Thereafter, the process returns to step ST1. If the recorded contents of the production plan database 42 have not been rewritten, the process returns to step ST1 without updating the recorded contents. As a result, it becomes possible to prepare information relating to food display (information relating to label issuance) corresponding to a product planned for manufacture and sale by the production management system 400.

[Information processing example in the label issuance management system]
FIG. 13 is a flowchart illustrating an information processing example in the label issuance management system 300. In this example, a user who manufactures or sells the product uses label printers 100, 200,..., Etc., information relating to label issuance that is affixed to the FTP server 20 when the product is manufactured or sold, for example, food display A request to download information about is made.

  With this as an information processing condition, the label issuance management system 300 accepts a download request for information relating to label issuance corresponding to the product in step ST11 of the flowchart shown in FIG. At this time, the FTP server 20 receives, from the user's label printer 100, 200...

  In step ST12, the FTP server 20 checks whether the label printer 100, 200,. The check at this time is performed by verifying whether the printer is a label printer 100, 200,... Constituting the issuer & issue expiration date management system 1. For example, it may be determined whether the label printer 100 is a management target based on whether or not the label printer is capable of storing a function for identifying a person authorized to issue a label and issuer identification information. Good.

In response to the above request, if the label printers 100, 200,... Are to be managed, the FTP server 20 sets issuer identification information for each user in step ST13. The issuer identification information is set for each of the label printers 100 and 200 from the FTP server 20. This issuer identification information becomes issuer list information D1 in which a plurality of persons permitted to perform label issuing operations are collected in a list. The issuer list information D1 is set for each corresponding label printer 100, 200 from the FTP server 20. In this example, the issuer identification information set in the label printer 100 includes information for specifying the authority for changing the expiration date.

After that, in step ST14, the FTP server 20 transmits the layout data D2 of the label 30 corresponding to the product and attached to the product to the managed label printer 100 or the like. Further, the FTP server 20 sets addition date information regarding the expiration date of each product in the label printers 100 and 200 . The expiration date of each product is calculated on the specified addition date.

  In step ST15, after issuing the label, the FTP server 20 receives the label issuance history information D4 from the managed label printers 100, 200,. The label issue history information D4 is a record including at least the issuer, the issue location, the number of issued items, and the expiration date of the label 30 generated by the issue operation of the label printers 100, 200,. Information. The label issuance history information D4 is stored as an issuance history file in the label printer 100, 200,. For example, the label issue history information D4 up to the previous day is uploaded (transmitted) to the FTP server 20 from the label printer 100 or the like.

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

  The FTP server 20 refers to the production plan database 42 of the production management system 400, and issues the issuer list information D1 based on the production plan of the product to be manufactured and sold, the layout data D2 related to the issuance of the label 30 every day, the reservation When the issue list data D3 and the like are rewritten, the contents recorded in the issue label database 32 and the issuer database 33 are updated. As a result, the FTP server 20 can accumulate and issue the label issuance history information D4 for each user.

[Example of operation in a label printer]
FIG. 14 is an explanatory diagram showing the flow of information in the FTP server 20 and the label printer 100, and shows an operation flowchart in the label printer 100. In this embodiment, a user (client) such as a label printer 100 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 300. Requests download (DL) of information relating to label issuance, for example, information relating to food labeling.

  The case where the information regarding the food display corresponding to the downloaded product is stored in a nonvolatile memory such as the CF card 79 or the internal memory 78 is taken as an example. In this example, the change contents at the time of label issuance can be stored in the above-mentioned nonvolatile memory as the label issuance history information D4.

  Under these operating conditions, the label printer 100 is subject to manufacture or sale in response to the user's operation input in step ST21 of the operation flowchart shown in FIG. The FTP server 20 of the label issue management system 300 is requested to download information relating to label issuance corresponding to the product, for example, information relating to food display.

Next, in step ST22, the label printers 100 and 200 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 100 and 200 from the FTP server 20. 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 100 , 200 from the FTP server 20.

  In this example, the issuer identification information set in the label printer 100 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 nonvolatile memory such as the CF card 79 or the internal memory 78.

  In step ST23, the label printer 100 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 74 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 ΔΔΔΔ”.

  Thereafter, the CPU 80 executes search processing for the issuer list file F1. In this example, “issuer ID number: 003” and “name ΔΔΔΔ” are already registered in the issuer list file F1 shown in FIG. Then, the CPU 80 executes an issuer ID number and name collation determination process.

  In this collation determination processing, input information relating to “issuer ID number: 003” and “name ΔΔΔΔ” output from the input operation unit 74 and pre-registered from the FTP server 20 to the internal memory 78 or the CF card 79. In addition, the CPU 80 compares the registration information related to “issuer ID number: 003” and “name ΔΔΔΔ”, and determines whether the input information and the registration information match or do not match.

  In this example, the issuer ID number “003” and “name △△△△” are registered in the issuer list file F1, and the “issuer ID number: 003” and “name △△△△” that have been input are processed. ”And“ issuer ID number: 003 ”and“ name ΔΔΔΔ ”registered in advance in the internal memory 78 or the CF card 79 from the FTP server 20 are transferred to step ST24.

  In step ST24, the label printer 100 selects a label to be issued by the user, and if the issuer has the authority to change the label and needs to change the expiration date, amount, etc., change the expiration date, amount, etc. The number of labels issued is determined. At this time, the CPU 80 executes an input process of change contents at the time of label issuance. For example, the content of the layout file F3 shown in FIG. 9A is rewritten to the content of the layout file F3 ′ shown in FIG. 9B.

  According to the layout file F3 shown in FIG. 9A and the rewrite example thereof, the quantity “8” for the item name “cookie assortment” of the link number “1”, the raw material “flour, eggs,... This is a case of updating (correcting) from “pieces” to “10 pieces”, and a case of updating the expiration date “3” (addition date) to the expiration date “5” (addition date). In this example, after label issuance, in order to describe the label issuance history information D4 in the issuance record file F4, the CPU 80 has a quantity “10” indicating a change at the time of issuance, a shelf life “5 (addition date)”, and the like. The internal storage data D52 is temporarily stored in the RAM 82.

In step ST25, the label printer 100 issues a label 30 based on information relating to food display such as layout data D2 and reservation issue list data D3. At this time, the CPU 80 controls the printing unit 7 to execute a label issuing process. The printing unit 7 prints out the label 30 based on the layout file F3 ′. At this time, the CPU 80 increments the issued number every time the printing unit 7 issues one label 30. After the label issuance, the CPU 80 temporarily stores in the RAM 82 internal storage data D52 indicating the number of issued labels 30 in order to describe the label issuance history information D4 in the issuance record files F4 and F4 ′.

In step ST26, the label printer 100 adds the label issue history information D4 and records it in a non-volatile memory such as the CF card 79 or the internal memory 78. For example, the CPU 80 controls the internal memory 78 and the CF card 79 so as to describe the label issue history information D4 in the issue record files F4 and F4 ′. At this time, the CPU 80 acquires the internal storage data D52 such as the quantity “10” and the expiration date “5 (addition date)” from the RAM 82, and, for example, the label issuance history in the issuance record file F4 ′ in the CF card 79. Information D4 is stored. The issue record file F4 ′ shown in FIG. 10B is provided with a description column for issue date, file number, number of issues, issuer ID number, name, and change contents # 1 and # 2 at the time of issue.

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

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

  In the label issuance management system 300, the issuance record (label issuance history information D4) of the label 30 issued at each food sales store or food manufacturing factory is transferred to the production management system 400 in a timely manner. The label issuance history information D4 is used in the production management system 400 and the management viewer system 500 when verifying whether or not the label issuance processing has been correctly performed by the label printer 100.

  In this example, when the uploading of the label issue history information D4 is completed, the label printer 100 determines the end of the label issue process in step ST28. For example, the CPU 80 monitors the operation data D74 from the input operation unit 74, 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 500 shown in FIG. 11, at step ST31, the information processing apparatus 51 generates at least the issuer, the issue location, and the issue of the label 30 caused by the issue operation of the label printer 100 or the like. The label issuance history information D4 including the number of sheets and the expiration date is received.

  Next, in step ST32, the information processing apparatus 51 checks the issuance record of the label 30 using a dedicated application, and verifies whether the label 30 has been issued as planned. In this verification process, for example, label issuance history information including the issuer of the label 30 in the product sales store, the product manufacturing factory, the number of issued labels, 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 device 51 compares and compares D4 with the 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 is issued according to the production plan as a result of the comparison and collation after moving to step ST33, the information processing apparatus 51 moves to step ST35 and uses the dedicated application to produce the next product. make a plan. Information relating to 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 obtained from the information processing apparatus 51 transferred to step ST35 by the production management system 400. It is transferred to the production plan database 42. In the production plan database 42, the recorded contents are updated based on information relating to 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 best-before date occurs, the process proceeds to step ST34 to eliminate the problem. The shipping error is grasped by tracking the label issuance history information D4 (issuance record). The information processing apparatus 51 makes a production plan for the corresponding product again using the dedicated application.

  Information relating to 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, and the production management is performed from the information processing apparatus 51. Transferred to the system 400 production plan database 42. In the production plan database 42, the recorded contents are updated based on information relating to label issuance generated by the reproduction plan. It should be noted that forgery can be prevented by limiting the change of the remaining date with respect to the issued expiration date.

  Thus, according to the issuer & issuance expiration date management system 1 as an embodiment, the production management system 400, the label issuance management system 300, the label printer 100, and the management viewer system 500 are provided, and the label issuance history information D4 is shared. However, the label 30 is issued by the production management system 400 + label issuance management system 300, the label 30 is issued by the label printer 100, 200,... Issuance history management can be centrally managed by the management viewer system 500 individually and independently by a three-way system.

  Moreover, the FTP server 20 is provided in the label issuance management system 300, and the FTP server 20 labels the label issuance history information D4 generated by the label issuance operation at the time of label issuance from the label printer 100 or the like in which the issuer identification information is set. Received after issue. Thereafter, the FTP server 20 accumulates the label issuance history information D4 received from the label printer 100, 200 or the like for each label printer 100, 200 and processes the information.

  Therefore, the label issuance history can be centrally managed for each of the label printers 100, 200,... Thereby, a production plan can be made based on the label issue history information D4 including the issuer of the label 30, the number of issued items, the amount of money, 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 400 or the management viewer system 500 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 (change contents at issue, issuer, issue date, etc.) of the label 30, but also expiration date management can be executed simultaneously. .

  The present invention is very suitable when applied to an issuer that issues information related to food labeling by printing on a label and an issue expiration date management system.

2 ... control unit,
7: Printing unit (printing means),
8: Control unit (control means),
11 ... Upper housing,
12 ... Lower housing,
13 ... Hinge mechanism,
20 ... FTP server (label issue management device),
21, 81 ... ROM (control means),
22, 82 ... RAM (control means),
24, 27, 84 ... interface for communication,
25, 80 ... CPU (control means),
26, 86 ... I / O interface (control means)
28, 29 ... external terminals,
31... Information storage device,
32 ... Issued label database,
33: Issuer database,
34, 74 ... input operation unit (input means),
35, 75 ... display section,
36-38 ... modem,
39: Data processing unit,
41 ... information terminal device 42 ... production plan database,
40, 43 ... communication means,
51 ... Information processing device 71 ... Label transport system (printing means),
72... Print head (printing means),
73 ... Interface for memory card,
76: Roll paper loading detection unit (printing means),
77 ... Printer control unit (printing means),
78 ... Internal memory,
79 ... CF card,
100, 200 ... label printer,
300 ... Label issue management system (label issue management device),
400 ... Production management system,
500 ... Management viewer system (information processing device)

Claims (3)

Multiple label printers that print information on label issuance on labels and output them,
A label issuance management device that stores and unifies the issuance history information received from the label printer for each label printer, and when the information for identifying the person authorized to issue the label is the issuer identification information, In a label issue information management system in which the label issue management device sets the issuer identification information for each label printer ,
The issuer identification information set for each label printer is:
It becomes issuer list information that summarizes a list of persons who are permitted to issue labels by the label printer.
The label issuance management device
Receiving a request for downloading information relating to label issuance from the label printer;
Check whether the label printer requesting download is a managed label printer,
As a result of the check, if the label printer is a label printer to be managed, the issuer list information is transferred to the label printer . The label printer is
A printing means for printing information on label issuance on a label and outputting it;
Input means for inputting identification information of an issuer issuing a label printed out by the printing means;
Control means for comparing the issuer identification information input by the input means with the issuer identification information set for each label printer from the label issue management apparatus, and receiving the label issue operation based on the check result The label issuance information processing system according to claim 1 . The label printer that is centrally managed by the label issue management device is provided with an issue history file,
3. The label issuance information processing system according to claim 2 , wherein identification information of the issuer is input and recorded in the issuance history file when a label is issued.

Images