System 800xA Training

Chapter 7 Historical Data Collection

TABLE OF CONTENTS

Chapter 7 Historical Data Collection ...................................................................................................................................... 1

7.1 General Information ..................................................................................................................................................... 2
7.1.1 Objectives.............................................................................................................................................................. 2
7.1.2 Legend .................................................................................................................................................................. 2
7.1.3 Reference Documentation ...................................................................................................................................... 2
7.2 800xA Architecture for Historical Functions ................................................................................................................. 3
7.2.1 Overview............................................................................................................................................................... 3
7.2.2 What is a Log?....................................................................................................................................................... 4
7.2.3 Log Hierarchy........................................................................................................................................................ 5
7.2.4 Configuration Overview......................................................................................................................................... 6
7.2.5 History Service ...................................................................................................................................................... 7
7.2.6 History Source Aspect............................................................................................................................................ 7
7.3 Log Templates.............................................................................................................................................................. 9
7.3.1 Creating a Direct Log Template ............................................................................................................................. 9
7.3.2 Hierarchical Log Templates ..................................................................................................................................12
7.4 Log Configuration .......................................................................................................................................................13
7.4.1 Creating a Log Configuration................................................................................................................................13
7.4.2 Log Configuration for Object Types ......................................................................................................................15
7.4.3 Presentation Settings.............................................................................................................................................16
7.5 Checking Historical Data Collection ............................................................................................................................17
7.5.1 Check the History Source......................................................................................................................................17
7.5.2 Check the Data Size ..............................................................................................................................................17
7.5.3 Read Log Contents...............................................................................................................................................18
7.5.4 Log Summary.......................................................................................................................................................19

Chapter 7 - 1
T315H-07 Historical Data Collection - RevE

7.1 General Information

7.1.1 Objectives
On completion of this chapter you will be able to:
• Set up the history source
• Describe how historical information is collected
• Configure log templates
• Configure logs

7.1.2 Legend
> Indicates when you go from one menu to a sub-menu
Italic Indicates object and file names
“ “ Indicates dialog box buttons, tabs, menus etc.
Bold Indicates important topics
Indicates start/explanation of student activity

7.1.3 Reference Documentation

3BDS011222 System 800xA
Configuration
3BSE030322 System 800xA Operations
Operator Workplace Configuration
3BSE041434 System 800xA
System Guide – Technical Data and Configuration

Chapter 7 - 2
 System 800xA Training

7.2 800xA Architecture for Historical Functions

7.2.1 Overview
The 800xA system supports a full array of historical and reporting functions. Many of
these functions such as archiving require the Information Manager software. However,
basic historical collection is performed by the Basic Historian in the Connectivity
Server and so it is available as a base feature of System 800xA.
If Information Manager is installed in the system, it gets its data from the
Connectivity Server’s basic historical logs using the OPC’s HDA standard protocol.
This protocol, unlike the DA protocol, can get multiple values for the same point with
one request. If the Information Manager machine is off line for a while, there is no
loss of data because it can retrieve the whole time period from the Connectivity Server
when it comes back on line.
Trend displays

Aspect Workplaces
Server (Clients)

Client/Server Network

Historical data Connectivity

Server

Control Network

Controllers

The Connectivity Server is usually redundant so it is unlikely that data will be lost due
to a failure. Both Connectivity Servers are always collecting the data so if one is off-
line, it will back fill from the other when it returns to service.
The data collection is done using the OPC DA standard but the Basic Historian also
has the ability to collect data through some proprietary protocols such as the AC 400
Controllers TTD logs.

Chapter 7 - 3
T315H-07 Historical Data Collection - RevE

7.2.2 What is a Log?

A log is a collection of time stamped (tagged) data. The process or system object from
which the data originates is called the data source.
The log is normally stored on a hard disk on the Connectivity Server. The storage size
is up to 10,000,000 data points per log. All logs are circular; the oldest data entry is
overwritten by the newest when the log is full.
NOTE! Log data cannot be archived, if not using Information
Manager.

Data Source

LOG

Storage Interval
t
0s 10s 20s 30s 2’592’000s
or
30 days

Storage Size

Logging can take place as fast as once per second. There is almost no limit to the
number of logged data items. But there is always a balance between the rate of logging
and the number of data points to be logged – if both are high then the network may be
considerably loaded.

The collections of historical data for tags in 800xA are called “property logs”. This is
because we are logging a property of an OPC item on a periodic basis. For example in
a PID loop, the signal for the set point, process variable, and control output are all
individual properties.

Chapter 7 - 4
 System 800xA Training

7.2.3 Log Hierarchy

A hierarchical log is one whose input data source is another log. The first log is a
direct log, with data coming from the OPC Server. The succeeding logs get their input
from the first log. The selection of aggregate (algorithm) determines the type of
processing done to the data before it is logged.
There is no hard limit to the number of hierarchical levels which can be configured.

Data Source Storage Size

OPC

LOG 1

Storage Interval
t
0s 10s 20s 30s 60s 2’592’000s
or
30 days

Aggregate

LOG 2

t
0s 60s 120s 180s 180 days

Example
LOG1 is a direct log, logging data from the OPC server every 10 seconds.
LOG2 is a hierarchical log, logging the time average of the samples from LOG1 over
a 60 second time period (6 samples from LOG1).

Chapter 7 - 5
T315H-07 Historical Data Collection - RevE

7.2.4 Configuration Overview

There are two parts to setting up values to be logged:

Library Structure

Log Template Control Structure

HOW DATA IS LOGGED

Log Configuration
WHAT IS LOGGED

Log Template aspect

This aspect is configured in the Library Structure. It determines the size of the log and
the frequency with which items are logged. It does NOT say what should be logged.

Default log templates are provided both for trend logs provided by the 800xA Basic
Historian and by the Information Management option.

Log Configuration aspect

This aspect is configured in the Control Structure as part of the object where the
signals to be logged are found. It defines which properties (for example Value) on the
object/signal to log, and how to log (by referring to a Log Template).

Chapter 7 - 6
 System 800xA Training

7.2.5 History Service

Before any logging can take place the log configurations need to know where to obtain
the data.
Just as 800xA has services to provide alarm and event functions, there is a service for
collecting history. It is called the Basic History service and the responsibility is to
acquire and make available data for logging. It communicates with the OPC Server to
obtain the data coming up from the controller.

The situation is similar to other service set-ups. The Basic History service is defined in
the Service Structure. This service may serve one or more History Service Groups.
We will have additional service groups if there are multiple Connectivity Servers
whether they are for AC 800M, Harmony, or other connectivity types.

The Basic History service gets installed and configured automatically during system
creation. Unless further service groups are required there is no work to be done in the
Service Structure. If we have redundant Connectivity Servers, there will be two
service providers in the Basic service group.

7.2.6 History Source Aspect

Before logging of properties can take place in any structure at least one History Source
aspect must be defined. This is done at a fairly high level in the structure. All objects
that are descendants (children) of the object containing the History Source aspect
inherit this source.
The History Source aspect is required to point to the service group which will be used
for all log configurations.
For logging from data inside objects in the Control Structure, it is usual to set up the
history source as an aspect of the Control Network, and then all objects below it will
use this history source.

Chapter 7 - 7
T315H-07 Historical Data Collection - RevE

1. Mark the Control Network object in the Control Structure.

2. Add an aspect of type History Source to the Control Project and name it History
Source.

3. Open the “Config View” for the History Source aspect.

4. Select the service group Basic from the list of the available service groups. This
service group is defined in the Service Structure > Basic History > Basic as
explained above.

5. Click onto “Apply”.

The history source is now configured. All objects and child objects of the Control
Project object are able to use this history source.

Chapter 7 - 8
 System 800xA Training

7.3 Log Templates

Just as there are templates to define alarms and trends, there are templates in the
Library Structure to define history logs. There are two kinds of logs that have
process data as their source, Direct and Hierarchical. A third type, Lab Data, is for
manual entry.
A log template is a re-usable template for building many similar logs. Modifying an
existing log template, will affect existing logs use that log template.
Two default log templates are available for use. We can either use these templates or
create new ones. As usual, if the defaults do not meet our needs, it is better to create
new ones than modify existing ones.

7.3.1 Creating a Direct Log Template

As a first step, we always have to create a Direct Log template. The direct log is the
collection of data directly from an OPC source.
1. Select the Library Structure.

2. Mark History Log Templates and select “New Object” from the context menu.
Create a new library for your own templates.

Chapter 7 - 9
T315H-07 Historical Data Collection - RevE

3. My History Log Templates is just a container of log templates (like a folder) in

which you create now a new object of type History Log Template.

4. Select the “Config View” of the Log Template aspect.

5. Create a new Property Log template by clicking the “Add” button. The first log
must always be a direct log.

Chapter 7 - 10
 System 800xA Training

6. Select the tab card “Data Collection” and specify how to collect data.

Sample Resolution / Data Compression

The sample resolution can be specified in terms of a minimum and maximum time for
taking a sample, and an exception deviation. This allows some data compression by
not collecting samples that have not changed significantly from the previous.
Min Time is the shortest time between two samples and Max Time is the maximum
time between two samples. If Max Time is set it guarantees that you get a new point at
that interval, even if the value has not changed. Max Time set to zero means that there
is no sampling if the input changes are less than the Exception Deviation.
Exception Deviation is the maximum input deviation that is allowed without a new
value is stored in the log. If we leave the Exception Deviation at 0.000%, samples will
always be collected at the minimum time. Read more in the Online Help about the
three different Exception Deviation types.

Storage Size
We can specify the amount of data to store in either number of points or length of
time.
The Min Capacity and Max Capacity figures at the bottom of the tab show the effect
of the decisions we make for storage interval and size based on whether data is
collected at the minimum or maximum resolution.
The Aggregates and Bad Data Quality Limit entries at the top are unavailable for a
Direct Log. We will see their use in the next section.

Chapter 7 - 11
T315H-07 Historical Data Collection - RevE

7. Select the tab card “Log Definition” and give a new name to the log.

NOTE! Log names should specify collection interval, log capacity

and aggregate (if applicable).

8. Apply your changes by clicking onto the “Apply” button.

7.3.2 Hierarchical Log Templates

A hierarchical log is one that uses another log as its source rather than a direct OPC
collection. The ultimate source of data is still the OPC collector, but we can use the
direct log to provide data to the hierarchical log. This provides a lot of flexibility in
how we handle the data with regard to compression.

Taking a look at the “Data Collection tab” of the second level of the hierarchical log,
we can decide how to reduce the resolution of the data. The Aggregate entry has
many selections from average to standard deviation, summation, interpolation and
many others.

The Bad Data Quality Limit specifies what percentage of the samples can be bad and
still create an acceptable aggregate. If more than this percentage is bad, the aggregate
sample will be marked bad in the hierarchical log.

Chapter 7 - 12
 System 800xA Training

7.4 Log Configuration

A Log Configuration aspect is required for each object which contains properties to be
logged. It is used to specify the properties to be logged and which log template to use
for each property.
Remember that each tag can have many different values associated with it and these
are called properties. For example in a PID loop, the signal for the set point, process
variable, and control output are all individual properties. Each one of these that we
want to maintain history for will need a separate log defined.

Typically Log Configuration aspects are placed on the objects in the Control
Structure to collect data from a specific tag (instance). We will see later in this
section that for certain type of tags it also makes sense to place a Log Configuration
aspect in the Object Type Structure.

7.4.1 Creating a Log Configuration

1. Open the Control Structure and select any process tag such as a function block
or a control module.

2. Add a Log Configuration aspect to the instance and give a proper name.

Chapter 7 - 13
T315H-07 Historical Data Collection - RevE

3. Select the “Config View” of the Log Configuration aspect. Click onto the button
“Add Property Log” to create a new log.

Must be checked

4. Select a property from the list and select a template.

5. Click onto the “OK” button. Click “Apply” to close the “Main View” of the Log
Configuration aspect.

6. To implement the log click “Apply”. The log is created in the server and the
sampling is started immediately.
NOTE! We can have more than one property log configured even
for the same property.

Chapter 7 - 14
 System 800xA Training

7.4.2 Log Configuration for Object Types

You might want to collect data from all instances of an object type. For instance, you
want to log the set point, process variable, and control output for all PID loop.
Then best is to crate a Log Configuration aspect on an object type in the Object Type
Structure, such that all instances of this object type automatically collect logs.

Follow the same procedure as explained above to create the Log Configuration aspect.

It is then important to define the Log Configuration aspect as “Copy to all instances”
in the Object Type Definition aspect .

Chapter 7 - 15
T315H-07 Historical Data Collection - RevE

7.4.3 Presentation Settings

You can set some basic values in the “Presentation” tab to display the trace in a trend
display in a proper way.

These values can be set in either of the:

• Object type (i.e. in the Property aspect)
• Object instance (i.e. in the Property aspect)
• Log (in the Log Configuration aspect)
• Trend display

The above listed are in override order. For example you can override a value set in the
Object Type by writing a value in the Object Instance. Another example is a value set
in the Object Type, the Object Instance for presentation attribute or the Log can be
overridden in the Trend Display.
To override a presentation attribute the box for the attribute must be checked. If the
box is unchecked the default value is displayed. The default value can be a property
name or a value, depending on what is specified in the Control Connection aspect.

Engineering Units are inherited from the source but can be overridden.
Normal Maximum / Minimum are scaling factors, used for the scaling of Y-axis in
the trend display. The values are retrieved from the source but can be overridden.
The number of Decimals is retrieved from the source but can be overridden.
The Display Mode can be either Interpolated or Stepped.
Interpolated is appropriate for real values, Stepped for binary.

Chapter 7 - 16
 System 800xA Training

7.5 Checking Historical Data Collection

7.5.1 Check the History Source

Check that the history source is working in the Control Structure:

Bad news Good news

Logging will not work Logging is working

Note that this indication will always show “History Source not specified” in the
Object Type Structure, but it should indicate “green” on the instances.

7.5.2 Check the Data Size

After you created a new log configuration and added a property log to it, some new tab
cards with different settings exist.

The “Property Log” tab displays log information. The Data Size is the size of the
property log on disk. It is the sum of the size of all logs. The size of each log file is the
sum of the file header and the data storage size.

Chapter 7 - 17
T315H-07 Historical Data Collection - RevE

7.5.3 Read Log Contents

You may read log contents by selecting the function block or control module in the
Control Structure. Then select the “Config view” of the Log Configuration aspect.
1. Select the logged property you want to read, then click on the tab “Status.

2. Press the “Read” button.

Chapter 7 - 18
 System 800xA Training

7.5.4 Log Summary

The Log Summary aspect gives an overview of all log configurations placed below the
aspect in the tree. You can see if the log configuration is enabled, the path to it and if it
is passed the consistency check.

By right-clicking over the list of log configurations, a menu will be displayed where
you can choose to enable, disable, delete or open log configurations. You can also
choose to run auto-correct if they have not passed the consistency check.

Chapter 7 - 19
T315H-07 Historical Data Collection - RevE

Select “Open Log Configuration” to navigate directly to log configuration of a spefici

tag.

F Exercise 7.1

Chapter 7 - 20
System 800xA Training

Chapter 7 - 21