JPH11110491A - Card issuing system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To make attainable the shortening of the time of delivery and the cost-down in an issuing work, by making it unnecessary to transmit a card issue specification to a program developer or to perform program developing and correcting for every work. SOLUTION: This is a card issuing system for issuing a card by a card issuing department 30 based on specification data (a) and master data (b). This system is provided with a specification registering part 12 for registering a processing specification from the input of an original to the issuing based on the specification data (a), inputting original part 21 for applying a pre-processing to the master data (b) based on the processing specification and preparing final proof reading data (c) necessary for the issue and an issue data preparing part 22 for converting the final proof reading data (c) into issue data (e) having the specific format of the card issuing department 30.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a card issuing system for issuing a card such as a credit card, an ID card, a magnetic card or an IC card by a card issuing section based on master data.

[0002]

2. Description of the Related Art Conventionally, this kind of card issuing system has
The card issuance unit issues a card based on master data submitted such as personal data. The card issuing unit includes an embossing / encoding unit that forms embosses such as names, numbers, and expiration dates on the card surface, encodes information on a magnetic stripe, a color printing unit that applies names and face photos on the card, and an IC module. It has an IC issuance unit that writes personal data, a sending board printing unit that prints a board for mailing the issued card, and the like.
A pre-processing program and a format conversion program have been developed to convert the format of the master data from the request destination into a data format unique to each unit.

[0003]

The above-mentioned conventional card issuing system has the following problems. (1) Difficulty of shortening delivery time and reducing cost of issuing business In the conventional card issuing system, each time the format of master data, print format on card, input format, etc. is changed, the above-mentioned program is modified. , Which makes it difficult to shorten delivery times and reduce costs.

(2) Necessity of Program Development and Correction Work for Each Business Recently, card issuance processing such as performing color printing such as a name and a face photograph on a card and writing personal data on an IC module has been performed. As the forms are diversified, the conventional card issuing system has to create several programs in order to issue one kind of card, which puts a heavy load on the development and modification of the programs.

(3) Difficulty in transmitting issuance specifications to program developers Due to the diversification of issuance specifications, program developers have
Technical skills are required to communicate the issuance specifications, and the conventional card issuance system has found the communication between the client and the program developer to be complicated and difficult.

The present invention provides a card issuing system which eliminates the need to transmit issuance specifications to a program developer, and develops and modifies programs for each transmission task, thereby shortening the delivery time and cost of the issuing task. It is to be.

[0007]

According to a first aspect of the present invention, a card is issued by a card issuing unit (30) based on specification data (a) and master data (b). In the card issuing system, a specification registration unit (12) for registering processing specifications from submission to issuance based on the specification data;
A submission unit (21) for performing pre-processing on the master data to create graduation data (c) necessary for issuance, and publishing the graduation data in a format unique to the card issuing unit; A card issuing system for converting the data into data (e).

According to a second aspect of the present invention, in the card issuing system according to the first aspect, the input unit includes a data verification function unit, a variable information extraction function unit, a file synthesis function unit,
A card issuing system comprising at least one of a common information addition function unit and a distribution function unit, wherein the specification registration unit sets function conditions of the function units.

[0009] The invention of claim 3 is claim 1 or claim 2.
In the card issuing system described in the above, the issued data creation unit has at least one of a field editing function unit, an issued data conversion function unit, an inspection list output function unit, and a preview function unit, and the specification registration unit, A card issuing system, wherein function conditions of each of the functional units are set.

[0010] The invention of claim 4 is the first to third aspects of the present invention.
The card issuing system according to any one of the above, further comprising a specification searching unit (11) for searching for and referencing registered processing specifications.

[0011] The invention of claim 5 is the invention of claims 1 to 4.
The card issuance system according to any one of the above, further comprising an issuance management unit (24) for managing a progress situation and an issuance situation for each business.

[0012] The invention of claim 6 is the first to fifth aspects of the present invention.
And managing at least one of file layout specifications, verification specifications, file editing specifications, field editing specifications, and card processing specifications registered in the specification registration unit. A database management unit (23) for managing a business database, a submission management database for managing submission history information submitted by the submission unit, and an issue management database for managing issue history information issued by the card issuing unit (23) )
And a card issuing system.

[0013]

Embodiments of the present invention will be described below in more detail with reference to the drawings. FIG.
1 is a diagram showing an embodiment of a card issuing system according to the present invention. In the card issuing system according to the present embodiment, the sections required for card issuance, such as the specification search / registration section 10, the data creation section 20, and the card issuing section 30, are formed into a network 40 via bus lines 41 and 42. The request destination system 50 is also connected online with specification data a from submission to issuance and master data b such as personal data. Note that the specification data a and the master data b may be transferred by a medium such as MT or FD. The roles of each department are as follows.

The specification search registration section 10 includes a specification search section 11
And a specification registration unit 12. The specification search unit 11 searches and refers to registered processing specifications, and can quickly respond to inquiries and change requests from issuance request destinations. The specification search unit 11 can search the contents of the issued specification based on, for example, a number (business ID) for managing the specification. Further, an emboss / encode unit 31, a color printing unit 32, an IC issuing unit 33,
It is possible to search the issuance specifications of the sending board print unit 34, a list of jobs, and the like, and refer to the corresponding job ID and its registered contents.

The specification registering section 12 is a section for registering specification data requested from an issuance request destination from submission to issuance in the submission section 21 and the issuance data creating section 22. The specification registering unit 12 can change or delete registered specifications. However, there is an exclusive function that the specification being processed by the submission unit 21 or the issued data creation unit 22 cannot be changed.

The registered contents of the specification registration unit 12 include the following specifications. (1) File layout specification such as character code system (for example, 1 to 30 bytes, JIS code) (2) Verification specification such as verification of data value (for example, 21
(Up to 22 bytes, 10 or more and 99 or less) (3) File editing specification that can extract only records that satisfy arbitrary conditions (including variable information extraction function, file synthesis function, and common information addition function) (4) Check field data Field editing specifications (eg, comma editing [1
000 → 1,000], editing with a pattern [Hanako Dainippon → Hanako Dainippon]) (5) Card processing specifications such as the position and character size for printing embossed data etc. on a card (for example, submission Field No. 1 [Card Member No.] is set to X = 1
(Printed in 10 cpi font from the position of 0 mm and Y = 15 mm) (6) Preview function that can display the layout image on the card based on the card processing specifications

Here, the variable information extracting function, file synthesizing function, and common information adding function of the file editing specification (3) will be described in detail. FIG. 5 is a diagram illustrating registration of the variable information extraction condition. Specification register 1
2 sets an extraction condition for a data field necessary for this issuing system in the master data b to be submitted. The relationship between the submitted master data and the data after extracting the variable information is as shown in FIG. Here, the data required for the issuance processing is obtained by setting a condition that the value of the record identification flag is B (all records of the record pattern (2)) (S201).

FIGS. 6 and 7 are diagrams for explaining the registration of the synthesis condition. The specification registering unit 12 sets a synthesizing condition for synthesizing the files of the master data b to be submitted into one file in order to synthesize the files for issuing processing. If the submitted master data b has a plurality of record layout patterns, a synthesizing process is performed between the files after extracting the variable information. FIG. 6 shows the relationship between the file before combination and the file after combination. Here, the file No. 1 and the file number. "Synthesis conditions" are set (S301) to combine the records when the member numbers of No. 2 match.

Next, a file No. having a record layout as shown in FIG. 1 to No. 4, an example in which files are combined as follows will be described. The above file No. 1 to No. 4 are combined with each other based on the following contents. In the “first synthesis” of S401, the file No. 1 and the file number. If the member number fields of No. 2 match, the records are combined. Here, the file No. 1 and file No. No. 2 has the same number of records, so the composition format is a 1: 1 format.

In the “second synthesis” of S402, the file No. 2 message flag field 9 (1) and the file No. 3 message identification flag field X
In (1), when the value of the message flag is 0-4, the value of the message identification flag is combined with the record of A, and when the value of the message flag is 5-9, the value of the message identification flag is Combine with record B. Here, the file No. 2 and file No. In No. 3, since the number of records is different, the composition format is a multi-to-one format.

In the “third synthesis” of S403, the file No. 2 branch code field and file N
o. If the branch code fields of No. 4 match, the respective records are combined. Here, the file No. 2 and file No. In No. 4, since the number of records is different, the composition format is a multi-to-one format. As described above, S401
As a result of Steps S403 to S403, the combined file has a file structure as shown in the lower part of FIG.

FIG. 8 is a diagram for explaining registration of common information extraction conditions. If the master data b to be submitted includes data used in common for all cases, the specification registration unit 12 sets conditions for extracting the common information. FIG. 8 shows the relationship between the file structures before and after extracting the common information. In this case, an extraction condition is set such that the issue date of the record layout pattern (1) is extracted as common information (S501), and each record of the record layout pattern (2) is combined with the extracted information as variable information. (S502).

The data creation section 20 includes an input section 21, an issue data creation section 22, a database 23, an issue management section 24, and the like. The submission unit 21 includes the specification registration unit 1
2. Based on the submission specifications and publishing specifications registered by
This is a section for performing pre-processing on master data b submitted from an issuance request destination and creating graduation data c required for issuance. Here, the pre-processing includes character code verification, data value verification, character code conversion, condition extraction, and file editing ((2) variable information extraction function, (3) file synthesis function, (4) common information Additional functions, etc.). The submission unit 21 creates distribution data d for each unit 31, 32, 33, 34 of the card issuing department 30 based on the school completion data c.

The submission unit 21 includes (1) a data verification function,
(2) variable information extraction function, (3) file synthesis function,
The specification registration unit 12 has (4) a common information addition function, (5) a distribution function, and the like, and sets and registers each function condition. Note that (1) the data verification function is related to (2) the verification specification of the specification registration unit 12, (2) the variable information extraction function,
The (3) file synthesizing function and the (4) common information adding function are related to (3) the file editing specification of the specification registering unit 12. The (5) distribution function is related to the (5) card processing specification of the specification registration unit 12 and knows what submission data (field) is required for each of the units 31 to 34 of the card issuing department 30, and inputs the data. Extract only necessary data (fields) from manuscript data.

The issuance data creating unit 22 is a unit that performs necessary field editing such as comma editing on the distribution data d for each of the units 31 to 34 of the card issuing unit 30. In addition, the data is converted into issue data e having an issue data format unique to each section of the card issuing section 30. The issuance data e is transferred to each unit 31 to 34 of each card issuing department 30 via the network 40 (or medium). Further, the issuance data creation unit 22 can create an inspection list based on the list printing specification.

The issue data creation unit 22 has (1) a field editing function, (2) an issue data conversion function, and (3) an inspection list output function. The specification registration unit 12 sets and registers each function condition. can do. The (1) field editing function relates to (4) the field editing specification of the specification registering section 12, and performs field editing on the actually sorted data. (2) The issuance data conversion function corresponds to (5) of the specification registration unit 12.
Each part 3 of the card issuing department 30 related to the card processing specification
It is converted into a unique format of 1 to 34. (3) The inspection list output function is described in (2) of the specification registration unit 12.
Verification specifications, (3) related to file editing specifications, for example,
For the range check, it is possible to output a record list of the submitted data that has become NG, a record list of the submitted data that does not satisfy the one-to-one combining condition, and the like.

The issuance management unit 24 is a part that manages the progress status and the issuance status for each business. This issuance management unit 24
Can display and replace information such as a checklist on a monitor at the issue site. Also,
The issuance management unit 24 manages the issuance data e created for each task and for each of the units 31 to 34 of the card issuing unit 30.
The issuance management unit 24 manages issuance / inspection history data g transmitted from each unit of the card issuing unit 30 and the inspection device.

The database 23 is the business database 2
3a, a submission management database 23b, an issuance management database 23c, and the like. Business database 23a
Is the (1) file layout specification of the specification registration unit 12,
This is a database that manages all specifications of (2) verification specifications, (3) file editing specifications, (4) field editing specifications, (5) card processing specifications, and (6) preview function.
The submission management database 23b is a database of the history information submitted by the submission unit 21 for each business ID. For example, when and what data of business ID and how many (or capacity)
Is it submitted? Issue management database 23
c is a database of issuance history information issued by the card issuing section 30. For example, when and which business I
The number of data (or JOB) of D has been issued. The submission management database 23b and the issuance management database 23c are used by the issuance management unit 24.

The card issuing section 30 includes an emboss / encode section 31, a color printing section 32, and an IC issuing section 33.
And a transmission board print unit 34 and the like. The emboss / encode unit 31 is a part for forming an emboss such as a name, a number, and an expiration date on the card surface, and for encoding information on a magnetic stripe. Color printing unit 32
Is a part for performing color printing such as a name and a face photograph on the card. The IC issuing unit 33 is a unit for writing personal data to the IC module. Sending mount print unit 34
Is a part for printing a mount for mailing the issued card. In addition, an inspection device for inspecting the processing result of each unit is arranged.

Next, processing steps from the actual registration of specifications to the conversion of submitted data (specification data a, master data b) into issue data e will be described. Each specification is centrally managed by a business ID. FIG. 2 is a flowchart showing the operation of the card issuing system according to the present embodiment, and FIGS. 3 and 4 are diagrams showing an example of a registration screen of the submission / issuing specification and card processing specification of the card issuing system according to the present embodiment. is there.

In step S101, the submission / issuance specification is registered. That is, as shown in FIG. 3A, all file layouts to be submitted are registered. Also, if you submit files with multiple different layouts,
File No. Attach and register each.

In step S102, the contents of verification and editing are registered. That is, the verification condition or the editing condition is registered. In this embodiment, as shown in FIG.
o. A variable information extraction condition for extracting a record in which the first byte of the first field of B is B'orC 'is registered.
If there is no record that satisfies the condition, the process is stopped and the fact is printed in a list.

In step S103, distribution conditions are set.
Here, as shown in FIG. 4, the sorting function (here, the sorting function is set as a part of the card processing specification) is set, and the second and third fields (V Seq. = 2,3). Also,
The second and third fields (V Se
q. = 2, 3). When the number of fields that can be allocated is small as in the present embodiment, it is not necessary to allocate each processing specification, and a file having the same format can be registered as common allocation data.

In S104, the card processing specifications are registered. The specifications are registered for each processing content or for each issuing system based on the file layout of the distribution data. In this embodiment, as shown in FIG. 4A, the processing contents are “emboss (EB)” and “color printing”.

As shown in FIG. 4B, the emboss (EB) specification is based on the V of the distribution data. Seq. = 2 and 3 are set in which position on the card and in which font. At this time, necessary edits (addition of check digit and display of date) are set for each print item.

The color printing specification is also shown in FIG.
As shown in FIG. Seq. = 2 and 3
Where to print in what font on the keyboard
Is set. Fixed data separately from distribution data
(F Set to print on all cards as 1)
You. Also, the face image data input from another
Set whether to print at the position.

As shown in FIG. 4D, the contents of the setting can be confirmed by displaying the layout image on the card using the preview function. In addition, the position setting value can be changed by dragging and moving each print item (object) on the preview screen. Although S103 and S104 have been described as separate steps for convenience, they correspond to the registration specifications in FIG.
Can be considered as one step.

In S105, the specification data a and the master data b are submitted, and the issuance data d is created. That is,
The submitted data (a, b) is verified according to the verification conditions. If editing is required at the same time, the file is edited and the submitted data is completed (completion data c). The completion data c is assigned only to fields required for each system (assignment data d). Distribution data d
Is converted into issuance data e based on the card processing specification. When the creation of the issuance data e is completed, the creation history data h is registered in the issuance management unit 24.

In S106, card processing is performed. The card issuance section 30 confirms whether or not the issuance data e has been created from the issuance management section 24. If the printing is completed, the card is embossed on the card by the embossing / encoding unit 31 based on the issuance data e, and the color printing unit 32
Performs color printing. At this time, issuance history data g such as when and what number card was issued
1 is registered in the issue management unit 24. The information necessary for the inspection is acquired from the issue management unit 24, the product room and the order are inspected, and the inspection history data g2 is registered in the issue management unit 24.

As described above, according to the present embodiment, the master data b is pre-processed based on the processing specifications to generate the graduation data necessary for card issuance. Even if the format or the like is changed, correction by a pre-processing program, a format conversion program, or the like becomes unnecessary (no program is required), so that the delivery date can be shortened and the cost can be reduced.

Further, the school completion data is transferred to the card issuing department 30.
Since the data is converted into the issuance data e having the unique format of, even if the form of the card issuance process is diversified, there is no need to develop or modify the program for each issuance operation.

Further, since the processing specifications from the submission to the issuance are registered based on the specification data a, even if the issuance specifications are diversified, the issuance specifications can be accurately and promptly transmitted to the card issuing department 30. be able to.

Also, for example, when the issuance specifications (specifications for printing and inputting on the card) are not changed and the file layout of the submission master is changed, only the file layout specifications (FIG. 3 (a)) are changed. The issuing process can be continued simply by doing so.

When a new business specification is registered by converting the business specification data into a DB, instead of registering the business specification data from scratch, business specification data of a similar specification is found by the specification search unit 11 and is referred to. Then, by modifying, the registration load can be reduced.

In the card issuing / shipping business such as check digit editing, “sama” editing, and comma (,) editing, frequently used field editing functions can be set as general-purpose tools by the specification registration unit 12. By implementing the encryption editing function and the like as an extension of the field editing function, it is possible to quickly respond to a change in the specification of an existing business (such as the addition of an IC issuing specification).

The issue management section 24 manages the input (submission) and output (issuance) histories in this system, so that not only operation management within the system can be performed, but also quick response to inquiries from requesters. By storing the data together with the submission management DB and the business DB, the card can be issued and dispatched in a timely manner only by the instruction (data) from the request destination without submission of the master data.

[0047]

As explained in detail above, the present invention provides:
There is an effect that, without developing a pre-processing program or a format conversion program, it is possible to issue input data in various formats and cards of various specifications in a short period of time and at low cost.

[Brief description of the drawings]

FIG. 1 is a diagram showing an embodiment of a card issuing system according to the present invention.

FIG. 2 is a flowchart showing the operation of the card issuing system according to the embodiment.

FIG. 3 is an illustration of a card issuing system according to the embodiment;
FIG. 9 is a diagram illustrating an example of a registration screen for issuing specifications.

FIG. 4 is a diagram illustrating an example of a registration screen of a card processing specification of the card issuing system according to the embodiment;

FIG. 5 is a diagram illustrating registration of a variable information extraction condition according to the embodiment.

FIG. 6 is a diagram illustrating registration of a synthesis condition according to the present embodiment.

FIG. 7 is a diagram illustrating registration of a synthesis condition according to the present embodiment.

FIG. 8 is a diagram illustrating registration of a common information extraction condition according to the present embodiment.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 10 Specification search / registration section 11 Specification search section 12 Specification registration section 20 Data creation section 21 Submitting section 22 Issued data creation section 23 Database 23a Business DB 23b Submittal management DB 23c Issue management DB 24 Issue management section 30 Card issuing section 31 Emboss / Encoding section 32 Color printing section A3 IC issuing section 34 Sending board print section 40 Network 50 Request destination system

Claims (6)

[Claims] 1. Based on specification data and master data,
In a card issuing system for issuing a card by a card issuing unit, a specification registering unit for registering a processing specification from submission to issuance based on the specification data; and a specification register for the master data based on the processing specification. An input unit that performs processing to create graduation data necessary for issuance; and an publishing data creation unit that converts the graduation data into issuance data having a format unique to the card issuing unit. A card issuing system characterized by the following. 2. The card issuing system according to claim 1, wherein the input unit includes at least a data verification function unit, a variable information extraction function unit, a file synthesis function unit, a common information addition function unit, and a distribution function unit. A card issuance system, wherein the specification registering unit sets function conditions of the functional units. 3. The card issuing system according to claim 1, wherein the issuing data creating unit includes at least a field editing function unit, an issuing data conversion function unit, an inspection list output function unit, and a preview function unit. A card issuing system, wherein the specification registering section sets function conditions of the functional sections. 4. The card issuance system according to claim 1, further comprising a specification search unit for searching for and referencing registered processing specifications. system. 5. The card issuance system according to claim 1, further comprising: an issuance management unit for managing a progress status and an issuance status of each business. Publishing system. 6. The card issuance system according to claim 1, wherein the file layout specification registered by the specification registration unit is provided.
A business database that manages at least one of a verification specification, a file editing specification, a field editing specification, and a card processing specification; an input management database that manages input history information input by the input unit; A card issuing system comprising a database management unit for managing an issue management database for managing issue history information issued by a card issuing unit.