Inform IT Prod Guide

InformIT
Enterprise Historian for Windows 2000

Version 3.2
Product Guide
InformIT
Enterprise Historian for Windows 2000
Version 3.2
Product Guide
NOTICE
The information in this document is subject to change without notice and should not be
construed as a commitment by ABB Inc. ABB Inc. assumes no responsibility for any errors that may appear in this document.
In no event shall ABB Inc. be liable for direct, indirect, special, incidental or consequential
damages of any nature or kind arising from the use of this document, nor shall ABB Automation Inc. be liable for incidental or consequential damages arising from use of any
software or hardware described in this document.
This document and parts thereof must not be reproduced or copied without written permission from ABB Inc., and the contents thereof must not be imparted to a third party nor
used for any unauthorized purpose.
The software or hardware described in this document is furnished under a license and
may be used, copied, or disclosed only in accordance with the terms of such license.
This product meets the requirements specified in EMC Directive 89/336/EEC and in Low
Voltage Directive 72/23/EEC.
Copyright 2001 ABB Automation Inc.
All rights reserved.
Release:
Document number:
November 2001
3BUF 000 987 R1
TRADEMARKS
Advant, AdvaCommand, AdvaInform, and AdvaBuild are registered trademarks of ABB Asea Brown Boveri
Ltd., Switzerland. Enterprise Historian is a trademark of ABB Asea Brown Boveri Ltd., Switzerland.
The following are registered trademarks of Pavilion Technologies, Inc.: Data Insights, Pavilion, Pavilion
Data Interface, Process Insights, Process Perfecter.
The following are trademarks of Pavilion Technologies, Inc.: Insights, Pavilion OnLine Applications, Pavilion RunTime Products, PDI, Plant Optimizer, Power Insights, Power Insights Suite, Process Optimizer,
Property Predictor.
Windows NT and Windows are registered trademarks of Microsoft Corporation.
Citect is a Registered trademark of Ci Technologies Pty Limited.
OLE for Process Control is a Registered trademark of OPC Foundation.
OPC is a Trademark of OPC Foundation.
Operate IT is a Trademark of ABB Inc.
Produce IT is a Trademark of ABB Inc.
Sattline is a Registered trademark of ABB Inc.
Symphony is a Trademark of ABB Inc.
Enterprise Historian is a Trademark of ABB Inc.
Advant is a Registered trademark of ABB Inc.
ORACLE is a Registered trademark of Oracle Corporation.
Table of Contents
TABLE OF CONTENTS
Section 1 - Introduction
What is Inform IT Enterprise Historian?.........................................................................11
Data Collection, Storage and Retrieval ................................................................15
Process data ......................................................................................15
Production Data...................................................................................15
Event data
......................................................................................17
User Interface .......................................................................................................18

Display Services..................................................................................18
DataDirect
......................................................................................19
DeskTop Trends ..................................................................................19

3rd Party System and Device interface ................................................................19
Data Analysis and Mining....................................................................................20
Reporting capabilities..........................................................................20
Process modeling and analysis............................................................20
Whats New in this Release .............................................................................................22
Bundling Options.............................................................................................................23
Enterprise Historian Collect .................................................................................24
Enterprise Historian Connect ...............................................................................28
Enterprise Historian Consolidate .........................................................................31
Licensing .........................................................................................................................31
Section 2 - Basic Software Components

System Services...............................................................................................................33
History Services...............................................................................................................34
Applications that Use History Services................................................................34
Process Data Storage............................................................................................36
Calculations ......................................................................................38
Data Compaction.................................................................................39
3BUF 000 987 R1
Table of Contents
Composite Log Applications .............................................................. 41

Secondary Logs for Different Resolution/Time Span Views.............. 42
Primary and Secondary Logs with Calculations................................. 43
Lab Data Logs for Asynchronous User Input ..................................... 44
Consolidating History Data with Distributed Logs ............................ 45
Collecting Data for Longer Time Period at Consolidate Level .......... 47
Composite Log with Local and Distributed Secondary Logs............. 47
Calculated Values on both Collect and Consolidate Levels................ 48
Collection from Enterprise Historian Connect ................................... 48
Collecting from Remote History Logs................................................ 49
Dual Configuration for Data Security................................................. 50
Collecting from OPC Data Sources .................................................... 52
Numeric Data Presentation ................................................................. 53
Seamless Retrieval .............................................................................. 54
Numeric Data Storage Considerations................................................ 54
Off-line Storage .................................................................................. 54
Event Data Storage .............................................................................................. 55
Event Presentation .............................................................................. 56
Off-line Storage .................................................................................. 56
Production Data Storage ...................................................................................... 56
Off-line Storage .................................................................................. 58
Presentation ...................................................................................... 58
Finished Report Storage....................................................................................... 60
Off-line Storage and Access ................................................................................ 61
History Database Configuration .......................................................................... 62
Display Services.............................................................................................................. 62
Building Displays ................................................................................................ 65
Display Elements ................................................................................ 68
Runtime Displays................................................................................................. 69
Active X Support ................................................................................ 69
History Displays ................................................................................. 70
Display Services Client-Server Architecture ....................................................... 72
3BUF 000 987 R1
Table of Contents
Display Server .....................................................................................72

Display Client......................................................................................73
Additional Display Services Capabilities............................................75
DataDirect........................................................................................................................76
Dialogs for Ad-hoc Data Retrieval/Data Entry ...................................77
Function Calls for Building Reports in Microsoft Excel ....................78
Using DataDirect Functions in Macros (VBA)...................................79
Requirements ......................................................................................79
Desktop Trends................................................................................................................80
Audit Trail .......................................................................................................................82
OLE DB Data Access ......................................................................................................84
Data Analysis and Mining ...............................................................................................86
Insights
.............................................................................................................86
Property Predictor ..................................................................................................................... 86

Report Services................................................................................................................87
Report Building ....................................................................................................87
Report Scheduling ................................................................................................89
Report Execution and Data Access ......................................................................89
Managing Report Instances..................................................................................90
User Interface .......................................................................................................90
User API ..........................................................................................................................92
Production Data Log (for Use with Produce IT Batch)....................................................92
Event Log (For systems with Master data connection only) ...........................................93
Event Log Configuration.....................................................................94
Event Log Communication .................................................................94
Accessing Event Messages From the Event Log ................................95
PLC Interface...................................................................................................................96
OPC Connectivity............................................................................................................98
Advant OCS Control Network Connections....................................................................98
Section 3 - Hardware/Software Requirements

Prerequisite Software .........................................................................................102
3BUF 000 987 R1
Table of Contents
Section 4 - Ordering Information

Enterprise Historian Products ....................................................................................... 103
Enterprise Historian Collect for Windows 2000 SP-B-EHSNT ........................ 103
Enterprise Historian Consolidate for Windows 2000 - SP-B-EHCNN ............. 104
Enterprise Historian Connect for Windows 2000 - SP-B-EHATC .................... 104
Display Services Expansion Nomenclature - SP-E-EHDSA............................. 105
Pavilion Technologies Products .................................................................................... 106
Enterprise Historian Pavilion Insights Client: SP-B-EHPCA............................ 106
Pavilion Property Predictor: Client (SP-B-EHPCB), and Server
(EH-B-EHSPP, SP-E-EHSPP) .......................................................... 106
Section 5 - Capacity and Performance

History Services ............................................................................................................ 107
Overall Capacity ................................................................................................ 107
Maximum Number of Primary Logs ................................................................. 107
Maximum Number of Entries Per Log .............................................................. 108
History Objects Miscellaneous Capacities ........................................................ 108
History Collection Maximum Sample Rate....................................................... 109
Fastest Sample Rate ........................................................................................... 110
Disk Requirements Per Log Entry ..................................................................... 110
Disk Space Allocation for Oracle and File-based Logs..................................... 111
History Archive.................................................................................................. 112
Event Log (Master) ....................................................................................................... 113
Display Services............................................................................................................ 113
PLC Interface ................................................................................................................ 114
Desktop Trends.............................................................................................................. 114
Report Services ............................................................................................................. 114
OLE DB Data Access.................................................................................................... 114
User API........................................................................................................................ 115
Connecting to Symphony/INFI 90 ................................................................................ 122
Connecting to Freelance................................................................................................ 123
Connecting to SattLine.................................................................................................. 124
OPC Connectivity ......................................................................................................... 125
3BUF 000 987 R1
Table of Contents
Connecting to the Advant OCS .....................................................................................126

Real Time Accelerator Board (RTA)..................................................................128
MOD 300 DCN Control Network Connections.................................................128
MasterBus 300 Control Network Connections ..................................................131
3BUF 000 987 R1
Table of Contents
10
3BUF 000 987 R1
Section 1 Introduction
What is Inform IT Enterprise Historian?
Information is a key asset of all manufacturing and process businesses. One
significant issue that such businesses face is the collection and distribution of
information from its point of origin to locations where it can be applied to improve
quality and productivity.
Manufacturing and process operations must be able to adapt to daily and hourly
changes in production schedules and resource availability. In today's business
environment, much of this information is available electronically, but must also be
presented to operations in a meaningful context.
Technology has driven information access lower and lower in the enterprise-wide
architecture to near real time. Production management and planning functions
require vertical integration of high value information. An information backbone is
required to integrate information from multiple systems upward into the supply
chain and decision making systems.
Industrial IT from ABB is a comprehensive approach for organizing information
collection and management functions across an enterprise. The information can be
leveraged through its use in process specific applications for improving process
operation and managing production quality. In Industrial IT, information is shared
across the enterprise with tools that reduce redundant entry and minimize deviations
between engineering and operations databases. ABB has created an infrastructure
for information across its manufacturing related products using open
communication standards. This lets you integrate ABB components and systems
with other information functions across the enterprise.
Inform IT Enterprise Historian supplies the information management component to
the backbone, integrating data from various levels of the business and making that
data available to the different levels of the organization. Each level has differing
information needs, Figure 1.
3BUF 000 987 R1
11
Figure 1. Industrial IT Information Management Component

Pivotal to being successful with Industrial IT, is the gathering and leveraging of
process and production information. Stored process and production information is
not only available to document production activities, but is also rich in information
which lets you review past performance of the process. Past information is used to
produce similar products, at similar rates and under similar operating conditions. It
also lets you seek and move to more optimal operating conditions based upon
quality and economics.
Enterprise Historian lets you leverage information available from process and
production operations to operate a business more wisely. With Enterprise Historian
you mine data and transform it into information, knowledge and wisdom for better
decision making.
12
3BUF 000 987 R1
Inform IT Enterprise Historian is a distributed information management system,

Figure 2. It provides the ability to collect data from multiple sources and combine it
into a single historical instance. This data can come from ABB control systems, 3rd
party automation systems such as DCSs and PLCs, and other devices like bar code
readers. A store and forward architecture increases data security and maintains a
high level of communications availability with the historical data sources.
Figure 2. Industrial IT Information Management Component

In this architecture, data is collected and stored in two locations. One is the
Enterprise Historian Collect server. This supports operators and other personnel at
the local control system. It provides services such as operator trends and shift/daily
production reports.
3BUF 000 987 R1
13
The other primary storage location is Enterprise Historian Consolidate server. This
combines data from Enterprise Historian Collect and Enterprise Historian Connect
servers. Enterprise Historian Consolidate provides access to data for desktop clients
and other personnel in the facility. It is also the primary supplier of data to business
and planning systems and other Manufacturing Execution System (MES)
applications. This function is best performed from the Consolidate server at the
plant level since it has the complete set of data that may be required.
Enterprise Historian Connect server provides connectivity to DCSs, PLCs and other
devices when that data is not required in the control domain. It provides store and
forward capability to the Enterprise Historian Consolidate server.
Due to the distributed nature of the Historian, data can reside on multiple servers
and yet appear to be on a single server. When making a request for data, you connect
to one server. If the data requested is not present at that server the Historian
automatically forwards the request to other servers. The response is returned from
whichever server has the requested data.
Enterprise Historian is a multi-tiered, client-server application that operates in a
distributed architecture. This lets you use computing resources effectively. ABB's
Enterprise Historian architecture is unique in its flexibility and versatile application
of standard functional components to a variety of process information management
situations. Enterprise Historian can apply its functionality locally to a single ABB
control system, or it can be applied across multiple control systems from multiple
vendors. History servers are logically linked at a site and across an enterprise to
provide a common historical data environment with simple desktop access.
There are four major components to an Enterprise Historian:
14
Data Collection, Storage and Retrieval
User Interface
3rd party system and device interfaces
Data analysis and mining
3BUF 000 987 R1

Enterprise Historian provides various techniques for data collection and becomes a
repository of process, event and production information. Data security has always
been a priority for Enterprise Historian. Dual and distributed storage techniques
offer duplicate storage of data in two or more places. Off-line storage and on-line
backup provide the ability to move data to a removable media for safe storage.
Rather than fitting diverse data types and relationships into the same storage
structure, Enterprise Historian offers varying storage capabilities so that diverse data
may be stored in a manner appropriate for the industry or application. Production
Data Logging (PDL) is used for structuring batch records and other production
specific data while specialized storage techniques are available for events, alarms,
and other system messages.
Process data
Process data such as pressure measurements, temperature indicators, and flow rate
are recorded at a basic resolution that is specific to each tag monitored by the history
function. Calculations such as minimum, maximum, averages and statistical
calculations can be performed as data is recorded in the historian. You have the
option of applying data compaction, or maintaining raw, uncompressed data when
raw data is required for application or documentation purposes.
Production Data
Enterprise Historian manages the storage of production related information about

resource usage and material/product activities based on standard user defined event
processing /monitoring. This data is stored in the Production Data Log (PDL) and
used in conjunction with ABB batch management systems such as Produce IT
Batch.
Often when a batch is being produced, the information associations are not
time-related and cannot be pre-configured or anticipated. PDL has built-in
provisions for the organization, storage and retrieval of this type of information.
PDL organizes critical process data such as operator interventions, alarm and
events, equipment usage and task start/stop and duration times. Figure 3 shows the
relationship of the data stored in a PDL for a batch process.
3BUF 000 987 R1
15
Figure 3. Data Stored in PDL for a Batch Application

PDL data is stored in Oracle tables and is accessible by standard SQL queries. The
information is available to Reports, other network-based reporting or analysis
packages and applications such as Microsoft Access and Excel.
PDL provides logically organized, easily retrievable production data. This data
correlation is not based solely on time. PDL information is associated with tasks
such as campaign, batch, unit, operation, phase and variables. PDL transforms data
into useful information for intelligent decision making.
16
3BUF 000 987 R1
Event data
Enterprise Historian also supports the collection of events and system messages
generated through standard control loop processing, operator control functions,
control applications, batch programming or user-defined applications. All data,
messages and production information recorded in history are managed together and
can be retrieved and reviewed from standard displays. Events are stored in Oracle to
provide a simple query mechanism for analyzing relationships between events over
time.
A specialized version of event storage is an Audit Trail for pharmaceutical and other
government regulated industries. The Audit Trail provides a complete trace of
changes that have been made to production data. The Audit Trail tracks changes
made to data stored in the Production Data Log and is completely integrated with
Produce IT Electronic Batch Record (EBR) for handling of manual production
steps. The Audit Trail holds the time of the data change, the identification of the
person that made the change, the old value and new value, and other valuable
information. Combined with the production data stored by a batch management
package such as Produce IT Batch and other process and event data stored in the
Historian, a complete electronic batch record can be generated. This is an important
element of satisfying the FDA 21 CFR Part 11 regulation.
Off-line Storage and On-line Backup
All data stored in the historian can be copied to removable disk media (Magneto
Optical disk). This can be done on a cyclic basis, manually, or on event such as the
end of a batch. In addition to the off-line storage capabilities, Enterprise Historian
also supports on-line backup functionality.
Historical values for points in the historian, as well as quality data are available via
OLE DB, SQL and ODBC. Event and production data are available via proprietary
COM interfaces, SQL and ODBC.
3BUF 000 987 R1
17
User Interface
User Interface
Data access from the desktop is critical. Enterprise Historian provides:
a very thin client for custom displays
the ability to look at all the data via Excel
the ability to integrate Enterprise Historian based data along with other data
sources (i.e. relational databases) into a single display.
Internet and intranet access is supported by a web-based trend package. Custom

displays are available as ActiveX controls and can be accessed from Internet
Explorer or a custom application that can host ActiveX controls.
The historical data managed by Enterprise Historian can be accessed via Display
Services. Display Services provide seamless operator and management views to real
time and historical information. Data can come from multiple Enterprise Historian
servers and other systems and can be combined on comprehensive displays. This
data can also be accessed through industry standard mechanisms such as OLE DB,
SQL, ODBC and OPC Foundation's OPC/DA (process Data Access) mechanisms.
This simplifies and facilitates integration with user preferred reporting and analysis
functions as well as established production management applications.
Enterprise Historian supports a number of different ways to view data. There is a
lightweight desktop display package, Excel plug-ins, and a stand alone trend
package.
Display Services
Through Display Services you can create custom graphics and view them from your
desktop. These displays can be process mimic displays, status overview or other
information management displays. A wide range of display elements are available
for creating these displays such as bar charts, pie charts, edit boxes and gauges as
well as traditional process elements like pumps, motors and vessels. Displays can be
viewed in the container provided with Enterprise Historian that supports navigation
through the different displays that have been built or can be viewed in a web
browser.
A display can include data from Enterprise Historian, OPC servers and ADO
(ODBC) data sources. Displays can read data from the system and also write data to
the historian.
18
3BUF 000 987 R1
3rd Party System and Device interface
DataDirect
DataDirect provides a set of ABB Add-ins to Microsoft Excel. These Add-ins

provide access to process variables, history values, messages, production data and
SQL-based data through dialog windows on spreadsheets. There is one dialog for
each of the different storage types within Enterprise Historian. Functions are also
provided so that you can create and execute standard reports. It is also possible from
these dialogs or functions to add data to the Enterprise Historian or modify values
that are already stored.
DeskTop Trends
Desktop Trends is a standalone trend package that lets you see trend and associated
data in a web browser. Parts of the trend package are:
a tag ticker which is a scrolling list of configured tags. Colors can be used to
show when a value is outside of its limits, has bad data quality, and a number of
other conditions.
a tag browser which lets you structure and browse points in an easy-to-access
manner.
a trend display that can be launched from either the tag ticker or the browser.
You can also drag and drop tags from the ticker and browser to the trend
display. The trend supports a full range of scrolling and zooming features,
including a unique feature called Active Zoom. This lets you zoom into a
section of the trend while maintaining the overall scope.
3rd Party System and Device interface

Enterprise Historian provides the ability to integrate data from 3rd party products
through a series of interfaces and protocols to PLCs (such as Siemens, A-B, AEG
Modicon), DCSs and other types of devices. The interfaces are accomplished via
either serial or Ethernet connection, depending on the type and age of the interface.
All data that comes through these interfaces are available via OPC. These device
interfaces are best used when an OPC server is not readily available. Drivers to more
than 250 devices are supplied as well as support for standard communications
protocols such as MODBUS and PROFIBUS.
3BUF 000 987 R1
19
Data Analysis and Mining
For added data security, data can be kept locally at the connection to the data source
and forwarded to the historical server when it is available.

What makes data valuable is the ability to analyze and learn from it. Enterprise
Historian embeds data analysis and mining tools. An integrated report scheduler is
also available to satisfy your reporting requirements.
Reporting capabilities
The report scheduler is a web-based user interface for scheduling reports to execute
in either Excel or Crystal Reports. Reports can executed on a cyclic basis, at given
time intervals (for example - 6:00PM on the last Friday of every month), manually,
and on event such as batch end. From the scheduler you can view the status of
reports that have been scheduled and navigate to completed instances of the reports.
Handling of finished reports includes e-mail, saving to file (and managing a number
of instances of that report), saving to history, and printing to a networked printer.
Files are saved in the formats supported by the reporting tool and are easily
launched back into that tool.
The report scheduler is compatible with Crystal Reports Professional and Developer
version 7.x or 8.x. Crystal Reports is not provided as part of Enterprise Historian
version 3.2 and must be purchased separately.
Process modeling and analysis
Unused historical data is a waste of valuable information. With Enterprise

Historian's data mining, analysis and modeling tools, provided by Pavilion
Technologies, you can create data driven models to analyze history data, predict key
process parameters and optimize processes.
Offline tools can be used to identify key variables and hidden interaction between
them, enabling you to transform data into knowledge for productivity
improvements. Effects of process inputs on outputs are ranked and what-if scenarios
show you how to improve operational efficiency, yield and quality control.
20
3BUF 000 987 R1
You can add modeling tools for property predictions, off-line and on-line model
predictive control and steady state optimization. You can optimize your processes
and see a rapid return on investment. Increased production capacity and tighter
quality control can be achieved while reducing energy consumption, process errors
and capital expenditures.
The following describes a basic step-by-step approach to data mining modeling and
analysis:
Start with InsightsTM (one license included with Enterprise Historian Collect
or Consolidate).
Extract data from History Services via an easy-to-use data extraction

wizard.
Filter and cleanse the data, removing out of range values by simply cutting
it from a trend.
Let Insights build Inferential Models based on your selected inputs and
outputs.
Perform What-ifs in an off-line manner and Sensitivity Analysis (effect of

inputs and changes to those on outputs) to identify the most important
process variables in your process.
Put models on-line with Property PredictorTM Virtual On-line Analyzers for
timely measurements.
Sensor validation for critical measurements
Inferential models for controllers
An additional license must be purchased for Property Predictor.
3BUF 000 987 R1
21
Whats New in this Release
Whats New in this Release

New Platform
Enterprise Historian server software runs on Windows 2000. Desktop client

applications may be installed on Windows 2000 or Windows NT. (Display client
and DataDirect software may be installed on Windows 95, Windows 98, and
Windows ME.)
New Bundling Options
See Bundling Options on page 23.

New Applications
The following new applications are available in Enterprise Historian version 3.2:
Desktop Trends - provides desktop data display functions that can be viewed in
stand-alone web page mode, or be integrated into other applications that are
ActiveX containers. See Desktop Trends on page 80.
Audit Trail for event/message logging for batch management applications such
as Electronic Batch Recording (EBR). See Audit Trail on page 82.
History data access via OLE DB, ODBC, and SQL. See OLE DB Data Access
on page 84.
Web-based Report Scheduler and Display. See Report Services on page 87.
MES Server and ComAware Removed from Automation Connections
The Select and Automation Connections standalone product offerings from earlier
releases of Enterprise Historian are restructured as Enterprise Historian Connect.
This provides the ability to collect data from OPC sources and other third party
devices with local data buffering before the data is transferred to the history data
server via distributed logs. The PLC drivers from Automation Connections are an
option to Enterprise Historian Connect. Because of the new product structure and
ability to distribute history logs, the MES Server was removed from the PLC
Interface component.
22
3BUF 000 987 R1
Bundling Options
If you are buying Enterprise Historian Connect to upgrade an existing Automation

Connections installation, carefully evaluate any changes required for this upgrade:
Applications using the MES Server to create omf type objects for history
collection will have to be re-engineered. The omf objects created via the MES
Server to collect the OPC data will have to be replaced by History logs
configured in History Services.
If other applications such as User API or Display Services accessed those omf
objects, a new solution will have to be developed. In Enterprise Historian 3.2,
Displays Services and DataDirect can use the OPC data provider to get data
from the PLCs rather than going through the MES Server.
Also the ComAware component of the MES Server will no longer be available
on the Enterprise Historian v3.2. The migration of applications developed
using this component of the software will need to be reworked. There is no
direct replacement in Enterprise Historian v3.2. Contact Product Management
with specific questions concerning your applications and future support.
Bundling Options
The core functionality for Enterprise Historian is installed on a Windows 2000based server. There are three bundling options for this core functionality:
Enterprise Historian Collect supports data collection directly from an ABB

automation system or OPC server. This bundle replaces Enterprise Historian
Professional from version 3.1.
Enterprise Historian Connect provides connectivity to 3rd party systems with

store and forward capability to Enterprise Historian Consolidate. This bundle
replaces Enterprise Historian Select from version 3.1 and Automation
Connections as a standalone application.
Enterprise Historian Consolidate combines data from multiple Enterprise

Historian Collect and Connect installations.
3BUF 000 987 R1
23
Enterprise Historian Collect

Enterprise Historian Collect provides historical services when the historian is
directly connected to the data source, either through OPC or on an ABB control
network. This bundle extends the short term historical data storage for ABB OCS
systems. It supports operators with trend and event data, and provides local
reporting. Complete data storage, retrieval and archival capabilities are provided
along with integrated data analysis and mining capabilities. Desktop access is
provided from Microsoft Office tools, a web browser and custom displays.
Enterprise Historian Collect may be a data source for Enterprise Historian
Consolidate as illustrated in Figure 4.
Collect is not to be used when collecting data from other history sources, including
Enterprise Historian Connect if data forwarding is being employed.
Figure 4. Enterprise Historian Collect
24
3BUF 000 987 R1
The core functionality and options are summarized in Table 1 and Table 2.
Table 1. Enterprise Historian Collect - Core Functionality
Component
Description
System Services
Supports basic services including network communications, object

handling, process supervision, and system messaging.
History Services with

minimum 250 tag license
Supports configuration, collection, storage, archival, and access to

History logs by DataDirect, Display Services, and User API.
Display Services with one

display build license and 5
data providers.
Supports building and viewing dynamic runtime displays on client

nodes connected to a display server.
Display IE
Both the Display client and DisplayIE may be installed locally on

the server and on remote PC clients.
DataDirect - one client

license
Microsoft Excel add-ins let you access information from Enterprise

Historian and other ABB OCS applications. This includes dialogs
for ad-hoc data retrieval and function calls for report building.
DataDirect may also be installed on remote PC clients.
Desktop Trends - one client

license
Lets you view trend data directly on your Enterprise Historian

desktop. Three trend presentations are available:
Display IE lets you launch the display client application as an

ActiveX Control via Windows Internet Explorer.
Trend Ticker shows a repeating stream of process data for

selected tags, similar to a stock market ticker.
Tag Explorer provides process data for selected tags in

tabular format. The presentation and mode of operation
resembles the Windows Explorer.
Trend Display shows traces for up to eight tags.
Desktop Trends may also be installed on remote PC clients.

Pavilion Insights license
- One client license
3BUF 000 987 R1
Enterprise Historian integrates with and includes one client license

for Pavilions Insights software. Additional seats may be
purchased as an option. Pavilions Insights lets you intelligently
analyze large volumes of historical process data with tools for
cleaning and preprocessing the historical data. Pavilion Insights
Client provides tools for building off-line process models.
25
Table 2. Enterprise Historian Collect - Options

Component
Description
User API
User API is installed with System Services. You must

purchase a license to use this software for application
development. This license provides services (functions) for
accessing Advant OCS process objects or historical data. To
develop applications, User API requires Microsoft Visual
Studio V6 or an equivalent c++ compiler. The User API
contains functions to read from, write to and manipulate the
Advant OCS objects in other ways. The User API also
provides services for system message and date and time
handling.
OLEDB Data Access
Supports OLE DB, ODBC, and SQL access to numeric logs

residing on a Windows-based History server. This is
required to:
Report Services Report Scheduling Server and

Display Components
support numeric log access by Crystal Reports when

this package is employed as the report building
package for Report Services.
support SQL access to Windows-based numeric logs

for DataDirect, Display Services, or other 3rd party
tools.
The server supports scheduling, execution, and retrieval of

reports built with Crystal Reports or Microsoft Excel. The
display component provides the graphical user interface for
performing these tasks. The display component may also be
installed on remote PC clients.
This component does not include a license for Crystal
Reports or Microsoft Excel.
26
3BUF 000 987 R1
Table 2. Enterprise Historian Collect - Options

Component
Description
Event Log
This component is applicable for the Advant OCS with

Master software. Event Log software is installed with History
Services. An Event Log license is required. This supports
secondary logging of event data in the Enterprise Historian
node. The primary logs - the event data sources - can be
located in one or more OS nodes, or ABB
MasterView 850/1.
Audit Trail
Audit Trail software is installed with History Services. An

Audit Trail license is required. This supports event/message
logging for Produce IT Electronic Batch Recording (EBR).
Production Data Logging (PDL)
PDL is installed with History Services. A PDL license is

required. PDLs store production data such as batch
start/end times, batch variables, and event/messages data
for presentation in batch reports. PDL is typically used with
Batch 300 or Produce IT Batch.
3BUF 000 987 R1
27
Enterprise Historian Connect

This bundle provides connectivity to ABB systems (such as Symphony and
Freelance) and non-ABB systems (DCSs, PLCs, and other devices). Connectivity to
3rd party devices is achieved through a series of drivers that are provided in this
bundle. Enterprise Historian Connect can also access data directly from OPC
servers.
Enterprise Historian Connect supports store and forward functionality to Enterprise
Historian Consolidate which is the primary data storage server. This bundle may
also be used as a gateway to Advant OCS systems, replacing Enterprise Historian
Select. This is primarily used to host applications that need to run close to the
control network. Enterprise Historian Connect obtains data directly from an Advant
system and provides data to 3rd party applications. When purchased with the PLC
Interface option, this bundle replaces Automation Connections. Otherwise, this is a
replacement for Enterprise Historian Select.
The core functionality and options for Enterprise Historian Connect are summarized
in Table 3 and Table 4.
Table 3. Enterprise Historian Connect - Core Functionality
Component
System Services
Description
Supports basic services including network communications, object
handling, process supervision, and system messaging.
History Services with

Supports limited History Services functionality based on purchased
minimum 250 tag license options. See Data Forwarding option in Table 4.
Display Services - 5 data Supports data access for DataDirect and Desktop Trends. Note: A
providers
builder license for creating new graphic displays is not standard. Such
a license may be ordered as a Display Services expansion.
28
3BUF 000 987 R1
Table 3. Enterprise Historian Connect - Core Functionality

Component
Description
DataDirect - one client

license
Microsoft Excel add-ins let you access information from Enterprise

Historian and other ABB OCS applications. This includes dialogs for
ad-hoc data retrieval and function calls for report building. DataDirect
may also be installed on remote PC clients.
Desktop Trends - one

client license
Lets you view trend data directly on your Enterprise Historian desktop.
Three trend presentations are available:
Trend Ticker shows a repeating stream of process data for

selected tags, similar to a stock market ticker.
Tag Explorer provides process data for selected tags in tabular

format. The presentation and mode of operation resembles the
Windows Explorer.
Trend Display shows traces for up to eight tags.
Desktop Trends may also be installed on remote PC clients.
3BUF 000 987 R1
29
Table 4. Enterprise Historian Connect - Options

Component
Description
User API
User API is installed with System Services. You must

purchase a license to use this software for application
development. This license provides services (functions) for
accessing Advant OCS process objects or historical data. To
develop applications, User API requires Microsoft Visual
Studio V6 or an equivalent c++ compiler. The User API
contains functions to read from, write to and manipulate the
Advant OCS objects in other ways. The User API also
provides services for system message and date and time
handling.
PLC Interface
Supports data exchange between Enterprise Historian

applications and third-party devices such as Programmable
Logic Controllers (PLCs), loop controllers, bar code readers,
scientific analyzers, remote terminal units, and distributed
control systems.
Data Forwarding
This option supports History configuration, collection and

storage for forwarding of data to an Enterprise Historian
Consolidate server.
Without this option, the functionality is limited to History
access support for Display Services, DataDirect, Desktop
Trends, and User API.
30
3BUF 000 987 R1
Enterprise Historian Consolidate
Enterprise Historian Consolidate

This combines and stores data from multiple Connect and/or Collect nodes. This is
the information management solution at a plant level or higher. The only network
connection for Enterprise Historian Consolidate server is to the TCP/IP network.
Complete data storage, retrieval and archival capabilities are provided along with
integrated data analysis and mining capabilities. Desktop access is provided from
Microsoft Office tools, a web browser and custom displays. The core functionality
and options provided in Enterprise Historian Consolidate are identical to those
provided with the Enterprise Historian Collect bundle as described in Table 1 and
Table 2. The exceptions are that the following options are not supported on the
Enterprise Historian Consolidate server:
Enterprise Historian Harmony OPC Integration
Event Log for systems with Master software
Licensing
Server software components are licensed on a per-server basis. This means one
license entitles you to install the software on one server. You must purchase a
license for any server software components that you intend to install.
Client software components are licensed on a concurrent-user basis. This means you
can install the client software on as many PCs as you wish. The server will control
the number of clients that may connect to the server based on the number of client
licenses you have purchased. For example, you may install Display Client software
on ten PCs, but if you purchase two Display Client licenses, only two client PCs will
be permitted to connect to the server at any one time.
For Display Client and DataDirect, each open Display and/or DataDirect window
occupies a client license, even if the windows are open on the same PC. Thus one
PC may occupy two or more client licenses concurrently.
For Desktop Trends, client licenses are occupied on a per-PC basis. You are
permitted to have as many trend displays open on a given PC as you wish. This
would still occupy just one client license.
3BUF 000 987 R1
31
Licensing
32
3BUF 000 987 R1
Section 2 Basic Software Components
System Services

Three basic software bundles are offered as described in Bundling Options on page
23. The components that comprise each of these products are described below.
System Services
System services are primarily configuration and support tools for developing and
integrating information management functions in your system, including:
a Core System that provides communication services for system functions as

well as customer applications.
System Status, System Message and other system management utilities.
Advant OCS communication software for integration of Enterprise Historian

applications with applications on other Advant OCS nodes via the Realtime
Accelerator board connection to the control network, or via TCP/IP.
OPC communication software provides OPC V1.0a or V2.0 OPC client for
collecting historical data from the PLC Interface, Operate IT OPC servers,
AC 800F and other 3rd party servers. See Appendix A, Control Network
Connections for more information on supported OPC servers.
3BUF 000 987 R1
33
History Services
History Services
History Services supports data collection with optional compression (polled, by
exception, user-supplied, or manual), storage, and retrieval. The degree of
functionality is based on the software bundle you purchase.
Collect and Consolidate provide full data collection, storage, compression

(optional), and retrieval functionality as described in this section.
Connect provides limited History Services functionality to store and forward

data to an Enterprise Historian Consolidate server.
The Data Forwarding option for Enterprise Historian Connect supports History
configuration, collection, and storage for forwarding to distributed logs on an
Enterprise Historian Consolidate server. Historical storage is limited to primary
logs. Secondary logs are not supported. Off-line storage is not supported either.
Without this option, History Services functionality is limited to History access
support for Display Services, DataDirect, Desktop Trends, and User API.
Applications that Use History Services

Enterprise Historian stores process data, events, and production data. The historical
data collected and stored by History Services is available for use in other
applications. For instance:
34
It is available to Pavilion Insights for data analysis and process modeling.
It can be presented on Enterprise Historian display applications such as Display

Services, DataDirect, and Desktop Trends. These applications let you view data
over the Internet using Internet Explorer.
It is available for custom applications via OLE DB, SQL, ODBC, and User API
(Application Programming Interface).
It can be viewed from Operate IT products by integrating Display Services and

desktop Trend into the Operate IT Display system, either as web pages or
ActiveX controls.
It can be displayed on AdvaCommand trend displays for the Advant OCS, and
on Multibus-based trend displays (MOD 300 only).
3BUF 000 987 R1
Applications that Use History Services
Data can be stored long term on disk. Archive supports copying data to a Magnetic
Optical (MO) Disk for extended data storage and data security.
Historical data is often the basis for further evaluation and improvements of your
process. Display Services provide excellent trend presentation to help you evaluate
and manage your process in the most effective way.
History collects samples from various data sources that may be located in any node
of the system, or in external devices such as PLCs. Some examples are:
Floating point and integer numerical values from process objects. These values
can come from ABB Control Systems, and/or 3rd-party automation systems
and devices, directly from a control network or via OPC.
Digital values
Messages - alarm and event, TCL (MOD 300 only), Audit Trail, OPC
Operator actions such as parameter changes
A typical historical application stores the values for thousands of individual data
sources. A common application of history is to periodically store values of process
variables such as flows, temperatures, or tank levels. For example, to store the value
of a steam flow, your data source is the measured variable of the loop that controls
the flow.
3BUF 000 987 R1
35
Process Data Storage

Process data is stored in numeric logs built within the composite log structure. A
composite log can be as simple as a single primary log (a log that is connected
directly to a data source), Figure 5.
$HSTC100,MEASURE-1-o
Data Source
Figure 5. Example - Simple Primary Log

More complex composite logs may have multiple primary and secondary logs
(secondary logs get their data either from a primary log, or another secondary log).
Some examples are illustrated in Figure 6 through Figure 8.
Average
Data Source
Primary Log
Secondary Log
Figure 6. Example - Primary Log with Secondary Log Storing Calculated Average
Primary Log Node A
Data Source
Distributed Log
Node C
Primary Log Node B
Figure 7. Example - Redundant Data Collection with Dual Log Distributed to a Remote Node
36
3BUF 000 987 R1
Node A
Data Source
Data Source
Node C
Data Source
Node B
Figure 8. Example - Remote Node Consolidating Primary Logs from Multiple Nodes
A composite log can collect from any one of the following data sources:
directly from the process object
from another history log
a TTD log in an AC450 or MP200
3BUF 000 987 R1
37
Calculations
You can configure History to perform calculations on collected data before the data
is actually stored in the log. The types of calculations you can specify are:
AVERAGE
MAXIMUM
MINIMUM
INSTANTANEOUS - no calculation (default)
SUM
SUM_OF_ SQRS
STANDARD DEVIATION
NUM_OF_ VALUES
You can specify calculations to be done on data before it is stored in a log (either
primary or secondary), Figure 9. This lets you store a single value to represent a
larger time span of values. For example, you can sample a variable every minute and
put those values into a primary log. Then you can calculate the hourly average,
minimum, and maximum on data in the primary log and store those calculated
values in secondary logs.
Data
Source
Calculation
Primary Log
OR
Data
Source
Primary Log
Calculation
Secondary Log
Figure 9. Calculations
38
3BUF 000 987 R1
Data Compaction
Data compaction is an optional space-saving technique for storing history data:
It reduces the load on the system by filtering out values that do not have to be
stored since there is not a significant change in the value.
It allows data to be stored on-line for a longer period of time since data is not
replaced (overwritten) as quickly.
Compaction is specified on an individual log basis. You may use it for some logs
and not for others. Compaction should not be used indiscriminately in all cases. For
instance:
If you want an accurate representation of your process over time, and you do
not require that every data sample be stored, you can use compaction.
If your application requires that every data sample be stored as an instance in

the log, you can not use compaction.
Compaction can not be used on logs connected to distributed logs.
Data compaction can be used on digital data sources so that only state changes are
saved.
Figure 10 shows how samples are stored when deadband is active. The deadband
function holds each sample until it determines whether or not the sample is required
to plot the trend. Samples that are not required are discarded.
A sample is stored when deadband is activated at 0s. The sample at 10s is held until
the next sample at 20s. Since there is no change in slope between 0s and 20s, the 10s
sample is discarded and the 20s sample is held. This pattern is repeated at each 10second interval until a change in slope is detected at 50s. When this occurs, the
samples at 40s and 50s are stored to plot the change. At 90s another change in slope
is detected, so the samples at 80s and 90s are stored.
3BUF 000 987 R1
39
Even though there are spikes between 80s and 90s, these values were not sampled so
the slope remains constant (as indicated by the dotted line). Another change in slope
is detected at 100s. The sample at 100s is stored to plot the slope. The sample at 90s,
also used to plot the slope, was already stored. The slope remains constant
thereafter. The next sample stored is 140s since the Deadband Storage Interval (40s)
elapses between 100s and 140s. The sample at 180s is also stored due to the
Deadband Storage Interval.
Deadband Storage Interval = 40s
Sample & Storage Interval = 10s
Samples stored at these Intervals

because Deadband Storage Interval
elapsed since last sample stored
Compaction activated,
sample stored
0 10
20
30 40 50
60
70 80 90 100 110 120 130 140 150160 170 180 190 200
Samples stored at these Storage Intervals to plot the trend
Figure 10. Data Compaction Example

Compaction effectively increases the log period so the same number of samples
stored (as determined by the log capacity) cover a longer period of time.
40
3BUF 000 987 R1
Composite Log Applications
To learn more about composite log applications see:
Secondary Logs for Different Resolution/Time Span Views on page 42
Primary and Secondary Logs with Calculations on page 43
Lab Data Logs for Asynchronous User Input on page 44
Consolidating History Data with Distributed Logs on page 45
Collecting Data for Longer Time Period at Consolidate Level on page 47
Composite Log with Local and Distributed Secondary Logs on page 47
Calculated Values on both Collect and Consolidate Levels on page 48
Collection from Enterprise Historian Connect on page 48
Dual Configuration for Data Security on page 50
Collecting from OPC Data Sources on page 52
3BUF 000 987 R1
41
Secondary Logs for Different Resolution/Time Span Views
You can provide different views of a process variable by configuring a different time
span for each individual log in the composite log. For example, in Figure 11 the
primary log HSTC100,MEASURE-1-o stores high resolution data for a short time
span, while secondary logs HSTC100,MEASURE-2-o and HSTC100,MEASURE3-o store progressively lower resolution data for longer time spans. This
configuration also lets you store data over longer periods using less storage capacity.
TC100.Measure
Secondary Log
Storage Rate: 1 Hour
Time period: 104 Weeks
Calculation: Average
Secondary Log
Storage Rate: 1 Minute
Calculation: Average
Primary Log
Storage Rate: 10 seconds
Calculation: Instantaneous
Figure 11. Example, Secondary Logs with Different Views of a Process Variable
42
3BUF 000 987 R1
Primary and Secondary Logs with Calculations
You can configure a calculation algorithm in a primary or secondary log to store

other aspects of the logged variable such as maximum and minimum values for a
specified time interval. The calculation is performed before the data is stored in the
log. This allows you to store a single value that represents a larger time span of
values, or key characteristics of the data. For example, you can sample a variable
every minute and put those values into a primary log. Then you can configure that
an hourly average, minimum, and maximum be calculated from data in the primary
log and store those values in secondary logs. This example is illustrated in
Figure 12.
Figure 12. Example, Composite Log using Calculations
3BUF 000 987 R1
43
Lab Data Logs for Asynchronous User Input
Lab data logs are a special type of numeric log. This log type is used to collect
asynchronous data entered manually or via an external application such as a User
API program. Asynchronous logs must be Oracle-based.
Lab Data logs must be primary logs. You can add a Lab Data log alone, or as part of
a composite where other primary logs are already connected, Figure 13.
Lab Data Log in a composite

with other numeric logs
Lab Data Log
Alone
Figure 13. Representation of Lab Data Log in Composite Log Hierarchy

When configured with synchronous logs, the asynchronous log does not receive
data from the data source. The connection is only graphical in this case.
44
3BUF 000 987 R1
Consolidating History Data with Distributed Logs
Moving data from an Enterprise Historian Collect or Connect server to a

Consolidate server is accomplished via distributed logs. A distributed log is a
secondary log that resides on a remote node. This composite log structure lets you
consolidate history data from one or more servers located to one or more ABB OCS
networks, on a remote Consolidate History server on the TCP/IP network. A
consolidation server may also receive data from an Enterprise Historian Connect
server which is collecting data from PLCs and forwarding to the consolidation
server.
For example, in Figure 14 primary logs 1-1, 2-1, and 3-1 reside on History nodes on
an ABB OCS network. Their respective secondary logs reside on remote History
server C on the TCP/IP network. Although not shown in Figure 14, History Node C
may contain a secondary log that collects data from a primary log in a History server
on another ABB OCS network as well.
log1-2
log2-2
log3-2
History Node C
TCP/IP Network
log1-1
log2-1
History Node A
log3-1
History Node B
ABB OCS Network
Figure 14. Example, Distributed Logs
3BUF 000 987 R1
45
Performance Considerations
You can configure a maximum of 50,000 distributed logs on the Consolidate server
on the TCP/IP network. Each ABB OCS network server can distribute up to 10,000
logs to a Consolidate server on the TCP/IP network. Thus, you can consolidate data
from up to five ABB network servers, where each ABB network server distributes
10,000 data sources, Figure 15. This limit (50,000) is based on each data source
having a single primary log with no secondary logs. Additional primary or
secondary logs in a composite log count toward the 50,000 log limit.
The samples have UTC timestamps so data can travel across different time zones.
TCP/IP Network Consolidate History Server
Up to 50,000 Distributed Sources
TCP/IP network
History Server 1
Up to 10,000 Data Sources
3rd-party network
History Server 5
Up to 10,000 Data Sources
ABB OCS network
Figure 15. Distributed Log Capacity

Distributed Log Applications
Some common applications for distributed logs are described in:
46
Collecting Data for Longer Time Period at Consolidate Level on page 47
Composite Log with Local and Distributed Secondary Logs on page 47
Calculated Values on both Collect and Consolidate Levels on page 48
Collection from Enterprise Historian Connect on page 48
Collecting from Remote History Logs on page 49
3BUF 000 987 R1
Collecting Data for Longer Time Period at Consolidate Level
In Figure 16, the primary log on the Enterprise Historian Collect server maintains
History data for a 5-week time period, while the secondary log on the Consolidate
server collects from the primary log and maintains the data for a 1-year time period.
Primary Log on roc175
Secondary Log on eng169 (Consolidate Server)
Figure 16. Storing Data for a Longer Time Period on the Enterprise Node
Composite Log with Local and Distributed Secondary Logs
The composite log may have additional secondary logs performing other functions
(for instance, calculations) on the Enterprise Historian Collect server. You can insert
additional secondary logs on the Enterprise Historian Collect server along with the
distributed logs on the Consolidate server. An example is shown in Figure 17.
Secondary Log on eng169 (Consolidate Server)
Additional Secondary Logs Inserted on Local Server
Figure 17. Composite Log with Local and Distributed Secondary Logs
3BUF 000 987 R1
47
Calculated Values on both Collect and Consolidate Levels
In Figure 18, the secondary logs on the Enterprise Historian Collect server calculate
average and standard deviation values and maintain the History data for a 5-week
time period, while the secondary logs on the Consolidate server collect those
calculated values and maintain them for a 1-year time period.
Figure 18. Calculations on Both Local and Consolidate Nodes

Collection from Enterprise Historian Connect
In Figure 19, the log on the Enterprise Historian Connect server acts as a store and
forward buffer for the instantaneous log on the Consolidate server. Average and
Standard Deviation calculations are then performed. Note that only primary logs can
be configured on the Enterprise Historian Connect server.
It is important to include the instantaneous log on the Consolidate server as a
buffer between the instantaneous log on the Enterprise Historian Connect server and
the calculation logs (Average and Standard Deviation) on the Consolidate server.
Without this buffer, each calculation log would be forced to collect data from the
Enterprise Historian Connect server independently and would significantly increase
traffic on the TCP/IP network.
Figure 19. Calculations on Consolidate Node Only
48
3BUF 000 987 R1
Collecting from Remote History Logs
This functionality may be used for the following applications:
When you have an existing database configuration, and you want to create
distributed logs without having to re-configure the existing composite logs.
When using Enterprise Historian Consolidate to collect from History servers

running earlier versions of Enterprise Historian software (version 3.1 for NT or
2.2 for HP-UX). This is because you cannot configure composite distributed
logs on History nodes that use different versions of History software.
Where source nodes reside on separate networks that are basically identical
(same architecture and tag names). This is illustrated in Figure 20.
History Consolidate Server
$HSTC101,MEASURE-1-o111.222.33.44
$HSTC101,MEASURE-1-0111.222.33.55
$HSTC10n,MEASURE-1-o111.222.33.44
$HSTC10n,MEASURE-1-0111.222.33.55
TCP/IP Network
History Server
111.222.33.44
TC101,MEASURE
TC101,MEASURE
TC10n,MEASURE
TC10n,MEASURE
ABB System Network 1

Controller 1
History Server
111.222.33.55
ABB System Network 2

Controller 1
TC101,MEASURE
TC101,MEASURE
TC10n,MEASURE
TC10n,MEASURE
Figure 20. Collecting from a Remote History Log
3BUF 000 987 R1
49
Dual Configuration for Data Security
Dual logs are a special type of numeric log for redundant data collection and
storage. A dual log has two identical log configurations that reside on two different
nodes. Both logs collect data from the same data source. As an option, you can
configure a secondary log for the dual log on a third node. For example, in Figure 21
log1-3 in node C can collect data from either log1-1(in Node A) or from log1-2 (in
Node B), depending on the availability of the given nodes. All History servers in
this configuration must run the same version of History software.
In this example, log1-1 is the primary source for log1-3 and log1-2 is the back-up.
Log 1-2 is only used when log1-1 is unavailable. When data collection switches to
log 1-2, it continues to be used as the source for log 1-3, even if log1-1 becomes
available again, until log1-3 is restarted, or log1-2 becomes unavailable.
History Server C
log1-3
TCP/IP Network
History Server B
History Server A
log1-1
Dual
Log
log1-2
ABB OCS Network

Data Source
Figure 21. Example, Distributed Logs for Redundant Data Collection
50
3BUF 000 987 R1
You can build a hierarchy of dual logs, and distribute the data from a dual log to a
remote node, Figure 22.
View as shown in
Composite Log Window
roc175
Sequen:3
Sequen:1
eng159
Sequen:4
Sequen:2
Sequen:5
Shows how logs are distributed

on their respective nodes
Sequen:6
Sequen:1 & Sequen:2 comprise one dual log,

Sequen:3 & Sequen:4 comprise another dual log,
Sequen:5 & Sequen:6 comprise a third dual log
Dual Log Distributed

to a Remote Node
Figure 22. Example Hierarchy of Dual Logs
3BUF 000 987 R1
51
Collecting from OPC Data Sources
History logs can be configured to collect from data sources via an OPC server.
Several OPC servers are available from ABB. This includes the PLC Interface and
the Accuray Object Server. Third party OPC servers are supported as well.
Figure 23 shows an example of OPC data collection.
History Services
on Windows 2000
PLC
OPC Server
NAME
REGISTERS
$HSTC101,VALUE-1-o
Loop1_PV
$HSTC102,VALUE-1-o
R101
Device
Driver
OPC
Loop2_PV
R102
Loopn_PV
R10n
$HSTC10n,VALUE-1-o
Figure 23. Example, OPC Data Collection
52
3BUF 000 987 R1
Numeric Data Presentation
Data Presentation in trend format is supported by operator console trend displays,

as well as trend displays built with Display Services display client functions,
Desktop Trends, and AdvaCommand trend displays. These displays are simple
graphs of process variables versus time, as shown in the following figure.
All analog and digital attributes recorded in History can be trended. Trend sources
can be changed and multiple trends can be displayed on one chart to compare other
tags and attributes. Stored process data may also be viewed in tabular format in
Microsoft Excel using DataDirect add-ins.
Figure 24. Historical Data on a Trend Display
3BUF 000 987 R1
53
Seamless Retrieval
Seamless retrieval makes it easier for applications to access historical data. For trend
data representation, when scrolling back in time beyond the capacity of the specified
log, the seamless retrieval function will go to the next (secondary) log in the log
hierarchy.
Applications do not need to know the name of the log in order to retrieve data.
Attributes such as access name (data source), log period, calculation algorithm, and
retrieval type can be specified and History will search for the log which most closely
fits the profile.
Numeric Data Storage Considerations
Log entries can be stored in either Oracle tables or directly in files maintained by
History. File storage is faster and uses less disk space than Oracle storage. Filebased storage is only applicable for synchronous numeric logs.
There are three log storage options:
Oracle-based numeric logs: 110 bytes per entry
Type 1: 24 bytes per entry
Type 2: 4 bytes per entry
Type 1 and Type 2 file based logs provide faster storage and use less disk space.
Type 1 logs include data quality and time stamp with every value stored. Type 2 logs
are appropriate for logs that have faster sample rates (5 minutes or less). For logs
with slower sample rates (greater than 5 minutes), Type 1 logs should be used. Type
1 logs should also be used any time you need the additional functionality they
support.
Off-line Storage
All process data stored in a numeric log can be copied to an off-line storage media.
This can be done on a cyclic or manual basis. See Off-line Storage and Access on
page 61.
54
3BUF 000 987 R1
Event Data Storage
Event Data Storage

Message Logs store events and system messages generated by control and operator
applications. There are three different types of message logs available, depending on
where the events are originating from and what functionality is needed:
Generic Event Storage. This event storage is modeled after the data
definitions in the OPC/Alarm and Event specification. It supports a number of
vendor specific attributes. This storage mechanism holds batch related events
from Produce IT Batch and the electronic logbook from Produce IT Electronic
Batch Record (EBR).
Audit Trail. This is a specialized version of the Generic Event Storage. It is

used to track changes made to production data. The Audit Trail message log
keeps the following information:
identification of the person that made the change
time that the change was made
previous and new value for the data being changed, as well as other
information.
The Audit Trail is used extensively by Produce IT EBR to manage changes

made in the manual entry forms as data is being entered into the system.
Advant OCS messages. This storage type supports message and event logging
from Advant OCS systems - systems with MOD300 or Master software.
For MOD300 systems, message logs store CCF and TCL messages as well
as operator action messages such as parameter change and logon/logoff.
For Master systems the event log stores events that are generated from the
control applications in the AC400 series controllers and MasterPiece
controllers.
Message logs are stored in the Enterprise Historian Oracle database. Client
applications such as Display Services and DataDirect access Oracle-based History
data, including message logs, via an ADO data provider.
3BUF 000 987 R1
55
Production Data Storage
Event Presentation
All events stored in the Enterprise Historian can be displayed in DataDirect, using a
dialog that supports easy selection of query criteria (such as displaying all the
alarms for a tag over a certain period of time).
Since the events are stored in Oracle it is also possible to query them using standard
SQL requests. This will commonly be done when reading messages into report
packages and other tools capable of accessing data via SQL or ODBC.
Off-line Storage
All events and messages stored in a message log can be copied to an off-line storage
media. This can be done on a cyclic or manual basis. See Off-line Storage and
Access on page 61.

Production data is stored in a data structure called the Production Data Log (PDL).
PDL does not collect the data and fit it into a pre-defined structure. It is a free format
storage mechanism where the data to be stored is sent to it by an application. In
most cases, the PDL has been used with ABB batch and production management
packages in the pharmaceutical, biotechnology and chemical industries.
Often when a batch is being produced, the information associations are not time
related and cannot be pre-configured or anticipated. PDL has built-in provisions for
the storage and retrieval of this type of information. PDL organizes critical data such
as task (campaign, batch, unit procedure, operation) start/stop and duration times,
operator interventions, alarm and events and equipment usage, and manages the
relationships between each of these different types of information.
With each of the tasks it is possible to store additional information. For example, if
the task is a heat phase, the initial temperature, target temperature and final
temperature could be stored as information with that phase record. In a batch
environment, this allows you to produce a complete batch record with the data
stored in the PDL.
56
3BUF 000 987 R1
History associations make an association to process data that is already being stored
in the Historian. Typically, this association represents the period of time that a
batch occupied a particular unit or a phase execution time period. The associations
are made for only those tags that are relevant. See Figure 25.
Figure 25. Batch Record in PDL

These associations make it easy to do batch-to-batch comparisons or to show data
from a batch without needing to know the actual time that the batch was in the unit.
All references and access to the data can be done by batch id.
When used with Produce IT Batch, the complete recipe (original and any changes
made to it) are stored in the PDL. Later, the recipe can be retrieved for viewing in
the same procedure editor in Produce IT Batch
3BUF 000 987 R1
57
Off-line Storage
All data contained in a PDL and the data associated with that PDL are treated as a
single entity by the Enterprise Historian. This means that when a PDL is archived to
a removable media, all the data stored in the PDL and any associations made from
that production record to other data in the historian is archived together. Then when
the record for a batch has to be reviewed a number of years later, all the data for that
batch is accessed as a single entity. Archiving can be done automatically at
campaign end or batch end. PDLs can also be automatically deleted after they have
been archived if so desired.
Presentation
PDL data is stored in Oracle tables and is accessible by standard SQL queries. The
information is available to reports built using Crystal Reports and Microsoft Excel,
and scheduled using the Inform IT Enterprise Historian Report Scheduler.
Inform IT Enterprise Historian DataDirect (an Excel plug-in) provides a dialog that
facilitates convenient browsing of the data stored in a PDL, allowing you to drill
down to any piece of information stored in the PDL for a batch. For example,
Figure 26 shows a list of campaigns (jobs) and for each campaign, you can drill
down into the batches that are a part of it. This information can be easily written to a
worksheet in Excel.
58
3BUF 000 987 R1
Figure 26. PDL Dialog in DataDirect
3BUF 000 987 R1
59
Finished Report Storage
Finished Report Storage

The purpose of a report log is to hold the finished output from reports scheduled and
executed via the Inform IT Enterprise Historian Report Scheduler. The report
schedule must specify that the report is to be saved to a specific report log
configured via the History Builder. This procedure is described in the Report
Services Operation Manual.
Reports stored in a report log can be archived to a removable media on either a
cyclic or manual basis. Access to archived reports logs is supported through the
Report Scheduler. When reviewing a restored report log, it will be presented in the
tool appropriate for the type of file the report was saved as (i.e. Internet Explorer
will be launched if the report was saved in .html format).
Generally you dedicate one report log to one report. For instance, if you have a
WKLY_SUM report, you make a log especially for it. You put each weeks version
of the WKLY_SUM report into the report log and use different report logs for other
reports. However, you are not required to do it this way. You are free to send more
than one type of report to one report log. For each report you can specify how many
occurrences of the report to save.
60
3BUF 000 987 R1
Off-line Storage and Access
Off-line Storage and Access

When a log is full, the oldest entries are replaced by new entries, or deleted. To
avoid losing History data in this way, you can set up an archival system that
maintains a complete and permanent record of all entries for specified logs.
Archiving copies the log entries for a specific time period from the history database
to a designated archive device. When you need to access archived History data, you
can restore the archived logs to the History database, or publish one or more
selected volumes for direct viewing. (Publishing applies to numeric logs only.) An
overview of this process is illustrated in Figure 27.
History Node
History Database Configuration
Archive Database
Runtime Database
Restored Database
Archive Entry 1
$HSTC100,MEASURE-1-r
Archive Entry n
$HSTCnnn.MEASURE-1-r
$HSTCnnn.MEASURE-1-o
2b
1b
1a - Specified logs copied from
runtime database to archive media
2a
1a
1b - Corresponding archive entry

recorded in archive database
Archive Device
Volume 1
2a - Specified archive entry restored

from archive media to restored database
2b - External application accesses
restored logs
External Application:
Display Services
DataDirect
User API
OCS Trend Display
Volume n
Figure 27. Archive and Restore
3BUF 000 987 R1
61
Archiving can be scheduled to occur periodically (timed), or you can execute a

manual archive on demand. Archive can also occur after an event such as the end of
a batch process.
When a timed or manual archive is requested, runtime logs are copied from the
runtime History database to an archive media. The runtime history database is
where on-going (current) storage of history data occurs.
In addition to this, a corresponding archive entry is recorded in the archive database
on both the History server and the archive media. The archive entry indicates the
volume ID, archive time, number of logs in the entry, archive group, and other
related information which is used when you want to restore archived logs.

You can configure the History database during the system engineering phase of a
project, or during runtime.
Generally, the History database is configured in part using the History Builder, and
then the majority of History configuration is finished using the dbConfig utility.
This utility processes text files, and is very efficient for creating large
configurations.
Display Services
Display Services supports building and viewing dynamic real-time and historical
displays on up to 32 simultaneous local and remote display clients connected to a
display server. Information can be collected from multiple sources and displayed
within the same display. Data entry and interactive query capabilities are built into
the package. This helps you create solutions that greatly simplify exploration of
information.
The Enterprise Historian architecture supports access to data not only from the
Enterprise Historian environment, but also to data from other sources via data
provider connections to the Display Services server.
This architecture provides a cost-effective graphics building and monitoring
capability throughout your facility, Figure 28. The user interface environment can
be distributed throughout a facility on a variety of platforms to provide process and
62
3BUF 000 987 R1
Display Services
production information. Supported platforms are PCs with Windows 2000 or

Windows NT, and X-windows.
Remote users
Corporate network users
Corporate WAN
Local
users
Local
users
Local Plant
Networks
Local Plant
Networks
Advant
Enterprise
Historian
HP-UX or NT
Advant Enterprise
Historian
HP-UX or NT
Control
Networks
Control
Networks
Figure 28. Display Services Architecture
3BUF 000 987 R1
63
Display Services
The displays you build with Display Services provide a user interface into your
process and production information, with access to other data sources through open
standard SQL or ODBC. An example is shown in Figure 29. Information can be
collected from multiple sources and displayed in the same display. Displays can be
used for:
Process monitoring
Overall plant status or process cross-sections
Downtime analysis, downtime statistics accumulation
Quality monitoring
Executive information
Manual data entry and interactive query capabilities are built in. This helps you
create effective display solutions that simplify an end users search for
information.You can view information from one or more process automation,
process support, or production management systems within a mill/plant or corporate
network.
Display Services follows Microsoft Windows standards and can be configured to
provide the look-and-feel of the operator console workplace or a plant information
terminal. All functions are mouse controlled. Runtime users need only basic
operator skills.
The displays are primarily for process monitoring, and are not intended to replace
the operator workstation. However, Display Services does support the following
control capability:
modifying and adding log entries in an existing a numeric log.
writing to process objects in ABB control systems.
The display client can be structured to launch predefined external applications (local
or remote) which could be used to interact with the control network using the User
API or other system services such as updating a process parameter or scheduling a
report.
64
3BUF 000 987 R1
Building Displays
Figure 29. Display Services, Collage Display Example
Building Displays
The Display Services - Display Builder function lets you build displays on your PC
and make them available for client users. Displays can also be built off-line when
using a Windows 2000 server. Figure 30 illustrates the windows usability features
such as:
Tree navigation for display hierarchy
Embedded help facility
3BUF 000 987 R1
65
Building Displays
Menus
Multiple Document Interface / Single Document Interface
Scaled displays, true type fonts, and full color palette support
Authority
Active X Control support
Figure 30. Display Services, Display Builder on NT

Displays are made up of static and dynamic display elements, Figure 31. Dynamic
display elements access data via the display server. Dynamic display elements can
be updated on an individual, periodic, configurable rate, demand, or based on the
update of another display element. Foreground and background colors are selected
from a user defined and controlled palette. You can use the full PC font and color
palettes.
66
3BUF 000 987 R1
Building Displays
The display elements can act independently or interact with one another. Attributes
of display elements are individually controllable and create a standardized look and
feel to graphics. Elements can be conveniently arranged on graphic displays (e.g.,
grouping, alignment, overlapping).
Figure 31. Display Services Graphical Display Example
3BUF 000 987 R1
67
Building Displays
Display Elements
The standard display elements include:
Display background (Blank, Colors)
Static elements from the tool bar: line, shape, text elements, and bitmaps
Dynamic display elements:
Value display - numeric, text, matrix, list, combo box
Bar charts - single and multi-bar (up to 35 bars), histogram, pareto
Softkey connection for display linking
Edit - numeric, text, list
Gauge, pie chart
Timer
X/Y Plot
Push buttons for display control, pop-up information dialogs or navigation
You can create your own (user) display elements from the standard elements. User
elements can be encrypted to protect them from modification, or add security to
proprietary logic. User built display elements can be saved as custom elements for
use on other displays. Display Services also provide a display element comment
property which can be applied to each element.
You can Drag-and-Drop or Copy-and-Paste elements. In the Builder, common
properties can be changed across selected elements simultaneously. You can also
use bitmaps as display elements. This lets you import graphics from over 40
different formats such as .eps, .tif, and so on.
68
3BUF 000 987 R1
Runtime Displays
Runtime Displays
Display Services supports run-time display functions including manual data entry,
and control dialogs. These displays are stored, controlled and edited at the server
causing minimal impact at the client node. The same displays are used for each
client type (PC, X-window, or Web) eliminating operator confusion. Some specific
runtime display features include: support for dialogs, user-to-user instant
messaging, unit arrays, and text file access.
Active X Support
Display Services gives you Active X support for Windows 2000 and Windows NT.
This provides the following benefits:
Public access to extensive libraries
Eliminates the need for components to be developed internally
Access to Microsoft COM through Active X controls
You can create highly customized displays with mixed native display elements and
Active X components.
The Display IE component supports access to displays as ActiveX controls. This
lets you embed the display in a web page, or within a custom Visual Basic
application. Using the display as an ActiveX control also lets you use the display
from Operate IT either as a standalone web page, or embedded in a graphic.
3BUF 000 987 R1
69
Runtime Displays
History Displays
Display Services can gather and display information from numeric and message
logs in History Services, Figure 32. In addition to this you can access information
from Production Data Logs (PDLs).
Figure 32. Trend Display with Data Applied to an Excel Spreadsheet Example
Display Services can access historical data from other systems which are seen
through database views created in the Enterprise Historian environment. Using data
entry display elements and SQL, you can create ad hoc views of historical data.
70
3BUF 000 987 R1
Runtime Displays
Figure 33. Display Services Tiled Display Showing X/Y Trend Plot Examples
The Display Services trend display element offers:
Up to 6 traces per trend window (includes trace with bar)
Individual data sources for each of the six trends
Zoom, scroll, and operator station-like ruler functions
User definable time scale format
NoData/BadData drawn in user defined colors
History access
SQL access
X/Y plot (gauging system, profile plots)
Note that a separate standalone web-based trend package called Desktop Trends is
also available, and is described in Desktop Trends on page 80.
3BUF 000 987 R1
71
Display Services Client-Server Architecture

Display Server
The Display Server is a collection of services for display call-up, management, and
data access. This server is installed on the Windows 2000 platform.
The Service Provider manages licensing, user authority, and user preferences. In
addition, the Service Provider supports the interface between the data access
services (described below) and Display Clients.
Data access services (also referred to as data providers) let you connect your
displays to different types of data sources. For this software release, the following
data providers are supported:
History Log Manager (ADSdpLOG) lets you access historical process data
from the Enterprise Historian.
OPC (ADSdpOPC) lets you access OPC data from OPC servers.
Microsoft ActiveX Data Object (ADSdpADO) lets you access data in thirdparty databases on a specified host (defaults to local host).
DCS Object (ADSdpDCS) lets you access real-time process data from a
specified Advant OCS node (defaults to local host).
Synchronous Oracle access on HP-UX (ADSdpORA) or Asynchronous Oracle

access on HP-UX (ADSdpDYN).
The Display Data Provider is a service that manages display generation when a
request for display is issued.
72
3BUF 000 987 R1
Display Client
The Display Client provides the graphical user interface for display building and
viewing, and for administration of Display Services. You can connect up to 32
display clients (MDI plus SDI) and 32 DataDirect clients to a display server.
You can also configure an external application such as Visual Basic or Internet
Explorer to launch the Display Client as an ActiveX control.
Displays viewed through any client are the same, because the common Display
Definition files are stored and managed by the service provider on a server. This
common view, provided by Display Services, greatly facilitates remote process and
application support and can provide production management information to process
operators that they would not have otherwise.
Data access by client applications such as Display Services, DataDirect, and

Produce IT Batch, are supported by a service provider and data providers installed
on the Enterprise Historian server. Data providers are installed and configured
according the options you select when you install the Display Server software.
The default data providers will support most data access applications; however,
certain applications require you to add a new data provider, or modify an existing
data provider.
3BUF 000 987 R1
73
How the Service Provider - Data Provider Architecture Works
Display clients connect to a service provider specified at log-in. The display client
can use all data providers connected to the service provider. This includes data
providers installed on the local display server, as well as data providers installed on
remote servers, Figure 34.
By default, only local data providers are connected to the service provider. In this
case the client can only access data from the display server it is connected to (the
local display server). This functionality is illustrated by Node #1 in Figure 34.
As an option, you can configure data providers on remote nodes and connect them
to the local service provider. This lets you combine data from multiple sources
(nodes) on the same screen. This functionality is illustrated by Node #2 in
Figure 34.
Display Services
PC CLIENT
Display Services
X Windows CLIENT
Node #1
Local Display Server
Node #2
Remote Display Server
Service
Provider
ORACLE1 HISTORY
ABB OCS
Real-time Data
ORACLE
ABB OCS
Real-time Data
Data Providers
Figure 34. Service Provider - Data Provider Architecture
74
3BUF 000 987 R1
Additional Display Services Capabilities
Printing - Display Services supports standard PC Windows print-screen functions

to capture display screens and send to a printer or to paste into a document.
Display Services also lets you print the contents of List, Combobox, and Edit
display elements from both the PC and X-clients. This is a useful feature for
printing reports.
User Preferences - This feature is similar to other desktop preferences. It lets users
custom configure their work environment to fit their individual needs by:
Disabling features
Establishing shortcuts
Color choices, and so on.
Security - Display Services offer the following security:
User Log-in
Read/Write access to information in Enterprise Historian, the ABB OCS

database and other systems
Ability to disable the Display Builder function to prevent unauthorized display

creation and modification
Ability to hide displays
Display Services places a minimal load and memory requirements on the Enterprise
Historian server for the client software functions, and so is a low risk to information
management workstation operation.
3BUF 000 987 R1
75
DataDirect
DataDirect
DataDirect is an add-in program for Microsoft Excel 97 or Office 2000 on Windows
NT and Windows 2000 workstations, Figure 35. These add-in tools facilitate data
access from Enterprise Historian applications, ABB OCS applications, as well as
Oracle and OPC data sources. By installing the DataDirect option on PC clients, you
have easy access to process data, historical (numeric and message) data, MOD 300
Unit array data, and SQL data via Microsoft Excel.
DataDirect lets you generate ad-hoc data queries via dialogs for ad hoc queries, or
use a series of function calls in Excel spreadsheets to create ad hoc, hourly, shift and
daily reports. With the proper authority you can update process values, and
add/modify entries in lab data logs.
DataDirect Menu Add-ins
DataDirect Tool Bar Add-Ins
Figure 35. Example, DataDirect Dialog to Query Process Values from Excel Spreadsheet
Specifically, DataDirect supports access to:
76
process values from ABB control network.
numeric-based historical data collected and maintained by History Services.
alarm and event messages stored in historical message logs.
TCL arrays (MOD 300 software userss Unit Arrays).
ad-hoc SQL queries without the use of SQL*NET or ODBC drivers.
3BUF 000 987 R1
DataDirect
Production management data or process tracking information stored in PDL

records by Produce IT Batch, Batch 300, TCL, and Profile Historian
applications. PDL is supported by ad-hoc access only. This functionality is not
supported by function calls.
Dialogs for Ad-hoc Data Retrieval/Data Entry
Interactive dialogs such as the one shown in Figure 36 let you generate ad-hoc
queries for process and historical data. Some dialogs also support data update
functions. User authority must be properly configured to support updates.
Figure 36. Example Dialog for Ad-hoc Data Query
3BUF 000 987 R1
77
DataDirect
Function Calls for Building Reports in Microsoft Excel
The DataDirect functions let you build and execute reports via Microsoft Excel
worksheets, Figure 37. The functions provide the same data retrieval capabilities as
the dialogs, except that the functions can be re-executed by running the spreadsheet.
The results can be saved, archived, printed and then rerun.
Figure 37. Example, DataDirect Function in an Excel Spreadsheet
78
3BUF 000 987 R1
DataDirect
Using DataDirect Functions in Macros (VBA)
The DataDirect functions can be embedded in VBA macros, as an alternative to

inserting them directly in an Excel spreadsheet. By embedding the functions in the
macros, they are not automatically executed when the spreadsheet is opened. This
gives you the capability to archive reports. In addition, these reports can be
distributed to Excel users that do not have DataDirect.
Requirements
A Display Services (Version 3.0 or later) display server must be available for a
DataDirect client. A client license for each concurrent DataDirect client is needed.
The PC running the DataDirect client software needs to have Microsoft Office 97
Excel with Service Release 1 or later. The client platform may be Windows NT or
Windows 2000. The client PC does NOT require ODBC or SQL*Net. This makes
installation and maintenance of a PC with DataDirect very simple.
DataDirect clients can be distributed throughout the plant network topology (see
Figure 28). They may reside on PCs directly on the control network, the local plant
network, on a corporate wide-area network or may remotely dial-in to the network.
The Display Services server supports a concurrent licensing scheme for clients and
an authority model for user access.
3BUF 000 987 R1
79
Desktop Trends
Desktop Trends
This standalone trend package lets you view trend and associated data in a web
browser. Three presentation formats are provided:
The Tag Ticker shows the current value for a scrolling list of configured
points, similar to a stock market ticker, Figure 38. It is an ActiveX control
displayed within Internet Explorer. Colors can be used to show when a value is
outside of its limits, has bad data quality and a number of other conditions.
Figure 38. Example, Trend Ticker
The Tag Browser lets you structure points in an easy to access manner, browse
through these and see the current value associated with it. Tags can be
organized into groups and subgroups to match the layout of the facility (i.e.
groups by unit). The presentation and navigation resembles that of Windows
Explorer, Figure 39.
Figure 39. Example, Tag Explorer
80
3BUF 000 987 R1
Desktop Trends
The Trend Display, Figure 40, can be launched from the tag ticker or the
browser. In addition to common trending functionality (scrolling, ruler, zoom,
filters and time offsets) a unique zooming feature called Active Zoom is
available. This lets you zoom into a section of the trend while maintaining the
overall scope. Limits can be defined for each trace and when enabled, the color
of the trace can change as it crosses a limit or reference value.
Figure 40. Example, Trend Display

Tags can be drag-and-dropped into the trend from either the tag ticker, the tag
browser or a Microsoft Office application like Excel. Since each of the elements are
ActiveX controls and are delivered hosted in html, navigation can be done through
standard web access mechanisms, using the favorites folder and the forward and
back arrows. The elements can also be embedded in custom displays from
Enterprise Historian or Operate IT.
3BUF 000 987 R1
81
Audit Trail
Audit Trail
The Inform IT Enterprise Historian Audit Trail supports event logging for
production management applications such as Produce IT Electronic Batch Record
(EBR). The Audit Trail also records log activation/deactivation events for History
Services.
The Audit Trail is a client/server application. The server side supports storage of
event messages in an Audit Trail Message Log configured in Enterprise Historian
History Services. The client side provides an API that lets remote client applications
such as Produce IT EBR store data in the Audit Trail message log. The client may
store events and data to message logs on multiple servers at the same time. The API
application may be installed on a remote PC client, or locally with the Enterprise
Historian server. The batch application (EBR) must reside on the same PC as the
API. This architecture is illustrated in Figure 41.
EBR
Message API
Configuration
COM
History Client
Message API
Audit Trail Log
Audit Trail Log
Audit Trail Log
History Server
History Server
History Server
Figure 41. Audit Trail Architecture

Messages and events generated by the source application (EBR) are routed via the
Message API to an Audit Trail message log configured in History Services. The
source application sends messages to the API via a COM interface. The Message
API stores the event messages locally until a configured number of messages have
been generated, or a specified amount of time has elapsed. When one or both of
these occur, the messages are sent to the specified History servers. The messages
can be read via the DataDirect. An example is shown in Figure 42.
82
3BUF 000 987 R1
Audit Trail
Figure 42. Example Audit Trail Message Read via DataDirect
3BUF 000 987 R1
83
OLE DB Data Access
OLE DB Data Access

OLE DB Data Access exposes the Enterprise Historian data by mapping Enterprise
Historian data types to OLE DB data types. OLE DB Data Access has a virtual
database table that supports access to Enterprise Historian data. COM-compliant
applications such as Crystal Reports can submit SQL queries toward the virtual
table. An OLE DB data provider parses queries submitted by the client application,
and returns the requested data to the client.
This release of OLE DB Data Access supports access to numeric log data collected
via History Services for Windows 2000.
OLE DB Data Access supports data access for Crystal Reports, Microsoft Excel,
and SQL*Plus. Microsoft Excel requires an ODBC driver. Both OLE DB Data
Access and the client application must be installed on the Enterprise Historian
Consolidate or Collect (server) node. The basic architecture for these client
applications is illustrated in Figure 43.
Access to data via ODBC and/or SQL is also supported through the relational data
model provided by OLE DB Data Access. This supports access to process data
stored in the Enterprise Historian by any application that can read data via ODBC.
84
3BUF 000 987 R1
OLE DB Data Access
Client Applications
Crystal Reports
Qurydemo
DataDirect
Display Services
C++
Microsoft Excel - without
DataDirect Add-ins
SQL*Plus
OLE DB Data Access

EHProvider
ODBC
History
Database
Instance
(Adva)
History Services
Enterprise
Historian
Database
Figure 43. OLE DB Data Access Architecture
3BUF 000 987 R1
85

Insights
Enterprise Historian integrates with and includes one client license for Pavilions
Insights software. Additional seats may be purchased as optional software.
This package provides intelligent analysis of historical data through neural network
modeling. This lets you perform what-if experiments off-line, so as not to affect the
running process. Insights includes a fully integrated wizard for data extraction from
History Services. This easy-to-use interface provides simple data extraction with a
quick validation mechanism that displays data quality before the data is extracted.
Pavilion Technologies Insights software lets you intelligently analyze large volumes
of historical process data with tools for cleaning and preprocessing the historical
data. It quickly builds and trains accurate process models.
Insights also runs complete off-line diagnostic tests on the process without risk.
Insights performs statistical analysis from basic to the most advanced levels. Key
variables are identified, and hidden interactions between these variables are
uncovered. Insights ranks the effect of process inputs on outputs and performs
valuable what-if scenarios that show how to improve operational efficiency, yield,
and quality control.
Property Predictor
Pavilion Technologies Property Predictor Solution is available as an add-on option
to Enterprise Historian. Property Predictor supports development and deployment of
linear and non-linear Virtual OnLine Analyzer models. Property Predictor
provides tools for configuration of a robust runtime implementation, and
deployment of an on-line Soft Sensor application.
Property Predictor is licensed as an option to Enterprise Historian. The first instance
contains licenses for the base and one model. Subsequent licenses are for additional
models. Note that a single model will often have more than one output prediction.
86
3BUF 000 987 R1
Report Services
Report Services
Report Services provides a complete interface for scheduling, viewing, and
archiving reports created with either Crystal Reports or Microsoft Excel. Report
Services is installed as part of the Enterprise Historian Consolidate or Collect
software bundle. Report Services consists of a report server and report scheduler
that let you schedule and view reports built with an external report building
application.
The report server must be integrated with a report builder (Crystal Reports or
DataDirect). The report builder must have access to the data in the Enterprise
Historian. For DataDirect this is supported by the functions supplied with
DataDirect. For Crystal reports, OLE DB or ODBC may be used to access the data.
This is described in OLE DB Data Access on page 84. Finished reports can be saved
to disk, be e-mailed, or saved to a report log in History Services.
The basic architecture is illustrated in Figure 44. The report scheduler may be
installed locally, or be installed on a remote data access client.
Report Building
This release of Report Services supports three report builder options:
InformIT DataDirect - DataDirect is an add-in program for Microsoft Excel.

DataDirect lets you integrate into a Microsoft Excel spreadsheet realtime and
historical data from Enterprise Historian applications, Advant OCS
applications, as well as other SQL data sources.
Crystal Reports - This is a third-party report builder package. For this release,
Crystal Reports can access historical data from the Enterprise Historian.
Microsoft Excel - You can use Microsoft Excel independent of DataDirect. For
this release, Excel can access historical data from the Enterprise Historian.
The designated report builder package must be installed on the Enterprise Historian
server with the report scheduling server. You can use remote report builder clients to
build the report files; however, the files must be stored locally, and the report builder
must also reside locally to support scheduling and execution via Report Services.
3BUF 000 987 R1
87
Report Building
Report Scheduler
Remote Client
To External
Email Recipients
5
Outlook
Express
Report Output:
- Email
- Export to Files
- Save to History
Report
Instance Files
Report Scheduler
Local Client
Report Execution Command to

Report Builder
Report Server
Report Builder
Application
1
Report Files Created With

Report Builder and Stored on
Enterprise Historian
Data Access
Application
Report Scheduling
& Output Specifications
Enterprise Historian on Windows 2000
Data Access for Reports

Realtime Data from ABB Control Systems
History Data from Enterprise Historian History Services
Third Party Data from OPC Data Sources
Figure 44. Report Services Architecture(1)

(1) When using DataDirect as the Report Builder, you can access both realtime and historical data, as well as data from
OPC data sources. For this release of Enterprise Historian, Crystal Reports and Excel without DataDirect plug-ins
can only access historical numeric log data.
88
3BUF 000 987 R1
Report Scheduling
Report Scheduling
The report scheduler is a client application to the report server. The report scheduler
may be local to the server, or it may be installed on a remote PC client.
The report scheduler lets you access a report definition file via the report server, and
specify scheduling and output instructions for running the report. You can schedule
reports to run immediately, one time in the future, or cyclically.
You can create a scheduling specification as a template, rather than apply the
scheduling specification directly to a report file. The template lets you specify a
delay interval to delay the execution of the report.
Report Execution and Data Access

The scheduling and output instructions are routed via the report server to the report
builder which executes the report. The report builder retrieves the required data
from any of the following data sources:
real-time process data from ABB control systems
historical process data from Enterprise Historian History Services
data from a third-party database on specified host
real-time data from either OPC\DA 1.0 & 2.0 data access server
The method for data access depends on the report building application being used:
Data access for DataDirect is via Inform IT Display Services.
For Microsoft without DataDirect and for Crystal Reports, data access is via
OLE DB Data Access. This is an optional component for Enterprise Historian
Consolidate or Collect, and must be installed with the report server when using
Crystal Reports or Excel without DataDirect.
The report builder outputs the report instance according to the instructions specified
via the report scheduler. Reports can be emailed via Outlook Express, saved to a
report log in History Services, or exported to a file on the report server. Reports can
also be printed via any printer that is accessible to the Enterprise Historian.
3BUF 000 987 R1
89
Managing Report Instances
Managing Report Instances

Report instances are maintained on the server according to configurable user
preferences. You can specify whether to have each new instance of a report
overwrite the previous instance, or to maintain a fixed number of report instances.
You can also specify how long report instances are maintained until they are
discarded.
The report scheduler also lets you run, pause/resume, stop/restart, and remove report
instances stored on the report server.
User Interface
The main window for the report scheduler is shown in Figure 45. Access to this
window is password protected.
The tabbed sections of this window let you:
90
schedule and specify output options for any reports stored on the server
view the status of all reports run or scheduled by the report scheduler
run, pause, stop, restart, remove and view actions against report instances
access saved reports either from files, or reports saved in report logs
set user preferences
3BUF 000 987 R1
User Interface
Figure 45. Report Scheduler Main Window
3BUF 000 987 R1
91
User API
User API
User Application Programmers Interface (API) lets your 3GL- application
programs interact with objects in the Advant OCS. A C-licence and C-development
software are included with Enterprise Historian System Services.
User API is the basis for software and application portability between different
Advant Station platforms and system generations. New applications developed on
the platform have the same access to system functions as system applications, thus
giving full but controlled access to system services.
The User API is split into three main functional parts to build applications and
distribute data:
Object Access Services: for direct interaction with the system objects. The
Object Access Services is the 3-GL Programming Interface to objects within
the system.
The Object Access Services provide:
commands: execute operations on objects
subscriptions: read data from objects on demand or cyclically
Basic Support Services: The Programming Interface to the system. This

covers, for example the 3-GL interface, system messages and data & time
functionality.
Microsoft Visual Studio V6.0 or an equivalent C++ compiler is required to

compile/write User API applications.
Production Data Log (for Use with Produce IT Batch)

Production Data Log (PDL) software is an option for History Services. A PDL is a
History log that stores production data such as batch start/end times, batch variables,
and event/messages data for presentation in batch reports. The PDL also stores
Produce IT Batch recipes.
Access to PDL data is via SQL and DataDirect. A number of database views have
been created specifically for reading PDL data via SQL statements. Archiving of
PDLs can be done either manually or automatically. PDL archives will also include
the associated numeric logs.
92
3BUF 000 987 R1
Section 2 Basic Software Components Event Log (For systems with Master data connection only)
Event Log (For systems with Master data connection

only)
The Event Log fits into the Advant OCS concept according to Figure 46 which
shows a configuration with the Event Log installed in an Enterprise Historian server
on a Control Network. Distributed access is available through SQL*NET and
SQL*Plus. The Event Log can be archived automatically on a time basis or
manually.
In the Advant OCS concept, the Event Log should be considered as a collection
facility for event data. It acts in a way that resembles TTD (Time Tagged Data)
logging from MasterPiece and Advant Controllers; however, in this case it collects
from event lists stored on the Realtime Accelerator (RTA) board in an Enterprise
Historian Collect server.
Communication
Event Log
Options
Options
User API
=
The additions to
System Services
for Basic Unit
Event Handling
=
Enterprise Historian
System Services
System Functions
User Interface
Database
Operating System
Advant Station 500 Series Hardware
Control or Plant Network
Figure 46. Event Log Overview

Data on events that take place in Controllers and in the Enterprise Historian server
are stored in event lists in Enterprise Historian server. The purpose of the Event Log
function is to copy records of event data from event lists to event logs.
Data on single events can only be sent within a control- or plant network whereas
the secondary logging (copying data from OS, MasterViews and Enterprise
Historian nodes) can take place on both plant- and control networks. Data stored in
Event Log are accessible by various means, for example via SQL or the Event Log
Presentation Display.
3BUF 000 987 R1
93
Event Log (For systems with Master data connection only) Section 2 Basic Software Components
Event Log Configuration
Event Logs are configured as part of Message Log configuration in History

Services.
Event Log Communication
Primary logging of data on process events can take place within control- and plant
networks. The event lists are located in the RTA-board of Enterprise Historian and
Operate IT nodes, or in MasterView. Typically, the event lists have room for 1010
records of event data (33 pages with 30 records each, plus 20 extra). If the primary
log is full, the oldest record is overwritten when a new event is logged.
The Event Log communication function copies data from event lists to Event Logs.
Figure 47 shows how event data is sent and received within the Event Log option.
Advant Station 500 Enterprise Historian

Alarm and event
distribution
Event Log
RTA
MasterView
OS
IMS 500
Advant Controller
Event List
Event logs
Primary logging
Secondary logging
Alternative storage
Figure 47. Event Log - Function overview

The event log communication function sends a request for a primary log. If all
records are not retrieved at once, another request is sent when all received records
94
3BUF 000 987 R1
Section 2 Basic Software Components Event Log (For systems with Master data connection only)
are stored in the Event Log. This procedure continues until the primary log
information is collected.
The secondary logging refers to the collection of primary log data by the event log.
This is governed entirely by the event log configuration. Event logs can be activated
individually via the configuration window, in History Services, or on a log set basis
as described in the History Services Users Guide.
Accessing Event Messages From the Event Log
All event data records collected from a primary log are stored in tables in a
relational data base. A view called EV_MSG can be used to access event data using
SQL queries. You can access this view via the Database Access window, as well as
other Enterprise Historian applications such as Display Services, DataDirect, and
3rd party packages that are ODBC compliant.
3BUF 000 987 R1
95
PLC Interface
PLC Interface
The PLC Interface is an option to the Enterprise Historian Connect software bundle
which runs on the Windows 2000 workstation. This interface lets Enterprise
Historian History Services, Display Services, and DataDirect access data from
Programmable Logic Controllers (PLCs) and other automation systems. It also
supports memory-based and disk-based (pseudo) I/O Devices for development and
testing.
Communicating with External I/O Devices

The PLC-OPC Server lets your computer communicate with control or monitoring
I/O Devices that have a communication port or data highway. This includes PLCs,
loop controllers, bar code readers, scientific analyzers, remote terminal units, and
distributed control systems. The PLC-OPC Server supports communication via your
own computers COM port, an installed serial board, or a proprietary PLC Interface
board, Figure 48.
PLC-OPC Server OPC Interface
PLC-OPC Server I/O Database
Device Drivers
RS 232
I/O
Device
Proprietary Hardware
RS 485
I/O
Device
I/O
Device
Figure 48. Configuring the Communications Between the PLC-OPC Server and I/O Devices
96
3BUF 000 987 R1
PLC Interface
The PLC Interface lets you configure the process I/O points on the automation
systems to be accessible via OPC. The OPC data can then be used by Enterprise
Historian in the following ways:
as a local history buffer to forward history data to a Consolidate server.
for viewing via Display Services and DataDirect.
An example application is illustrated in Figure 49.

History Services
on Windows 2000
PLC Interface
PLC-OPC Server
PLC
NAME
REGISTERS
$HSTC101,VALUE-1-o
Loop1_PV
$HSTC102,VALUE-1-o
R101
Device
Driver
OPC
Loop2_PV
R102
Loopn_PV
R10n
$HSTC10n,VALUE-1-o
Figure 49. Example, PLC Interface Application

The extensive set of device drivers in the PLC Interface supports data access for
wide variety of third-party automation systems. This includes Siemens S5 and S7,
MODBUS, and Allen Bradley PLC2, PLC3, and PLC5. The PLC Interface also
supports data access to other OPC servers.
The complete list of supported interfaces is provided in Appendix B, Supported
Interfaces.
3BUF 000 987 R1
97
OPC Connectivity
The interface must be set up on two levels:

Use the PLC Interface to Configure the PLC-OPC Server
The PLC Interface lets you specify I/O servers, boards, ports, and variable tags for
the PLC-OPC server. You can also use the PLC Interface to map I/O device registers
to variable tags in the PLC-OPC server. This lets you group registers more
efficiently to increase performance.
Set Up OPC Access for the Enterprise Historian Client Application
History Services, Display Services, and DataDirect are clients to the PLC-OPC
server. These clients must be configured to support OPC data access.
OPC Connectivity
Enterprise Historian provides an OPC client connection that can be used to collect
data from OPC servers such as the PLC Interface, Symphony, Freelance, and
SattLine. The client supports OPC data access 1.0a and 2.0 servers. For details refer
to Appendix A, Control Network Connections.
Advant OCS Control Network Connections

Advant OCS Network Connection supports communication between Enterprise
Historian applications, and other applications in the Advant OCS. Communication
is via the Distributed Control Network (DCN) or MasterBus 300 control network
(MB300). The communication software provides a bi-directional link between the
Real-time Accelerator Board (RTA), located in the workstation where the Enterprise
Historian software runs, and the control network.
For systems connecting to the MOD 300 DCN, the RTA software
bundle with System Services is based on version 14r5 software.
This means that Enterprise Historian 3.2 can only run with other
MOD 300 nodes at this version.
If the Advant OCS communication is excluded, the RTA board is not required. The
node operates in a stand-alone capacity and the following functions will be limited:
98
3BUF 000 987 R1
System Status functionality is limited to Node Status and OMF TCP/IP Status.
Network communication and Overview Status displays (only applicable to
Master), are not included.
Network communication is TCP/IP
For details regarding control network connections, refer to Appendix A, Control

Network Connections.
3BUF 000 987 R1
99
100
3BUF 000 987 R1
Section 3 Hardware/Software Requirements

Hardware Requirements
Hardware for the Enterprise Historian Server
The recommended PCs are HP-Visualize P-class, HP X2000, Compaq EN Series

Deskpro or Compaq AP series 250 minitower, Compaq Workstation WS300,
Compaq Workstation AP550, Compaq Workstation WS6000, or IBM IntelliStation
M Pro, when using the PCI RTA board for Advant OCS.
The following hardware is required to support the basic Enterprise Historian server
software (System Services, Display Services, and web browser):
Intel Pentium CPU, minimum 450 MHz clock frequency.
Primary Memory: 256 Mbytes minimum.
Disk Space: 1.1 GB free space required for installation and optional software.
4Gbytes for PDL and message Log support for Produce IT Batch
500 Mbytes for PDL for Batch 300
plus storage for numeric logs
The PC should have a large screen - at least 19.
SCSI disk recommended
Magnetic Optical Disk for data archive- HP SureStore 5200ex, 5.2 GB per MO
disk, HP SureStore 9100mx, 9 GB per MO disk
If connection to an Advant OCS is required, the PC must have one PCI

expansion slot for the ABB RTA board
Only the PCI Form Factor RTA Board is supported. The following
RTA boards are not supported in Enterprise Historian version 3.2:
3BUF 000 987 R1
PCI RTA board with USB port
The EISA form factor RTA board
DAT tape for system backup
101
Prerequisite Software
Hardware for Desktop and Remote Access Tools
The following hardware is required to support Enterprise Historian desktop tools:
Intel Pentium CPU, minimum 166 MHz clock frequency.
Primary Memory: 96 MB for Windows NT or 128 MB for Windows 2000.
Disk Space: 100 MB free space.
The PC should have a large screen - at least 19.
Windows 95/98 can be used for existing applications (Display client, DataDirect),
but cannot be used for Desktop Trends or Report Scheduling Display clients.
Prerequisite Software
The software in Table 5 must be installed on all server and client PCs, BEFORE you
install the Enterprise Historian software.
Table 5. Prerequisite Software
Software
Microsoft Windows 2000, SP2
Comments
A fresh install of Windows 2000 is recommended.
Microsoft Internet Explorer 5.01 or later

Microsoft Office 97 Excel with Service
Must be installed BEFORE DataDirect.
Release 1, or Microsoft Office 2000 Excel.
Adobe Acrobat Reader 4.05 or later
For reading on-line documentation for Enterprise

Historian products. It can be installed before or after
the Enterprise Historian software.
Report Services 1.0 is compatible with Crystal Reports Professional and Developer
version 7.x or 8.x. Crystal Reports is not provided as part of Enterprise Historian
version 3.2 and must be purchased separately.
The following software is also recommended:
102
HTML Help 1.0 (included in MicroSoft Internet Explorer 4.01)
Software package that provides backup image capability
Remote diagnostic support may be provided using PC Anywhere
3BUF 000 987 R1
Section 4 Ordering Information
Enterprise Historian Products

Enterprise Historian Products
The Enterprise Historian Product suite consists of three different bundling options.
The Enterprise Historian Collect software is a full-featured bundle that is specified
when connecting directly to the OCS. The Connect software bundle provides a
history buffer for store and forward of numeric history data to a Consolidate
software node. In addition, the Connect software includes options for PLC Interface
I/O, and a gateway function for Advant OCS. The Consolidate software bundle is a
full-featured package that takes history data from multiple Collect or Connect
software installations and integrates the data into one server.
Enterprise Historian Collect for Windows 2000 SP-B-EHSNT

When placing an order for the Windows 2000 Server nomenclature, you will receive
the following licenses:
Qty: one (1) license for Enterprise Historian Collect Base Nomenclature, prefix
code SP-B-EHSNT
Qty. one (1) license for Display Services Base Nomenclature, prefix code SPB-EHDSA
Qty. one (1) license for Pavilion Insights Client Base Nomenclature, prefix
code SP-B-EHPCA.
Enterprise Historian is licensed by point count: a point is defined as a value/attribute

that is stored in a numeric history log. For example, measured value and setpoint for
the same tag represent two points to the Enterprise Historian.
The Enterprise Historian Collect product highlights a history engine for
recording/storing historical data and one Pavilion Insights license, a data mining
tool used for process analysis and modeling historical data. The history engine can
collect data from OPC servers, the PLC interface and directly from controllers in an
Advant OCS. When ordering, please specify the maximum point count based on the
number of points that will be recorded into history.
3BUF 000 987 R1
103
Enterprise Historian Consolidate for Windows 2000 - SP-B-EHCNN Section 4 Ordering Information
Enterprise Historian Collect servers are delivered with Display Services (prefix
code SP-B-EHDSA). Display Services provides graphic display capability for
history data and process objects. The Display Services Data Direct client provides
Excel plug-ins for history and process data. The base license contains one (1)
Display Builder for graphic displays, one (1) Data Direct license for Excel plug ins,
one (1) Desktop Tend license and five (5) data providers for data access and display
storage. Included with each Display Services graphic client (MDI or SDI), is a
Desktop Trend display.
When specifying the product nomenclatures, any Options specified must be ordered
at the same point count as specified for the base Historian product.
If your application requires additional graphic display MDI/SDI clients, DataDirect
clients, or Desktop Trend clients, order additional products using the Enterprise
History Display Services Expansion nomenclature SP-E-EHDSA.
CD based documentation and media are included when the nomenclature is ordered.
Paper copies of individual user's guides can be ordered from the Accessories and
Peripherals section of this price book.
For Advant OCS connections, please refer to the hardware section of this price book
for RTA and network, interface ordering information.
Enterprise Historian Consolidate for Windows 2000 - SP-B-EHCNN

This node is used to collect/consolidate history data from one or more Enterprise
Historian Collect or Connect Servers. The Consolidate node collects data via
TCP/IP.
The Consolidate node server is delivered with the same licenses as the Enterprise
Historian Collect for Windows 2000.
Enterprise Historian Connect for Windows 2000 - SP-B-EHATC

The Enterprise Historian Connect software can be applied in different ways.
The Enterprise Historian Connect can be used as store and forward node for
numeric history data. In this configuration, the local history engine collects from
OPC and/or Advant OCS. The data is stored in a local history data base on the
Connect node, and then this data can be forwarded to an Enterprise Historian
Consolidate. The intent of this function is to provide a low cost solution for
104
3BUF 000 987 R1
Display Services Expansion Nomenclature - SP-E-EHDSA
consolidating history data from different sources. This solution also provides local
data buffering which enables maintenance on the Consolidate historian without
loosing any data stored during the maintenance time.
Enterprise Historian Connect includes a PLC interface option used to interface a
variety of PLC types, OCSs and other devices to the Enterprise Historian. When
specified with this option, the Enterprise Historian Connect replaces the
functionality previously provided by Automation Connections. When the PLC
interface option is specified, also specify the Data Forwarding option. This will
enable the PLC data to be stored into a local history buffer that can then be
forwarded to an Enterprise Historian Consolidate. For Connect specify the overall
point count. If there is a need to read data from multiple OPC servers, specify PLC
interface to act as the concentrator.
If history buffering and data forwarding, or PLC interface are not required,
Enterprise Historian Connect with the addition of the User API option, can be used
as a gateway towards Advant Systems with MOD 300 or Master software. For
Enterprise Historian Connect, specify point count based on the number of process
attributes that will be read by the User API. This configuration is a replacement for
the previous product known as Enterprise Historian Select.
The Enterprise Historian Connect has limited capability/licenses compared to the
Enterprise Historian Collect and Consolidate software packages.
There is one (1) DataDirect and one(1) Desktop Trend license included, but a
Display Build license is not included, though it can be added via the Display
Expansion Nomenclature.
There is no Pavilion Insights license included with Connect.
The history engine on Connect does not support archive.
Other options for reports and so on cannot be added to Connect.
Display Services Expansion Nomenclature - SP-E-EHDSA

Order from this expansion nomenclature when adding additional display clients,
data direct clients, trend clients, builders and data providers to Enterprise Server
products. Provide the hardware ID of the Enterprise Historian server when ordering
additional client licenses.
3BUF 000 987 R1
105
Pavilion Technologies Products
Pavilion Technologies Products

These product components are typically licensed to server hardware ID and client
hardware ID. The server machine executes run-time components of any model for
the associated product component. The client machine is used to build models offline and test model results.
Enterprise Historian Pavilion Insights Client: SP-B-EHPCA

This is client software for data mining, data analysis and model building using
neural network technology. There is no server component license required for this
product component. One (1) Pavilion Insights license is included with each
Enterprise Historian Collect or Consolidate Server ordered. For an additional client
seat of Insights, order this item. Each nomenclature ordered will deliver one (1)
license for Insights.This item is licensed to a specific hardware ID.
There is no expansion nomenclature for this item because each additional client will
be licensed to different client hardware. If multiple clients are needed, order
multiple instances of this nomenclature.
Pavilion Property Predictor: Client (SP-B-EHPCB), and Server (EH-B-EHSPP,

SP-E-EHSPP)
This is client-server software for applying property predictions for virtual analyzers
and maintenance management of critical sensors. Property Predictor is an extension
of the base Insights functionality. When ordering the Property Predictor product,
order both the server and client nomenclatures. Two nomenclatures are required
because it is possible to run the server and client software on different machines.
You must provide the hardware ID for each nomenclature for proper licensing.
The Property Predictor Server expansion nomenclature is used to include additional
property prediction models to the same server. Again, when ordering an expansion,
the hardware ID of the server must be supplied.
106
3BUF 000 987 R1
Section 5 Capacity and Performance

History Services
Overall Capacity
History Services can manage up to 50,000 logs (combination of primary and
secondary) on one Enterprise Historian node.
Maximum Number of Primary Logs

The maximum number of primary logs is based on the type of data source as
described in Table 6.
Table 6. Maximum Number of Channels
Function/Data Source
Channels (Data Sources Collected From)
Collecting from TTDs (Master)
10,000
Collecting directly from process objects
For systems with MOD 300 software: 6,000

For systems with Master software: 2000
Collecting from a combination of process

objects and TTDs
Up to 10,000 logs total without exceeding the

limit for process objects described above
OPC Server
30,000
Collecting from Enterprise Historian Collect 50,000

or Connect node
3BUF 000 987 R1
107
Maximum Number of Entries Per Log
Maximum Number of Entries Per Log

Log capacity and number of logs determine tablespace and disk requirements. The
limits indicated in Table 7 should be sufficient for most applications.
Table 7. Entries Per Log
Log Type
Entries
File-based 4-byte
32,000,000
File-based 24-byte
5,000,000
Oracle-based and SPC
50,000
Message (this includes MODMSGLOG,

250,000
EVMSGLOG, REVMSGLOG, and EAMSGLOG)
Restored Logs
Limit based on available restored tablespace
OPC message Log for Audit Trail and Produce

IT Batch
3,000,000
History Objects Miscellaneous Capacities

Table 8 describes size limitations for composite logs, log sets, and archive groups.
Table 8. History Object Miscellaneous Capacities
Object
Size
Maximum number of Primary and Secondary Logs in a Composite Log 16
108
Maximum number of Logs in a Log Set
10,000
Maximum number of Logs in an Archive Group
10,000
3BUF 000 987 R1
History Collection Maximum Sample Rate
History Collection Maximum Sample Rate

History Services can collect from different types of data sources, and limitations on
sample rate are imposed based on the type of data source. These limitations are
described in Table 9.
Table 9. Maximum Sample Rates
Rate(1)
Collection Type
TTDs
25,000 points/minute (6.2 TTD request/second) for the

maximum number of TTDs - Table 6.
Advant OCS w/ MOD 300 Software 15,000 samples from 6000 objects.
Direct Collection from Process Objects
Advant OCS w/ Master Software 5000 samples from 2000 objects.
Direct Collection from Process Objects
OPC Server
30,000 samples/minute
Consolidate Node (via TCP/IP)
60,000 samples per minute
Distribution to a Consolidate Node forwarding History data from node

where it is collected to a Consolidate
node via TCP/IP
The number of samples collected from control network

data sources can be forwarded to the Consolidate
node within the limits defined above.
Batch 300 Storage to PDL
5-10 storages per second
(1) Actual performance is based on the platform where History software runs, and control system topology.
Blocking rate and stagger function must be used to balance CPU

loading.
3BUF 000 987 R1
109
Fastest Sample Rate
Fastest Sample Rate

The fastest sample rate supported for TTDs is 1 second periodic data.
This sample rate is also supported for direct collection from process objects;
however, during periods when system load is high, one-second subscription to local
or remote objects are likely to be interrupted. As a result, NO_DATA entries will be
inserted in the log when these spikes occur. Therefore, the fastest practical sample
rate is based on the History database configuration, and use of History node
resources by History and other applications. Refer to the History Services Release
Notes for further information on frequency of NO_DATA entries.
Disk Requirements Per Log Entry

Disk space requirements for each History value stored are indicated in Table 10.
Table 10. Bytes Required Per Log Entry
Log Type
Bytes Per Entry
Type 2 file based
Type 1 file based
24
Oracle and SPC
110
Message in a message log 250

Message in an event log
250
Restored log entry
100
For example: Disk Space for TYPE1 Log with 1-minute storage interval, and
90-day log period:
1440 samples/day * 90 days = 129,600 samples
129,600 samples * 24 bytes/sample = 3.1 MB per log
110
3BUF 000 987 R1
Disk Space Allocation for Oracle and File-based Logs
Disk Space Allocation for Oracle and File-based Logs

Default Oracle Tablespace
History uses nine Oracle tablespaces. The default tablespace sizes are indicated in
Table 11.
Table 11. Default Oracle Tablespace
Tablespace
Default Size
Inform_HS_RunTime
75 MB
HS_Indexes
40 MB
HS_Archive
5 MB
HS_Restored
50 MB
HS_Reports
10 MB
HS_Config
40 MB
HS_Iconfig
40 MB
HS_PDL
60 MB
HS_IPDL
50 MB
Default Allocation for File-based Storage
A History mount point for file-based logs is automatically created. It allocates 200
MB.
Capacity Based on Default Oracle Tablespaces and File-based Allocation
These default sizes provide space for approximately:
1000 logs
4,000,000 log entries
200,000 restored log entries
30,000 archive entries
3BUF 000 987 R1
111
History Archive
If your system requires greater storage capacity, you can extend the size of the
applicable tablespace(s) and allocate more disk space for file-based logs. Keep track
of the number of runtime logs in your system, the number of potential runtime log
entries, and the number of restore log entries so you can extend the sizes BEFORE
you exceed any of the above limits.
Keep a record of the number of logs you configure in the system. To determine the
potential number of log entries in your system, calculate the sum of the log capacity
attribute values for each numeric log in your system. You can view the number of
restored logs via the Number of Logs field in the Archive Logs window.
History Archive
Supported device: HP SureStore 5200ex Single Magneto Optical Disk. 5.2 GB

per platter (2.6GB/surface) or HP SureStore 9100mx Single Magneto Optical
Disk. 9 GB per platter (4.5GB/surface)
Operation: Disk must be manually removed and turned over to record to second
surface of disk
Usable Storage/Surface: 2.05 or 4.2 GB
Storage per numeric history value stored: 21bytes
Capacity per side: 97 million or 200 million entries (approximate for numeric
logs)
Storage per message: 260 bytes
Capacity per side: 7.8 million or 16 million messages (approximate for

message log)
After volume (one surface) is filled, volume must be changed
manually before buffered archive data exceeds volume capacity.
112
With 2.05 GB) - approximately 24 hours at 60,000 numeric

storages/minute. Deadband compaction can be used to
minimize volume of data stored on-line, and archived.
With 4.2 GB - approximately 48 hours at the same storage

rate.
3BUF 000 987 R1
Event Log (Master)
Event Log (Master)

Maximum log size
250,000 messages
Maximum size of history collection buffer
30,000 messages
RTA Message Buffer
1000 messages
Maximum Number Process Sectioning
16 (1-15, or All)
Display Services
Maximum number of graphic display clients
(MDI/SDI) per server
32
Maximum number of DataDirect clients per server
32
Maximum number of configured values/second from 200/second nominal

Advant OCS objects based on User API
load/subscription to data. Using LastHistoryValue will
minimize this load while providing near-realtime data.
Maximum size of request returned by DataDirect
Functions - 5460 elements/function call

Dialogs:
History - 500 history values/log
SQL - 65,536 records
Maximum rate for writing to process objects
1 value/second
Maximum rate for writing to history logs
5 values/second
3BUF 000 987 R1
113
PLC Interface
PLC Interface
Maximum number of configured I/O points:
10,000
Maximum Throughput
10,000 points/minute
Desktop Trends
Maximum number of trends on a trend display
8 traces
Maximum number of tags per Tag Explorer Group
50 tags
Maximum number of tags per Ticker file
50 tags
Maximum number of concurrent trend controls on one client
Trend display call-up from local Enterprise Historian server

with eight trends
15 seconds or less
Report Services
Maximum number of reports in a report log
2000
Maximum number of report instances in the status window
5000
OLE DB Data Access

Maximum number of values for one query against History
114
300,000
3BUF 000 987 R1
User API
User API
User API can be used to read data from History, or to read/write data to Advant OCS
objects. This section describes User API performance for reading/writing data to
Advant OCS objects.
The User API does not use any disk space. Therefore it is only dependent on
primary memory and CPU power for performance.
The capacity limitations for data retrieval are described for the Do Request
functionality. In general it is recommended to write all applications using Do
Request for the best possible performance and ease of use.
Do Request has the highest performance of the available methods for data retrieval,
except when many objects are read at very fast cyclic intervals (1 or 2 seconds). The
upper limit for the throughput is dependent on the number of attributes read in each
request and the number of objects in each request.
The tests described in this section were performed using an HP Kayak 400 MHz
pentium II with 256MB RAM. These tests were run under lab conditions. Individual
results can vary based on configuration, size, and the complexity of your system.
Figure 50 and Figure 51 show average time to read two attributes per object from
requests with varying numbers of objects. The comparison shows bciDoRequest
is a more efficient method than bciGetAttributes.
For Advant OCS applications that use MOD 300 software - nominal rate is 750
attributes/second.
For Advant OCS applications that use Master software - nominal rate is 550
attributes/second.
Do Request is not recommended when sending execute operations. This is because

operation parameters can not be changed when using Do Request. However, Do
Request can be useful if you want to send identical operation requests (same
parameters all the time) with high frequency. Simulation is one such example.
When you use API execute operations to update objects try to optimize the number
of requests in one call to between 10 and 20 to get the best performance and least
CPU load. For execute operations there is a slight difference when accessing an
Advant Controller or a MasterPiece. The higher performance of the Advant
Controller gives higher throughput.
3BUF 000 987 R1
115
User API
When requesting for 10 or more execute operations at a time the upper limit is
typically 60 to 80 operations per second. This also depends on the Advant
Controllers load.
Figure 52 and Figure 53 show the time to write attributes based on the number of
objects.
For Advant OCS applications that use MOD 300 software, use a nominal rate
of 125 writes/second.
For Advant OCS applications that use Master software, use a nominal rate of
100 writes/second.
Figure 50. Average Time to Read Two Attributes - MOD 300 Results
116
3BUF 000 987 R1
User API
Figure 51. Average Time to Read Two Attributes - Master Results
3BUF 000 987 R1
117
User API
Figure 52. Time to Write Attributes Based on Number of Objects - MOD 300 Results
118
3BUF 000 987 R1
User API
Figure 53. Time to Write Attributes Based on Number of Objects - Master Results
3BUF 000 987 R1
119
User API
120
3BUF 000 987 R1
Appendix A Control Network Connections

The Enterprise Historian can connect to the Advant OCS via Realtime Accelerator
(RTA) board. Connections to the following ABB control systems are also supported:
Symphony/INFI 90 - Harmony/Melody controllers
Freelance
SattLine
OPC connectivity is available through third party operator interface packages, and
control network vendors.
3BUF 000 987 R1
121
Connecting to Symphony/INFI 90
Connecting to Symphony/INFI 90
The Enterprise Historian may collect data from ABB Harmony and Melody
Controllers via an OPC Server, Figure 54. This requires the Harmony OPC
Integration software to be loaded on the Enterprise Historian. OPC add-ons are
required on the Real-Time Data Server (RTDS). The OPC Server is automatically
enabled and available. There is no additional configuration required on the RTDS.
Enterprise Historians OPC client is configured to point to the Symphony/INFI 90
OPC Server using the IP address, the RTDS/OPC Server system name, and Global
Unique I.D. (GUID). Any process objects can be accessed by the Enterprise
Historian via its OPC Client (for example, FIC100.PV for Harmony). Third party
OPC data collected into a Generic OPC Server may also be accessed.
Figure 54. Connectivity to Symphony/INFI 90
122
3BUF 000 987 R1
Connecting to Freelance
Connecting to Freelance
Connectivity to Freelance controllers can be accomplished using the OPC server in
a DigiVis station, Figure 55.
Figure 55. Connectivity to FreeLance
3BUF 000 987 R1
123
Connecting to SattLine
Connecting to SattLine
Connections to SattLine can be accomplished using the OPCMMS.Server version
2.0, Figure 56. The SattLine PROG_ID and ClassID are not included in the
configuration file, but they can be added via a text editor.
Figure 56. Connectivity to SattLine
124
3BUF 000 987 R1
OPC Connectivity
OPC Connectivity
OPC connectivity is available through third party operator interface packages such
as Wonderware, Intellution, and Iconics, Figure 57. OPC connectivity is also
available via third party control network vendors such as Honeywell, Yokogawa,
and Fisher-Rosemount.
Each OPC server will communicate with one or more control networks. A single
server may support multiple control network protocols and hardware interfaces (not
supplied by ABB).
Data values are mapped from the local control network and made available at the
OPC server. From there, the data values can be accessed by OPC client applications
such as Display Services and DataDirect.
Figure 57. OPC Connectivity to Third Party Applications
3BUF 000 987 R1
125
Connecting to the Advant OCS

The Enterprise Historian node may be connected to the Advant OCS network via
the Realtime Accelerator (RTA) board, Figure 58. This connection lets Enterprise
Historian applications talk to ABB Advant Controllers via the:
DCN - for systems with MOD 300 software.

For systems connecting to the MOD 300 DCN, the RTA software
bundle with System Services is based on version 14r5 software.
This means that Enterprise Historian 3.2 can only run with other
MOD 300 nodes at this version.
MB 300/300E - for systems with Master software.
This ensures a high level of availability due to redundant control networks. It

facilitates historical data collection. You configure logs by tag name, History finds
them in the appropriate controller. Any objects that are in the system can be
accessed by the Enterprise Historian (for example, FIC100.MEASURE or
FIC100.VALUE). Master software users can collect from TTDs.
Further, this type of connection lets the Enterprise Historian communication with:
Advant Operator Stations, OperateIT for MOD 300, and AdvaSoft Operator
Workplace for Master.
In Figure 58 the Enterprise Historian server is loaded as a separate station. Data is
collected directly from the DCN (or MB 300/300E) via the RTAB.
Native Trend client in Operator Station can display data from the Enterprise
Historian. Access is via the control network. Data in the Enterprise Historian can
also be displayed on PCs on the plant network.
126
3BUF 000 987 R1
Figure 58. Connectivity to Advant OCS with MOD 300 or Master Software
3BUF 000 987 R1
127
Real Time Accelerator Board (RTA)
Real Time Accelerator Board (RTA)

For connection to the Advant OCS control network (Distributed Control Network or
MasterBus 300), the workstation running Enterprise Historian must be equipped
with a Real-Time Accelerator (RTA) board.
The RTA board is a slave processor board with its own memory and two
communication ports. The RTA board consists of a mother board with a DCN
communication module (PU514 version) or a MB300 communication module
(PU515 version) mounted on it. The on-board software is downloaded to the RTA at
start up of the workstation.
The RTA is installed inside the System Unit on the PCI bus adapter. The
communication connectors are available on the rear bulkhead of the System Unit.
Do not use the RTA with USB Port PU518/519.
Real-Time Accelerator Board
Network Interface Board
MC68040
Figure 59. Real-Time Accelerator Board PU514/515
MOD 300 DCN Control Network Connections

The Distributed Communications Network (DCN) connections are made to the
Real-Time Accelerator Board connectors on the rear of the System Unit.
Channel 1 Channel 2
Real-Time Accelerator
Board Connectors
Figure 60. RTA Connector at Rear of System Unit
128
3BUF 000 987 R1
The DCN physical media is a twin-axial cable or fiber optic cable. The DCN is
connected to the Real-Time Accelerator connectors on the System Unit through the
TC530 or TC532 DCN T-box and a TK513 cable. The TC530 T-Box is connected to
the DCN by a TK510 DCN cable. The TC532 T-Box is connected to the DCN by a
6057C fiber optic DCN cable.
Table 12. Wire DCN Cable Connections
Type
Description
TC530
DCN T-Box for wire DCN communication interface
TK513
Cable assembly T-Box to DCN connector on the System Unit, 3 meters, 15-pos
Socket - 15-pos Pin
TK510
Cable assembly, DCN to T-Box, Standard lengths available: 3 to 30 meters in 3m

increments, and 75 to 300 meters in 75m increments.
TK511
Cable assembly, DCN Extension to cable adapter., Standard lengths available: 3

to 30 meters in 3m increments, and 75 to 1200 meters in 75m increments.
TK512
DCN Cable Adapter, TK511 to TK510
Table 13. Fiber Optic DCN Cable Connections

Type
Description
TC532
DCN T-Box for fiber optic DCN communications interface
TK513
Cable assembly T-Box to DCN connector on the System Unit, 3 meters, 15pos Socket - 15-pos Pin
6057C
Fiber optic DCN cable, standard lengths available:10 to 3220 meters
6059N
Fiber Optic Media Interchange: fiber optic cable to wire DCN cable adapter
3BUF 000 987 R1
129
Channel 2
Channel 1
TK513
DCN Control Network
TC530
TK510
TK511
DCN Control Network

TC530
TK512
Figure 61. Wire DCN Connections
Channel 2
TK513
Channel 1
TC532
DCN Control Network

DCN Control Network
6057C
TC532
AC Power Source
TK510
6057C
6059N
Figure 62. Fiber Optic DCN Connections
130
3BUF 000 987 R1
MasterBus 300 Control Network Connections

The MasterBus 300 control network connections are made to the Real-Time
Accelerator Board connectors on the rear of the System Unit.
Channel 1 Channel 2
Real-Time Accelerator
Board Connectors
Figure 63. Real-Time Accelerator Board Connector at the Rear of the System Unit
The physical media of the MB300 is a thick Ethernet cable. It is connected to the
Real-Time Accelerator connector through the MB300K01 transceiver and a 15-wire
cable. A toolkit is available for the transceiver installation.
The Real Time Accelerator (RTA) board connectors are standard
AUI connectors except for the fixing of the cable. The AUI cable is
fixed to the RTA board with screws. This is why special AUI cables
are needed for the RTA board.
Table 14. MasterBus 300 to RTA Connection Cables

Type
TK526V050
Description of Cable
Cable assembly AUI Connector Cable 5 m, 15-pos Socket - 15pos Pin for attachment of System Unit to Transceiver.
Note: Equipped with screw lock at the RTA end.
TK526V115
Cable assembly AUI Connector Cable 15 m, 15-pos Socket 15-pos Pin for attachment of System Unit to Transceiver.
Note: Equipped with screw lock at the RTA end.
3BUF 000 987 R1
131
Table 15. MasterBus 300 Transceiver and Tool Kit

Type
Description
MB300K01
Transceiver set for one MasterBus 300 or GCOM

communication interface
MB300K02
Tool kit for transceiver installation
Channel 1
Channel 2
TK526V050 (5 m)
TK526V115 (15 m)
MB300K01
MB300K01
MasterBus 300
MasterBus 300
Figure 64. MasterBus 300 connections
132
3BUF 000 987 R1
Appendix B Supported Interfaces

Table 16. Supported Interfaces
Vendor
Hardware
All standard protocols
3BUF 000 987 R1
Description
Protocol
Bar code readers, etc.
ASCII
DF1 (Half-Duplex)
KE
DNP3.0
DNP
European Installation Bus

(EIB)
OPC
Modbus ASCII
MODBUSA
Modbus RTU
MODBUS
Modbus RTU (slave)
MBSLAVE
OPC Client
OPC
Profibus DP (Softing
PROFIboard)
OPC
Profibus FMS (CP5412 +

Softing s/w)
PROFI
Profibus FMS (CP5412A2 +

Siemens s/w)
SFMSINDX
Profibus FMS (Softing

ProfiBoard)
PROFIBD
SNMP
SNMP
133

Vendor
Hardware
OPC
AC160 (Advant Controller 160) AF100 (KB Article Q2632)
OPC
Serial (Modbus)
MODBUS
Serial (Modbus)
MODBUS
AC410 (Advant Controller 410) Serial (Modbus)
MODBUS
AC450 (Advant Controller 450) Serial (Modbus)
MODBUS
AC70 (Advant Controller 70)
AF100 (KB Article Q2632)
OPC
Serial (Modbus)
MODBUS
Commander 100
Serial (Modbus)
MODBUS
Commander 150
Serial (Modbus)
MODBUS
Commander 200
Serial (Modbus)
MODBUS
Commander 300
Serial (Modbus)
MODBUS
INSUM
Serial (Modbus)
MODBUS
Masterpiece
Serial (Modbus)
MODBUS
Serial (XCOM)
ASEA
Serial (RS232)
ABBMOD
Arcnet
CS31DIR
Arcnet (with FBs)
CS31ARC
Serial
CS31DIR
Serial
CS31DIR
MOD300
Procontic CS31 Series
T200 Series PLCs
134
Protocol
AC110 (Advant Controller 110) Serial (OPC Server, see KB

Q2624)
AC31 (Advant Controller 31)
ABB
Description
3BUF 000 987 R1

Vendor
Hardware
ABB
Controller, Controller XL,
Instrumentation Recorder & Math Unit
Advantech
Alfa Laval
Automation
TAYLOR
Serial
ICN
Serial (Modbus)
MODCELL
Kingfisher RTU's Series 1
Serial (Modbus)
MODBUS
Kingfisher RTU's Series 2
Serial
KINGFISH
Serial (Modbus)
MODBUS
Adam 4000 Series
Serial
ADAM
Adam 5000 Series
Serial
ADAM
PCL-752 Intelligent System

Monitoring Card
Serial
ADISMC
SattCon05
Serial (COMLI)
COMLI
SattCon15
Serial (COMLI)
COMLI
SattCon200
Serial (COMLI)
COMLI
SattCon31
Serial (COMLI)
COMLI
SattCon35
Serial (COMLI)
COMLI
ControlNet (via IOLinx)
ABIOLINX
ControlNet (via RSLinx)
OPC
Ethernet (via RSLinx)
OPC
Serial
ABRSLINX
MicroLogix 1000
Serial (Half Duplex DF1)
KE
PLC2
1784-KT
KT
1784-KT (DH+ with RSLinx)
ABKT
ControlLogix
Allen-Bradley
3BUF 000 987 R1
Protocol
Serial
MODCELL 2000
Action Controls
Description
135

Vendor
Hardware
Description
Protocol
1784-KT, -KTX, -KTXD (DH+) ABTCP
PLC2
Allen-Bradley
ABTCP
DH+ (5136-SD card)
ABTCP
Ethernet (TCP/IP with

RSLinx)
ABEI
Ethernet (TCP/IP)
ABTCP
RSLinx
ABRSLINX
Serial
KE
1784-KT
KT
ABKT
PLC3
PLC5
136
DH (5136-SD card)
DH (5136-SD card)
ABTCP
DH+ (5136-SD card)
ABTCP

RSLinx)
ABEI
Ethernet (TCP/IP)
ABTCP
RSLinx
ABRSLINX
Serial
KE
1784-KT
KT
ABKT

DH+ (5136-SD card)
ABTCP

RSLinx)
ABEI
3BUF 000 987 R1

Vendor
Hardware
PLC5
Description
Protocol
Ethernet (TCP/IP)
ABTCP
RSLinx
ABRSLINX
Serial
KE
Serial
DF1FD
1784-KT
KT
ABKT
Allen-Bradley
PLC5/250
DH+ (5136-SD card)
ABTCP

RSLinx)
ABEI
Ethernet (TCP/IP)
ABTCP
RSLinx
ABRSLINX
Serial
KE
1784-KT
KT
ABKT
SLC500
Ampcontrol
3BUF 000 987 R1
Minescan RTU
DH+ (5136-SD card)
ABTCP

RSLinx)
ABEI
Ethernet (TCP/IP)
ABTCP
RSLinx
ABRSLINX
Serial
DF1FD
Serial
KE
Serial
MINESCAN
137

Vendor
April
B&R
Hardware
Description
Protocol
A2000
Serial (Modbus)
MODBUS
A5000
Serial (Modbus)
MODBUS
A7000
Serial (Modbus)
MODBUS
PB200
Serial (Modbus)
MODBUS
PB400
Serial (Modbus)
MODBUS
PB80
Serial (Modbus)
MODBUS
B&R PLCs
Arcnet
ARCNET
Serial
MININET
Baker Hughes
EXS-1000 RTU
Serial (Modbus)
MODBUSA
Beckhoff
TwinCAT PLC
Local software
TWINCAT
Bosch
RK512/3964R capable
devices
Serial (3964R / RK512)
SIEMENS
Bristol Babcock 3300 Series RTUs
OpenBSI
OPENBSI
Cegelec
Serial (CCM)
CCM
Alspa 8035
Serial (via programming port) SNP

Alspa 8075
Serial (CCM)
CCM
Serial (via programming port) SNP

Contemporary
Control
Systems
PCX20 Series
Arcnet
CCSARC
Contrec
Systems
405B
Serial
CONTREC
405D
Serial
CONTREC
Control
Microsystems
Inc.
TeleSAFE
Serial
MODBUS
138
3BUF 000 987 R1

Vendor
Hardware
Description
Protocol
Control
Techniques
Mentor II
Serial
MENTOR
Data
Electronics
50, 500, 600 Data Loggers

Series
Serial
DATATAKR
Detroit Diesel
Corporation
DDEC III ECM
Serial
DDEC
Eberle
511S, 514S PLCs
Serial
SIEMENS
Echelon
LON Devices
EasyLon OPC Server (see KB OPC

Q2683)
CIC01
Serial
BAILEY
CIC03
Serial
BAILEY
INFI90
Serial
BAILEY
Serial (SEMAPI)
SEMAPI
Network 90 (N CIU02/03/04)
Serial
BAILEY
DX Servo Controllers
Serial
PCM
Micro DCI 53MC1000
Serial
MICROD
Micro DCI 53MC2000
Serial
MICROD
Micro DCI 53MC5000
Serial
MICROD
Micro DCI 53MC6000
Serial
MICROD
Fisher and
Paykel
PSC-3
Serial
PSC
TCP/IP
PSC
Fisher Controls
ROC 364 devices
Serial
ROC
Serial (OPC Server, see KB

Q2624)
OPC
Serial
FOX
Elsag Bailey
Emerson
Fischer & Porter
Foxboro
3BUF 000 987 R1
731 Loop Controller
139

Vendor
Foxboro
Fuji Electric
Hardware
Description
Protocol
760 Loop Controller
Serial
FOX
761 Loop Controller
Serial
FOX
762 Loop Controller
Serial
FOX
I/A Series
SA85 card (Modbus Plus)
MBPLUS
Flex-PC (NB)
Serial
FLXPCNB
Flex-PC (NJ-CPU-B16)
Serial
FLXPCN
Flex-PC NB or NJ Series
Serial
FLEXN
Ethernet (TCP/IP)
MICRXNET
Serial
FUJI
T-Link (FFU080A Card)
FUJIT
Micrex-F Series PLCs
Gantner
ISM Series
Serial (MODBUS)
MODBUS
GE
Multilin
Serial (Modbus)
MODBUS
PCIM Card (GENIUS)
GENIUS
Serial (CCM)
CCM
Serial (Modbus via CMM)
MODBUS
Serial (SNP)
SNP
TCP/IP
GETCP
PCIM Card (GENIUS)
GENIUS
Serial (CCM)
CCM
Serial (Modbus via CMM)
MODBUS
Serial (SNP)
SNP
TCP/IP
GETCP
PCIM Card (GENIUS)
GENIUS
9030 Series PLCs
GE Fanuc
9070 Series PLCs
Series Six PLCs
140
3BUF 000 987 R1

Vendor
Hardware
Description
Protocol
GE Fanuc
Series Six PLCs
Serial (CCM)
CCM
GEC
GEM80 PLCs
Ethernet
GEMLAND
Serial
GEM
GEC Alsthom
K-Series HV Protection Relays Serial
COURIER
Harris Controls
D20 RTU
Serial (DNP)
DNP
Hewlett Packard HP3852A
HPIB
HP3852A
Hitachi
H20, H200, H250, H252,

H300, H700 series PLCs
Serial
HITACHI
620 Series PLCs
Serial
HWELL
620-12/1633/36
Ethernet
EIM
TDC2000
Data Hiway
SX
TDC3000
Data Hiway
SX
UDC3000 Series
Serial (Modbus)
MODBUS
PDS Compact 500 Telemetry

Processor
Serial (Modbus)
MODBUS
PDS RTU Manager
Serial (Modbus)
MODBUS
PDS500 Telemetry Processor
Serial (Modbus)
MODBUS
Clean Room Monitoring

System
Software Interface
STARPMS
StarGate System 7 DCS
Software Interface
STARGATE
Izumi FA Series PLCs
Serial
IZUMI
Micro3 PLCs
Serial (RS232)
MICROIII
Honeywell
HWT (formerly
Hunter
Watertech)
ICON Control
Systems
Idec Izumi
Innotech
3BUF 000 987 R1
Genesis II DDC (Direct Digital DDE Server

Controller)
DDEDRV
141

Vendor
Hardware
Description
Protocol
Intelligent
Field Devices
Instrumentation
Data Acq. card
BURRB
Intuitive
Technologies
@aGlance/IT Servers
@aGlance/IT API
AGLANCE
Johnson
Controls
DR-9101
Serial
JCONTROL
DX-9100, DC-9100, XT/XP9100 TC-9100, SC-9100
Serial
JCONTROL
Kaye
RP-3G, RP-4H
Instruments Inc
Serial
RAMP
Keyence
KV-300
Serial
KV
316 Series
Serial
KLOCMOEL
416 Series
Serial
KLOCMOEL
PS316, Sucos PS 32
Serial (Applicom card)
APPLIC
Leeds &
Northrup
Micromax 1
Serial
MICROMAX
Micromax 2
Serial
MICROMAX
LG Industrial
Systems
Glofa
Ethernet (TCP/IP)
GLOFAEUE
Master-K Series (500 and

1000)
Serial
LGDIRECT
FP Series PLCs
Ethernet (TCP/IP)
MEWTOCOM
Serial
MEWTOCOL
Serial (New!)
MEWTOCOM
Klockner
Moeller
Matsushita
Mauell
ME30
Serial
SIEMENS
Measurex
MXopen Servers
TCP/IP
MEASUREX
Mindata
MD3500 Data Logger
Serial
SDA
Mitsubishi
Melsec Fx Series PLCs
Serial
MELSECF
142
3BUF 000 987 R1

Vendor
Mitsubishi
Hardware
Protocol
Serial
MELSEC
TCP/IP
MELSCNET
Melsec-AnA Series PLCs
Serial
MELSEC
Melsec-QnA Series PLCs
TCP/IP
MELSCQNA
IO express Data Collection

Units
Serial
MOORE
Serial via Model 320
MOOREP
APACS
MBI Card
APACS
MDLC Gateway
TCP/IP
MOSCAD
Moscad
Serial (Modbus)
MODBUS
MTL
Instruments
MTL8000 Series
Serial (Modbus RTU)
MODBUS
National
Instruments
Data Acquisition H/W
OPC Server for NIDAQ
OPC
FieldPoint distributed I/O
FieldPoint OPC Server
OPC
Nematron
OpenControl framework
Software API
OPENCTRL
NJ International ISAGraf
Ethernet (TCP/IP)
OPC
Omnitronics
Serial
OPENCTRL
Controller Link
FINS
Ethernet
FINS
Serial
FINS
Serial
OMRON
Sysmac Link
FINS
TCP/IP
OMFINS
Moore
Industries
Melsec-A Series PLCs
Description
Moore Products 351& 352 Controllers 383

Multipoint Display
Motorola
Omnitronics RTUs
All Omron PLCs

Omron
CV Series PLCs
3BUF 000 987 R1
143

Vendor
Opto 22
Phoenix
Contact
Hardware
Description
Protocol
Mistic
OptoControl
OPTOMIST
Optomux I/O Controllers
Serial
OPTOMUX
Interbus S compatible devices IBS PC CB/I-T or IBS PC

CB/COP/I-T
PC ISA SC/I-T
IBS
INTERBUS
Remote Field Controller (RFC) Ethernet (TCP/IP)
OPC
DL105 Series PLCs
Serial (K Sequence)
KSEQ
Ethernet
KOYONET
Serial (DirectNet)
CCM
Serial (K Sequence)
KSEQ
DL305 Series PLCs
Serial (DirectNet)
CCM
DL405 Series PLCs
Ethernet
KOYONET
Serial (DirectNet)
CCM
SU-6B
Serial
CCM
All Reliance PLCs
R-NET PC Link Card
RNET
Serial
RELIANCE
Automax DCS
Direct hardware access
AUTOMAX
Rosemount
EC 300 Controller
Serial (Modbus)
MODBUS
RTP
RTP2x00
TCP/IP
RTP
S-S
Technologies
5136-SD Card
Data HiWay
SSTAB
Serial (Modbus)
MODBUS
SAAB
SAAB Radar tank level gauge
Serial (Modbus)
MODBUS
SAIA
PCD2
Serial
SBUS
DL205 Series PLCs

PLC Direct
(Koyo)
Reliance
Electric
144
3BUF 000 987 R1

Vendor
Hardware
Serial (SBUS via Applicom

card)
APPLIC
PCD4
Serial
SBUS

card)
APPLIC
Serial
SBUS

card)
APPLIC
Fara PLC
Serial
MEWTOCOM
Hibrain PLC
Serial
HITACHI
Model 764S Access

Controllers
Serial (RS232)
S764CMD
Serial (RS232)
S764OP
SE 804S/SN/SX
Serial
SCHLAGE
Serial
SATTBUS
SE 808S/SN/SX
Serial
SATTBUS
484 PLCs
Serial (Modbus)
MODBUS
584 PLCs
SA85 (Modbus Plus)
MBPLUS
Serial (Modbus)
MODBUS
884 PLCs
Serial (Modbus)
MODBUS
984 PLCs
SA85 (Modbus Plus)
MBPLUS
Serial (Modbus)
MODBUS
TSX Quantum
TCP/IP
MODNET
Entire SY/MAX range
SA85 (Modbus Plus via

NR&D module)
MBPLUS
PCD6
Schlage
Electronics
Schneider
Automation
(Modicon)
Schneider
Automation
(Square D)
3BUF 000 987 R1
Protocol
PCD2
SAIA
Samsung
Description
145

Vendor
Hardware
Entire SY/MAX range
Schneider
Automation
(Square D)
Description
Serial (Modbus via NR&D
module)
MODBUS
Sy/Link card
SQUARED
Ethernet (SFI610 card)
SYENET
Ethernet (via Softhub S/W)
SQDNET
Model 50 PLCs
Serial
IZUMI
All (including TSX Series)
Serial (Uni-Telway via

Applicom card)
APPLIC
Serial (Uni-Telway)
UNITEL
Applicom communications
server
APPLIC
Model 450 & 650 ranges
Ethway devices
Mapway Network - Pre Version Mapway

4 PLCs
Schneider
Mapway Network - Version 4
Automation
or Later PLCs
(Telemecanique
)
TSX Micro
TSX Nano
146
Protocol
TELMAP
Mapway
TELMAP
FIPWAY via Applicom card
APPLIC
SA85 (Modbus Plus)
MBPLUS
Serial (Modbus via PCMCIA

card)
MODBUS

Applicom card)
APPLIC

PCMCIA)
UNITEL

Applicom card)
APPLIC
Serial (Uni-Telway)
UNITEL
3BUF 000 987 R1

Vendor
Hardware
Schneider
Automation
(Telemecanique
TSX Premium
)
S5-115U
Siemens
S5-135U, S5-155U
3BUF 000 987 R1
Description
Protocol
FIPWAY via Applicom card
APPLIC
SA85 (Modbus Plus)
MBPLUS
Serial (Modbus)
MODBUS

Applicom card)
APPLIC
Serial (Uni-Telway)
UNITEL
Profibus DP (Applicom)
APPLIC
Profibus DP (Softing OPC)
OPC
Profibus FDL (Applicom)
APPLIC
Profibus FMS (CP5412)
PROFI
Profibus FMS (PROFIboard)
PROFIBD
Profibus FMS (SST OPC)
OPC
Serial (3964R / RK512)
SIEMENS
Serial via prog. port (see KB

Q2136)
SIDIRECT
Sinec (H1-TF - CP1413)
SINEC_H1
Sinec (L2-TF - CP5412)
SINEC_L2
Sinec FDL (CP5412)
SINECFDL
Sinec FDL (CP5412A2)
SFDL
APPLIC
OPC
APPLIC
PROFI
PROFIBD
147

Vendor
Hardware
S5-135U, S5-155U
Siemens
S5-90U, 100U, 102U, 103U

PLCs
S5-95U
S7-200 series
S7-300 series
148
Description
Protocol
OPC
Serial (RK512 / 3964R)
SIEMENS
Serial via prog. port (see KB

Q2136)
SIDIRECT
SINEC_H1
Sinec (L2-TF - CP5412)
SINEC_L2
Sinec FDL (CP5412)
SINECFDL
SFDL
Serial via programming port
SIDIRECT
APPLIC
OPC
APPLIC
OPC
Serial via programming port
SIDIRECT
Sinec FDL (CP5412)
SINECFDL
SFDL
Serial (Applicom)
APPLIC
Serial (Modbus - see KB

Q2188)
MODBUS
Serial (PPI - see KB Q2188 )
SIMPPI
APPLIC
OPC
PROFI
3BUF 000 987 R1

Vendor
Hardware
Description
Protocol
PROFIBD
OPC
S7 Functions - MPI (Windows S7WIN

95/98)
S7 Functions - MPI (Windows S7NT
NT)
S7-300 series
Siemens
S7-400 series
S7 Functions - Profibus
(Windows 95/98)
S7WIN
(Windows NT)
S7NT
S7 Functions - TCP/IP
(Windows 95/98)
S7WIN
(Windows NT)
S7NT
Serial (RK512 / 3964R - See

KB Q2498)
SIEMENS
Serial via CP340
S7PTP
APPLIC
OPC
PROFI
PROFIBD
OPC
S7 Functions - MPI (Windows S7WIN

95/98)
S7 Functions - MPI (Windows S7NT
NT)
3BUF 000 987 R1
149

Vendor
Hardware
Protocol
(Windows 95/98)
S7WIN
(Windows NT)
S7NT
(Windows 95/98)
S7WIN
(Windows NT)
S7NT
Serial (RK512 / 3964R - See

KB Q2498)
SIEMENS
Serial via CP441
S7PTP
Simatic PM500 PLCs
Serial via Computer Interface

Module
TICIM
Simatic TI305 PLC
Serial
CCM
Serial
TIDIRECT
Serial via Unilink Host

Adapter
TISERIAL
TINEC
TCPIP (CP2572)
TITCPIP
TIWAY
TIWAY
S7-400 series
Siemens
Description
TI505 Series PLCs
SIXNET
Sixnet I/O
Proprietary software
SIXNET
Softing GMBH
4Control
OPC
OPC
Sprecher &
Schuh
390, 490, 590, 690 series

PLCs
Serial
HITACHI
Steeplechase
Visual Logic Controller (VLC)
DataExpress
STEEPLE
OPC Server
OPC
150
3BUF 000 987 R1

Vendor
Hardware
DPCS, PCS, OIS, SIS all
models
Description
Protocol
ADMAP Network (AAMI2

card)
TOSADMAP
ADMAP Network (JAMI1

card)
JAMI
EX100 PLCs
Serial
TOSHIBA
EX2000 PLCs
Serial
TOSHIBA
EX250 PLCs
Serial
TOSHIBA
EX500 PLCs
Serial
TOSHIBA
MCS1000, MCS1200
Proprietary software
PCMP
ONS
Ethernet (TCP/IP)
TONS
T1
Serial
PROSEC
T2
Serial
PROSEC
T3
Serial
PROSEC
Tosdic 200 DCS
Serial
TOSDIC
Transmitton
Telemetry Control Systems
Serial
TXMITTON
Triconex
Corporation
Triconex via 4119 Module
Serial (Modbus)
MODBUS
Triplex
Serial (Modbus)
MODBUS
Unidata
Data logger 6003, 6004-1,

6004-2, 6004-3, 7000
Serial
STARLOG
Weidmuller
Weidmuller 810977 CPU
Profibus FMS (CP5412A1)
PROFI
PROFIBD
Toshiba
Westinghouse
PLC1500 PC1200
Serial (Modbus)
MODBUS
Woojin
Pymax
Serial
PYMAX
Yokogawa
3880 Hybrid Recorder
Serial
HR
3BUF 000 987 R1
151

Vendor
Hardware
152
Protocol
4082 Hybrid Recorder
Serial
HR
Centum CS
Ethernet (TCP/IP) via

ACG10S-E Gateway
OPC
Centum XL
TCP/IP
YOK_CXLE
Green Series
Serial
YOKGRN
Micro XL
Serial
YOK_UXLS
ZWorld MicroG controller
Serial (Modbus)
MODBUS
Yokogawa
ZWorld
Description
3BUF 000 987 R1
3BUF 000 987 R1

November 2001

Inform IT Prod Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Inform IT Prod Guide

Uploaded by

Copyright:

Available Formats

InformIT

Enterprise Historian for Windows 2000

User Interface .......................................................................................................18

DeskTop Trends ..................................................................................19

Section 2 - Basic Software Components

3BUF 000 987 R1

Composite Log Applications .............................................................. 41

3BUF 000 987 R1

Display Server .....................................................................................72

Property Predictor ..................................................................................................................... 86

Section 3 - Hardware/Software Requirements

3BUF 000 987 R1

Section 4 - Ordering Information

Section 5 - Capacity and Performance

3BUF 000 987 R1

Connecting to the Advant OCS .....................................................................................126

3BUF 000 987 R1

3BUF 000 987 R1

What is Inform IT Enterprise Historian?

3BUF 000 987 R1

What is Inform IT Enterprise Historian?

Figure 1. Industrial IT Information Management Component

3BUF 000 987 R1

What is Inform IT Enterprise Historian?

Inform IT Enterprise Historian is a distributed information management system,

Figure 2. Industrial IT Information Management Component

3BUF 000 987 R1

What is Inform IT Enterprise Historian?

Data Collection, Storage and Retrieval

3rd party system and device interfaces

Data analysis and mining

3BUF 000 987 R1

Data Collection, Storage and Retrieval

Data Collection, Storage and Retrieval

Enterprise Historian manages the storage of production related information about

3BUF 000 987 R1

Data Collection, Storage and Retrieval

Figure 3. Data Stored in PDL for a Batch Application

3BUF 000 987 R1

Data Collection, Storage and Retrieval

3BUF 000 987 R1

a very thin client for custom displays

the ability to look at all the data via Excel

Internet and intranet access is supported by a web-based trend package. Custom

3BUF 000 987 R1

3rd Party System and Device interface

DataDirect provides a set of ABB Add-ins to Microsoft Excel. These Add-ins

3rd Party System and Device interface

3BUF 000 987 R1

Data Analysis and Mining

Data Analysis and Mining

Unused historical data is a waste of valuable information. With Enterprise

3BUF 000 987 R1

Data Analysis and Mining

Extract data from History Services via an easy-to-use data extraction

Perform What-ifs in an off-line manner and Sensitivity Analysis (effect of

Sensor validation for critical measurements

Inferential models for controllers

An additional license must be purchased for Property Predictor.

3BUF 000 987 R1

Whats New in this Release

Whats New in this Release

Enterprise Historian server software runs on Windows 2000. Desktop client

See Bundling Options on page 23.