Sunteți pe pagina 1din 344
B0193YL REV E I/A Series ® Information Suite AIM*Historian™ User’s Guide December 17, 2002
B0193YL REV E I/A Series ® Information Suite AIM*Historian™ User’s Guide December 17, 2002

B0193YL

REV E

I/A Series ® Information Suite AIM*Historian™ User’s Guide

December 17, 2002

B0193YL REV E I/A Series ® Information Suite AIM*Historian™ User’s Guide December 17, 2002

AIM*API, AIM*AT, AIM*Historian, AIM*SPC, Fox, Foxboro, and I/A Series are registered trademarks of Invensys Systems, Inc. Invensys is a trademark of Invensys plc. Access, Windows, and Windows NT are registered trademarks of Microsoft Corporation.

Applicom is a trademark of Applicom International. BASEstar is a trademark of Compaq Computer Corporation. Computer Highway Interface Program (CHIP) is a trademark of Fisher-Rosemount Systems.

Informix is a trademark of IBM Corporation.

Modbus and ModbusPlus are trademarks of AEG Schneider Automation, Inc. OPC is a trademark of the OPC Foundation.

Oracle is a trademark of Oracle Corporation. Sun and Solaris are registered trademarks of Sun Microsystems, Inc. UNIX is a registered trademark of X/Open Company Ltd. All other brand names may be trademarks of their respective companies.

Copyright 1999-2002 Invensys Systems, Inc. All rights reserved

SOFTWARE LICENSE AND COPYRIGHT INFORMATION

Before using the Invensys Systems, Inc. supplied software supported by this documentation, you should read and understand the following information concerning copyrighted software.

1. The license provisions in the software license for your system govern your obligations and usage rights to the software described in this documentation. If any portion of those license provisions is violated, Invensys Systems, Inc. will no longer provide you with support services and assumes no further responsibilities for your system or its operation.

2. All software issued by Invensys Systems, Inc. and copies of the software that you are specifically permitted to make, are protected in accordance with Federal copyright laws. It is illegal to make copies of any software media provided to you by Invensys Systems, Inc. for any purpose other than those purposes mentioned in the software license

Contents

Figures

xi

Tables

xv

Preface

xvii

Who Should Read This Book

xvii

What You Should Know

xvii

Revision Information

xviii

Related Documents

xix

Document Overview

xix

Conventions

xxi

Request for Comments

xxii

1. Overview

1

AIM*Historian Features

1

AIM*Historian Architecture

2

AIM*Historian Product Structure

3

AIM*Historian Instance

3

Instance Components

4

Collectors

4

Default Collector Configuration

5

I/A Series Real-Time Collector

5

I/A Series Event Message Collector

5

I/O Gate Data Collector

6

Real-Time Points

7

Time Stamps

9

Collection Frequency

9

Event Messages

9

Control Groups

11

Reduction Groups

12

AIM*Historian Interface Structure

13

AIM*API Interface

15

ODBC Interface

15

I/A Series Interface

15

Export to Oracle

15

AIM*AT OPC Server

15

AIM*AT OLE DB Provider

15

B0193YL – Rev E

Contents

2. AIM*Historian Configuration

17

AIM*Historian Configuration Tools

17

AIM*Historian Configurator Window

18

Configuring Server Connections for Wizard Browsing

19

Starting the AIM*Historian Configurator

20

Selecting an Instance

22

AIM*Historian Components Tree

24

Configuration File Windows

24

Application Menu Bar

26

Command Buttons

26

Creating an AIM*Historian Instance

27

Configuring Real-time Points

28

Adding RTPs with the Data Object Wizard

29

Filter Page Controls

29

AIM*AT Server Filter

31

I/A Series Compound-Block Filter

33

Parameter Type Filter

35

Filtering by I/A Series Descriptions

36

Searching Dialog Box

37

Results Page

38

Defining the RTP Configuration

41

Configuring Messages

42

Creating Control Groups

45

Adding Reduction Groups

50

Editing Configuration Files

55

Instance Configuration File

55

RTP Configuration Window

56

Editing RTPs

57

Deleting RTPs

59

Adding a Collector

59

Other Configuration File Windows

62

Server Status

62

Finishing an AIM*Historian Configurator Session

63

Configuration Using Input Text Files

64

Instance Configuration

65

Collector Stations

68

Real-Time Points

69

Event Message Configuration

72

I/A Series Legacy Message Groups

72

I/A Series Alarms

74

Reduction Groups

76

Control Groups

77

Committing the Session

77

Permanent Delete

78

Contents

B0193YL Rev E

Using histsave

79

Instance Configuration with histbatch

81

Instance Configuration with histcbatch

83

Modifying Maximum Value Attributes

84

3. AIM*Historian Operation

87

AIM*Historian Manager Window

87

Application Menu Bar and Tool Bar

89

AIM*Historian Components Tree

91

Tree Menu

92

AIM*Historian Manager Pages

93

On/Off Controls

93

Server Page

94

Instance Page

94

Collector Page

96

Communications Page

97

Log File Page

99

Configuration Tools

100

Displaying Process History

100

An Overview of the AIM*Historian Data Display

100

Starting the AIM*Historian Data Display

101

Defining the Sampled RTP Data to Display

102

Saving, Opening, and Deleting Configurations

103

Selecting the AIM*Historian Instance and Server

103

Specifying the Time Interval and Data Type for the RTPs

103

Assigning RTPs to Report Columns

104

Viewing the Data Report or Trend Display

105

Exiting the AIM*Historian Data Display

105

Viewing the Data Report

105

The Data Report Window Format

106

Using the Data Report Menu Bar

107

Printing Reports

107

Printer Setup

108

Viewing the Data Trend Display

111

Manual Data Entry

112

Annotating MDE Values

115

AIM*Historian Archiver

116

AIM*Historian Spy

116

Server Status

119

AIM*Historian Demand Writes

120

Legacy Interface Servers

122

Starting Legacy Servers for Local Instances

122

Starting Legacy Servers for Remote Instances

123

B0193YL Rev E

Contents

Stopping AIM*Historian

124

4.

Database Management

127

AIM*Historian Database

127

File Maintenance Functions

128

Configuration Files

129

Event Message Files

130

Sample Files

130

Reduced RTP Files

131

Deleting an AIM*Historian Instance

132

Optimizing Disk Space Usage for RTP Files

133

Starting the DB Wizard

134

Selecting an AIM*Historian Instance

135

Using the Optimization Window

137

Using the DB Wizard Menus and Tool Bar

138

Filtering the RTP List

138

RTP Information Displayed in the Optimization Window

140

Selecting RTPs

140

Optimizing RTP Sample File Disk Usage

141

Reviewing Results

143

On-Demand Archiving

143

AIM*Historian Archiver Window

144

Application Menu Bar and Tool Bar

145

Selecting Database Files

147

Selecting an AIM*Historian Instance

149

Locating a File in the Database List

150

Filtering the Database List

151

Checking Files

152

Deleting Database Files

152

Moving Database Files

153

Copying Database Files

153

Using the AutoArchiver

154

AutoArchiver Features

154

AutoArchiver Configuration

156

AutoArchiver Test Mode

160

Display of Archived Files

161

5.

Troubleshooting

163

Version Information

163

Troubleshooting Tools

164

Diagnostic Utilities

166

clearcfg

168

dumpcvs

168

dumprcol

169

dumpred

172

Contents

B0193YL Rev E

histspy

172

apitst

173

Example 1

173

Example 2

175

Example 3

175

Example 4

176

Example 5

176

msgcheck

176

Known Problems

177

msgfix

178

Known Problems

179

msgtst

180

sec2asc

181

rtpcheck

181

rtpfix

183

testhv

184

testvar

186

xrebuild

188

fh_sacego

189

Stub Library for Off-Platform Testing

189

Tailoring Default Collector Stub Values

190

Troubleshooting Procedures

190

No RTP Values Inserted in .fdb Files

192

No Event Messages Inserted in .fdb Files

193

No RTP Values or Event Messages Inserted in .fdb Files

193

No TCP/IP Connection to Remote Collector

194

AIM*Historian Client Cannot Connect with Server

195

AIM*Historian Data Not in Trend Display

195

Incorrect AIM*Historian Data in Trend Display

197

Unexplained Program Crashes; Inability to Start Programs

198

Sample vmstat Output

199

Adding Swap Space

199

Appendix A. Error Codes

201

Error Codes Returned by AIM*API

201

Appendix B. AIM*Historian Sample Status and Quality

207

Status Definition for I/A Series Version 4.3 and Later

207

RTP Value Types

209

Quality Definition

211

Appendix C. AIM*Historian Reduction Status and Quality

213

Appendix D. Data Reduction Algorithms

215

Data Reduction Formulas

215

B0193YL Rev E

Contents

I/A Series and AIM*Historian Data Reduction

216

Configuring Reduction Intervals and Managing RTP Data Files

218

Overview of RTP Data File Choice

218

Time Stamps of Data in Reduction Files

218

Algorithm for Choosing File Type to Satisfy a Reduction Request

218

Configuring Reduction Intervals

219

Use of Sample Files

220

Examples

220

How Long to Keep Data Files

221

Appendix E. AIM*Historian Component Attributes

223

Session Component

225

Session Component How To

225

Session Attribute Descriptions

225

Instance Component

226

Instance Component How To

226

Instance Attribute Descriptions

228

Note on Reduction Intervals

236

Collector Component

237

Collector Component How To

237

Collector Station Attribute Descriptions

238

RTP Component

247

RTP Component How To

247

RTP Attribute Descriptions

249

Event Message Component

257

Event Message Component How To

257

Event Message Attribute Description

258

Control Group Component

260

Control Group Component How To

260

Control Group Attribute Descriptions

261

Reduction Group Component

263

Reduction Group Component How To

263

Reduction Group Attribute Descriptions

264

Note on Time Stamps

266

IATIME Parameter Change

266

Collector Time Format

267

TZ and DST Parameters

267

TZ Parameter

267

DST Parameter

267

Migrating Data from Previous Versions

268

Appendix F. Sizing Guidelines

269

Sizing Factors

269

RTP Samples

269

Contents

B0193YL Rev E

Reduction Values

270

Event Messages

270

Other Sizing Considerations

271

Finding an Appropriate Data Collection Rate

271

Data Collection Rate Parameters

271

Which Points to Collect

273

Specifying RTP File Sizes

273

Appendix G. Exporting to Oracle

275

HistExport

277

HistMove

278

Hist2Oracle

279

Data Export Configuration Files

279

The export.ini File

279

The msg.ini File

280

The hist2oracle.ini File

280

The createtables.sql Script File

281

Created Files

282

Database Tables

283

Database Table: msgs

283

Messages Table Example

284

Database Table: <msggroup>_<msgname>

285

Message Name Table Example

285

Database Table: rtps

287

RTP Table Example

288

Database Table: rtps_strings

289

String Type RTP Table Example

290

Database Table: rtps_numbers

291

Non-String RTP Table Example

292

Database Table: rgroup_data

293

Reduction Group Example

294

Running Data Export

295

Naming Conventions for Exported Files

296

Message Files

296

RTP Files

296

Reduction Groups

296

Appendix H. AIM*OLE DB Provider

297

Client/Server Architecture and Remote Access

297

Supported Standards

297

Installation and Authorization

297

Sample Project

298

Data Structures

298

B0193YL Rev E

Contents

Dictionary Schema

299

InstCfg

299

RTPCfg

300

MsgTableCfg

301

MsgFieldCfg

301

CollectorStationCfg

302

ControlGroupCfg

302

ControlGroupRTPs

303

ControlGroupMsgs

303

ReductionGroupCfg

303

REDUCTIONGroupRTPs

304

Message Schemas

304

RTP Data Schema

304

RTPEntries

304

LinearRTPEntries

305

AIM*OLE DB Provider Schemata

305

Usage

306

Connect Statement

306

Select Statement

309

Column Exp

310

Table Spec

310

Condition

311

Lexicon

311

Insert Statement

311

Index

313

Figures

1-1.

AIM*Historian Client/Server Architecture

2

1-2.

AIM*Historian Instance

4

1-3.

Sample Message Definition

10

1-4.

AIM*Historian Data Retrieval

14

1-5.

AIM*Historian Interface Structure

16

2-1.

AIM*Historian Configuration Overview

17

2-2.

Server Connection Dialog Box

19

2-3.

AIM*Historian Configurator Window

21

2-4.

Instance Selection Dialog Box

22

2-5.

Real Time Points Page

23

2-6.

AIM*Historian Components Tree

24

2-7.

AIM*Historian Configurator Window with Instance Configuration File Open

25

2-8.

Create AIM*Historian Instance Dialog Box

27

2-9.

Real Time Points Page

28

2-10.

Data Object Wizard Filter Controls

29

2-11.

Selected Server Stations Dialogue Box

30

2-12.

Data Object Wizard Server Filter Page

32

2-13.

Compound-Block Filter Page Sorted by Compound

33

2-14.

Compound-Block Filter Page Sorted by Block

34

2-15.

Parameter Type Filter Page

35

2-16.

Description Filter Page

36

2-17.

Object Search Dialog Box

37

2-18.

Data Object Wizard Results Page

38

2-19.

Add Item Dialog Box

39

2-20.

Data Object Tree in the RTP/Message Dialog Box

40

2-21.

Messages Page

42

2-22.

Message Definition Dialog Box

43

2-23.

New Key Dialog Box

44

2-24.

Control Page in the Groups Dialog Box

45

2-25.

Control Group Dialog Box

46

2-26.

Trigger RTPs Dialog Box

47

2-27.

Controlled RTPs Dialog Box

48

2-28.

Controlled Messages Dialog Box

49

2-29.

Reduction Group Dialog Box

51

2-30.

Parameters Dialog Box

52

2-31.

Reduction Group RTPs Dialog Box

53

2-32.

Reduction Group Operations Dialog Box

54

2-33.

AIM*Historian Cfg Window and Instance Parameters

55

2-34.

RTP Configuration Window

57

2-35.

Edit RTP Window

58

2-36.

Collector Station Configuration File Window

60

2-37.

Collector Station Type Dialog Box

60

2-38.

Collector Setup Window

61

2-39.

Server Status Dialog Box

62

B0193YL Rev E

Figures

2-40.

Closing Options Dialog Box

63

2-41.

Establishing the Instance

65

2-42.

Configuring Instance Attributes

66

2-43.

Configuring Instance Attributes, Continued

67

2-44.

Configuring a Remote I/O Gate Collector

68

2-45.

Configuring a Remote I/O Gate Collector, Continued

69

2-46.

Configuring an RTP

70

2-47.

Condensed Syntax for Configuring RTPs

71

2-48.

Updating RTP Configurations

71

2-49.

Configuring I/A Series Event Message Collection

73

2-50.

Configuring the iaalarm Message Group

74

2-51.

Replicating the Message Fields

75

2-52.

Configuring a Reduction Group

76

2-53.

Configuring a Control Group

77

2-54.

Committing the Configuration

77

2-55.

Deleting an RTP

78

2-56.

histsave Window

79

2-57.

histbatch Window

81

2-58.

Completed Configuration Session

82

2-59.

MAXIMA Input File

85

3-1.

AIM*Historian Manager Window

88

3-2.

AIM*Historian Components Tree

91

3-3.

On/Off Controls on the Instance and Collector Pages

93

3-4.

AIM*Historian Manager Server Page

94

3-5.

AIM*Historian Manager Instance Page

95

3-6.

AIM*Historian Manager Collector Page

97

3-7.

AIM*Historian Manager Communications Page

97

3-8.

AIM*Historian Manager Log File Page

99

3-9.

RTP Definition Window

102

3-10.

Data Report Window

105

3-11.

AIM*Historian Data Report Components

106

3-12.

Print Dialog Box for Solaris Systems

107

3-13.

Printer Setup Dialog Box for Solaris Systems

108

3-14.

Add Printer Dialog Box for Solaris Systems

109

3-15.

Modify Printer Dialog Box on Solaris Systems

109

3-16.

Delete Printer Dialog Box on Solaris Systems

110

3-17.

The Data Trend Display

111

3-18.

Manual Data Entry Window

112

3-19.

MDE Window Tool Bar

113

3-20.

MDE Annotation Window

115

3-21.

AIM*Historian histspy Window

116

3-22.

AIM*Historian Spy RTP Database File

117

3-23.

RTP Values Window

118

3-24.

Server Status Dialog Box

119

3-25.

AIM*AT Control Panel Applet Dialog Box

125

3-26.

AIM*Historian Page

125

4-1.

The AIM*Historian Instance Selection Dialog Box

135

4-2.

DB Wizard Optimization Window

137

Figures

B0193YL Rev E

4-3.

Filter Tools for Selectively Displaying RTPs

138

4-4.

Optimization Window Command Buttons

139

4-5.

Tools for Adjusting RTP Storage Load

141

4-6.

Estimated Results of a Read Delta Changes

141

4-7.

Dialog Box for Confirming Application of New Read Delta Attributes

142

4-8.

Dialog Box for Adjusting the AutoArchiver Configuration

143

4-9.

AIM*Historian Archiver Window

145

4-10.

Select AIM*Historian Instance Dialog Box

149

4-11.

Selecting Instances from the Tool Bar

149

4-12.

Go To File Dialog Box

150

4-13.

Filter File List Dialog Box

151

4-14.

AIM*Historian AutoArchiver Configurator Window

156

4-15.

AutoArchiver Scheduling Page

157

4-16.

AutoArchiver Sample Page

158

4-17.

Cfg and Xref Page in the AutoArchiver Window

160

4-18.

Display of Archived RTP Files in the AIM*Historian Spy Window

161

5-1.

Sample dumprcol Output

170

5-2.

Generating Hourly Reduced Values

174

5-3.

testvar Usage Synopsis

186

5-4.

Values Returned by testvar

187

G-1.

A Summary of the AIM*Historian Data Export Process

276

H-1.

AIM*OLE DB Provider Dialog Box

308

B0193YL Rev E

Figures

Tables

1-1.

RTP Data Types

8

1-2.

RTP Trigger Values

12

2-1.

AIM*Historian Configurator Application Menu Bar

26

2-2.

Message Definition Fields

43

2-3.

RTP Trigger Values

48

2-4.

Default AIM*Historian Installation Directories

64

3-1.

AIM*Historian Manager Functions

89

3-2.

Components Tree Pop-Up Menus

92

3-3.

Data Report Window Menu Bar

107

4-1.

Reduced RTP Files

131

4-2.

Samples and Storage for Different Deltas

133

4-3.

DB Wizard Functions

138

4-4.

RTP Information Provided in the Optimization Window

140

4-5.

Archivable Database Files

144

4-6.

AIM*Historian Archiver Functions

146

5-1.

Summary of Diagnostic Utilities

166

5-2.

Circular File Header Fields in dumprcol Output

171

5-3.

No RTP Values Inserted in .fdb Files

192

5-4.

No Event Messages Inserted in .fdb Files

193

5-5.

No RTP Values or Event Messages Inserted in .fdb Files

193

5-6.

No TCP/IP Connection Between histreceive and histsend

at the Remote Collector

194

5-7.

Error Message “Server Name Unknown”

195

5-8.

Failure to Display AIM*Historian Data in Trend Display

195

5-9.

Incorrect AIM*Historian Data in Trend Display

197

5-10.

Unexplained Crashes; Inability to Start Programs

198

A-1.

AIM*API Function Returns

201

A-2.

AIM*API Error Codes

201

B-1.

Status Definition with I/A Series Version 4.3 and Later

207

B-2.

RTP Value Types

209

B-3.

RTP Quality Definition with I/A Series Version 4.2 and Later

211

C-1.

Status Returned by Reductions APIs

213

C-2.

Reduction Value Types

214

D-1.

Algorithms for Reducing Data

215

D-2.

Supported Reduction Operations

217

D-3.

Selection of Sample Files for a Reduction Request

220

D-4.

Selection of Reduced Data Files for a Reduction Request

221

D-5.

Selection of Medium and Fast Reduction Files for a Reduction Request

221

E-1.

AIM*Historian Components

224

E-2.

AIM*Historian Defined Actions

224

E-3.

AIM*Historian Session Attributes

225

E-4.

AIM*Historian Instance Component Attributes

228

E-5.

Collector Station Component Attribute

239

E-6.

TZ Attribute Values

246

 

B0193YL Rev E

Tables

E-7.

RTP Component Attributes

249

E-8.

RPT Data Types

256

E-9.

Event Message Component Attributes

258

E-10.

Control Group Component Attributes

261

E-11.

Reduction Group Component Attributes

264

G-1.

Oracle Database Tables Used to Store Historian Data

283

G-2.

Columns in the msgs Database Table

283

G-3.

Columns in the <msggroup>_<msgname> Database Table

285

G-4.

Columns in the rtps Database Table

287

G-5.

Columns in the rtps_strings Database Table

289

G-6.

Columns in the rtps_numbers Database Table

291

G-7.

Columns in the rgroup_data Database Table

293

H-1.

AIM*OLE DB Provider Table Hierarchy

298

H-2.

AIM*OLE DB Provider Table InstCfg

299

H-3.

AIM*OLE DB Provider Table

300

H-4.

AIM*OLE DB Provider Table MsgTableCfg

301

H-5.

AIM*OLE DB Provider Table MsgFieldCfg

301

H-6.

AIM*OLE DB Provider Table CollectorStationCfg

302

H-7.

AIM*OLE DB Provider Table ControlGroupCfg

302

H-8.

AIM*OLE DB Provider Table ControlGroupRTPs

303

H-9.

AIM*OLE DB Provider Table ControlGroupMsgs

303

H-10.

AIM*OLE DB Provider Table ReductionGroupCfg

303

H-11.

AIM*OLE DB Provider Table ReductionGroupRTPs

304

H-12.

AIM*OLE DB Provider Table <MsgGroup>.<MsgName>

304

H-13.

AIM*OLE DB Provider Table RTPEntries

304

H-14.

AIM*OLE DB Provider LinearRTPEntries

305

H-15.

AIM*OLE DB Provider Schemata Tables

305

H-16.

Connect Arguments

307

H-17.

Lexical Elements Used in AIM*OLE DB Provider

311

Preface

The AIM*Historianclient/server software collects, stores, and archives process data from I/A Series ® nodes and other distributed control systems on the enterprise intranet. You can retrieve historical data stored in the AIM*Historian database and perform:

Graphical and statistical analysis

Regulatory and Batch reporting

Product quality analysis

Financial reporting.

This guide explains how to:

Configure AIM*Historian instances for collection, storage, and retrieval

Configure real-time point (RTP), message, reduction group, and control group components

Operate AIM*Historian instances

Maintain AIM*Historian databases

Troubleshoot instances.

Who Should Read This Book

This document is intended for process engineers, system administrators, developers using AIM*Historian data for other applications, and operators who are responsible for starting and stopping AIM*Historian instances.

What You Should Know

Prior to using this book, you should be familiar with the target control systems from which the AIM*Historian is to collect process data and have a working knowledge of the platforms involved in the applications.

B0193YL Rev E

Revision Information

Preface

For Version 3.2 of the AIM*AT, the following changes were made:

Chapter 1 Overview

Revised to describe AIM*Historian support for HPS Message Manager and sequence of events (SOE) data collection

Updated to include the AIM*Historian OLE DB Provider, an optional interface that provides access to AIM*Historian data from customer-developed OLE DB applications

Updated description of support for UTC time stamps when supplied by the I/A Series system or other control systems

Chapter 2 AIM*Historian Configuration

Modified to describe the revised histsave program.

Chapter 3 AIM*Historian Operation

Modified to describe new On/Off controls in the AIM*Historian Manager

Revised to reflect improved collector operation, implementation of the histstop command, and new start scripts for the Legacy Interfaces

Chapter 4 Database Management

Updated to include a description of the DB Wizard, which enables users to analyze data storage loads for an AIM*Historian instance and optimize the real-time point (RTP) configurations accordingly

Chapter 5 Troubleshooting

Modified to reflect changes in collector operation and changes to the dumprcol utility

Appendix A Error Codes

Updated to include new error codes related to collector operation

Appendix E AIM*Historian Component Attributes

Updated to reflect new instance and collector attributes

Appendix H AIM*OLE DB Provider

Added to describe a new interface for accessing AIM*Historian data.

Various minor changes have been made throughout the document to reflect changes made for Version 3.2.

Preface

Related Documents

B0193YL Rev E

The following documents provide information related to installing, maintaining, and sourcing AIM*Historian:

AIM*AT™ Installation Guide (B0193YM)

AIM*AT I/O Gate Drivers™ User’s Guide (B0193YU)

AIM*API™ User’s Guide (B0193YN)

AIM*SPC™ User’s Guide (B0193YH)

AIM*DataLink™ User’s Guide (B0193YJ)

AIM*Explorer™ User’s Guide (B0193YK)

AIM*API User’s Guide (B0193YN)

AIM*AT OPC Server User’s Guide (B0400DG)

AIM*Inform User’s Guide (B0400DS)

Wonderlink I/O Server User’s Guide (B0193YP)

NetAPI MFC Class User’s Guide (B0400BJ).

The following I/A Series documents provide information for AIM*Historian instances that access I/A Series data:

Historian (B0193BL)

Process Operation and Displays (B0193MM)

System Operation Guide (Windows NT Operating System) (B0400CR)

System Operation Guide (B0193CR).

Document Overview

This guide is organized into the following sections:

Chapter 1 Overview

Features, architecture and information about product structure.

Chapter 2 AIM*Historian Configuration

Using AIM*Historian Configurator and other tools to configure AIM*Historian instances and individual instance components such as RTP and Event message configuration files.

Chapter 3 AIM*Historian Operation

Using AIM*Historian Manager and other tools to start, monitor, and stop operation of AIM*Historian instances.

Chapter 4 Database Management

AIM*Historian file structure, database packing and reduction, and on-demand and automatic archiving.

B0193YL Rev E

Chapter 5 Troubleshooting

Preface

Diagnostic utilities and troubleshooting tables.

Appendix A Error Codes

Error codes returned by AIM*API calls to access AIM*Historian.

Appendix B AIM*Historian Sample Status and Quality

Description of the AIM*Historian RTP status word.

Appendix C AIM*Historian Reduction Status and Quality

Description of the status word returned by AIM*Historian reduction APIs.

Appendix D Data Reduction Algorithms

Table listing the algorithms for reducing data.

Appendix E AIM*Historian Component Attributes

Attribute descriptions of the AIM*Historian components.

Appendix F Sizing Guidelines

Information for determining the amount of disk space required to hold AIM*Historian database files.

Appendix G Exporting to Oracle

A description of the AIM*Historian interface for exporting RTP and mes- sage data to Oracle DBMS tables.

Appendix H AIM*OLE DB Provider

Documents the command interface and data structures used to access AIM*Historian data from customer-developed OLE DB applications.

Preface

Conventions

In this document, the following conventions are used:

B0193YL Rev E

Verbatim keyboard entries are shown in this type, while variable information is shown in italic. For example,

Invoke the sec2asc program.

sec2asc <Seconds>

In numbered instructions, this type is used for menu items, options, and buttons that are to be selected on the screen.

Instructions for making selections from the application menu bar and associated pull-down menus use the following format:

1. Choose File > New.

The example is shorthand for Pull down the File menu from the application menu bar and select the New option from the menu.

Instructions for using the mouse on Windows ® platforms assume the mouse is con- figured for the right hand, that is, the left mouse button is used for normal select and drag operations, and the right mouse button is used for context menus and special drag operations.

Appendix E AIM*Historian Component Attributesand other sections of this guide use the UNIX ® convention when giving file or directory names. If you have a Windows NT ® based system, please adjust these accordingly:

Prefix with drive letters such as d:

Use a backslash (\) instead of a forward slash (/)

Add .exe to the executable file name.

The table below lists the location of AIM*Historian programs and instances for vari- ous platforms if the AIM*Historian software was installed using default directories. The instruction examples in this guide assume the software was installed using the default locations.

Platform

Program Directory

Database Directory

Solaris ® Servers including I/A Series AW/AP51s

/opt/aim/bin

/opt/aim/inst

Windows NT Servers

c:\Program Files\aim\bin

c:\Program Files\aim\inst

I/A Series AW70s

d:\opt\aim\bin

d:\opt\aim\inst

B0193YL Rev E

Request for Comments

Preface

Please direct your comments and suggestions concerning the AIM*Historian, other AIM*AT products, and this documentation to:

Customer Satisfaction Center Invensys Systems, Inc. 33 Commercial Street Foxboro, MA 02035-2099 Telephone within the US: 866-746-6477 Telephone from outside the US: 508-549-2424 Facsimile: 508-549-4999

1. Overview

This chapter introduces AIM*Historian, describes the product architecture and the major software components, and defines key concepts used throughout this guide.

AIM*Historian is a client/server application that collects, organizes, and stores historical data. AIM*Historian accepts data from I/A Series systems and other types of automation and control systems, including distributed control systems (DCSs), programmable logic controllers, and supervisory control and data acquisition (SCADA) systems. Historical data can include real-time point (RTP) values and Event messages such as process alarms and Batch definition messages.

AIM*Historian Features

AIM*Historian provides diversified platform support and operates on network servers running any of the following:

Solaris 2.5.1 or later, including I/A Series AP/AW51s

Windows NT 4.0 or later, including I/A Series AW70s

Windows Terminal Server, including I/A Series Server 70s

Windows 2000

Windows XP Professional.

AIM*Historian and the I/A Series Historian can run on the same I/A Series node. You can migrate Historian configurations and data to an AIM*Historian instance (see AIM*Historian Instanceon page 3), but not vice versa. AIM*Historian can also emulate the I/A Series Historian and support the following I/A Series software:

Display Manager

FoxView

FoxAnalyst

I/A Series Report Package.

AIM*Historian supports other AIM*AT applications and sources data to AIM*Inform, AIM*DataLink, AIM*Explorer, and AIM*SPC, as well as to custom applications developed with AIM*API.

AIM*Historian also supports other programs using the libhist.a interface.

For backward compatibility only, you can interface with AIM*Historian using the I/A Series Historian servers supplied with AIM*Historian. However, the interface for I/A Series Historian servers does not support the AIM*Historian configuration function.

B0193YL Rev E

1. Overview

AIM*Historian operates on I/A Series stations and on corporate networks to provide these features:

Support for databases of up to 250,000 points each

Data collection from proprietary systems via the I/O Gate Data Collector and specific I/O Gate Drivers.

Support for numerous data types including:

Simple value types such as integers, floats, and booleans

Files and arrays

Binary large objects (BLOBS).

An ODBC driver that supports access to AIM*Historian from Windows desktops

Option to time stamp data in either coordinated universal time (UTC) or I/A Series time

Export of sample and message databases to Oracle ® DBMS applications.

AIM*Historian Architecture

An AIM*Historian instance contains a user-defined configuration that specifies the data to be col- lected and where to store the historized data.

Multiple AIM*Historian instances can reside on a host computer. For example, you can define one instance to collect recent data for support of local displays and define another instance for long-term collection and storage of plant-wide data. Each AIM*Historian instance has one server component and one or more data collector components. Figure 1-1 displays the AIM*Historian client/server architecture.

1-1 displays the AIM*Historian client/server architecture. The AIM*Historian instance server operates on Solaris and

The AIM*Historian instance server operates on Solaris and Windows NT stations including I/A Series AP/AWs

AIM*Historian Archives AIM*Historian Database Local Event Message and RTP Collector I/O Gate Collector

Remote I/A Series Event Message and Real-Time Collector

Remote I/A Series Event Message and Real-Time Collector I/O Gate Device Process Unit Process Unit Figure
I/O Gate Device
I/O Gate
Device

Process Unit

and Real-Time Collector I/O Gate Device Process Unit Process Unit Figure 1-1. AIM*Historian Client/Server
and Real-Time Collector I/O Gate Device Process Unit Process Unit Figure 1-1. AIM*Historian Client/Server

Process Unit

Figure 1-1. AIM*Historian Client/Server Architecture

1. Overview

B0193YL Rev E

The AIM*Historian server component performs the following tasks:

Manages additions to the AIM*Historian data repository from local or remote collectors

Manages AIM*Historian archives

Provides services to applications such as desktop displays and remote databases.

AIM*Historian collectors collect RTP and Event message data. When communication with the server component is not available, remote AIM*Historian collectors buffer the data.

AIM*Historian Product Structure

The AIM*Historian product structure consists of:

AIM*Historian instance

AIM*Historian database

AIM*Historian interface structure.

AIM*Historian Instance

An AIM*Historian instance consists of a set of configuration and database files residing on an AIM*Historian server. You can create, configure, and modify AIM*Historian instances using one of the following methods:

AIM*Historian Configurator (histcfg)

Batch configuration using a configuration input text file (histbatch or histcbatch)

AIM*API fh_Cfg() call.

AIM*Historian supports multiple instances on a single host computer. An AIM*Historian instance name must be unique within the host computer on which AIM*Historian is installed. However, AIM*Historian instance names on different host computers can be the same. The files associated with a specific AIM*Historian instance are stored in a separate directory in the /inst directory. The name of the separate directory is the instance name. For example, the hist01 instance files are stored in /opt/aim/inst/hist01.

B0193YL Rev E

Instance Components

1. Overview

An AIM*Historian instance consists of the following components:

One or more data collectors

Zero or more real-time points (RTPs)

Zero or more Event messages

Zero or more control groups

Zero or more reduction groups.

Figure 1-2 displays the components that represent an AIM*Historian instance.

AIM*Historian

Instance

an AIM*Historian instance. AIM*Historian Instance Data Collectors Reduction Groups Real-Time Points
an AIM*Historian instance. AIM*Historian Instance Data Collectors Reduction Groups Real-Time Points

Data

Collectors

instance. AIM*Historian Instance Data Collectors Reduction Groups Real-Time Points Control Groups Event
instance. AIM*Historian Instance Data Collectors Reduction Groups Real-Time Points Control Groups Event

Reduction

Groups

Real-Time

Points

Control

Groups

Reduction Groups Real-Time Points Control Groups Event Messages Figure 1-2. AIM*Historian Instance The

Event

Messages

Figure 1-2. AIM*Historian Instance

The principal instance program, histmain, activates the instance, checks for changes in the configuration, and processes optional control groups.

Collectors

AIM*Historian uses collectors to acquire and historize process data and messages (collector types are defined on page 5). An AIM*Historian instance can have as many as 100 collectors.

All collector types can reside on the same computer as the AIM*Historian instance or on another computer connected to the instance host via a network. The remote collector saves all send data in a file to facilitate burst-mode communication. Remote collectors save the updates when the con- nection to the instance host breaks. When communication is restored, the collector sends the data to the instance. The configuration information is always configured at the AIM*Historian instance.

1. Overview

B0193YL Rev E

The collectors are installed from the AIM*AT CD. AIM*Historian provides three distinct collec- tor types:

Real-time collectors for I/A Series systems

Event message collectors for I/A Series systems

The I/O Gate Collector for any I/O Gate Device driver.

AIM*Historian also allows configuration of collectors to support Sequence of Event (SOE) data collection applications developed by Invensys. Information on configuring these specialized col- lectors is not provided in this document, but is supplied with the application.

Default Collector Configuration

When you create an AIM*Historian instance, the program automatically creates a local I/A Series real-time point (RTP) collector with the same name as the instance.

When an off-platform instance collects I/A Series data points, the instance requires an I/A Series collector on an AW/AP to serve as a remote collector for the data.

I/A Series Real-Time Collector

The I/A Series real-time collector collects real-time values from the I/A Series system, and sends the value updates to the receiver program in the AIM*Historian server software. The default col- lector, which resides on the same system as the receiver, stores the changes directly into the instance database files. An instance can have multiple local I/A Series collectors and multiple remote collectors.

The I/A Series real-time collector operates on AW/AP51s and AW70s running I/A Series software Version 6.1 and higher. The task requires AIM*API on the station.

I/A Series Event Message Collector

The I/A Series Event message collector (ipchisti) collects I/A Series messages such as CP alarms, Operator Action Journal messages, and System Monitor messages. The task sends all configured Event messages to the AIM*Historian instance and selected messages to the Alarm Summary file. The AIM*Historian application also accepts messages from the HPS Message Manager.

The collector can operate on AW/AP51s and AW70s running I/A Series software Version 6.1 and higher. The collector can run as either a local or a remote collector.

The ipchisti message collector program registers with the I/A Series Inter-Process Communica- tion subsystem for each AIM*Historian instance directory on the instance host server, and checks periodically to account for the creation and deletion of AIM*Historian instances.

B0193YL Rev E

1. Overview

If the histsend program has been run for a specific instance, histsend marks an internal flag which tells the message running on the same machine to write its messages for the instance to a pre- defined circular file. The histsend program reads the circular file and transmits the messages over the network to the histreceive program running at the machine where the data files for the instance reside. The histreceive program writes the messages to the message data files.

NOTE

The histsend program is run for a particular instance and for the I/A Series real-time collector. If the histsend program has not been run for a specific instance, that is, the data files for the instance reside on the same system, the message collec- tor writes its messages directly to the message data files for the instance, that is, to m10.fdb, m20.fdb, and so on.

I/O Gate Data Collector

The I/O Gate Data Collector acquires real-time values from an I/O Gate Driver that supports a specific protocol. There are eight I/O Gate Drivers:

Applicom

Collects data from Siemens S7 and other PLCs that support the Applicom network protocol.

BASEstar

Links AIM*Historian instances with factory automation systems that use the Compaq ® Computer Corporation BASEstar Networking Solution ® .

CHIP

Interfaces with control products that use the Computer Highway Inter- face Program (CHIP) provided by Fisher-Rosemount.

DDE

Communicates with control process using Microsofts Dynamic Data Exchange (DDE) protocol.

ModbusPlus

Supports data collection from PLCs, such as AEG Schneider Automation Modicon 984 Compact and 984 Slot-Mount Controller, via an RS-232C serial connection and the ModbusPlus protocol.

ModbusTCP

Reads values from Modbus controllers using a TCP/IP connection to the control system.

OPC

Connects with systems using OLE for Process Control protocol (OPC) developed by the OPC Foundation.

REMIO

Provides connections for the AIM-Supervisor Remote Input/Output (REMIO) subsystem provided by Simulation Sciences Inc.

The collector is a client program accessing data remotely from the I/O Gate based device drivers.

The AIM*Historian instance sends initialization information defining the RTPs to be collected to the I/O Gate data collector. The collector then accesses the configured points from the I/O Gate drivers and accumulates the points at the configured frequency.

The collector can retrieve and store values from multiple ports and multiple devices per port, but it can only collect for one AIM*Historian instance.

1. Overview

B0193YL Rev E

The I/O Gate collector is installed from the AIM*AT CD. The collector is not automatically installed. You must select the collector type as an option in the integrated AIM*AT setup pro- gram. You must then specifically configure the collector in the Collector Station Cfg window, as described in Adding a Collectoron page 59 or Collector Stationson page 68.

The I/O Gate Collector and the selected I/O Gate Driver must be installed on the same station. See AIM*AT I/O Gate Drivers Users Guide (B0193YU) for information on installing and operating the drivers.

Real-Time Points

Real-time values are defined by real-time point objects (RTPs). RTP values are collected by real- time collectors such as the I/A Series collector, or generated by applications such as the AIM*Historian manual data entry program. The values are sent to AIM*Historian for storage in the AIM*Historian database. A real-time data collector requires a definition of the RTP it has to collect. The collector starts the collection of the data as specified in the RTP configuration and stores the data in the AIM*Historian database.

The operation of an RTP is determined by its collection method (COLMETH attribute). There are four options:

Connected

The default configuration for RTPs is the Connected method in which the real-time collector reads values of connectable points in the I/A Series system or other DCS.

Getval

This method is used for collecting I/A Series block parameters that are non-configurable/non-connectable. This method is also used when collecting string data.

MDE

The Manual Data Entry (MDE) configuration enables you to enter values into an instance database as if they had been collected from the DCS. Using the AIM*Historian MDE window or an AIM*API application, you can enter time stamp, value, status, and optional annotations. MDE only writes values to the AIM*Historian Database; it does not change values in the control system database.

WRITE

RTPs configured for the WRITE collection method are used to write val- ues to the DCS and record that output in the AIM*Historian database. The values to be written to the DCS are entered with one of three AIM*API functions calls:

an_write_objects()

an_write_valstat()

fh_FdbPutValue().

Refer to AIM*Historian Demand Writeson page 120 and to AIM*API Users Guide (B0193YN) for information on the use of these calls.

B0193YL Rev E

An RTP has the following name attributes:

1. Overview

A tag name (NAME attribute) which uniquely defines an RTP within an AIM*Historian instance. For backwards compatibility with the I/A Series Historian and AIM*API, the NAME can be up to 32 characters long.

A name specific to a DCS system (NAMEINCOL attribute) which uniquely defines a point within an AIM*Historian collector. NAMEINCOL can be up to 256 characters.

RTPs can represent many data types as displayed in Table 1-1.

Table 1-1. RTP Data Types

Data Type

     

Category

Data Type

 

Number of Bytes

 

Number of Elements

I/A Series

Integer

4

Bytes

1

Element

array types

Float

   

Long

Boolean

Character

Packed integer

Packed long

non-I/A Series

Character array

1

Byte

User-defined

array types

Short array

2

Bytes

Unsigned short array

2

Bytes

Integer array

4

Bytes

Unsigned integer array

4

Bytes

Float array

4

Bytes

Double array

8

Bytes

String

String

User-defined, including the longest possible string plus null terminator byte.

User-defined

BLOBS

Binary large objects

User-defined

1

Element

The data content of BLOBs is unknown to AIM*Historian.

Files

Data file contents

1

Byte

Number of elements is the number of bytes in the file

File contents are sent if file data is updated or RTP is triggered.

Time Stamp

Time stamp for distin- guishing a time value from a long data type

4

Bytes

1

Element

1. Overview

Time Stamps

B0193YL Rev E

An AIM*Historian instance can be configured to store time stamps in either coordinated universal time (UTC) format or in I/A Series time. AIM*Historian can provide collection of data from a mixed I/A Series environment in which IATIME and UTC are used by different control stations.

Collection Frequency

An RTP has a fast and slow collection frequency. You specify those frequencies in the RTP con- figuration. The data collectors send RTP values at a fast frequency. The value is stored at either the fast or slow frequency, according to the currently selected frequency for the RTP.

For example, an RTP is configured with a fast frequency of one sample per minute and a slow fre- quency of one every five minutes. The collector always sends the data to the instance at the one- per-minute rate, but you can set the instance to accept all data (fast frequency) or any one sample every five minutes (slow frequency).

A real-time data collector collects and sends RTP data if one of the following has occurred:

The RTP value changes significantly, that is, the change is more than or equal to the specified delta.

The RTP files time stamp changes.

The RTP is triggered by a significant change in another point. The triggering point can be any RTP in the same data collector.

The maximum time between samples (MTBS) of the RTP is reached.

The RTP status changes.

Event Messages

Event messages represent data that cannot be defined by an RTP. Event messages may have a variable length and a combination of data types within the data.

Event messages include:

Alarm messages

Annotation messages

Batch definition messages such as those sent from FoxBatch.

Event messages are stored in AIM*Historian databases. You first configure an event message and initiate the data collection process to start storing the messages in the AIM*Historian database. The event message definition consists of assigning a key to each field in the message.

A message key is defined by:

Key name

If this key is ODBC accessible, the key name also represents an ODBC column (the ODBC driver only recognizes single element columns).

ODBC accessibility

Key sequence number

Field data type

Number of elements in the field data type.

B0193YL Rev E

1. Overview

You can add new message types at any time, but you can remove or modify the definition of exist- ing message types only if no messages have been collected for the message type at the time of modification.

Event message definitions also include a message group name and a message name. Examples of group names are iaalarm and foxbatch. Use the group name definitions to avoid name conflicts between two application packages using the same message name. The message group AIMHistorianis reserved for use by AIM*Historian.

Figure 1-3 is a sample message definition.

by AIM*Historian. Figure 1-3 is a sample message definition. Figure 1-3. Sample Message Definition In the

Figure 1-3. Sample Message Definition

In the example, a definition is established for a message in the group my_message_group with the message name my_message_name.

The first three keys (group, message, and time) are compulsory and cannot be modi- fied or deleted.

The flag, alarm_type, event_nr, and text keys are optional.

The first field after the equal sign in the sample represents the sequence number and is used to check for omitted key definitions.

The second field after the equal sign represents the ODBC flag. If the field is Y, the key is read by the ODBC driver.

The third field after the equal sign represents the data type.

The fourth field after the equal sign represents the number of elements of the specified data type.

NOTE

The message configuration input file includes complete definitions for all I/A Series messages (See Configuration Using Input Text Fileson page 64).

1. Overview

B0193YL Rev E

Control Groups

Some client applications require that groups of AIM*Historian RTPs or event messages be switched in one operation to a different state or frequency. You can associate certain RTPs and event messages in a control group that can be controlled by a client application or by triggering RTPs.

For example, a plant runs from 8:00 a.m. to 5:00 p.m. and there is a shared variable (PlantONOFF) that indicates the running of the plant. The value of the shared variable is represented as 1 for the plant running and 0 for the plant when it is stopped. All historical collection of all the control values in the plant can be started and stopped by creating a control group that holds all the RTPs in the instance. The On/Off trigger RTP in the control group is the PlantONOFF RTP and the threshold value is 1.

RTPs in a control group are switched in one autonomous operation between the following states:

On and Off

Bad and OK

Fast collection frequency and Slow collection frequency (see Collection Frequencyon page 9).

The changes can be based on the same or different triggers. Event messages in a control group are switched in one autonomous operation between on and off.

A Control Group can be controlled either by a function call or by up to three RTPs.

NOTE

In addition, you can use two AIM*API calls, fh_RTPControl() and fh_MsgControl (), to change RTP and Event message status individually.

Up to three RTPs can be assigned as the controlling RTPs for the control group. Switching

is performed at a specified threshold value. A triggering value falling below the threshold

value turns the control groups RTPs to Off, OK, or Slow. A triggering value rising to or above the threshold value turns the control groups RTPs to On, Bad, or Fast. One triggering RTP determines the Bad/OK state of all the RTPs, one triggering RTP determines the Slow/Fast state of all the RTPs, and another triggering RTP determines the On/Off state of all the RTPs and event messages.

B0193YL Rev E

1. Overview

Table 1-2 displays the RTP point values and the results for trigger values.

Table 1-2. RTP Trigger Values

Trigger

   

Type

If the trigger value is:

Then:

OnOff

Less than the threshold value

All RTP and event messages in the group are turned Off.

Greater than or equal to the threshold value

All RTP and event messages in the group are turned On.

BadOK

Less than the threshold value

Do not force the setting of the bad bit in the status word for subsequent values for all RTPs in the group.

Greater than or equal to the threshold value

Set the bad bit in the status word for subsequent values for RTPs in the group.

FastSlow

Less than the threshold value

All RTPs in the group are collected at the slow collection frequency.

Greater than or equal to the threshold value

All RTPs in the group are collected at the fast collection frequency.

Reduction Groups

A reduction group is an AIM*Historian component you configure to allow another application such as the I/A Series Historian to retrieve reduced data from AIM*Historian.

The parameters for the reduction group are:

Reduction group name

Description

Reduction interval

Percent of RTPs in the interval that must be valid for the points to be reduced

Operations list including name and type for each operation (the operation name is used as the column name for ODBC and database export purposes)

Member RTP name list.

A reduction group cannot contain other reduction groups, nor can a reduction groups values be the basis for the reduction.

NOTE

A reduction group is a retrieval mechanism only. It does not cause the generation of reduced data in reduction data files.

1. Overview

AIM*Historian Interface Structure

B0193YL Rev E

AIM*Historian instances reside on a host computer that runs AIM*Historian. The AIM*Historian server stores data from the data collectors and communicates with client applications.

The AIM*Historian server interfaces with the AIM*API server for AIM*Historian instances and with I/A Series stations for I/A Series Historians. The I/A Series station is accessed by an I/A Series Historian name such as hist01. The I/A Series station interface can only be used for data retrieval of I/A Series Historians and MDE (manual data entry) update. The I/A Series sta- tion interface does not support configuration interface functions such as adding an RTP. Use the AIM*API server interface to retrieve and store data for an AIM*Historian instance and perform configurations for an AIM*Historian instance.

The AIM*Historian server that interfaces with the I/A Series station communicates with I/A Series client applications such as Display Manager, FoxView, and FoxTrend. The AIM*Historian server that interfaces with the AIM*API server communicates with AIM*API client applications such as AIM*Historian Configurator.

When you access an AIM*Historian instance from an AIM*API client application using an AIM*API server, the instance is identified first by its IP name and then by its instance name. First, connect to the AIM*API server where the AIM*Historian instance resides; for example, by calling an_open_server(). Then reference the desired AIM*Historian instance by its instance name in the Historian argument of the API you are using.

You can access data from an AIM*Historian instance using one of these interfaces:

AIM*API Interface, ODBC Interface, I/A Series Interface, AIM*AT OLE DB Provider, and Oracle Export Utility.

Figure 1-4 illustrates how AIM*Historian information is retrieved.

B0193YL Rev E

1. Overview

AIM*API Client

ODBC Client

FoxView, DM

Application

Applications

FoxAnalyst

  AIM*API Server   ODBC Driver     I/A Series Interface for Historian Legacy Interface
  AIM*API Server   ODBC Driver     I/A Series Interface for Historian Legacy Interface
  AIM*API Server   ODBC Driver     I/A Series Interface for Historian Legacy Interface
 

AIM*API Server

 

ODBC

Driver

   

I/A Series

Interface

for Historian

Legacy Interface

     
I/A Series Interface for Historian Legacy Interface         AIM*Historian Database  
I/A Series Interface for Historian Legacy Interface         AIM*Historian Database  
I/A Series Interface for Historian Legacy Interface         AIM*Historian Database  
 
  AIM*Historian Database  

AIM*Historian Database

 
I/A Series Interface for Historian Legacy Interface         AIM*Historian Database  
I/A Series Interface for Historian Legacy Interface         AIM*Historian Database  
I/A Series Interface for Historian Legacy Interface         AIM*Historian Database  

Export

AIM*AT