Tips/Troubleshooting:
1. Certain fields must match for INtools to import the data. If
you're running the import module successfully, but your actual data
sheet in INtools does not reflect the imported data, check the fields
below in your import file to make sure that the values are the values
that you are expecting. Fisher software exports the values that were
originally exported from INtools. If the values in the Fisher export
file are not expected values, you may have a problem with INtools
exporting blank or erroneous values in the first place. You may manually
correct the values on the Fisher export file and then import. You may
also want to contact Intergraph to correct the problems in INtools. You
may need to update your version with a service patch from
Intergraph.
INtools fields that must be present and matching in the Fisher export
file in order to import data into INtools:
1. ProjectName
2. PlantName
3. AreaName
4. UnitNumber
5. ProjectUnit
6. LoopName
7. MeasuredVariable
8. ItemTag
9. InstrumentTypeName
2. The import module may tell you that "Case ID" or "Case Number" is
a problem when running the import. INtools made a change after the
Fisher interface was built to accommodate for different process data
cases. The import module looks for data to define which "case" you want
the data to import to. To work around the issue, open the links for the
FIRSTVUE interface in the import module. The calculation and spec sheet
links include fields for "case" in the mapping. Map these to '' (two
single quote marks). This will default the case value and satisfy the
import module so that you can import the data.
3. Data imports into the wrong fields in the Fisher program. The
interface built into INtools is based upon the use of spec form 70
inside of INtools. This is an ISA spec sheet for control valves. The
user defined fields on the spec form 70 are mapped to field names used
in the Fisher program. If another spec sheet is used or if spec 70 is
modified on the project, the fields mapping may need to be corrected.
4. The export file from the Fisher program may be opened in excel.
Please note if excel provides a warning that reads "File not loaded
completely". This can occur if more that 256 fields were exported
(function of the mapping used to export the values). If you get this
warning, you are free to read the file in excel, but saving in excel
will result in loosing fields that were beyond the 256 displayed. Note
that you can use notepad or other text editing files to edit and save
also.
5. INtools has a utility that allows you to rename the units of
measure when you export or import data. This mapping has already been
done for the FIRSTVUE interface with spec 70, but will need to be done
if you are using an import link other than the FIRSTVUE link (ie, a
custom link to interface with a different spec form). Failure to use
this renaming utlity when using a link other than the FIRSTVUE link will
result in a failed import when the data is imported into FIRSTVUE
because FIRSTVUE will not understand the INtools units of measure.
The utility is located in the import module. In order to access this,
select the import link (ie, a custom link created for the project) that
you would like to modify the units of measure for. Now select the system
codes selection in the main menu. Now select Adapt UOM codes. This will
provide a list of all of the units of measure used in INtools with space
to enter the matching FIRSTVUE units.
For a complete list of units used in FIRSTVUE, click
here.
6. Process data fields are managed by the process module. This
controls the variations of data that are required for gas/vapor vs
liquid, for example. Failure to enter process data in the Process
Data module will result in the omission of critical fields like
compressibility and other fields that are critical to sizing control
valves.
7. Be sure to close the csv file from FIRSTVUE prior to importing it
into the import module. Failure to do so will result in an error similar
to the one below. In this event, simply close the csv file and try
again. This error can also be a result of conflicts with the file name
(special characters or blanks in the file name or folder) or even if the
path to the file name is too long. If your csv file is closed and you
get this error, try renaming the file and folders in the path and moving
the file to a directory with a shorter path. If the message persists,
contact Intergraph support.
8. Note that multiple Fisher fields can be mapped to import
into a single field in INtools. The links in the import module can
be written such that more than on Fisher field is mapped to a single
INtools field. The import module will concatenate the two Fisher
fields and assign the resulting value to the INtools field. Text
can also be inserted as needed; for example, Fisher's lower and upper
benchset values can be imported into a single INtools field as 'minbenchrange'+'
- '+'maxbenchrange' to import a bench set of '3 - 15' into one field for
bench set in INtools.
