Advanced Project

Importing with Fisher

Specification Manager
Import Tag Comparison and Mapping

LET’S BEGIN…
Let’s consider the first task…
 1. Select an existing project

3. Select Import 2. Select File

 2. Click Select Import File

1. Select a File Delimiter *

* It is assumed that the

basic project importing
tutorial has been viewed.

Note: The existing tags

are listed as Source Tags,
meaning they may or
may not be replaced by
the uploaded tags
(Destination Tags).
1. Select your import
file

2. Click Open
 1. Select the program
the Import file is from

2. Select the Import File Type

3. Click Upload File

 In this scenario, the imported
tags have the same titles as
the existing tags. A Local
Fisher Representative or
Sales Office has completed
the spec and we just uploaded
it to consider the differences.

Let’s consider the

existing 55 FV 102…

…and compare it to
our uploaded 55 FV 102.
The Compare window …different colors are
…and check boxes
appears. The tags used to identify
identify which variable
being compared are differences between
changes will be imported.
identified… the tags…

Let’s simplify this

view by clicking on
Show Only Fields
with Changes.
 Notice, small differences, such as
We now only see the differences
spacing, can sometimes make
between the two tags.
identical values show up as “Not Equal”.

We may decide that

Scrolling down all these changes are
further, we begin to fine, except for the
see how the tag trim. We choose not
has been worked on. to accept the changes.

By clicking OK and moving on with our

importing, we have chosen to import only
the fields selected in this tag. This
comparison and selection can be done with
all the tags before they are finally imported.
 There are two
more things to
consider before
finally importing.

Also, if we don’t want to import a tag, we can

uncheck the Select box directly to the left.

The OverRide
feature, when
checked, tells
Now, let’s go over Mapping… the program to
replace the
Source Tag
with the
Destination Tag.
If left unchecked,
the Source
Tag is
considered a
revision, leaving
the Destination
Tag as the
working tag.
 Import maps are used to “translate” data from one program to the next. In the case of valve
sizing, there are many different labels used to identify valve attributes, units, and application
information. These labels can be paired with Fisher Specification Manager’s labels via a map.

Fisher Specification Manager has

built-in import maps for programs
commonly associated with Fisher
and valve sizing…

…However, we realize that there

are many other ways sizing data
can be arranged, either by a
customer or another program. Such
arrangements call for a custom map.

A very common way of storing and

organizing sizing data is in an
Excel spreadsheet. If you plan to
import data from such a file, you
should arrange it in a manner that
Fisher Specification Manager will
recognize…
 For example…

Tag names are listed in Attribute titles are listed in Attribute values should be directly below their
column A, rows 2 and up. row 1, columns A and up. respective titles and in the their tag’s row.

When mapping
attributes,
unit fields have Specific unit mapping will
“UOM” at the end. be discussed later in the
It is important to note that units are allotted tutorial.
cells separate from their respective values.
Let’s look at creating a map…

1. Click on Select Mapping

 The Mapping window is used to
create custom maps for importing
files that were created in a
program other than those identified
on the Import window.
Fisher
Titles
The default map that appears when
Mapping is opened contains a
complete list of all the program’s
attributes listed as both the
System and Map Name.
Attribute titles that Fisher
Specification Manager uses are
listed as SystemName. MapName
is used to denote titles used by
the source program of the project
Source
Program
Titles
 If our import file has the same or When our map
Next, we take out
almost the same attribute data, then is complete, we
any attributes that
we only need to alter the existing can click on
our file doesn’t
map by changing the MapNames Save As to keep
have data for…
to the source program’s titles… for future use.

…let’s
consider
this
example…
 Most often, though, editing the
Let’s make a map We observe what Now that we know
default map is not the best option.
for the spreadsheet attributes we have what attributes we need,
Starting with a blank map and
we used as an example and match them to we can highlight them
adding only the attributes you
earlier in the tutorial… the listed attributes. from the master list…
need is often easiest…

…let’s
consider
this
Once all the desired
example…
attributes are highlighted,
we click Select…

Now, we need to change the
MapNames so they match our
spreadsheet attribute titles...
Finally, to complete any map,
we have to make sure the
program will recognize our units.
If we have attributes that aren’t listed in the
program, then the program doesn’t have a
…we continue until all the use for such information. To tell the program
MapNames are replaced to ignore this attribute, click Add User Defined
(including unit titles!). Field and fill in the attribute title…
 We may represent our units
differently than Fisher
Specification Manager does.
Therefore, we need to make
sure our unit symbols are
matched up to the programs’.

If our units can’t be found

under System Units, then we
should enter its title under Map
Unit as well as a conversion
factor to make it equal to
its paired System Unit.
 Let’s review…
…finally, we matched up our
We found which attributes …then we mapped our …we used a User Defined units to the System Units,
we needed and selected attribute names to the Map Field to map an adding conversion factors
them… System Names… attribute that isn’t listed… when necessary…

Imported Tags have

been compared to Existing
Tags and a proper Map has been
created for importing an
outside file.

You’re Done!
Use the “Back” button to return to the Help System

OR

Continue clicking to repeat the tutorial