Procidia iWare TrendWorX32...TrendWorX32 Viewer Real Time Trend The pen is configured to an OPC tag....

Protection notice / Copyright notice

Procidia iWare TrendWorX32TrendWorX32 ConfiguratorApril 2010

© Siemens AG 2008. All rights reserved.

Industry Automation / Process Instrumentation & Analytics© Siemens AG 2008. All rights reserved.

April 2010 F. Monino

Introduction / Contents

Procidia iWare is an operator interface software designed to support the 353 series controller.

TrendWorX32 is a suite of applications within Procidia iWare that manages trend data collection, logging, and viewing.

This presentation illustrates how to build the TrendWorX32 SQL Server database.

Sections

Overview 3

Project Management 12

Configurator 14

SQL Server 84

Technical Support 95


TrendWorX32 Overview




TrendWorX32 Overview

TrendWorX32 Components

TrendWorX32 Configurator

TrendWorX32 SQL ServerAlso referred to as the TrendWorX32 SQL Data Logger

TrendWorX32 ViewerGraphWorX32 ActiveX component

Persistent Trending Configurator

TrendWorX32 Report




TrendWorX32 Configurator builds the Historical Trend Configuration database.The Configuration database defines historical tags and trend criteria.

Historical tags are process variables associated with an OPC tag

Trend CriteriaData collection rateData logging rate

The Configurator also creates the Historical Trend Logging database.Logging database is where raw or statistical data is stored.

The Logging database and the Configuration database can use the same database file.



TrendWorX32 SQL Server

The TrendWorX32 SQL Server collects and logs data.

The Server connects to the Historical Trend Configuration database for list of historical tags and for the trend criteria.

The Server connects to the OPC servers for raw data collection.Historical tags are associated with OPC tags.

The Server also connects to the Historical Trend Logging database for logging of data.



TrendWorX32 Viewer

The TrendWorX32 Viewer is an ActiveX object that runs within GraphWorX32.

In run-time, the Viewer displays pen trends.Historical trendReal time trendPersistent trend



TrendWorX32 Viewer

Historical TrendThe pen is configured to a historical tag.

Historical tags are a connection to the Historical Trend Logging database.

In run-time mode, the Viewer updates whenever the SQL Server logs to the database.

In freeze mode, the operator can scroll back in time to review historical data.



TrendWorX32 Viewer

Real Time TrendThe pen is configured to an OPC tag.

When the Viewer opens, the Viewer connects to the OPC server and starts to collect data.

The operator must wait for the trend line to develop.

Once data scrolls off the Viewer, it is lost.



TrendWorX32 Viewer

Persistent TrendPersistent trending is real time trend except that when the Viewers open it is populated with recent data.

The pen is configured to a Persistent Trend tag.

The Persistent Trend utility collects a limited number of data samples per tag.

When the Viewer opens, it connects to the Persistent Trend utility and downloads the recent trend data.

Once data is loaded, the Viewer connects to the OPC server and begins to collect real time data.

Once data scrolls off the Viewer, it is lost.



Persistent Trending Configurator

Persistent Trending Configurator utility is both the database configurator and server.

Its purpose is to collect real time data in advance of opening a TrendWorX32 Viewer.

When the Viewer opens, it is populated with recent data.Operator does not need to wait for viewer to build a trend line.

Persistent Trending utility must be opened independent of GraphWorX32 and run in the background.

Recent data is saved in RAM memory.



TrendWorX32 Report

TrendWorX32 Report permits printing of historical trend data.Report print out is to Microsoft Excel spreadsheet or text file

TrendWorX32 Report connects to the Historical Trend Logging database.

Reports are run on a time schedule.Periodic reportsOne time reports

A report covers a specified reporting period.

The report performs statistical analysis on raw data.Report provides an average value per time intervalOther statistical data, like maximum value, can be reported per time interval.


TrendWorX32 Project Management




Database Management

The Procidia project is stored in the Procidia APPs folder.

Create a Server Database folder in Procidia APPs.

The Server Database folder organizes the project database configurations.

Historical trend databaseAlarmWorX32 Server configurationSecurity Server configuration

Create Server Database folderin Procidia APPs




Open TrendWorX32 ConfiguratorClick Task Bar Start buttonSelect programs/ Siemens Procidia/ iWare PC/

TrendWorX32/ TrendWorX32 Configurator




Start new Historical Trend Configuration database

Select Menu bar File/ New



Configuration Database Wizard

Selecting File/ New opens the TrendWorX32 Logging Configurator Database Wizard.

The Wizard helps to select and create the Historical Trend Configuration database file.

Start Configuration Database Wizard

Click Next button




The Historical Trend Configuration database can be either a Microsoft Access or SQL database.

Procidia iWare installs Microsoft Access drivers if not already installed.

Current version of iWare does not provide SQL drivers.

This tutorial is for a Microsoft Access database.

Select MS Access database

Click Next button




With the database type specified, the next step is to create the database file.

The default location is iWare/ Bin folder.

It is recommended to save the Historical Trend Configuration database in Procidia APPs/ Server Database folder.

Create a new Historical TrendConfiguration database

Click Ellipsis button




In Procidia iWare, Microsoft Access (mdb) database files are used for many types of database files.

When naming a database file, identify the project (for example Boiler) and identify the database type (Trend).

Select Server Database folderEnter database file name

Click Save button




Finish creating the Historical Trend Configuration database file.

Click Finish button



Historical Trend Configuration Database

The Configurator Title bar identifies the Historical Trend Configuration database file name.

The left-hand window is the Configuration database tree view.

The current view in the right-hand window is the Configurations Overview.

It lists all configurations.Local_Configuration is the default configuration.



Configurator Overview

The Configuration database is built in four tiers.

Configurations Tree Header

Configuration – Tier 1

Database Group – Tier 2

Logging Group – Tier 3

Historical Tag – Tier 4




Configurations Tree Header

The Configurations Tree Header is the container for the configuration.

The Configurator can contain more than one configuration.However, the SQL Server only runs one configuration.Only one instance of the SQL Server runs on a PC.




Configuration – Tier 1

This is the top configuration level.

At the configuration level, the connection between the SQL Server and the configuration database is established and managed.

Make current configuration activeDownload configuration changes

At this level, the SQL Server can be started and stopped.This feature is for convenience while in the design phase.For run-time applications, use GenTray to start the server.




Database Group – Tier 2

A Database Group is where the connection between the SQL Server and the logging database is established and managed.

An ODBC data source connection is established between the SQL Server and a Microsoft Access database.

The configuration database and the logging database can be separate files.




Logging Group – Tier 3

In a logging group, the data collection and logging rates are specified.Data is collected and saved in memory until logged to the logging database.Raw or statistical data can be logged.

Raw data is all collected data samples.Statistical data is computational results of all samples collected within a time interval.

Multiple logging groups can be created in order to organize historical tags by logical groupings.

Logging groups with different logging criteria can also be created in order to optimize the logging database.

Data logged to a Microsoft Access database is saved in data tables.




Historical Tag – Tier 4

A historical tag is the process variable being collected and logged.

At this level, the individual historical tag is configured.The historical tag name is assigned.The OPC tag connection is specified.Engineering units are defined.

Typically, a logging group contains multiple historical tags.



Configuration Header

A new configuration can be added by highlighting Configurations and selecting File/ New/ Configuration.

It is easier to start configuring the default Local_Configuration.

Open Local_ConfigurationClick Local_Configuration



Configuration Panel

This opens the Configuration panel.

Name, ModifiedConfiguration nameLocal_Configuration is good.

Network Node NameSpecifies node with SQL Server.Recommend Local



Configuration Panel

Connect/ Disconnect buttonsEstablishes a connection between the SQL Server and the Configurator.This permits configuartion downloads and start/ stop of server.

Make Active buttonDownloads configuration changes to the SQL Server.If configuration changes are made while the server is running, then stop the server and click Make Active button to force a download of the new configuration.



Configuration Panel

Start Datalogging/ Stop Datalogging buttonsStarts and stops the SQL Server.This feature is for convenience during the design phase.In normal run-time, use GenTray to launch SQL Server.



Configuration Panel

Use Global Connection check boxDefault is enabled.Global means that the SQL Servermaintains a constant connection withthe database.

Use UTC Time check boxTime stamps are stored in UTCformat.UTC compensates for change of localtime due to daylight savings.

Click Advance>> button



Configuration Panel

Advance>>/ Simple<< buttonsButtons display/hide Retrials, RetrialDelay, Max Samples, and MaxLogging Packets parameters.

Retrials and Retrial DelayIn the event that the logging operationfails, the server retries to log thelogging packet.

Max SamplesParameter specifies maximumnumber of samples to be maintainedin memory buffer prior to loggingdata on a per tag basis.



Configurations Panel

Max Logging PacketsA logging packet is a block of data to be logged.

The greater the number of retrials and the number of logging packets specified, the more system memory is reserved by the SQL Server.

Adjust Log Params buttonAfter adjusting logging parameters, click Adjust Log Params button to apply changes.



Configuration Panel

To add a Database Group to a Configuration:

First highlight Local_Configuration;Then open Edit menu:

Click menu bar Edit, or Right mouse click Configuration;

Select New method;And select Database Group.

Add a Database GroupClick Local_Configuration and highlightSelect menu bar: Edit/ New/ Database Group



Database Group Panel

NameAssign Database Group nameUsually only one Database Group iscreated; therefore the name candescribe the project.

ODBC Data SourceAssign an ODBC Data SourceThe ODBC establishes theconnection between the MS Accesslogging database and the SQLServer.

Enter Database Group name

Click ODBC Data Source Browse button



ODBC Data Source

The Select Data Source dialog box displays available Data Source connections.

For TrendWorX32 data logging, create a new ODBC Data Source.

Create new ODBC Data SourceSelect Machine Data Source tabClick New button



ODBC Data Source

Select System Data Source radio buttonClick Next button

Select Microsoft Access Driver v4.0Click Next button



ODBC Data Source

Assign a data source name that identifies it as the connection for the TrendWorX32 SQL Logging Server and a Procidia project.

This will be helpful when system house cleaning.

Click Finish button

Enter Data Source Name



ODBC Data Source

The next step is to assign or create the logging database file.

The logging database can use the same Configuration database file or it can be a separate database file.

Select – To assign an existing database file.Create – To create a new file.

It is recommended to use the same Configuration database file.

Click Select button



ODBC Data Source

ODBC connection is complete.Note Database connection.

Select Server Database folderSelect Configuration database fileClick OK

Click OK



ODBC Data Source

The new Procidia system data source is listed.

Data Source supports securityIt is not required.

Click OK

Click OK




ODBC Data SourceNew Procidia system ODBCconnection

Database TypeMS Access

Save workClick Apply button




Database Group was added to the configuration.

Test DB ConnectionPerform Test button verifies connection to logging database.

Test Database ConnectionClick Perform Test button




Connection is good.

ReviewAdd Database Group to theConfiguration.Assign Database Group name.Create a system ODBC databaseconnection using MS Access drivers.Assign the Configuration database fileas the logging database.Click Apply button to save anddownload changes.

Click OK




To add a Logging Group to a Database Group:

First highlight the Database Group;Then open Edit menu:

Click menu bar Edit,or Right mouse click Database Group;

Select New method;And select Logging Group.

Add a Logging GroupClick Database Group and highlightSelect menu bar Edit/ New/ Logging Group



Logging Group Panel

NameAssign the Logging Group name.Name should describe the logginggroup.

A Database Group can contain multiple Logging Groups.

Enter Logging Group name

Click Apply button



Logging Group Panel

All tags in a logging group are polled at the same rate.

At startup, the SQL Server connects to an OPC server and provides it a list of tags with the update rate.

The OPC server polls those tags at the specified update rate; and when collected, it provides the data to the SQL Server.All data samples are time stamped.

Data is not immediately saved to the MS Access database file.The Server collects and saves data in system memory.

All data is logged to the database file as a logging packet at a specified logging rate.



Logging Group Panel – Data Collection Tab

Data Collection tab panelData collection criteria is specified.Start and stop conditions are also specified.

Control Board sub-panelThe Data Collection rate is specified.When logging statistical data, the calculation period is also specified.

Select Data Collection tabSelect Control Board panel button

Enter Data Collection RateEnter Calculation Period




Collection Rate

This is the rate at which data samples are polled.

When setting the collection rate, it is important to understand the process variables being collected.

Fast changing process variables require a fast collection rate in order to capture events.

A 3 to 5 second collection rate is recommended.One (1) second collection rate is possible in small networks.

Slow changing process variables should be collected at a slower rate.Example: 30 seconds is good for storage tank level and temperature.This helps to minimize the size of the logging database file.




Collection Rate

The faster the collection rate, the more PC resources are consumed.

Faster collection rates result in more data samples being collected and logged.

This increases the size of the logging database file.

Collected data, prior to being logged, is stored in memory.This consumes system memory.




Calculation Period

The Calculation Period is the time interval for logging of statistical data.Typical statistical data is average, maximum value, minimum value.

All samples collected during the time interval undergo statistical analysis.The logged value is the statistical result.

For statistical data, the Calculation Period is greater than the Collection Rate.When determining the rate and period, make sure that sufficient samples are collected to provide meaningful statistics.

For raw data (where all collected samples are logged), the Calculation period is set equal to the Collection Rate.

The Calculation Period can never be less than the Collection Rate.




Start Conditions sub-panel

On Start check boxDefault start conditionData collection starts whenever the SQL Server is started.

Select Start Conditions panel button

Select On Start check box




Start Conditions sub-panel

On ConditionData collection starts when a specific condition is true.The start condition can be the state of a process variable (OPC tag) or an expression (more than one variable is true).Feature permits collecting data only when the process is running and not idle.

On TimeData collection starts at a specific time of day.Method implies that data collection is also stopped daily.

On IntervalData collection starts at a fixed time interval.Method also implies that the data collection is stopped on a regular basis.




Stop Conditions sub-panel

No condition selectedDefaultData collection stops when the SQL Server is stopped.

On ConditionCompliments start conditions

On TimeCompliments start conditions

On IntervalCompliments start conditions

Select Stop Conditions panel button



Logging Group Panel – Logging Tab

Logging tab panel

These parameters specify data logging criteria.

On Interval check boxDefault conditionRecommended logging criteria2 minute interval is good

On RecordsDefaultData is logged when 30 samples for any tag have been collected.

Select Logging tab

Check On Interval check boxEnter logging frequencyCheck On Records check box



Logging Group Panel – Table Management Tab

Table Management tab panel

Table Management is a method of controlling the MS Access database size.

MS Access has a 2 GB limit.When the database approaches 2 GB, the SQL Server cannot manage the database.Available RAM memory also affects performance.It is recommended that the system have at least 1 GB SDRAM memory when using TrendWorX32.

Select Table(s) Management tab




MS Access organizes data in tables.When data is logged in Access, it is added to a data table.In theory, data will be added to one data table until the database reaches maximum capacity.

To control the database size, create a daily table and limited the number of tables that are created.

Since the data collection rate is constant, then the number of daily records will be consistent.Therefore, each table will be limited and all tables will be of similar size.When the last table is completed, the oldest table is deleted and a new replacement table is created.




Table Name text boxThis is the name assigned to the data table.Default is Logging Group Name.The default name is recommended.When multiple tables are created, the table number is appended to the name. For example:

Boiler 1_1, Boiler 1_2, etc.

Number of Tables list boxThis parameter specifies the maximum number of data tables per logging group.

Accept default Table NameEnter number of Tables




Number of Tables

Estimate the size of a daily data table.Table Size, MB/table = (# Tags) * (1 day/table) * (86,400 sec/day) / (collection rate, sec/sample) / (36 samples/record) * (2560 bytes/record) / (1024 bytes/KB) / (1000 MB/KB)

Estimate the number of daily tables that the database can support.Number of tables = (500 MB) / (Table size, MB/table)

Each logging group will generate its set of tables.




Number of Tables

TrendWorX32 historian is ideal for collection of process data for performance monitoring and maintenance diagnostics.

30 days is a realistic maximum retention period.

For monthly programs, such as efficiency performance and energy management, generate monthly summary reports.

EPA emissions permits require retention of data for 2 to 5 years.In this case, copy the database to a back-up system on a monthly basis.Emissions reports are usually submitted monthly.




Create New Table frameThese parameters specify when to create a new table

On Time check boxMethod creates a daily table.Parameter specifies time of day.This is the recommended method.

Any Time Logging StartsA new table is started every time the Server is started.Default conditionMethod is also recommended.

Select On Time check boxEnter time of day to create new table

Select Any Time Logging StartsClick Apply button




Create New Table frame

It is important to ensure that all collected data is periodically saved to the logging database.

This releases system memory.Otherwise, performance will deteriorate as available system memory decreases.



Logging Group Panel

To add a Historical Tag to a Logging Group:

First highlight the Logging Group;Then open Edit menu:

Click menu bar Edit,or Right mouse click Logging Group;

Select New method;And select OPC Tag.

Add a Historical TagClick Logging Group and highlightSelect menu bar Edit/ New/ OPC Tag



OPC Tag Browser

Historical Tags are associated with an OPC Tag.

Adding an OPC Tag opens the OPC Tag Browser.

Assign OPC TagExpand My ComputerExpand Data AccessSelect OPC Server

Expand OPC Server tag databaseSelect Device (Boiler 1)Select OPC TagClick OK



Logging Group Panel

Expand the logging group in order to view historical tags.

Note that the default tag name is the OPC tag name.

In order to configure the Historical Tag, click on the tag name.

Configure Historical TagExpand Logging GroupClick on Tag



Historical Tag Panel

This opens the Historical Tag configuration panel.

Signal NameSignal name is the OPC Tag data source.Do not edit!

Edit Historical TagEnter DescriptionEnter Logging NameEnter Engineering UnitsEnter Range LimitsClick Apply button




Logging NameThe Logging Name is the historical tag name.Special characters are not allowed in the Logging Name.

DescriptionWhen a Historical tag is imported into a Trend Viewer, the description is used as the pen name.

Engineering UnitsEngineering units are imported into the Trend Viewer.

Range LimitsRange limits specify the visible range in the Trend Viewer.




Deadband frame

Deadband specifies the data logging method.Data loggers do not necessarily log every data sample.Data logging algorithms compact the database.

Absolute optionIn the Absolute method, all collected samples are logged.However, if the sample value is identical to the previous sample, then the sample is not logged.Every minute, a sample is logged regardless of change of value.

Percent optionIn the Percent method, the sample is logged when its value has exceeded the last logged value by the value specified in the text box field.The method includes a data compacting algorithm that is based on rate of change.




After configuration edits have been applied, the Historical Tag name in the tree view is updated with the Logging Name.

Click and drag tree view window edge in order to view complete Logging Name.

Re-size tree view windowClick Advance button




Advance and Simple buttonsThe Advance button displays the Log to Disk frame.

Log to Disk frameThe type of data to be logged is specified.

Raw dataStatistical result

All Samples optionDefault settingEach data sample collected is logged.




Statistical Variable OptionOnly one statistical variable can be selected to be logged.

When a statistical variable is selected, the Use Calculation Period check box is enabled.

When unchecked, the statistical result is calculated from all samples collected during the logging period.

When checked, the statistical result is calculated from all samples collected during the Calculation Period. Click Reset button




Reset clears all changes made since last apply.

Add New Tag button is short cut to add another historical tag to the logging group.

Add a new historical tagClick Add New Tag button




A logging group typically has multiple tags.

Add another tag to the logging group.

Edit Historical TagSelect OPC tagEnter DescriptionEnter Logging NameEnter Engineering UnitsEnter Range LimitsClick Apply button




In current example, logging group has three (3) tags:

Drum LevelDrum PressureSteam Flow

Click on Configuration tier



Configuration Panel

After building the configuration database, download the configuration to the SQL Server.

Make Active button forces download.

The Server Status indicates if the SQL Server is stopped or running.

Make sure SQL Server is stopped before downloading configuration

Start data logging.

Click Make Active button

Click Start Data Logging button



Configuration Panel

The Server Status indicates that SQL Server is running.

The Green Traffic light tool bar button also indicates SQL Server status.

The Server can also be started and stopped by clicking on the traffic light button.

Go to Logging Group.

Click on Logging Group



Logging Group Panel

When the logging group has started data collection, both the status folder and the Logging Group folder turn from blue to gold.



Server Database Folder

Open the Server Database folder in Procidia APPs folder.

The BoilerTrend.mdb file is the configuration and logging database.

The BoilerTrend.ldb file exists whenever the SQL Server is running.



Historical Trend Database File

If the operator station has Microsoft Access, then the BoilerTrend.mdb database can be opened.

Open with Microsoft Access 2003.

In this example, 4 tables have been created.

Boiler_1_4

The Boiler_1_Tags table contains the tag configured in the Boiler_1 logging group.



Logging Group Panel

Stop data logging.

Click Traffic Light tool bar button




The TrenWorX32 SQL Server collects and logs historical data.The historical trend configuration is built in the TrendWorX32 Configurator.Make Active saves changes to the configuration database and downloads pointers to the SQL Server.

Only one instance of the SQL Server runs in the operator station.The server only runs one configuration at a time.A configuration can have multiple logging groups.




Open TrendWorX32 SQL ServerClick Task Bar Start buttonSelect programs/ Siemens Procidia/ iWare PC/

TrendWorX32/ TrendWorX32 SQL Data Logger




The TrendWorX32 has a limited GUI (Graphical user Interface).

Current Configuration:Configuration Name

Status:SQL Server run status




Menu bar ActionsStart/Stop SQL Server

Start SQL ServerSelect menu bar Actions/

Start Logging




In applications with historical trending, it is recommended to automatically start the TrendWorX32 SQL Server when the operator logs onto the operator station.

The operator may not remember to start the SQL Server.

Starting the server from the Configurator or the SQL Server GUI is for convenience during the design phase.

For run-time applications, start the SQL Server using GenTray.



GenTray

Open GenTray utilityClick task bar Start buttonSelect Programs/ SIEMENS Procidia/ iWare PC/ Tools/ GenTray



GenTray

When GenTray is opened, a pink triangle icon appears in the task bar notification area.

GenTray manages the Procidia iWare servers.It starts and stops servers manually or automatically.

GenTray is the method to ensure that the SQL Server is started when the Procidia application starts.



GenTray

When GenTray is started, it starts all servers configured to Auto Start.

Configure TrendWorX32 SQL Server to Auto StartClick on GenTray iconSelect TrendWorX32Select TrendWorX32 SQL ServerClick Auto Start



GenTray

Check mark indicates that the Auto Start feature is enabled.

The SQL Server can also be started and stopped manually from GenTray.

If Start is enabled and stop is grayed- out, then the server is stopped.

Click Start to start the server.

If Stop is enabled and Start is grayed- out, then the server is running.

Click Stop to stop the server.



GenTray

Refer to the GenTray tutorial for more configuration guidelines.

The tutorial illustrates a method to automatically start GenTray when the operator logs onto the operator station.

It also illustrates methods to control the start sequence of the SQL Server.

Protection notice / Copyright notice© Siemens AG 2008. All rights reserved.

Technical SupportTel: 1-800-333-7421Hours: 8:00 am – 4:45 pm M-F (except holidays)

Internet Support Requesthttp://www.siemens.com/automation/support-request

Public Internet Sitehttp://www.usa.siemens.com/PI

Technical Support

http://www.siemens.com/automation/support-request

http://www.usa.siemens.com/PI

Procidia iWare TrendWorX32...TrendWorX32 Viewer Real Time Trend The pen is configured to an OPC tag....

Documents

Transcript of Procidia iWare TrendWorX32...TrendWorX32 Viewer Real Time Trend The pen is configured to an OPC tag....