DeltaV, the DeltaV design, SureService, the SureService design, SureNet, the SureNet design, and PlantWeb are marks of one of the Emerson
Process Management group of companies. All other marks are property of their respective owners. The contents of this publication are presented for
informational purposes only, and while every effort has been made to ensure their accuracy, they are not to be construed as warrantees or guarantees,
express or implied, regarding the products or services described herein or their use or applicability. All sales are governed by our terms and conditions,
which are available on request. We reserve the right to modify or improve the design or specification of such products at any time without notice.
DeltaV-INtools Integration
This document explains how data can be exchanged between the DeltaVTM and INtoolsTM databases.
TMThe information that can be transferred spans both conventional I/O, including HART, and Fieldbus I/O systems.
The INtools product has been enhanced to be 'DeltaV-aware'. This means that DeltaV terminology and I/O
objects appear in INtools. INtools users can go to the Intergraph support site, log in, and download DeltaV I/O
card definitions to jump start their instrument database, making initial data entry even easier and faster.
This integration capability is embedded directly into the DeltaV system architecture, thereby ensuring its
commitment to ongoing enhancement and support.
TM
Whitepaper
DeltaV-INtools Integration
November 2004 —Page 4
On the INtools Side
The INtools Default Panel Manager library does not have the DeltaV I/O card definitions when shipped. These
defintions must be downloaded after logging into the following WEB site : http://ppocrm.intergraph.com. The
defintions are updated when new I/O objects are introduced into DeltaV. This allows the INtools library to be kept
current with the latest DeltaV definitions. Once the defintions are imported, the DeltaV I/O card types will appear
in the INtools Default Panel Manager, as if they were standard INtools panels.
Fig. 1: DeltaV I/O definitions loaded into INtools
TM
Whitepaper
DeltaV-INtools Integration
November 2004 —Page 5
After the DeltaV definitions are imported, they can be used as if they are standard INtools panels. The DeltaV I/O cards
can be configured and the I/O channels can be bound to instrument tags. INtools will also allow the name of the DeltaV
controller to be specified. If this controller does not exist in the DeltaV database then it will be created when the data is
saved to DeltaV. INtools has detailed help available on how to correctly configure the DeltaV items.
Fig. 2: A DeltaV I/O card being configured in INtools
TM
Whitepaper
DeltaV-INtools Integration
November 2004 —Page 6
From one menu in INtools all the relevant data from the various INtools configuration modules will be collected and
exported into one file. The data for each DeltaV controller can be exported in a separate file.
Fig. 3: Exporting INtools data to the DeltaV system!
TM
Whitepaper
DeltaV-INtools Integration
November 2004 —Page 7
On the DeltaV Side
An Excel add-in is provided with the DeltaV installation to process the INtools data. This add-in can load an export from
INtools and save the data to the DeltaV database. The add-in detects and highlights errors in the data. It also compares
the data in the spreadsheet to data that may already exist in the DeltaV database and highlights the differences.
Training centers for INTools
Re: Training centers for INTools
