You are on page 1of 23

DataMapper 2.

0
Users Manual


NBS DataMapper Confidential
NBS 2 of 23 Copyright 2005


REVISION HISTORY
Rev. Date Author Description
1.0 03/07/2005 bsb Initial Version
1.1 3/15/05 Dmb Minor revisions
1.2 03/28/2005 Bsb More updates





DISCLAIMER OF WARRANTY
NBS Technologies Incorporated makes no representation warranties, either expressed or implied by,
or with respect to anything in this guide.
COPYRIGHT NOTICE
This documentation is protected by copyright and is distributed under licenses restricting its use,
copying and distribution. No part of this documentation may be reproduced in any form by any
means without prior written authorization of NBS Technologies Incorporated and its licensors.
All rights reserved, NBS Technologies Incorporated., 10925 Bren Road East, Minneapolis, Minnesota,
55343, U.S.A.
TRADEMARKS
All company and product names are trademarks or registered trademarks of their respective owners.
LIMITATION OF LIABILITY
NBS Technologies Incorporated is not responsible for any lost, corrupted or misdirected data through
the use of this product. No warranties, whether expressed or implied, are given. NBS Technologies
Incorporated reserves the right to change the specifications of this product at any time without
notice

NBS DataMapper Confidential
NBS 3 of 23 Copyright 2005

1. INTRODUCTION ...................................................................................................... 5
1.1 Overview ............................................................................................. 5
1.2 Scope and Audience ............................................................................... 5
1.2.1 Scope .................................................................................................... 5
1.2.2 Audience ................................................................................................ 5
1.2.3 Definitions .............................................................................................. 6
1.3 References .......................................................................................... 6
2. Using DataMapper GUI ............................................................................................. 7
2.1 Introduction ......................................................................................... 7
2.2 Supported Input File Formats .................................................................... 7
2.3 Starting the DataMapper GUI .................................................................... 7
2.4 Using the DataMapper GUI ........................................................................ 8
2.4.1 Making a New DataMap ............................................................................... 8
2.4.1.1 Setup the Format of the Input File ............................................................. 8
2.4.1.1.1 Fixed Length .................................................................................. 8
2.4.1.1.2 Pattern Delimited ............................................................................ 9
2.4.1.1.3 Header Record ................................................................................ 9
2.4.1.1.4 Trailing Record ............................................................................... 9
2.4.1.2 Select the location of the Input File ............................................................ 9
2.4.1.3 Select the required applications to map data .............................................. 10
2.4.1.4 Use Drag and Drop to map the data .......................................................... 12
2.4.2 DataMapping Magnetic Stripe to EMV ............................................................ 13
2.4.3 Handling ASCII to Hex conversions ............................................................... 15
2.4.4 Clearing mapped tags ............................................................................... 18
2.4.5 Using the Set Tag Calculation Field Menu ....................................................... 19
2.4.6 DataMapping non smart card information ....................................................... 20
2.4.7 Saving a Data Map ................................................................................... 21
2.4.8 Creating a PI Prime File (Processing a Data Map).............................................. 21
2.4.9 Opening an existing DataMap ...................................................................... 22

NBS DataMapper Confidential
NBS 4 of 23 Copyright 2005

Figure 1: Example of DataMapper startup screen ......................................................... 7
Figure 2: Configure Input Data to Select Input File Information ........................................ 8
Figure 3: Select Input File window ........................................................................... 8
Figure 4: Error when Input File does not meet specification ............................................ 9
Figure 5: Contents of Example Input File after Successful Selection ................................ 10
Figure 6: Window to add or remove applications for data mapping ................................. 11
Figure 7: Tags for modules .................................................................................. 11
Figure 8: User selects a field in Input File ................................................................ 12
Figure 9: Results after information dragged to tag ..................................................... 13
Figure 10: User selects Magnetic Stripe Track 1 data from Input File ............................... 14
Figure 11: Results after user drags Magnetic Stripe Track 1 data to appropriate tag (e.g. 5F20)15
Figure 12: Window indicating the data format or length is incorrect ................................ 15
Figure 13: Incorrectly mapped tag indicator ............................................................. 16
Figure 14: Selecting the Data Conversion menu for an incorrectly mapped tag ................... 17
Figure 15: Selection of Data Conversion Options ........................................................ 17
Figure 16: Successful conversion of the field ............................................................ 18
Figure 17: Clearing the mapping from a tag .............................................................. 19
Figure 18: Option to convert tag to secondary tag ...................................................... 19
Figure 19: Using the Set Tag Calculation Field menu ................................................... 20
Figure 20: Mapping of pass through information ......................................................... 21
Figure 21: Selecting the name and location of the PI Prime file ..................................... 22
Figure 22: Successful creation of PI Prime file ........................................................... 22
Figure 23: Sample error message from incorrect data map ........................................... 22
Figure 24: Browsing for a DataMap ......................................................................... 23
Figure 25: Invalid Data map error message ............................................................... 23
NBS DataMapper Confidential
NBS 5 of 23 Copyright 2005

1. INTRODUCTION
1.1 Overview
In the smart card industry, there has never been a well-accepted standard for an input file
into a Data Preparation process. As many smart card projects are for financial institutions,
the files that contain ISO-format magnetic stripe information are simply used for smart card
personalization as well.
In developing a Data Preparation process, NBS used a Tag-Length-Value file format developed
by VISA (1). This format eventually became known as P3. NBS called the input file format to
Data Preparation, PI Prime (2), and adopted P3 as the name of the output from Data
Preparation.
Despite the popularity of P3, the market continued to demand processing of varying file
formats; in particular fixed length file formats (e.g. Certegy Base2000, CTL, EDS Vision). To
solve the problem of handling varying fixed length file formats; a program was developed to
facilitate conversion of a file to PI Prime.
1.2 Scope and Audience
1.2.1 Scope
The first section of this document discusses the use of the DataMapper Graphic User Interface
(GUI) to create a Datamap file to convert an input file format into PI Prime.
The second section describes the use of a function of NBS Persomaster called DataConvert to
run the map file created by the DataMapper GUI.
1.2.2 Audience
This document is intended for users that intend to write Datamaps or use NBS Persomaster to
process an input file using a previously generated Datamap file.
Familiarity with Windows 2000 or Windows XP is required.
NBS DataMapper Confidential
NBS 6 of 23 Copyright 2005

1.2.3 Definitions
Term Defintion
Datamap A file generated to provide instructions on the
conversion of an input file to PI Prime.
DataMapper GUI The graphic user interface for generating a Datamap.
It also contains a facility for creating PI Prime file
from input files.
DataMapRun A program used to allow automation of the
datamapping process. Largely superseded by the NBS
Persomaster Scheduler function.
input file File specified for use in creating smart cards.
PI Prime File Internal Tag Length Value file format used by NBS for
DataPreparation. The PI Prime File
1
contains all the
required components of the card personalization
process.
1.3 References
(1) Visa International Initialization and Personalization: Reloadable Stored Value Cards with
Public Key Technology version 1.1, Visa International, January 1997.
(2) UbiQ Prime Developer's Guide version 1.4, July 2003
NBS DataMapper Confidential
NBS 7 of 23 Copyright 2005
2. Using DataMapper GUI
2.1 Introduction
This section focuses on the steps that are necessary to create a datamap to convert an input
file to PI Prime file format.
2.2 Supported Input File Formats
The DataMapper GUI currently only supports fixed length and pattern delimited record files.
However, DataMapper GUI does handle header and trailer information for the entire file.
Information in the file header and trailer cannot be accessed for datamapping.
If header and trailer information are provided per record, then the header and trailer sections
must exist for each record in the file. DataMapper GUI will need to handle record headers
and trailer as part of one record, so if the sections do not exist for some records, then the file
will not conform to a fixed length file.
2.3 Starting the DataMapper GUI
The DataMapper GUI is started either from a shortcut on the desktop or from a file menu
option. Once the program is started, the user is given an initial display as shown below.

Figure 1: Example of DataMapper startup screen
NBS DataMapper Confidential
NBS 8 of 23 Copyright 2005
2.4 Using the DataMapper GUI
Once the DataMapper GUI has been started, the user can either load an existing DataMap by
using the Open button on the Toolbar or File Menu or create a new DataMap by using the
New button on the Toolbar or the File Menu (see Figure 1).
2.4.1 Making a New DataMap
Once the new DataMap option has been selected, any existing Datamap information will be
cleared. The basic steps for creating a datamap are:
1. Setup the Format of the Input File
2. Select the location of the Input File
3. Select the required applications to map data
4. Use Drag and Drop to map the data
2.4.1.1 Setup the Format of the Input File
Once the user selects to create a new DataMap, the user must specify the format of the file.
by selecting the Select button in the Configure Input Data window as shown below.

Figure 2: Configure Input Data to Select Input File Information
When the Select button is selected, a window opens to allow the user to specify information
about the input file as shown below.

Figure 3: Select Input File window
At this point, the user has options to specify information about the format of the input file.
The goal is to give DataMapper GUI information about the structure of the records in the input
file.
2.4.1.1.1 Fixed Length
NBS DataMapper Confidential
NBS 9 of 23 Copyright 2005
If the records in the input file are always the same number of bytes, then the user may enter
the information here to indicate the number of bytes that make a record.
2.4.1.1.2 Pattern Delimited
If a delimiter such as carriage return/line feed always separates the records in the input file,
then the user may enter the information here to indicate the pattern that indicates the end
of each record.
2.4.1.1.3 Header Record
If the input file contains header information, then DataMapper GUI should ignore that
information when it starts with the first record. The user may specify a fixed size of the
header record or a pattern to indicate the end of the Header record.
2.4.1.1.4 Trailing Record
If the input file contains trailer information, then DataMapper GUI should ignore that
information when it ends with the last record. The user may specify a fixed size of the trailer
record or a pattern to indicate the end of the trailer record.
If no information is provided for the Header and/or Trailing Record field then DataMapper GUI
will assume that the record does not exist.
2.4.1.2 Select the location of the Input File
Once the information about the size of records in the input file and any necessary header and
trailer information are entered, the user should select the appropriate input file using the
Browse button.
The user should understand the size and format of the input file before using DataMapper. If
the file which is selected, does not meet the information entered in the specification,
DataMapper will either attempt to parse the file with the incorrect size requirements or
return an error message

Figure 4: Error when Input File does not meet specification
If the input file is loaded successfully, then the contents of the first record are displayed as
shown below.
NBS DataMapper Confidential
NBS 10 of 23 Copyright 2005

Figure 5: Contents of Example Input File after Successful Selection
At this point, the user has the option to toggle the display of the data file between ASCII and
hexadecimal using the Display in Hex checkbox or select the entire record using the Select
All Record Data button.
2.4.1.3 Select the required applications to map data
Once the user has selected the appropriate data, the applications such as VSDC that are to
receive data need to be selected to allow an association to be made between the PI Prime
module, EMV Tag, and data in the input file.
To choose the desired applications, the user selects the Add/Remove Profile Modules Button
from the Modules window (see Figure 5: Contents of Example Input File after Successful
Selection). Once the button is selected, a window appears to allow the user to add modules
as shown below.
NBS DataMapper Confidential
NBS 11 of 23 Copyright 2005

Figure 6: Window to add or remove applications for data mapping
At this point, the user may check the check box next to the modules to include or uncheck
the check box next to the modules to remove.
The user checks the OK button when done with the selection, and the appropriate modue(s)
are displayed in the modules window as tabs. In the example below, the user selected the
PassThru (for Embossing, Magnetic Stripe, etc.) and VSDC modules.

Figure 7: Tags for modules
Once the modules are displayed, the user may display information about the tags in the
module by selecting the corresponding tab.
NBS DataMapper Confidential
NBS 12 of 23 Copyright 2005
2.4.1.4 Use Drag and Drop to map the data
Once the modules are added to the DataMap, the user can begin mapping by using the mouse
to highlight information in the Configure Input Data Screen and dragging to the value field of
the tag in the desired module.
In the examples below, the user wants to map information from the data file into the VSDC
Module for the tag CardHolder Name Extended 9F0B. The user first highlights the appropriate
information in the input file display using the left mouse button then releases the button.
Next, the user moves the mouse over the selected area, holds the left mouse button down,
and moves the mouse to the value field of the 9F0B tag. The user then releases the mouse
button and the data is mapped.

Figure 8: User selects a field in Input File
NBS DataMapper Confidential
NBS 13 of 23 Copyright 2005

Figure 9: Results after information dragged to tag
As a check, selecting a mapped tag in the modules window will display the highlighted region
in the Input File.
2.4.2 DataMapping Magnetic Stripe to EMV
A majority of DataMapping is done to convert Cardholder specific information into EMV
parameters. As many cardholder data systems produce magnetic stripe information,
functions were added to DataMapper GUI to convert ISO format Magnetic Stripe Track 1 and
Track 2 into EMV parameters. Also, the conversion between magnetic stripe and chip often
required rules as specified in EMV, so functions were defined in DataMapper GUI to
automatically use the conversion rules.
Mapping the Track data to EMV data is now reduced to a simple drag and drop operation. For
Track 1 data, the user simply highlights the magnetic stripe data (including start and end
sentinels), and then drags it to any appropriate cardholder tag (5A, 5F20, 5F24, 5F30, 9F1F)
and the remainder of the tags is automatically populated. For Track 2, the user highlights the
data, and drags it to tag 57.

NBS DataMapper Confidential
NBS 14 of 23 Copyright 2005

Figure 10: User selects Magnetic Stripe Track 1 data from Input File
NBS DataMapper Confidential
NBS 15 of 23 Copyright 2005

Figure 11: Results after user drags Magnetic Stripe Track 1 data to appropriate tag (e.g. 5F20)
2.4.3 Handling ASCII to Hex conversions
In most EMV tags, the format is binary, but the user views the Input File as ASCII, in this case,
the user may still drag and drop the tag, but DataMapper GUI will warn the user that the
format is incorrect as shown in the figure below.

Figure 12: Window indicating the data format or length is incorrect
The user is still allowed to make the mapping, but a crossed out (incorrectly mapped field)
icon is displayed next to the tag in the modules section to indicate that the tag is incorrectly
mapped as shown in the figure below.
NBS DataMapper Confidential
NBS 16 of 23 Copyright 2005

Figure 13: Incorrectly mapped tag indicator
The user may convert the data from ASCII to Binary by right clicking on the incorrectly
mapped field. This causes a menu to be displayed that allows the user to select the Data
Conversion menu as shown in the figure below.
NBS DataMapper Confidential
NBS 17 of 23 Copyright 2005

Figure 14: Selecting the Data Conversion menu for an incorrectly mapped tag
Once the user selects the Data Conversion menu, a window is displayed to give the user
choices on the conversions to make as well as information about the location of the data in
the input file as shown below.

Figure 15: Selection of Data Conversion Options
Note that at this point, if needed, the user can manually set the offset (position) and length
of the tag in the file.
NBS DataMapper Confidential
NBS 18 of 23 Copyright 2005

Figure 16: Successful conversion of the field
If the conversion does not remove the incorrectly mapped tag icon, then it is possible that the
wrong information was mapped to the tag or there is a problem with the specification of the
data file.
2.4.4 Clearing mapped tags
Once a tag is mapped, a user may want to remove the information for the mapping. This can
be done by right clicking on the tag and selecting the Clear Tag Calculation Field menu.
NBS DataMapper Confidential
NBS 19 of 23 Copyright 2005

Figure 17: Clearing the mapping from a tag
Once the user selection the Clear Tag Calculation Field menu, a message appears to allow
the user to make the tag a secondary tag, secondary tags are defined as tags that are
generally not displayed to a user because it is expected that mapping will not be done on the
tag.

Figure 18: Option to convert tag to secondary tag
If the user selects Yes to convert the tag to a secondary tag, then the tag will be unmapped
and removed from the Module window. The user is able to view the tag again using the
Display All Tags checkbox at the top of the Module window. If the user selects No, the tag is
unmapped and remains in the Module window.
2.4.5 Using the Set Tag Calculation Field Menu
As an alternative to Drag and Drop, the user may highlight the information in the Input Data
window, and instead of dragging it to the appropriate tag in the Module window; the user may
right click and select Set TAG Calculation Field.
NBS DataMapper Confidential
NBS 20 of 23 Copyright 2005

Figure 19: Using the Set Tag Calculation Field menu
At this point, the information highlighted in the Input Data window is entered into the value
field of the tag as if it had been dragged and dropped there.
2.4.6 DataMapping non smart card information
Data which is not part of a smart card application including Embossing, Magnetic Stripe,
Mailer, Form, Photo, Job Information, and Graphics must be mapped as part of a contiguous
field into the DF01 tag of the PassThru field as shown in the figure below.
NBS DataMapper Confidential
NBS 21 of 23 Copyright 2005

Figure 20: Mapping of pass through information
2.4.7 Saving a Data Map
A user may save a data map using the Save button from the toolbar or the Save menu item in
the File menu.
2.4.8 Creating a PI Prime File (Processing a Data Map)
For a user to create a PI Prime from their data map, they may select the Process button from
the Toolbar or Process Datamap from the Options Menu.
Once processing is requested, DataMapper GUI displays a dialog box to allow the user to
select a directory and filename to save the PI Prime as shown in the figure below.
NBS DataMapper Confidential
NBS 22 of 23 Copyright 2005

Figure 21: Selecting the name and location of the PI Prime file
Once the user selects the Save button, processing begins. If the processing is successful, the
user receives a message indicating the number of records created as shown in the figure
below.

Figure 22: Successful creation of PI Prime file
If the data mapping is not successful, a message indicating the error will be displayed as
shown in the example below.

Figure 23: Sample error message from incorrect data map
In this case, the error specifically indicates that there is a problem in record 3 with tag DF01.
A check of the data indicates that there is no data in the required location for DF01.
In general, a user should review the information in the error message with the format and
specification of the DataMap to determine the problem.
2.4.9 Opening an existing DataMap
A user may open an existing DataMap using Open in the File Menu or the Open button in the
Toolbar. Once the function is selected a window appears to allow the user to browse to the
directory and file name of the data map as shown in the figure below.
NBS DataMapper Confidential
NBS 23 of 23 Copyright 2005

Figure 24: Browsing for a DataMap
When a datamap is selected and the user selects the Open button, the DataMap is read into
the GUI. If the DataMap is formatted correctly, the Modules and Input Data file will be
displayed in the DataMapper GUI window.
If the DataMap is invalid, a message like one shown below will be displayed. The user will be
returned to the DataMapper GUI and can then reopen a valid datamap.

Figure 25: Invalid Data map error message