Procidia iware TrendWorX32. TrendWorX32 Configurator April 2010

Transcription

1 Procidia iware TrendWorX32 TrendWorX32 Configurator Siemens Protection AG notice All / Copyright rights reserved. notice

2 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 Page 2

3 TrendWorX32 Overview Siemens Protection AG notice All / Copyright rights reserved. notice

4 TrendWorX32 Overview TrendWorX32 Components TrendWorX32 Configurator TrendWorX32 SQL Server Also referred to as the TrendWorX32 SQL Data Logger TrendWorX32 Viewer GraphWorX32 ActiveX component Persistent Trending Configurator TrendWorX32 Report Page 4

5 TrendWorX32 Configurator 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 Criteria Data collection rate Data 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. Page 5

6 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. Page 6

7 TrendWorX32 Viewer The TrendWorX32 Viewer is an ActiveX object that runs within GraphWorX32. In run-time, the Viewer displays pen trends. Historical trend Real time trend Persistent trend Page 7

8 TrendWorX32 Viewer Historical Trend The 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. Page 8

9 TrendWorX32 Viewer Real Time Trend The 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. Page 9

10 TrendWorX32 Viewer Persistent Trend Persistent 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. Page 10

11 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. Page 11

12 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 reports One time reports A report covers a specified reporting period. The report performs statistical analysis on raw data. Report provides an average value per time interval Other statistical data, like maximum value, can be reported per time interval. Page 12

13 TrendWorX32 Project Management Siemens Protection AG notice All / Copyright rights reserved. notice

14 Database Management The Procidia project is stored in the Procidia APPs folder. Create Server Database folder in Procidia APPs Create a Server Database folder in Procidia APPs. The Server Database folder organizes the project database configurations. Historical trend database AlarmWorX32 Server configuration Security Server configuration Page 14

15 TrendWorX32 Configurator Siemens Protection AG notice All / Copyright rights reserved. notice

16 TrendWorX32 Configurator Open TrendWorX32 Configurator Click Task Bar Start button Select programs/ Siemens Procidia/ iware PC/ TrendWorX32/ TrendWorX32 Configurator Page 16

17 TrendWorX32 Configurator Start new Historical Trend Configuration database Select Menu bar File/ New Page 17

18 Configuration Database Wizard Selecting File/ New opens the TrendWorX32 Logging Configurator Database Wizard. Start Configuration Database Wizard The Wizard helps to select and create the Historical Trend Configuration database file. Click Next button Page 18

19 Configuration Database Wizard The Historical Trend Configuration database can be either a Microsoft Access or SQL database. Select MS Access 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. Click Next button Page 19

20 Configuration Database Wizard With the database type specified, the next step is to create the database file. Create a new Historical Trend Configuration database The default location is iware/ Bin folder. It is recommended to save the Historical Trend Configuration database in Procidia APPs/ Server Database folder. Click Ellipsis button Page 20

21 Configuration Database Wizard In Procidia iware, Microsoft Access (mdb) database files are used for many types of database files. Select Server Database folder Enter database file name When naming a database file, identify the project (for example Boiler) and identify the database type (Trend). Click Save button Page 21

22 Configuration Database Wizard Finish creating the Historical Trend Configuration database file. Click Finish button Page 22

23 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. Page 23

24 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 Page 24

25 Configurator Overview 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. Page 25

26 Configurator Overview 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 active Download 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. Page 26

27 Configurator Overview 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. Page 27

28 Configurator Overview 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. Page 28

29 Configurator Overview 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. Page 29

30 Configuration Header A new configuration can be added by highlighting Configurations and selecting File/ New/ Configuration. Open Local_Configuration Click Local_Configuration It is easier to start configuring the default Local_Configuration. Page 30

31 Configuration Panel This opens the Configuration panel. Name, Modified Configuration name Local_Configuration is good. Network Node Name Specifies node with SQL Server. Recommend Local Page 31

32 Configuration Panel Connect/ Disconnect buttons Establishes a connection between the SQL Server and the Configurator. This permits configuartion downloads and start/ stop of server. Make Active button Downloads 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. Page 32

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

34 Configuration Panel Use Global Connection check box Default is enabled. Global means that the SQL Server maintains a constant connection with the database. Click Advance>> button Use UTC Time check box Time stamps are stored in UTC format. UTC compensates for change of local time due to daylight savings. Page 34

35 Configuration Panel Advance>>/ Simple<< buttons Buttons display/hide Retrials, Retrial Delay, Max Samples, and Max Logging Packets parameters. Retrials and Retrial Delay In the event that the logging operation fails, the server retries to log the logging packet. Max Samples Parameter specifies maximum number of samples to be maintained in memory buffer prior to logging data on a per tag basis. Page 35

36 Configurations Panel Max Logging Packets A 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 button After adjusting logging parameters, click Adjust Log Params button to apply changes. Page 36

37 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 Group Click Local_Configuration and highlight Select menu bar: Edit/ New/ Database Group Page 37

38 Database Group Panel Name Assign Database Group name Usually only one Database Group is created; therefore the name can describe the project. Enter Database Group name ODBC Data Source Assign an ODBC Data Source The ODBC establishes the connection between the MS Access logging database and the SQL Server. Click ODBC Data Source Browse button Page 38

39 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 Source Select Machine Data Source tab Click New button Page 39

40 ODBC Data Source Select System Data Source radio button Click Next button Select Microsoft Access Driver v4.0 Click Next button Page 40

41 ODBC Data Source Click Finish button Enter Data Source Name 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. Page 41

42 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 Page 42

43 ODBC Data Source Select Server Database folder Select Configuration database file Click OK ODBC connection is complete. Note Database connection. Click OK Page 43

44 ODBC Data Source The new Procidia system data source is listed. Click OK Data Source supports security It is not required. Click OK Page 44

45 Database Group Panel ODBC Data Source New Procidia system ODBC connection Save work Click Apply button Database Type MS Access Page 45

46 Database Group Panel Database Group was added to the configuration. Test Database Connection Click Perform Test button Test DB Connection Perform Test button verifies connection to logging database. Page 46

47 Database Group Panel Connection is good. Review Add Database Group to the Configuration. Assign Database Group name. Create a system ODBC database connection using MS Access drivers. Assign the Configuration database file as the logging database. Click Apply button to save and download changes. Click OK Page 47

48 Database Group Panel 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 Group Click Database Group and highlight Select menu bar Edit/ New/ Logging Group Page 48

49 Logging Group Panel Name Assign the Logging Group name. Name should describe the logging group. Enter Logging Group name A Database Group can contain multiple Logging Groups. Click Apply button Page 49

50 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. Page 50

51 Logging Group Panel Data Collection Tab Data Collection tab panel Data collection criteria is specified. Start and stop conditions are also specified. Select Data Collection tab Select Control Board panel button Control Board sub-panel The Data Collection rate is specified. When logging statistical data, the calculation period is also specified. Enter Data Collection Rate Enter Calculation Period Page 51

52 Logging Group Panel Data Collection Tab 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. Page 52

53 Logging Group Panel Data Collection Tab 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. Page 53

54 Logging Group Panel Data Collection Tab 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. Page 54

55 Logging Group Panel Data Collection Tab Start Conditions sub-panel On Start check box Default start condition Data collection starts whenever the SQL Server is started. Select Start Conditions panel button Select On Start check box Page 55

56 Logging Group Panel Data Collection Tab Start Conditions sub-panel On Condition Data 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 Time Data collection starts at a specific time of day. Method implies that data collection is also stopped daily. On Interval Data collection starts at a fixed time interval. Method also implies that the data collection is stopped on a regular basis. Page 56

57 Logging Group Panel Data Collection Tab Stop Conditions sub-panel No condition selected Default Data collection stops when the SQL Server is stopped. On Condition Compliments start conditions On Time Compliments start conditions On Interval Compliments start conditions Select Stop Conditions panel button Page 57

58 Logging Group Panel Logging Tab Logging tab panel These parameters specify data logging criteria. Select Logging tab On Interval check box Default condition Recommended logging criteria 2 minute interval is good On Records Default Data is logged when 30 samples for any tag have been collected. Page 58 Check On Interval check box Enter logging frequency Check On Records check box

59 Logging Group Panel Table Management Tab Table Management tab panel Table Management is a method of controlling the MS Access database size. Select Table(s) Management tab 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. Page 59

60 Logging Group Panel Table 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. Page 60

61 Logging Group Panel Table Management Tab Table Name text box This 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. Accept default Table Name Enter number of Tables Number of Tables list box This parameter specifies the maximum number of data tables per logging group. Page 61

62 Logging Group Panel Table Management Tab 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. Page 62

63 Logging Group Panel Table Management Tab 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. Page 63

64 Logging Group Panel Table Management Tab Create New Table frame These parameters specify when to create a new table Select On Time check box Enter time of day to create new table On Time check box Method creates a daily table. Parameter specifies time of day. This is the recommended method. Any Time Logging Starts A new table is started every time the Server is started. Default condition Method is also recommended. Select Any Time Logging Starts Click Apply button Page 64

65 Logging Group Panel Table Management Tab 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. Page 65

66 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 Tag Click Logging Group and highlight Select menu bar Edit/ New/ OPC Tag Page 66

67 OPC Tag Browser Historical Tags are associated with an OPC Tag. Adding an OPC Tag opens the OPC Tag Browser. Assign OPC Tag Expand My Computer Expand Data Access Select OPC Server Expand OPC Server tag database Select Device (Boiler 1) Select OPC Tag Click OK Page 67

68 Logging Group Panel Expand the logging group in order to view historical tags. Note that the default tag name is the OPC tag name. Configure Historical Tag Expand Logging Group Click on Tag In order to configure the Historical Tag, click on the tag name. Page 68

69 Historical Tag Panel This opens the Historical Tag configuration panel. Signal Name Signal name is the OPC Tag data source. Do not edit! Edit Historical Tag Enter Description Enter Logging Name Enter Engineering Units Enter Range Limits Click Apply button Page 69

70 Historical Tag Panel Logging Name The Logging Name is the historical tag name. Special characters are not allowed in the Logging Name. Description When a Historical tag is imported into a Trend Viewer, the description is used as the pen name. Engineering Units Engineering units are imported into the Trend Viewer. Range Limits Range limits specify the visible range in the Trend Viewer. Page 70

71 Historical Tag Panel Deadband frame Deadband specifies the data logging method. Data loggers do not necessarily log every data sample. Data logging algorithms compact the database. Absolute option In 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 option In 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. Page 71

72 Historical Tag Panel After configuration edits have been applied, the Historical Tag name in the tree view is updated with the Logging Name. Re-size tree view window Click Advance button Click and drag tree view window edge in order to view complete Logging Name. Page 72

73 Historical Tag Panel Advance and Simple buttons The Advance button displays the Log to Disk frame. Log to Disk frame The type of data to be logged is specified. Raw data Statistical result All Samples option Default setting Each data sample collected is logged. Page 73

74 Historical Tag Panel Statistical Variable Option Only 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 Page 74

75 Historical Tag Panel Reset clears all changes made since last apply. Add a new historical tag Click Add New Tag button Add New Tag button is short cut to add another historical tag to the logging group. Page 75

76 Historical Tag Panel A logging group typically has multiple tags. Add another tag to the logging group. Edit Historical Tag Select OPC tag Enter Description Enter Logging Name Enter Engineering Units Enter Range Limits Click Apply button Page 76

77 Historical Tag Panel In current example, logging group has three (3) tags: Drum Level Drum Pressure Steam Flow Click on Configuration tier Page 77

78 Configuration Panel After building the configuration database, download the configuration to the SQL Server. Make Active button forces download. Click Make Active button 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 Start Data Logging button Page 78

79 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 Page 79

80 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. Page 80

81 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. Page 81

82 Historical Trend Database File If the operator station has Microsoft Access, then the BoilerTrend.mdb database can be opened. Open with Microsoft Access 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. Page 82

83 Logging Group Panel Stop data logging. Click Traffic Light tool bar button Page 83

84 TrendWorX32 SQL Server Siemens Protection AG notice All / Copyright rights reserved. notice

85 TrendWorX32 SQL Server 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. Page 85

86 TrendWorX32 SQL Server Open TrendWorX32 SQL Server Click Task Bar Start button Select programs/ Siemens Procidia/ iware PC/ TrendWorX32/ TrendWorX32 SQL Data Logger Page 86

87 TrendWorX32 SQL Server The TrendWorX32 has a limited GUI (Graphical user Interface). Current Configuration: Configuration Name Status: SQL Server run status Page 87

88 TrendWorX32 SQL Server Menu bar Actions Start/Stop SQL Server Start SQL Server Select menu bar Actions/ Start Logging Page 88

89 TrendWorX32 SQL Server 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. Page 89

90 GenTray Open GenTray utility Click task bar Start button Select Programs/ SIEMENS Procidia/ iware PC/ Tools/ GenTray Page 90

91 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. Page 91

92 GenTray When GenTray is started, it starts all servers configured to Auto Start. Configure TrendWorX32 SQL Server to Auto Start Click on GenTray icon Select TrendWorX32 Select TrendWorX32 SQL Server Click Auto Start Page 92

93 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 grayedout, then the server is stopped. Click Start to start the server. If Stop is enabled and Start is grayedout, then the server is running. Click Stop to stop the server. Page 93

94 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. Page 94

95 Technical Support Technical Support Tel: Hours: 8:00 am 4:45 pm M-F (except holidays) Internet Support Request Public Internet Site Siemens Protection AG notice All / Copyright rights reserved. notice