Inform IT Prod Guide

InformITEnterprise Historian for Windows 2000

Version 3.2

Product Guide

Product Guide

InformITEnterprise Historian for Windows 2000

Version 3.2

NOTICEThe information in this document is subject to change without notice and should not beconstrued as a commitment by ABB Inc. ABB Inc. assumes no responsibility for any er-rors that may appear in this document.

In no event shall ABB Inc. be liable for direct, indirect, special, incidental or consequentialdamages of any nature or kind arising from the use of this document, nor shall ABB Au-tomation Inc. be liable for incidental or consequential damages arising from use of anysoftware or hardware described in this document.

This document and parts thereof must not be reproduced or copied without written per-mission from ABB Inc., and the contents thereof must not be imparted to a third party norused for any unauthorized purpose.

The software or hardware described in this document is furnished under a license andmay 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 LowVoltage Directive 72/23/EEC.

Copyright 2001 ABB Automation Inc.All rights reserved.

Release: November 2001Document number: 3BUF 000 987 R1

TRADEMARKSAdvant, AdvaCommand, AdvaInform, and AdvaBuild are registered trademarks of ABB Asea Brown BoveriLtd., 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, PavilionData Interface, Process Insights, Process Perfecter.

The following are trademarks of Pavilion Technologies, Inc.: Insights, Pavilion OnLine Applications, Pavil-ion 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

3BUF 03BUF 0

TABLE OF CONTENTS00 987 R1 500 987 R1 5

Section 1 - IntroductionWhat is Inform IT Enterprise Historian?.........................................................................11

Data Collection, Storage and Retrieval ................................................................15Process data ......................................................................................15Production Data...................................................................................15Event data ......................................................................................17

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

3rd Party System and Device interface ................................................................19Data Analysis and Mining....................................................................................20

Reporting capabilities..........................................................................20Process modeling and analysis............................................................20

Whats New in this Release .............................................................................................22Bundling Options.............................................................................................................23

Enterprise Historian Collect .................................................................................24Enterprise Historian Connect ...............................................................................28Enterprise Historian Consolidate .........................................................................31

Licensing .........................................................................................................................31

Section 2 - Basic Software ComponentsSystem Services...............................................................................................................33History Services...............................................................................................................34

Applications that Use History Services................................................................34Process Data Storage............................................................................................36

Calculations ......................................................................................38Data Compaction.................................................................................39

Table of Contents

6

Composite Log Applications .............................................................. 41Secondary Logs for Different Resolution/Time Span Views..............42Primary and Secondary Logs with Calculations................................. 43Lab Data Logs for Asynchronous User Input .....................................443BUF 000 987 R1

Consolidating History Data with Distributed Logs ............................ 45Collecting Data for Longer Time Period at Consolidate Level ..........47Composite Log with Local and Distributed Secondary Logs............. 47Calculated Values on both Collect and Consolidate Levels................ 48Collection from Enterprise Historian Connect ................................... 48Collecting from Remote History Logs................................................49Dual Configuration for Data Security.................................................50Collecting from OPC Data Sources .................................................... 52Numeric Data Presentation .................................................................53Seamless Retrieval ..............................................................................54Numeric Data Storage Considerations................................................54Off-line Storage ..................................................................................54

Event Data Storage ..............................................................................................55Event Presentation ..............................................................................56Off-line Storage ..................................................................................56

Production Data Storage ...................................................................................... 56Off-line Storage ..................................................................................58Presentation ...................................................................................... 58

Finished Report Storage.......................................................................................60Off-line Storage and Access ................................................................................ 61History Database Configuration .......................................................................... 62

Display Services..............................................................................................................62Building Displays ................................................................................................ 65

Display Elements ................................................................................ 68Runtime Displays................................................................................................. 69

Active X Support ................................................................................ 69History Displays .................................................................................70

Display Services Client-Server Architecture .......................................................72

Table of Contents

3BUF 03BUF 0

Display Server .....................................................................................72Display Client......................................................................................73Additional Display Services Capabilities............................................75

DataDirect........................................................................................................................7600 987 R1 700 987 R1 7

Dialogs for Ad-hoc Data Retrieval/Data Entry ...................................77Function Calls for Building Reports in Microsoft Excel ....................78Using DataDirect Functions in Macros (VBA)...................................79Requirements ......................................................................................79

Desktop Trends................................................................................................................80Audit Trail .......................................................................................................................82OLE DB Data Access ......................................................................................................84Data Analysis and Mining ...............................................................................................86

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

Report Services................................................................................................................87Report Building ....................................................................................................87Report Scheduling ................................................................................................89Report Execution and Data Access ......................................................................89Managing Report Instances..................................................................................90User Interface .......................................................................................................90

User API ..........................................................................................................................92Production Data Log (for Use with Produce IT Batch)....................................................92Event Log (For systems with Master data connection only) ...........................................93

Event Log Configuration.....................................................................94Event Log Communication .................................................................94Accessing Event Messages From the Event Log ................................95

PLC Interface...................................................................................................................96OPC Connectivity............................................................................................................98Advant OCS Control Network Connections....................................................................98

Section 3 - Hardware/Software RequirementsPrerequisite Software .........................................................................................102

Table of Contents

8

Section 4 - Ordering InformationEnterprise Historian Products ....................................................................................... 103

Enterprise Historian Collect for Windows 2000 SP-B-EHSNT ........................ 103Enterprise Historian Consolidate for Windows 2000 - SP-B-EHCNN ............. 1043BUF 000 987 R1

Enterprise Historian Connect for Windows 2000 - SP-B-EHATC .................... 104Display Services Expansion Nomenclature - SP-E-EHDSA............................. 105

Pavilion Technologies Products .................................................................................... 106Enterprise Historian Pavilion Insights Client: SP-B-EHPCA............................ 106Pavilion Property Predictor: Client (SP-B-EHPCB), and Server

(EH-B-EHSPP, SP-E-EHSPP) .......................................................... 106

Section 5 - Capacity and PerformanceHistory Services ............................................................................................................ 107

Overall Capacity ................................................................................................ 107Maximum Number of Primary Logs ................................................................. 107Maximum Number of Entries Per Log .............................................................. 108History Objects Miscellaneous Capacities ........................................................ 108History Collection Maximum Sample Rate....................................................... 109Fastest Sample Rate ........................................................................................... 110Disk Requirements Per Log Entry ..................................................................... 110Disk Space Allocation for Oracle and File-based Logs..................................... 111History Archive.................................................................................................. 112

Event Log (Master) ....................................................................................................... 113Display Services............................................................................................................ 113PLC Interface ................................................................................................................ 114Desktop Trends.............................................................................................................. 114Report Services ............................................................................................................. 114OLE DB Data Access.................................................................................................... 114User API........................................................................................................................ 115Connecting to Symphony/INFI 90 ................................................................................ 122Connecting to Freelance................................................................................................ 123Connecting to SattLine.................................................................................................. 124OPC Connectivity ......................................................................................................... 125

Table of Contents

3BUF 03BUF 0

Connecting to the Advant OCS .....................................................................................126Real Time Accelerator Board (RTA)..................................................................128MOD 300 DCN Control Network Connections.................................................128MasterBus 300 Control Network Connections ..................................................13100 987 R1 900 987 R1 9

Table of Contents

10 3BUF 000 987 R1

Section 1 Introduction What is Inform IT Enterprise Historian?

3BUF 0

Section 1 Introduction

Wha00 987 R1 11

t is Inform IT Enterprise Historian?Information is a key asset of all manufacturing and process businesses. Onesignificant issue that such businesses face is the collection and distribution ofinformation from its point of origin to locations where it can be applied to improvequality and productivity.

Manufacturing and process operations must be able to adapt to daily and hourlychanges in production schedules and resource availability. In today's businessenvironment, much of this information is available electronically, but must also bepresented to operations in a meaningful context.

Technology has driven information access lower and lower in the enterprise-widearchitecture to near real time. Production management and planning functionsrequire vertical integration of high value information. An information backbone isrequired to integrate information from multiple systems upward into the supplychain and decision making systems.

Industrial IT from ABB is a comprehensive approach for organizing informationcollection and management functions across an enterprise. The information can beleveraged through its use in process specific applications for improving processoperation and managing production quality. In Industrial IT, information is sharedacross the enterprise with tools that reduce redundant entry and minimize deviationsbetween engineering and operations databases. ABB has created an infrastructurefor information across its manufacturing related products using opencommunication standards. This lets you integrate ABB components and systemswith other information functions across the enterprise.

Inform IT Enterprise Historian supplies the information management component tothe backbone, integrating data from various levels of the business and making thatdata available to the different levels of the organization. Each level has differinginformation needs, Figure 1.

What is Inform IT Enterprise Historian? Section 1 Introduction

12 3BUF 000 987 R1

Pivotal to being successful with Industrial IT, is the gathering and leveraging ofprocess and production information. Stored process and production information isnot only available to document production activities, but is also rich in informationwhich lets you review past performance of the process. Past information is used toproduce similar products, at similar rates and under similar operating conditions. Italso lets you seek and move to more optimal operating conditions based uponquality and economics.

Enterprise Historian lets you leverage information available from process andproduction operations to operate a business more wisely. With Enterprise Historianyou mine data and transform it into information, knowledge and wisdom for betterdecision making.

Figure 1. Industrial IT Information Management Component

Section 1 Introduction What is Inform IT Enterprise Historian?

3BUF 0

Inform IT Enterprise Historian is a distributed information management system,Figure 2. It provides the ability to collect data from multiple sources and combine itinto a single historical instance. This data can come from ABB control systems, 3rdparty automation systems such as DCSs and PLCs, and other devices like bar code00 987 R1 13

readers. A store and forward architecture increases data security and maintains ahigh level of communications availability with the historical data sources.

In this architecture, data is collected and stored in two locations. One is theEnterprise Historian Collect server. This supports operators and other personnel atthe local control system. It provides services such as operator trends and shift/dailyproduction reports.

Figure 2. Industrial IT Information Management Component

What is Inform IT Enterprise Historian? Section 1 Introduction

14

The other primary storage location is Enterprise Historian Consolidate server. Thiscombines data from Enterprise Historian Collect and Enterprise Historian Connectservers. Enterprise Historian Consolidate provides access to data for desktop clientsand other personnel in the facility. It is also the primary supplier of data to business3BUF 000 987 R1

and planning systems and other Manufacturing Execution System (MES)applications. This function is best performed from the Consolidate server at theplant level since it has the complete set of data that may be required.

Enterprise Historian Connect server provides connectivity to DCSs, PLCs and otherdevices when that data is not required in the control domain. It provides store andforward capability to the Enterprise Historian Consolidate server.

Due to the distributed nature of the Historian, data can reside on multiple serversand yet appear to be on a single server. When making a request for data, you connectto one server. If the data requested is not present at that server the Historianautomatically forwards the request to other servers. The response is returned fromwhichever server has the requested data.

Enterprise Historian is a multi-tiered, client-server application that operates in adistributed architecture. This lets you use computing resources effectively. ABB'sEnterprise Historian architecture is unique in its flexibility and versatile applicationof standard functional components to a variety of process information managementsituations. Enterprise Historian can apply its functionality locally to a single ABBcontrol system, or it can be applied across multiple control systems from multiplevendors. History servers are logically linked at a site and across an enterprise toprovide a common historical data environment with simple desktop access.

There are four major components to an Enterprise Historian: Data Collection, Storage and Retrieval User Interface 3rd party system and device interfaces Data analysis and mining

Section 1 Introduction Data Collection, Storage and Retrieval

3BUF 0

Data Collection, Storage and RetrievalEnterprise Historian provides various techniques for data collection and becomes arepository of process, event and production information. Data security has alwaysbeen a priority for Enterprise Historian. Dual and distributed storage techniques00 987 R1 15

offer duplicate storage of data in two or more places. Off-line storage and on-linebackup provide the ability to move data to a removable media for safe storage.

Rather than fitting diverse data types and relationships into the same storagestructure, Enterprise Historian offers varying storage capabilities so that diverse datamay be stored in a manner appropriate for the industry or application. ProductionData Logging (PDL) is used for structuring batch records and other productionspecific 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 rateare recorded at a basic resolution that is specific to each tag monitored by the historyfunction. Calculations such as minimum, maximum, averages and statisticalcalculations can be performed as data is recorded in the historian. You have theoption of applying data compaction, or maintaining raw, uncompressed data whenraw data is required for application or documentation purposes.

Production Data

Enterprise Historian manages the storage of production related information aboutresource usage and material/product activities based on standard user defined eventprocessing /monitoring. This data is stored in the Production Data Log (PDL) andused in conjunction with ABB batch management systems such as Produce ITBatch.

Often when a batch is being produced, the information associations are nottime-related and cannot be pre-configured or anticipated. PDL has built-inprovisions for the organization, storage and retrieval of this type of information.PDL organizes critical process data such as operator interventions, alarm andevents, equipment usage and task start/stop and duration times. Figure 3 shows therelationship of the data stored in a PDL for a batch process.

Data Collection, Storage and Retrieval Section 1 Introduction

16 3BUF 000 987 R1

PDL data is stored in Oracle tables and is accessible by standard SQL queries. Theinformation is available to Reports, other network-based reporting or analysispackages and applications such as Microsoft Access and Excel.

PDL provides logically organized, easily retrievable production data. This datacorrelation is not based solely on time. PDL information is associated with taskssuch as campaign, batch, unit, operation, phase and variables. PDL transforms datainto useful information for intelligent decision making.

Figure 3. Data Stored in PDL for a Batch Application

Section 1 Introduction Data Collection, Storage and Retrieval

3BUF 0

Event data

Enterprise Historian also supports the collection of events and system messagesgenerated through standard control loop processing, operator control functions,control applications, batch programming or user-defined applications. All data,00 987 R1 17

messages and production information recorded in history are managed together andcan be retrieved and reviewed from standard displays. Events are stored in Oracle toprovide a simple query mechanism for analyzing relationships between events overtime.

A specialized version of event storage is an Audit Trail for pharmaceutical and othergovernment regulated industries. The Audit Trail provides a complete trace ofchanges that have been made to production data. The Audit Trail tracks changesmade to data stored in the Production Data Log and is completely integrated withProduce IT Electronic Batch Record (EBR) for handling of manual productionsteps. The Audit Trail holds the time of the data change, the identification of theperson that made the change, the old value and new value, and other valuableinformation. Combined with the production data stored by a batch managementpackage such as Produce IT Batch and other process and event data stored in theHistorian, a complete electronic batch record can be generated. This is an importantelement of satisfying the FDA 21 CFR Part 11 regulation.

Off-line Storage and On-line BackupAll data stored in the historian can be copied to removable disk media (MagnetoOptical disk). This can be done on a cyclic basis, manually, or on event such as theend of a batch. In addition to the off-line storage capabilities, Enterprise Historianalso supports on-line backup functionality.

Historical values for points in the historian, as well as quality data are available viaOLE DB, SQL and ODBC. Event and production data are available via proprietaryCOM interfaces, SQL and ODBC.

User Interface Section 1 Introduction

18

User InterfaceData access from the desktop is critical. Enterprise Historian provides:

a very thin client for custom displays3BUF 000 987 R1

the ability to look at all the data via Excel

the ability to integrate Enterprise Historian based data along with other datasources (i.e. relational databases) into a single display.

Internet and intranet access is supported by a web-based trend package. Customdisplays are available as ActiveX controls and can be accessed from InternetExplorer or a custom application that can host ActiveX controls.

The historical data managed by Enterprise Historian can be accessed via DisplayServices. Display Services provide seamless operator and management views to realtime and historical information. Data can come from multiple Enterprise Historianservers and other systems and can be combined on comprehensive displays. Thisdata 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 analysisfunctions as well as established production management applications.

Enterprise Historian supports a number of different ways to view data. There is alightweight desktop display package, Excel plug-ins, and a stand alone trendpackage.

Display ServicesThrough Display Services you can create custom graphics and view them from yourdesktop. These displays can be process mimic displays, status overview or otherinformation management displays. A wide range of display elements are availablefor creating these displays such as bar charts, pie charts, edit boxes and gauges aswell as traditional process elements like pumps, motors and vessels. Displays can beviewed in the container provided with Enterprise Historian that supports navigationthrough the different displays that have been built or can be viewed in a webbrowser.

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 tothe historian.

Section 1 Introduction 3rd Party System and Device interface

3BUF 0

DataDirect

DataDirect provides a set of ABB Add-ins to Microsoft Excel. These Add-insprovide access to process variables, history values, messages, production data andSQL-based data through dialog windows on spreadsheets. There is one dialog for

3rd Pa00 987 R1 19

each of the different storage types within Enterprise Historian. Functions are alsoprovided so that you can create and execute standard reports. It is also possible fromthese dialogs or functions to add data to the Enterprise Historian or modify valuesthat are already stored.

DeskTop TrendsDesktop Trends is a standalone trend package that lets you see trend and associateddata 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 toshow when a value is outside of its limits, has bad data quality, and a number ofother conditions.

a tag browser which lets you structure and browse points in an easy-to-accessmanner.

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 trenddisplay. The trend supports a full range of scrolling and zooming features,including a unique feature called Active Zoom. This lets you zoom into asection of the trend while maintaining the overall scope.

rty System and Device interfaceEnterprise Historian provides the ability to integrate data from 3rd party productsthrough a series of interfaces and protocols to PLCs (such as Siemens, A-B, AEGModicon), DCSs and other types of devices. The interfaces are accomplished viaeither 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 deviceinterfaces are best used when an OPC server is not readily available. Drivers to morethan 250 devices are supplied as well as support for standard communicationsprotocols such as MODBUS and PROFIBUS.

Data Analysis and Mining Section 1 Introduction

20

For added data security, data can be kept locally at the connection to the data sourceand forwarded to the historical server when it is available.

Data Analysis and Mining3BUF 000 987 R1

What makes data valuable is the ability to analyze and learn from it. EnterpriseHistorian embeds data analysis and mining tools. An integrated report scheduler isalso available to satisfy your reporting requirements.

Reporting capabilitiesThe report scheduler is a web-based user interface for scheduling reports to executein either Excel or Crystal Reports. Reports can executed on a cyclic basis, at giventime 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 ofreports 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 numberof 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 easilylaunched back into that tool.

The report scheduler is compatible with Crystal Reports Professional and Developerversion 7.x or 8.x. Crystal Reports is not provided as part of Enterprise Historianversion 3.2 and must be purchased separately.

Process modeling and analysisUnused historical data is a waste of valuable information. With EnterpriseHistorian's data mining, analysis and modeling tools, provided by PavilionTechnologies, you can create data driven models to analyze history data, predict keyprocess parameters and optimize processes.

Offline tools can be used to identify key variables and hidden interaction betweenthem, enabling you to transform data into knowledge for productivityimprovements. Effects of process inputs on outputs are ranked and what-if scenariosshow you how to improve operational efficiency, yield and quality control.

Section 1 Introduction Data Analysis and Mining

3BUF 0

You can add modeling tools for property predictions, off-line and on-line modelpredictive control and steady state optimization. You can optimize your processesand see a rapid return on investment. Increased production capacity and tighterquality control can be achieved while reducing energy consumption, process errors00 987 R1 21

and capital expenditures.

The following describes a basic step-by-step approach to data mining modeling andanalysis:

Start with InsightsTM (one license included with Enterprise Historian Collector 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 cuttingit from a trend.

Let Insights build Inferential Models based on your selected inputs andoutputs.

Perform What-ifs in an off-line manner and Sensitivity Analysis (effect ofinputs and changes to those on outputs) to identify the most importantprocess variables in your process.

Put models on-line with Property PredictorTM Virtual On-line Analyzers fortimely measurements.

Sensor validation for critical measurements

Inferential models for controllers

An additional license must be purchased for Property Predictor.

Whats New in this Release Section 1 Introduction

22

Whats New in this Release

New Platform3BUF 000 987 R1

Enterprise Historian server software runs on Windows 2000. Desktop clientapplications may be installed on Windows 2000 or Windows NT. (Display clientand DataDirect software may be installed on Windows 95, Windows 98, andWindows ME.)

New Bundling OptionsSee Bundling Options on page 23.

New ApplicationsThe following new applications are available in Enterprise Historian version 3.2:

Desktop Trends - provides desktop data display functions that can be viewed instand-alone web page mode, or be integrated into other applications that areActiveX containers. See Desktop Trends on page 80.

Audit Trail for event/message logging for batch management applications suchas Electronic Batch Recording (EBR). See Audit Trail on page 82.

History data access via OLE DB, ODBC, and SQL. See OLE DB Data Accesson page 84.

Web-based Report Scheduler and Display. See Report Services on page 87.

MES Server and ComAware Removed from Automation ConnectionsThe Select and Automation Connections standalone product offerings from earlierreleases of Enterprise Historian are restructured as Enterprise Historian Connect.This provides the ability to collect data from OPC sources and other third partydevices with local data buffering before the data is transferred to the history dataserver via distributed logs. The PLC drivers from Automation Connections are anoption to Enterprise Historian Connect. Because of the new product structure andability to distribute history logs, the MES Server was removed from the PLCInterface component.

Section 1 Introduction Bundling Options

3BUF 0

If you are buying Enterprise Historian Connect to upgrade an existing AutomationConnections installation, carefully evaluate any changes required for this upgrade:

Applications using the MES Server to create omf type objects for historycollection will have to be re-engineered. The omf objects created via the MES

Bun00 987 R1 23

Server to collect the OPC data will have to be replaced by History logsconfigured in History Services.

If other applications such as User API or Display Services accessed those omfobjects, 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 datafrom the PLCs rather than going through the MES Server.

Also the ComAware component of the MES Server will no longer be availableon the Enterprise Historian v3.2. The migration of applications developedusing this component of the software will need to be reworked. There is nodirect replacement in Enterprise Historian v3.2. Contact Product Managementwith specific questions concerning your applications and future support.

dling OptionsThe core functionality for Enterprise Historian is installed on a Windows 2000-based server. There are three bundling options for this core functionality:

Enterprise Historian Collect supports data collection directly from an ABBautomation system or OPC server. This bundle replaces Enterprise HistorianProfessional from version 3.1.

Enterprise Historian Connect provides connectivity to 3rd party systems withstore and forward capability to Enterprise Historian Consolidate. This bundlereplaces Enterprise Historian Select from version 3.1 and AutomationConnections as a standalone application.

Enterprise Historian Consolidate combines data from multiple EnterpriseHistorian Collect and Connect installations.

Enterprise Historian Collect Section 1 Introduction

24

Enterprise Historian CollectEnterprise Historian Collect provides historical services when the historian isdirectly connected to the data source, either through OPC or on an ABB controlnetwork. This bundle extends the short term historical data storage for ABB OCS3BUF 000 987 R1

systems. It supports operators with trend and event data, and provides localreporting. Complete data storage, retrieval and archival capabilities are providedalong with integrated data analysis and mining capabilities. Desktop access isprovided from Microsoft Office tools, a web browser and custom displays.Enterprise Historian Collect may be a data source for Enterprise HistorianConsolidate as illustrated in Figure 4.

Collect is not to be used when collecting data from other history sources, includingEnterprise Historian Connect if data forwarding is being employed.

Figure 4. Enterprise Historian Collect

Section 1 Introduction Enterprise Historian Collect

3BUF 0

The core functionality and options are summarized in Table 1 and Table 2.

Table 1. Enterprise Historian Collect - Core Functionality

Syste

Historminim

Displadispladata p

Displa

DataDlicens

Desktlicens

Pavilio- One00 987 R1 25

Component Description

m Services Supports basic services including network communications, objecthandling, process supervision, and system messaging.

y Services withum 250 tag license

Supports configuration, collection, storage, archival, and access toHistory logs by DataDirect, Display Services, and User API.

y Services with oney build license and 5roviders.

y IE

Supports building and viewing dynamic runtime displays on clientnodes connected to a display server.Display IE lets you launch the display client application as anActiveX Control via Windows Internet Explorer.Both the Display client and DisplayIE may be installed locally onthe server and on remote PC clients.

irect - one cliente

Microsoft Excel add-ins let you access information from EnterpriseHistorian and other ABB OCS applications. This includes dialogsfor ad-hoc data retrieval and function calls for report building.DataDirect may also be installed on remote PC clients.

op Trends - one cliente

Lets you view trend data directly on your Enterprise Historiandesktop. 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 operationresembles the Windows Explorer.

Trend Display shows traces for up to eight tags.Desktop Trends may also be installed on remote PC clients.

n Insights licenseclient license

Enterprise Historian integrates with and includes one client licensefor Pavilions Insights software. Additional seats may bepurchased as an option. Pavilions Insights lets you intelligentlyanalyze large volumes of historical process data with tools forcleaning and preprocessing the historical data. Pavilion InsightsClient provides tools for building off-line process models.

Enterprise Historian Collect Section 1 Introduction

26

Table 2. Enterprise Historian Collect - Options

User

OLED

RepoRepoDispla3BUF 000 987 R1


API User API is installed with System Services. You mustpurchase a license to use this software for applicationdevelopment. This license provides services (functions) foraccessing Advant OCS process objects or historical data. Todevelop applications, User API requires Microsoft VisualStudio V6 or an equivalent c++ compiler. The User APIcontains functions to read from, write to and manipulate theAdvant OCS objects in other ways. The User API alsoprovides services for system message and date and timehandling.

B Data Access Supports OLE DB, ODBC, and SQL access to numeric logsresiding on a Windows-based History server. This isrequired to: support numeric log access by Crystal Reports when

this package is employed as the report buildingpackage for Report Services.

support SQL access to Windows-based numeric logsfor DataDirect, Display Services, or other 3rd partytools.

rt Services -rt Scheduling Server andy Components

The server supports scheduling, execution, and retrieval ofreports built with Crystal Reports or Microsoft Excel. Thedisplay component provides the graphical user interface forperforming these tasks. The display component may also beinstalled on remote PC clients.This component does not include a license for CrystalReports or Microsoft Excel.

Section 1 Introduction Enterprise Historian Collect

3BUF 0

Event Log This component is applicable for the Advant OCS with

Audit

Produ

Table 2. Enterprise Historian Collect - Options

Component Description00 987 R1 27

Master software. Event Log software is installed with HistoryServices. An Event Log license is required. This supportssecondary logging of event data in the Enterprise Historiannode. The primary logs - the event data sources - can belocated in one or more OS nodes, or ABBMasterView 850/1.

Trail Audit Trail software is installed with History Services. AnAudit Trail license is required. This supports event/messagelogging for Produce IT Electronic Batch Recording (EBR).

ction Data Logging (PDL) PDL is installed with History Services. A PDL license isrequired. PDLs store production data such as batchstart/end times, batch variables, and event/messages datafor presentation in batch reports. PDL is typically used withBatch 300 or Produce IT Batch.

Enterprise Historian Connect Section 1 Introduction

28

Enterprise Historian ConnectThis bundle provides connectivity to ABB systems (such as Symphony andFreelance) and non-ABB systems (DCSs, PLCs, and other devices). Connectivity to3rd party devices is achieved through a series of drivers that are provided in this

System

Historminim

Displaprovid3BUF 000 987 R1

bundle. Enterprise Historian Connect can also access data directly from OPCservers.

Enterprise Historian Connect supports store and forward functionality to EnterpriseHistorian Consolidate which is the primary data storage server. This bundle mayalso be used as a gateway to Advant OCS systems, replacing Enterprise HistorianSelect. This is primarily used to host applications that need to run close to thecontrol network. Enterprise Historian Connect obtains data directly from an Advantsystem and provides data to 3rd party applications. When purchased with the PLCInterface option, this bundle replaces Automation Connections. Otherwise, this is areplacement for Enterprise Historian Select.

The core functionality and options for Enterprise Historian Connect are summarizedin Table 3 and Table 4.

Table 3. Enterprise Historian Connect - Core Functionality


Services Supports basic services including network communications, objecthandling, process supervision, and system messaging.

y Services withum 250 tag license

Supports limited History Services functionality based on purchasedoptions. See Data Forwarding option in Table 4.

y Services - 5 dataers

Supports data access for DataDirect and Desktop Trends. Note: Abuilder license for creating new graphic displays is not standard. Sucha license may be ordered as a Display Services expansion.

Section 1 Introduction Enterprise Historian Connect

3BUF 0

DataDirect - one clientlicens

Microsoft Excel add-ins let you access information from Enterprise

Desktclient

Table 3. Enterprise Historian Connect - Core Functionality

Component Description00 987 R1 29

e Historian and other ABB OCS applications. This includes dialogs forad-hoc data retrieval and function calls for report building. DataDirectmay also be installed on remote PC clients.

op Trends - onelicense

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 theWindows Explorer.

Trend Display shows traces for up to eight tags.Desktop Trends may also be installed on remote PC clients.

Enterprise Historian Connect Section 1 Introduction

30

Table 4. Enterprise Historian Connect - Options

User

PLC I

Data3BUF 000 987 R1


API User API is installed with System Services. You mustpurchase a license to use this software for applicationdevelopment. This license provides services (functions) foraccessing Advant OCS process objects or historical data. Todevelop applications, User API requires Microsoft VisualStudio V6 or an equivalent c++ compiler. The User APIcontains functions to read from, write to and manipulate theAdvant OCS objects in other ways. The User API alsoprovides services for system message and date and timehandling.

nterface Supports data exchange between Enterprise Historianapplications and third-party devices such as ProgrammableLogic Controllers (PLCs), loop controllers, bar code readers,scientific analyzers, remote terminal units, and distributedcontrol systems.

Forwarding This option supports History configuration, collection andstorage for forwarding of data to an Enterprise HistorianConsolidate server.Without this option, the functionality is limited to Historyaccess support for Display Services, DataDirect, DesktopTrends, and User API.

Section 1 Introduction Enterprise Historian Consolidate

3BUF 0

Enterprise Historian ConsolidateThis combines and stores data from multiple Connect and/or Collect nodes. This isthe information management solution at a plant level or higher. The only networkconnection for Enterprise Historian Consolidate server is to the TCP/IP network.

Lice00 987 R1 31

Complete data storage, retrieval and archival capabilities are provided along withintegrated data analysis and mining capabilities. Desktop access is provided fromMicrosoft Office tools, a web browser and custom displays. The core functionalityand options provided in Enterprise Historian Consolidate are identical to thoseprovided with the Enterprise Historian Collect bundle as described in Table 1 andTable 2. The exceptions are that the following options are not supported on theEnterprise Historian Consolidate server:

Enterprise Historian Harmony OPC Integration

Event Log for systems with Master software

nsingServer software components are licensed on a per-server basis. This means onelicense entitles you to install the software on one server. You must purchase alicense for any server software components that you intend to install.

Client software components are licensed on a concurrent-user basis. This means youcan install the client software on as many PCs as you wish. The server will controlthe number of clients that may connect to the server based on the number of clientlicenses you have purchased. For example, you may install Display Client softwareon ten PCs, but if you purchase two Display Client licenses, only two client PCs willbe permitted to connect to the server at any one time.

For Display Client and DataDirect, each open Display and/or DataDirect windowoccupies a client license, even if the windows are open on the same PC. Thus onePC may occupy two or more client licenses concurrently.

For Desktop Trends, client licenses are occupied on a per-PC basis. You arepermitted to have as many trend displays open on a given PC as you wish. Thiswould still occupy just one client license.

Licensing Section 1 Introduction

32 3BUF 000 987 R1

Section 2 Basic Software Components System Services

3BUF 0

Section 2 Basic Software Components

Syst00 987 R1 33

Three basic software bundles are offered as described in Bundling Options on page23. The components that comprise each of these products are described below.

em ServicesSystem services are primarily configuration and support tools for developing andintegrating information management functions in your system, including:

a Core System that provides communication services for system functions aswell as customer applications.

System Status, System Message and other system management utilities.

Advant OCS communication software for integration of Enterprise Historianapplications with applications on other Advant OCS nodes via the RealtimeAccelerator board connection to the control network, or via TCP/IP.

OPC communication software provides OPC V1.0a or V2.0 OPC client forcollecting historical data from the PLC Interface, Operate IT OPC servers,AC 800F and other 3rd party servers. See Appendix A, Control NetworkConnections for more information on supported OPC servers.

History Services Section 2 Basic Software Components

34

History ServicesHistory Services supports data collection with optional compression (polled, byexception, user-supplied, or manual), storage, and retrieval. The degree of

Applic3BUF 000 987 R1

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 forwarddata to an Enterprise Historian Consolidate server.

The Data Forwarding option for Enterprise Historian Connect supports Historyconfiguration, collection, and storage for forwarding to distributed logs on anEnterprise Historian Consolidate server. Historical storage is limited to primarylogs. Secondary logs are not supported. Off-line storage is not supported either.Without this option, History Services functionality is limited to History accesssupport for Display Services, DataDirect, Desktop Trends, and User API.

ations that Use History ServicesEnterprise Historian stores process data, events, and production data. The historicaldata collected and stored by History Services is available for use in otherapplications. For instance:

It is available to Pavilion Insights for data analysis and process modeling.

It can be presented on Enterprise Historian display applications such as DisplayServices, DataDirect, and Desktop Trends. These applications let you view dataover 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 anddesktop Trend into the Operate IT Display system, either as web pages orActiveX controls.

It can be displayed on AdvaCommand trend displays for the Advant OCS, andon Multibus-based trend displays (MOD 300 only).

Section 2 Basic Software Components Applications that Use History Services

3BUF 0

Data can be stored long term on disk. Archive supports copying data to a MagneticOptical (MO) Disk for extended data storage and data security.Historical data is often the basis for further evaluation and improvements of yourprocess. Display Services provide excellent trend presentation to help you evaluate00 987 R1 35

and manage your process in the most effective way.

History collects samples from various data sources that may be located in any nodeof the system, or in external devices such as PLCs. Some examples are:

Floating point and integer numerical values from process objects. These valuescan come from ABB Control Systems, and/or 3rd-party automation systemsand 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 datasources. A common application of history is to periodically store values of processvariables such as flows, temperatures, or tank levels. For example, to store the valueof a steam flow, your data source is the measured variable of the loop that controlsthe flow.

Process Data Storage Section 2 Basic Software Components

36

Process Data StorageProcess data is stored in numeric logs built within the composite log structure. Acomposite log can be as simple as a single primary log (a log that is connecteddirectly to a data source), Figure 5.

Figu

D

Dat3BUF 000 987 R1

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.

Figure 5. Example - Simple Primary Log

Figure 6. Example - Primary Log with Secondary Log Storing Calculated Average

re 7. Example - Redundant Data Collection with Dual Log Distributed to a Remote Node

$HSTC100,MEASURE-1-oData Source

$HSTC100,MEASURE-1-o

ata Source

$HSTC100,MEASURE-2-oAverage

Secondary LogPrimary Log

Node C

Node B

Node A


a Source

$HSTC100,MEASURE-3-oPrimary Log

Primary Log

Distributed Log$HSTC100,MEASURE-2-o

Section 2 Basic Software Components Process Data Storage

3BUF 0

$HSTC100,MEASURE-1-oData Source


Data

Data00 987 R1 37

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

Figure 8. Example - Remote Node Consolidating Primary Logs from Multiple Nodes

$HSTC200,MEASURE-1-oSource

$HSTC300,MEASURE-1-oSource

Node A

Node B

Node C




38

CalculationsYou can configure History to perform calculations on collected data before the datais actually stored in the log. The types of calculations you can specify are:

DS3BUF 000 987 R1

AVERAGEMAXIMUMMINIMUMINSTANTANEOUS - no calculation (default)SUMSUM_OF_ SQRSSTANDARD DEVIATIONNUM_OF_ VALUES

You can specify calculations to be done on data before it is stored in a log (eitherprimary or secondary), Figure 9. This lets you store a single value to represent alarger time span of values. For example, you can sample a variable every minute andput 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 calculatedvalues in secondary logs.

Figure 9. Calculations

Calculation

OR

DataSource

ataource Calculation

Primary Log

Primary Log Secondary Log


3BUF 0

Data CompactionData 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 be00 987 R1 39

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 notreplaced (overwritten) as quickly.

Compaction is specified on an individual log basis. You may use it for some logsand not for others. Compaction should not be used indiscriminately in all cases. Forinstance:

If you want an accurate representation of your process over time, and you donot require that every data sample be stored, you can use compaction.

If your application requires that every data sample be stored as an instance inthe 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 aresaved.

Figure 10 shows how samples are stored when deadband is active. The deadbandfunction holds each sample until it determines whether or not the sample is requiredto 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 untilthe next sample at 20s. Since there is no change in slope between 0s and 20s, the 10ssample is discarded and the 20s sample is held. This pattern is repeated at each 10-second interval until a change in slope is detected at 50s. When this occurs, thesamples at 40s and 50s are stored to plot the change. At 90s another change in slopeis detected, so the samples at 80s and 90s are stored.


40

Even though there are spikes between 80s and 90s, these values were not sampled sothe slope remains constant (as indicated by the dotted line). Another change in slopeis 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

Samp

0

Dead

Comsam

103BUF 000 987 R1

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 theDeadband Storage Interval.

Compaction effectively increases the log period so the same number of samplesstored (as determined by the log capacity) cover a longer period of time.

Figure 10. Data Compaction Example

le & Storage Interval = 10s

40 80 120 160

band Storage Interval = 40s

paction activated,ple stored

180 200100 1406020

Samples stored at these Storage Intervals to plot the trend

Samples stored at these Intervalsbecause Deadband Storage Intervalelapsed since last sample stored

30 50 70 90 110 130 150 170 190


3BUF 0

Composite Log ApplicationsTo learn more about composite log applications see:

Secondary Logs for Different Resolution/Time Span Views on page 4200 987 R1 41

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


42

Secondary Logs for Different Resolution/Time Span ViewsYou can provide different views of a process variable by configuring a different timespan for each individual log in the composite log. For example, in Figure 11 theprimary log HSTC100,MEASURE-1-o stores high resolution data for a short time

TC103BUF 000 987 R1

span, while secondary logs HSTC100,MEASURE-2-o and HSTC100,MEASURE-3-o store progressively lower resolution data for longer time spans. Thisconfiguration also lets you store data over longer periods using less storage capacity.

Figure 11. Example, Secondary Logs with Different Views of a Process Variable




Storage Rate: 10 secondsTime period: 2 Weeks

Primary Log

Storage Rate: 1 MinuteTime period: 13 Weeks

Secondary Log

Storage Rate: 1 HourTime period: 104 Weeks

Secondary Log0.Measure

Calculation: Instantaneous

Calculation: Average

Calculation: Average


3BUF 0

Primary and Secondary Logs with CalculationsYou can configure a calculation algorithm in a primary or secondary log to storeother aspects of the logged variable such as maximum and minimum values for aspecified time interval. The calculation is performed before the data is stored in the00 987 R1 43

log. This allows you to store a single value that represents a larger time span ofvalues, or key characteristics of the data. For example, you can sample a variableevery minute and put those values into a primary log. Then you can configure thatan hourly average, minimum, and maximum be calculated from data in the primarylog and store those values in secondary logs. This example is illustrated inFigure 12.

Figure 12. Example, Composite Log using Calculations


44

Lab Data Logs for Asynchronous User InputLab data logs are a special type of numeric log. This log type is used to collectasynchronous data entered manually or via an external application such as a UserAPI program. Asynchronous logs must be Oracle-based.

Lab Dawith ot3BUF 000 987 R1

Lab Data logs must be primary logs. You can add a Lab Data log alone, or as part ofa composite where other primary logs are already connected, Figure 13.

When configured with synchronous logs, the asynchronous log does not receivedata from the data source. The connection is only graphical in this case.

Figure 13. Representation of Lab Data Log in Composite Log Hierarchy

ta Log in a compositeher numeric logs

Lab Data LogAlone


3BUF 0

Consolidating History Data with Distributed LogsMoving data from an Enterprise Historian Collect or Connect server to aConsolidate server is accomplished via distributed logs. A distributed log is asecondary log that resides on a remote node. This composite log structure lets you00 987 R1 45

consolidate history data from one or more servers located to one or more ABB OCSnetworks, on a remote Consolidate History server on the TCP/IP network. Aconsolidation server may also receive data from an Enterprise Historian Connectserver which is collecting data from PLCs and forwarding to the consolidationserver.

For example, in Figure 14 primary logs 1-1, 2-1, and 3-1 reside on History nodes onan ABB OCS network. Their respective secondary logs reside on remote Historyserver C on the TCP/IP network. Although not shown in Figure 14, History Node Cmay contain a secondary log that collects data from a primary log in a History serveron another ABB OCS network as well.

Figure 14. Example, Distributed Logs

History Node C

TCP/IP Network

History Node A History Node B

log2-1log1-1 log3-1

log1-2 log2-2 log3-2

ABB OCS Network


46

Performance ConsiderationsYou can configure a maximum of 50,000 distributed logs on the Consolidate serveron the TCP/IP network. Each ABB OCS network server can distribute up to 10,000logs to a Consolidate server on the TCP/IP network. Thus, you can consolidate data

U

3rd-pa3BUF 000 987 R1

from up to five ABB network servers, where each ABB network server distributes10,000 data sources, Figure 15. This limit (50,000) is based on each data sourcehaving a single primary log with no secondary logs. Additional primary orsecondary 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.

Distributed Log Applications

Some common applications for distributed logs are described in:

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

Figure 15. Distributed Log Capacity

TCP/IP network

History Server 1

ABB OCS network

p to 10,000 Data Sources

TCP/IP Network Consolidate History ServerUp to 50,000 Distributed Sources

History Server 5Up to 10,000 Data Sources

rty network


3BUF 0

Collecting Data for Longer Time Period at Consolidate LevelIn Figure 16, the primary log on the Enterprise Historian Collect server maintainsHistory data for a 5-week time period, while the secondary log on the Consolidateserver collects from the primary log and maintains the data for a 1-year time period.00 987 R1 47

Composite Log with Local and Distributed Secondary LogsThe composite log may have additional secondary logs performing other functions(for instance, calculations) on the Enterprise Historian Collect server. You can insertadditional secondary logs on the Enterprise Historian Collect server along with thedistributed logs on the Consolidate server. An example is shown in Figure 17.

Figure 16. Storing Data for a Longer Time Period on the Enterprise Node

Figure 17. Composite Log with Local and Distributed Secondary Logs

Secondary Log on eng169 (Consolidate Server)Primary Log on roc175

Additional Secondary Logs Inserted on Local Server

Secondary Log on eng169 (Consolidate Server)


48

Calculated Values on both Collect and Consolidate LevelsIn Figure 18, the secondary logs on the Enterprise Historian Collect server calculateaverage and standard deviation values and maintain the History data for a 5-weektime period, while the secondary logs on the Consolidate server collect those3BUF 000 987 R1

calculated values and maintain them for a 1-year time period.

Collection from Enterprise Historian ConnectIn Figure 19, the log on the Enterprise Historian Connect server acts as a store andforward buffer for the instantaneous log on the Consolidate server. Average andStandard Deviation calculations are then performed. Note that only primary logs canbe configured on the Enterprise Historian Connect server.

It is important to include the instantaneous log on the Consolidate server as abuffer between the instantaneous log on the Enterprise Historian Connect server andthe calculation logs (Average and Standard Deviation) on the Consolidate server.Without this buffer, each calculation log would be forced to collect data from theEnterprise Historian Connect server independently and would significantly increasetraffic on the TCP/IP network.

Figure 18. Calculations on Both Local and Consolidate Nodes

Figure 19. Calculations on Consolidate Node Only


3BUF 0

Collecting from Remote History LogsThis functionality may be used for the following applications:

When you have an existing database configuration, and you want to create

Histo

AB

T

$H

$H

111.200 987 R1 49

distributed logs without having to re-configure the existing composite logs.

When using Enterprise Historian Consolidate to collect from History serversrunning earlier versions of Enterprise Historian software (version 3.1 for NT or2.2 for HP-UX). This is because you cannot configure composite distributedlogs 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.

Figure 20. Collecting from a Remote History Log

TCP/IP Network

History Consolidate Server

ry Server

B System Network 1

Controller 1

C101,MEASURE

TC101,MEASURE

TC10n,MEASURE

TC10n,MEASUREHistory Server

ABB System Network 2

TC101,MEASURE

TC10n,MEASURE

Controller 1

STC101,MEASURE-1-o111.222.33.44

STC10n,MEASURE-1-o111.222.33.44

$HSTC101,MEASURE-1-0111.222.33.55

$HSTC10n,MEASURE-1-0111.222.33.55

22.33.44 111.222.33.55

TC101,MEASURE

TC10n,MEASURE


50

Dual Configuration for Data SecurityDual logs are a special type of numeric log for redundant data collection andstorage. A dual log has two identical log configurations that reside on two differentnodes. Both logs collect data from the same data source. As an option, you can

ABB O3BUF 000 987 R1

configure a secondary log for the dual log on a third node. For example, in Figure 21log1-3 in node C can collect data from either log1-1(in Node A) or from log1-2 (inNode B), depending on the availability of the given nodes. All History servers inthis 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 tolog 1-2, it continues to be used as the source for log 1-3, even if log1-1 becomesavailable again, until log1-3 is restarted, or log1-2 becomes unavailable.

Figure 21. Example, Distributed Logs for Redundant Data Collection

TCP/IP Network

History Server A History Server B

log1-1 log1-2

log1-3

CS NetworkData Source

DualLog

History Server C


3BUF 0

You can build a hierarchy of dual logs, and distribute the data from a dual log to aremote node, Figure 22.

Showson the

Dual Lto a Re00 987 R1 51

Figure 22. Example Hierarchy of Dual Logs

Sequen:1Sequen:3

Sequen:5

roc175

Sequen:2Sequen:4

Sequen:6

eng159

how logs are distributedir respective nodes

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

View as shown inComposite Log Window

og Distributedmote Node


52

Collecting from OPC Data SourcesHistory 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 andthe Accuray Object Server. Third party OPC servers are supported as well.

$HS

Ho

$HS

$H3BUF 000 987 R1

Figure 23 shows an example of OPC data collection.

Figure 23. Example, OPC Data Collection

OPC

OPC Server PLC

DeviceDriver

TC101,VALUE-1-o

istory Servicesn Windows 2000

TC10n,VALUE-1-o

NAME

Loop1_PV

Loop2_PV

STC102,VALUE-1-o

Loopn_PV

R101

REGISTERS

R102

R10n


3BUF 0

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 simple00 987 R1 53

graphs of process variables versus time, as shown in the following figure.

All analog and digital attributes recorded in History can be trended. Trend sourcescan be changed and multiple trends can be displayed on one chart to compare othertags and attributes. Stored process data may also be viewed in tabular format inMicrosoft Excel using DataDirect add-ins.

Figure 24. Historical Data on a Trend Display


54

Seamless RetrievalSeamless retrieval makes it easier for applications to access historical data. For trenddata representation, when scrolling back in time beyond the capacity of the specifiedlog, the seamless retrieval function will go to the next (secondary) log in the log3BUF 000 987 R1

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, andretrieval type can be specified and History will search for the log which most closelyfits the profile.

Numeric Data Storage ConsiderationsLog entries can be stored in either Oracle tables or directly in files maintained byHistory. File storage is faster and uses less disk space than Oracle storage. File-based 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 logsare appropriate for logs that have faster sample rates (5 minutes or less). For logswith slower sample rates (greater than 5 minutes), Type 1 logs should be used. Type1 logs should also be used any time you need the additional functionality theysupport.

Off-line StorageAll 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 onpage 61.

Section 2 Basic Software Components Event Data Storage

3BUF 0

Event Data StorageMessage Logs store events and system messages generated by control and operatorapplications. There are three different types of message logs available, depending onwhere the events are originating from and what functionality is needed:00 987 R1 55

Generic Event Storage. This event storage is modeled after the datadefinitions in the OPC/Alarm and Event specification. It supports a number ofvendor specific attributes. This storage mechanism holds batch related eventsfrom Produce IT Batch and the electronic logbook from Produce IT ElectronicBatch Record (EBR).

Audit Trail. This is a specialized version of the Generic Event Storage. It isused to track changes made to production data. The Audit Trail message logkeeps 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 otherinformation.

The Audit Trail is used extensively by Produce IT EBR to manage changesmade in the manual entry forms as data is being entered into the system.

Advant OCS messages. This storage type supports message and event loggingfrom Advant OCS systems - systems with MOD300 or Master software.

For MOD300 systems, message logs store CCF and TCL messages as wellas operator action messages such as parameter change and logon/logoff.

For Master systems the event log stores events that are generated from thecontrol applications in the AC400 series controllers and MasterPiececontrollers.

Message logs are stored in the Enterprise Historian Oracle database. Clientapplications such as Display Services and DataDirect access Oracle-based Historydata, including message logs, via an ADO data provider.

Production Data Storage Section 2 Basic Software Components

56

Event Presentation

All events stored in the Enterprise Historian can be displayed in DataDirect, using adialog that supports easy selection of query criteria (such as displaying all thealarms for a tag over a certain period of time).

Produ3BUF 000 987 R1

Since the events are stored in Oracle it is also possible to query them using standardSQL requests. This will commonly be done when reading messages into reportpackages and other tools capable of accessing data via SQL or ODBC.

Off-line StorageAll events and messages stored in a message log can be copied to an off-line storagemedia. This can be done on a cyclic or manual basis. See Off-line Storage andAccess on page 61.

ction Data StorageProduction 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 formatstorage mechanism where the data to be stored is sent to it by an application. Inmost cases, the PDL has been used with ABB batch and production managementpackages in the pharmaceutical, biotechnology and chemical industries.

Often when a batch is being produced, the information associations are not timerelated and cannot be pre-configured or anticipated. PDL has built-in provisions forthe storage and retrieval of this type of information. PDL organizes critical data suchas task (campaign, batch, unit procedure, operation) start/stop and duration times,operator interventions, alarm and events and equipment usage, and manages therelationships between each of these different types of information.

With each of the tasks it is possible to store additional information. For example, ifthe task is a heat phase, the initial temperature, target temperature and finaltemperature could be stored as information with that phase record. In a batchenvironment, this allows you to produce a complete batch record with the datastored in the PDL.

Section 2 Basic Software Components Production Data Storage

3BUF 0

History associations make an association to process data that is already being storedin the Historian. Typically, this association represents the period of time that abatch occupied a particular unit or a phase execution time period. The associationsare made for only those tags that are relevant. See Figure 25.00 987 R1 57

These associations make it easy to do batch-to-batch comparisons or to show datafrom 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 changesmade to it) are stored in the PDL. Later, the recipe can be retrieved for viewing inthe same procedure editor in Produce IT Batch

Figure 25. Batch Record in PDL

Production Data Storage Section 2 Basic Software Components

58

Off-line StorageAll data contained in a PDL and the data associated with that PDL are treated as asingle entity by the Enterprise Historian. This means that when a PDL is archived toa removable media, all the data stored in the PDL and any associations made from3BUF 000 987 R1

that production record to other data in the historian is archived together. Then whenthe record for a batch has to be reviewed a number of years later, all the data for thatbatch is accessed as a single entity. Archiving can be done automatically atcampaign end or batch end. PDLs can also be automatically deleted after they havebeen archived if so desired.

Presentation

PDL data is stored in Oracle tables and is accessible by standard SQL queries. Theinformation 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 thatfacilitates convenient browsing of the data stored in a PDL, allowing you to drilldown 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 drilldown into the batches that are a part of it. This information can be easily written to aworksheet in Excel.

Section 2 Basic Software Components Production Data Storage

3BUF 000 987 R1 59

Figure 26. PDL Dialog in DataDirect

Finished Report Storage Section 2 Basic Software Components

60

Finished Report StorageThe purpose of a report log is to hold the finished output from reports scheduled andexecuted via the Inform IT Enterprise Historian Report Scheduler. The reportschedule must specify that the report is to be saved to a specific report log3BUF 000 987 R1

configured via the History Builder. This procedure is described in the ReportServices Operation Manual.

Reports stored in a report log can be archived to a removable media on either acyclic or manual basis. Access to archived reports logs is supported through theReport Scheduler. When reviewing a restored report log, it will be presented in thetool appropriate for the type of file the report was saved as (i.e. Internet Explorerwill be launched if the report was saved in .html format).Generally you dedicate one report log to one report. For instance, if you have aWKLY_SUM report, you make a log especially for it. You put each weeks versionof the WKLY_SUM report into the report log and use different report logs for otherreports. However, you are not required to do it this way. You are free to send morethan one type of report to one report log. For each report you can specify how manyoccurrences of the report to save.

Section 2 Basic Software Components Off-line Storage and Access

3BUF 0

Off-line Storage and AccessWhen a log is full, the oldest entries are replaced by new entries, or deleted. Toavoid losing History data in this way, you can set up an archival system thatmaintains a complete and permanent record of all entries for specified logs.

Ar

1a - Sruntim

1b - Crecord

2a - Sfrom a

2b - Erestor00 987 R1 61

Archiving copies the log entries for a specific time period from the history databaseto a designated archive device. When you need to access archived History data, youcan restore the archived logs to the History database, or publish one or moreselected volumes for direct viewing. (Publishing applies to numeric logs only.) Anoverview of this process is illustrated in Figure 27.

Figure 27. Archive and Restore

History Database Configuration

Runtime Database


$HSTCnnn.MEASURE-1-o

chive Database

Archive Entry 1

Archive Entry n

Restored Database

$HSTC100,MEASURE-1-r

$HSTCnnn.MEASURE-1-r

History Node

Volume 1

Volume n

Archive Device

External Application:Display ServicesDataDirectUser APIOCS Trend Display

1a

1b

pecified logs copied frome database to archive media

orresponding archive entryed in archive database

pecified archive entry restoredrchive media to restored database

xternal application accesses

2a

2b

ed logs

History Database Configuration Section 2 Basic Software Components

62

Archiving can be scheduled to occur periodically (timed), or you can execute amanual archive on demand. Archive can also occur after an event such as the end ofa batch process.

When a timed or manual archive is requested, runtime logs are copied from the

Histor

Disp3BUF 000 987 R1

runtime History database to an archive media. The runtime history database iswhere on-going (current) storage of history data occurs.In addition to this, a corresponding archive entry is recorded in the archive databaseon both the History server and the archive media. The archive entry indicates thevolume ID, archive time, number of logs in the entry, archive group, and otherrelated information which is used when you want to restore archived logs.

y Database ConfigurationYou can configure the History database during the system engineering phase of aproject, or during runtime.Generally, the History database is configured in part using the History Builder, andthen the majority of History configuration is finished using the dbConfig utility.This utility processes text files, and is very efficient for creating largeconfigurations.

lay ServicesDisplay Services supports building and viewing dynamic real-time and historicaldisplays on up to 32 simultaneous local and remote display clients connected to adisplay server. Information can be collected from multiple sources and displayedwithin the same display. Data entry and interactive query capabilities are built intothe package. This helps you create solutions that greatly simplify exploration ofinformation.

The Enterprise Historian architecture supports access to data not only from theEnterprise Historian environment, but also to data from other sources via dataprovider connections to the Display Services server.

This architecture provides a cost-effective graphics building and monitoringcapability throughout your facility, Figure 28. The user interface environment canbe distributed throughout a facility on a variety of platforms to provide process and

Section 2 Basic Software Components Display Services

3BUF 0

production information. Supported platforms are PCs with Windows 2000 orWindows NT, and X-windows.

AdvEnterHisto

HP-UX00 987 R1 63

Figure 28. Display Services Architecture

Corporate network users

Localusers

Remote users

Corporate WAN

Local PlantNetworks

ControlNetworks

Localusers

Local PlantNetworks

ControlNetworks

antpriserianor NT

Advant EnterpriseHistorian

HP-UX or NT

Display Services Section 2 Basic Software Components

64

The displays you build with Display Services provide a user interface into yourprocess and production information, with access to other data sources through openstandard SQL or ODBC. An example is shown in Figure 29. Information can becollected from multiple sources and displayed in the same display. Displays can be3BUF 000 987 R1

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 youcreate effective display solutions that simplify an end users search forinformation.You can view information from one or more process automation,process support, or production management systems within a mill/plant or corporatenetwork.

Display Services follows Microsoft Windows standards and can be configured toprovide the look-and-feel of the operator console workplace or a plant informationterminal. All functions are mouse controlled. Runtime users need only basicoperator skills.

The displays are primarily for process monitoring, and

Inform IT Prod Guide

Documents

Transcript of Inform IT Prod Guide