processhistorianprhienus en us

7/27/2019 ProcessHistorianPRHIenUS en US

1/30

rocess Historian Administration ______________________________________

___________________

___________________

SIMATICProcess Historian V8.0 Update 1Process Historian Administration

System Manual

04/2012A5E03916798-02

Basics 1

Hardware configuration 2

Management console 3

Process control messages 4


2/30

Legal informationLegal informationWarning notice system

This manual contains notices you have to observe in order to ensure your personal safety, as well as to preventdamage to property. The notices referring to your personal safety are highlighted in the manual by a safety alertsymbol, notices referring only to property damage have no safety alert symbol. These notices shown below aregraded according to the degree of danger.

DANGERindicates that death or severe personal injury willresult if proper precautions are not taken.

WARNINGindicates that death or severe personal injury mayresult if proper precautions are not taken.

CAUTIONwith a safety alert symbol, indicates that minor personal injury can result if proper precautions are not taken.

CAUTIONwithout a safety alert symbol, indicates that property damage can result if proper precautions are not taken.

NOTICEindicates that an unintended result or situation can occur if the relevant information is not taken into account.

If more than one degree of danger is present, the warning notice representing the highest degree of danger willbe used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating toproperty damage.

Qualified PersonnelThe product/system described in this documentation may be operated only by personnel qualifiedfor the specifictask in accordance with the relevant documentation, in particular its warning notices and safety instructions.Qualified personnel are those who, based on their training and experience, are capable of identifying risks andavoiding potential hazards when working with these products/systems.

Proper use of Siemens productsNote the following:

WARNINGSiemens products may only be used for the applications described in the catalog and in the relevant technicaldocumentation. If products and components from other manufacturers are used, these must be recommendedor approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation andmaintenance are required to ensure that the products operate safely and without any problems. The permissibleambient conditions must be complied with. The information in the relevant documentation must be observed.

TrademarksAll names identified by are registered trademarks of Siemens AG. The remaining trademarks in this publicationmay be trademarks whose use by third parties for their own purposes could violate the rights of the owner.

Disclaimer of LiabilityWe have reviewed the contents of this publication to ensure consistency with the hardware and softwaredescribed. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, theinformation in this publication is reviewed regularly and any necessary corrections are included in subsequenteditions.

Siemens AGIndustry SectorPostfach 48 48

90026 NRNBERGGERMANY

Order number: A5E03916798-02 04/2012 Technical data subject to change

Copyright Siemens AG 2012.All rights reserved


3/30

Process Historian Administration

System Manual, 04/2012, A5E03916798-02 3

Table of contents

1 Basics........................................................................................................................................................ 51.1 Overview ........................................................................................................................................5

1.2 Data structures...............................................................................................................................7

1.3 Segmentation...............................................................................................................................11

2 Hardware configuration............................................................................................................................ 133 Management console .............................................................................................................................. 15

3.1 Overview ......................................................................................................................................153.2 Process Historian Management dashboard.................................................................................17

3.3 System structure dashboard ........................................................................................................17

3.4 I/O systems dashboard ................................................................................................................18

3.5 Diagnostics dashboard ................................................................................................................19

3.6 Backup/Restore dashboard .........................................................................................................203.6.1 Introduction ..................................................................................................................................203.6.2 Creating segment backups ..........................................................................................................213.6.3 Restoring a segment....................................................................................................................223.6.4 Deleting a segment ......................................................................................................................23

3.7 Configuring compression .............................................................................................................24

3.8 Changing segment settings .........................................................................................................25

3.9 Licensing dashboard....................................................................................................................27

4 Process control messages....................................................................................................................... 29


4/30

Table of contents


4 System Manual, 04/2012, A5E03916798-02


5/30


System Manual, 04/2012, A5E03916798-02 5

Basics 11.1 OverviewIntroduction

SIMATIC Process Historian is a central archiving system for storing process data, such asprocess values and messages. The Process Historian uses the Microsoft SQL Server 2008R2 SP1, 64-bit, and archives historical data that originates from a PCS 7 Operator Station(OS) and SIMATIC Batch. The data can belong to different PCS 7 projects. Access to the

historical data is transparent for the OS Clients.

ServicesProcess Historian employs four services for processing, storing and backing up data:

SIMATIC Process Historian ServerThis service implements all functions the server needs to process and store data.

Process Historian Maintenance ServiceThis service implements all functions that are necessary to maintain the ProcessHistorian database. The Maintenance Service handles tasks such as starting mirroring,

mirror monitoring, restore functions, maintenance of the transaction log and suchlike. Process Historian Redundancy Service

This service implements functions that are necessary for data exchange between tworedundant server systems.

Process Historian Discovery ServiceThis service supports the search for connected Process Historian systems. TheDiscovery Service is essential for the functionality of the Process Historian.


6/30

Basics

1.1 Overview


6 System Manual, 04/2012, A5E03916798-02

Operating statesYou can use the shortcut menu of the icon in the system tray to switch the Process Historian

to the following operating states: Starting Shutting down Starting restoreThe following table provides an overview of the operating states and the color coding of theassociated icons in the system tray:

Symbol Process Historian operating state DescriptionActive In the "Active" operating state, the Process Historian archives data. You

can query data from the OS Server or Information Server.

Restoring In the "Restoring" operating state, the Process Historian requests data froman OS Server for a recognized period of inactivity.

The preceding and the subsequent operating state is "Active".

Starting restore This operating state starts "Restoring".

Stopping restore This operating state terminates "ActiveRecovery" and is an intermediatestate between "ActiveRecovery" and "Active".

Deactivated The Process Historian changes to the "Deactivated" operating state in thecase of maintenance tasks where access to the database is limited. Themaintenance tasks can include the creation or the backing up/restoring ofsegments.

The system is offline in this operating state. Access via a network is notpossible.

Deactivate "Deactivate" is the intermediate state between "Active" and "Deactivated".

Error The "Error" operating state occurs when an error has been recognized orwhen no connection to the SIMATIC Process Historian service exists.

Inactive No data is archived in the "Inactive" operating state. In this operating state,you can carry out updates and maintenance work on the Process Historian

PC or restart the PC.Shutting down Intermediate state between "Active" and "Inactive"

Starting Intermediate state between "Inactive" and "Active"

Not defined Initial state for "Inactive"


7/30

Basics

1.2 Data structures


System Manual, 04/2012, A5E03916798-02 7

1.2 Data structuresTime variant value sequences

The Process Historian operates with time-variant value sequences that include runtime dataand configuration data in the form of context information. Each time-variant value sequenceis identified by a sequence identifier that references the configuration data and runtime datafor a time-variant value sequence.

A Process Historian database can contain several time-variant value sequences for whichthe following properties may be different:

Times for values Distances between values Number of values within a time period

Data groupMost time-variant value sequences are divided into groups in the Process Historian for betterparallel processing.

Each of these groups refers to a shared cluster of physical sources within the ProcessHistorian and the Process Historian database. This makes for better parallelization of thegroups.

Time-variant value sequences are always assigned to a fixed data group for a specific pointin time.

NoteYou can distribute the data groups among the available hard disks in order to influence theperformance and the scaling of the system used. Distribution is carried out using the Wizardwhen creating the database.


8/30

Basics

1.2 Data structures


8 System Manual, 04/2012, A5E03916798-02

PartitionThe amount of runtime data of a single time-variant value sequence is unlimited and grows

constantly. The entire amount of data that is assigned to an individual time-variant valuesequence or group must therefore be divided into several "partitions" using the time axis.

A partition includes runtime data for one or several time-variant value sequences that arelimited by time values.

The limited time values within a certain partition are referred to as "partition limitations".

Data groups are divided into partitions using the time axis.

The following conditions apply to partitions:

Each partition has a high and low limit for the time period. The time limits can be moved as required, but the high time limit must always be higher

than the low one.

The partitions of a data group should not overlap. It must always be possible to map each existing time value of a data group on an existing

partition. There may be no time gaps with undefined partitions.


9/30

Basics

1.2 Data structures


System Manual, 04/2012, A5E03916798-02 9

Segment of a runtime databaseA "segment" combines the data partitions of several data groups.


10/30

Basics

1.2 Data structures


10 System Manual, 04/2012, A5E03916798-02

A database segment S consists of the sum of partitions of all data groups that share thesame high and low time limits. These groups correspond to the limits of the segment.

The difference between the high and low time limit is referred to as the "time period" of thedatabase segment.

The time periods of all partitions within a segment must be aligned across all data groups. Ifthere is a partition with the low and high time limits t1 andt2 , there must also be a partitionwith the same time limits for each other data group. The time periods of segments do nothave to be identical here.

Each segment has a unique segment number.

The start segment, the first segment created in a system, has the number 100,000. The segment whose low limit is equal to the high limit of segment n is referred to as

segment n+1.

The segment whose high limit is equal to the low limit of segment n is referred to assegment n-1.


11/30

Basics

1.3 Segmentation


System Manual, 04/2012, A5E03916798-02 11

1.3 SegmentationIntroduction

The Process Historian can process and manage very large amounts of data. The saved datais split up into segments so that performance is not impaired.

Segments are defined by a time period with a high and low time limit. A segment containsthe amount of data that was recorded during the defined time period.

By default, segments are created with a segment size of one week when theProcess Historian database is created. You can change this setting. You can find informationon changing segment configurations under Changing segment settings(Page 25).

You cannot retroactively reconfigure segments that already contain data.

Segmentation configurationYou can change the properties of segmentation on the "Segmentation" dashboard asProcess Historian administrator.

You can make the following settings:

Anchor point of segmentation Time period of a segment Number of prepared segments Total number of runtime segmentsThe following table provides an overview of the basic segmentation parameters:

Parameter Value DescriptionAnchor pointof segmentation

Date, time Start time of the segment

Time periodof the segment

Week, month, quarter, year Segment size

Prepared segments Total number of prepared segmentsNumberof segments Total number of runtime

segmentsNumber of segments not yet archived and still inruntime

The Process Historian continuously creates segments with the defined time period. Toensure that the entire period of possible times is covered, there is a high and a low "Catchall" segment. These segments collect all incoming data that lies outside the current runtimesegment. The segments are called "Catch-all-upper" (CAU) and "Catch-all-lower" (CAL). TheCAL and CAU segments exist permanently. They cannot be deleted, removed or set tooffline.


12/30

Basics

1.3 Segmentation


12 System Manual, 04/2012, A5E03916798-02

Anchor pointIf you change the anchor point, it has to refer to a time after the last time stamp stored in the

segment filled last.If you change the segmentation configuration, all segments whose anchor point refers to atime after the new anchor point are deleted.

No data is lost when the segments are deleted, as only segments without content aredeleted.

NoteIf the last segment of the existing segmentation configuration ends before the anchor point ofthe new segmentation, an intermediate segment must be created. This intermediatesegment starts with the end time of the last segment of the existing segmentationconfiguration and ends with the start time of the new segmentation configuration. A suitable

anchor point is suggested to avoid the need for an intermediate segment. If you reject thissuggestion, an intermediate segment is created automatically.

If the anchor point of the new segmentation configuration is located before the end time ofthe segment currently being used and after the last value saved, the end time of the segmentcurrently being used is specified as the new anchor point. A minimum safety time interval isset in the process.

The required number of future segments is created according to the new segmentationsettings.

Segment types and segment statusesIn the Process Historian, a distinction is made between segments of the "Runtime" and"Archive" types. Runtime segments are displayed on the "Segmentation" dashboard. Theyhave the following properties:

Data in runtime segments can be changed by the Process Historian system at any time Available in the quantity as configured under "Segmentation" Runtime segments cannot be compressed Runtime segments cannot be backed up

Archive segments are displayed on the "Backup/Restore" dashboard. Archive segments arecompressed or uncompressed, depending on the setting.

The status of a segment is classified as "Online" or "Offline". Segments of the "Runtime" typealways have the status "Online". Segments of the "Archive" type can have the status"Online" or the status "Offline".

You can only read the contents of segments that are online. You cannot read data fromarchived segments that are offline.

In order to read the contents of segments that are offline, you have to restore thesesegments.

Information about restoring a segment is available under Restoring a segment(Page 22).


13/30


System Manual, 04/2012, A5E03916798-02 13

Hardware configuration 2Overview

The described hardware configurations refer to the SIMATIC Process Historian and theInformation Server. The simple configuration of Process Historian provides a clear overviewof the topology.

The following figure illustrates a simple configuration:

A sufficiently powerful PC system is capable of handling all tasks involved. This configurationis suitable for small-scale installations with corresponding quantity frameworks.


14/30

Hardware configuration


14 System Manual, 04/2012, A5E03916798-02

Hardware example for small quantity frameworksThe example applies to a Process Historian computer on IPC base under the following

conditions: Data from up to three OS Maximum archiving load of 1,000 values per secondWe recommend the following hardware equipment in this case:

CPU Core i7-610E (2C/4T, 2.53 GHz, 4 MB Cache,TB, VT-x, VT-d, EM64-T)

RAM 8 GB DDR3 SDRAM (2 x 4 GB), DIMM, ECC,Dual Channel

1 x 100 GB SSD SATA; internal for operating system and softwareHard disks

RAID5 (3 x 1 TB, HDD SAS) in removableframe, hot swap, on front, HW RAID controller

for transaction log and data

PCIe X8 in PCIe X16 slots including batterybackup unit (BBU)

Drives DVDRW

The described RAID5 system has a size of about 1.8 TB. All SAS hard drives are connectedto the hardware RAID controller.

The example configuration demonstrates the minimum hardware requirements. CPUperformance, work memory, and the I/O systems may have to be expanded, depending onthe data volume.

Hardware example for larger quantity frameworksThe following example describes the configuration of a PRIMERGY TX300 S6 with thefollowing minimum equipment:

CPU Intel Xeon X5660 6C/12T 2.80 GHz

RAM 3 x 16 GB DDR3

1 x 300 GB HDD SAS for operating system and programs

1 x 300 GB HDD SAS for transaction log

Hard disk

4 x 900 GB HDD SAS RAID 10 for archive data

RAID controller SAS / 512 MB with BBU expansion

The RAM and the number of processors and hard disks can be expanded with thisconfiguration.

Storage Area Network (SAN) is supported.


15/30


System Manual, 04/2012, A5E03916798-02 15

Management console 33.1 Overview

The management console is included in the installation of the Process Historian. It is usedfor diagnostics and configuration of the Process Historian system and is automaticallystarted upon logon. For a manual start, the management console is available under "Start >Programs > Siemens Automation > SIMATIC > Process Historian > Process HistorianManagement Console".

The following table shows the dashboards of the management console and their tasks:

Dashboard DescriptionProcess HistorianManagement

Display of fundamental hardware indicators and performance indicators forthe PC and operating system

Display of basic indicators for the status and current activity of theProcess Historian Server

Display of the license status Changing the operating state

System structure Display of connected projects Display of the OS Server systems Display of the PC name

I/O systems Display of the available input and output devices Display of the memory space used Detailed information about the load

Diagnostics Diagnostic messages of the Process Historian Messages from the event display of the operating system

Backup/Restore Display of the segments of the "Archive" type Creating segment backups Restoring backed-up segments

Compression Display of the compression state Turning on and turning off the post-compression Configuration of the number of uncompressed archive segments

Segmentation Display of the current segmentation setting Changing the segmentation settings

Licensing Display of the current license status of server and project


16/30

Management console

3.1 Overview


16 System Manual, 04/2012, A5E03916798-02

NoteProcess Historian does not archive dataIf the Process Historian does not archive data, check the MS Message Queuing and thedatabases.


17/30

Management console

3.2 Process Historian Management dashboard


System Manual, 04/2012, A5E03916798-02 17

3.2 Process Historian Management dashboardThe "Process Historian Management" dashboard includes information about:

Basic indicators for monitoring the PC:Processor utilizationFree memoryHard drive utilization

Basic indicators on Process Historian:Number of connected data sourcesStored tags per secondStored messages per second

Operating state of the Process Historian server License status of the Process Historian

Changing the operating modeYou can change the operating state of the Process Historian on the"Process Historian Management" dashboard.

You can choose from the following operating modes:

Start

Shutting down Starting restoreFor this purpose, select the respective entry from the drop-down list in the "Process HistorianStatus" area.

3.3 System structure dashboardThe "System structure" dashboard displays all projects that are currently integrated in thesystem. The following information on the project is displayed when you select a project:

Name Type


18/30

Management console

3.4 I/O systems dashboard


18 System Manual, 04/2012, A5E03916798-02

3.4 I/O systems dashboardThe "I/O systems" dashboard displays the entire memory system to which there is read andwrite access and in which data is archived. The dashboard displays all hard drives integratedin the system. This includes hard drives that do not contain archive data.

The "I/O systems" dashboard displays the following information on the storage system:

Name and drive letter of the hard drives File system Total storage space Absolute available storage space Free storage space in percent Absolute storage space usedThe states of the input and output devices are graphically monitored by the system. If youselect a drive, you receive the following detailed information on the selected drive:

Idle time of the hard drive Average duration per transfer Average length of queue for read access Average length of queue for write access Reading speed in bytes per second Writing speed in bytes per second


19/30

Management console

3.5 Diagnostics dashboard


System Manual, 04/2012, A5E03916798-02 19

3.5 Diagnostics dashboardThe upper area of the "Diagnostics" dashboard displays the last 1000 diagnostic messagesfrom the Process Historian event log.

The event log of the Process Historian contains the following information:

Log entry ID Severity of the message Time stamp Name of application domain Process ID MessageThe lower section of the dashboard includes the last 100 entries from the event log forWindows applications. The following information is displayed:

Time stamp Message Category Source


20/30

Management console

3.6 Backup/Restore dashboard


20 System Manual, 04/2012, A5E03916798-02


3.6.1 IntroductionBackup types

The Process Historian saves process values and messages in temporally defined segments.Back up the contents of the Process Historian database correspondingly by segment.

When an archive segment is backed up, the runtime data is stored in the backup file. Thestored data includes:

Process values Messages Configuration data


21/30

Management console



System Manual, 04/2012, A5E03916798-02 21

3.6.2 Creating segment backupsRequirement

The segment to be backed up has the "Archive" status.

NoteDuring backup or restore, the Process Historian switches to the "Deactivated" state up to twotimes.

No runtime data is archived in this operating state. Your access to the database is limited.

Procedure1. Select the "Backup/Restore" dashboard in the navigation of the management console.2. Select the segment you want to back up in the "Archive segment" area.3. Click the "Backup" button to launch backup.

NoteIf you activate the "Set segment offline after backup" option, the segment is deleted assoon as the backup has been successfully completed.

You cannot access the data of a deleted segment with the "Offline" status until the

segment has been restored.

4. Select the storage location for the backup file in the "Backup segment" dialog box thatopens. Click "Backup."

You can specify further identifiers and descriptions for the backup such as the name ornumber of the data medium.

ResultA backup is created and the date of the backup entered. The segment remains in the"Online" status and is not moved.

If you have activated the "Set segment offline after backup" option, the selected segmentsare backed up and moved to the "Restore segment" section.


22/30

Management console



22 System Manual, 04/2012, A5E03916798-02

3.6.3 Restoring a segmentIf you want to access data that is stored in an archived segment, you must restore the

respective segments. When restoring a segment, the backup file corresponding to thesegment is selected.

NoteDuring backup or restore, the Process Historian switches to the "Deactivated" state up to twotimes.

No runtime data is archived in this operating state. Your access to the database is limited.

Requirement The corresponding backup file for the segment to be restored is available. The Process Historian is in the "Active" operating state.

Procedure1. Select the "Backup/Restore" dashboard in the navigation of the management console.2. Select the desired segment in the "Restore segments" section.3. Click on the "Restore" button.4. In the "Backup segment" dialog, select the corresponding backup file for the segment that

is to be restored.5. Click "Restore."

ResultYou can access the data of the restored segment from the OS Server, OS Client or theInformation Server.


23/30

Management console



System Manual, 04/2012, A5E03916798-02 23

3.6.4 Deleting a segmentRequirement

There is a valid backup for the segment that is to be deleted.

NoteYou can only use the "Delete" button if a backup of the selected segment has already beencreated and this segment is marked as "valid". A segment is, for example, marked as"invalid" if additional runtime data for the segment has accumulated after the creation of abackup. In this case, create a backup of the relevant segment again.

You can only delete segments individually.

Procedure1. Select the "Backup/Restore" dashboard in the navigation of the management console.2. Select the segment you want to delete in the "Archive segments" area.3. Click "Delete".

ResultThe segment is deleted from the database.


24/30

Management console

3.7 Configuring compression


24 System Manual, 04/2012, A5E03916798-02

3.7 Configuring compressionOn the "Compression" dashboard, you can see the current compression state as well as thecurrent default number of uncompressed segments contained. The contained uncompressedsegments are counted starting from the first archive segment.

NoteThe archive segments are compressed automatically in the background. You can set thenumber of archive segments that are not to be compressed. The possible compressionfactor depends on additional influences, such as the number and archiving cycles of theprocess values.

Procedure1. Select the "Compression" dashboard in the navigation of the management console.2. Enable the Activate option button.3. Enter the number of uncompressed segments you want to keep in the "Configuration"

area.

4. Click the "Update settings" button.

ResultThe settings for the compression of archive segments have been modified.


25/30

Management console

3.8 Changing segment settings


System Manual, 04/2012, A5E03916798-02 25

3.8 Changing segment settingsThe "Segmentation" dashboard provides an overview of the current segmentationconfiguration.

The segment states are color coded:

Segment status ColorCompleted runtime segment Gray

Current segment Green

Prepared segment Blue

You can modify the configuration of the segmentation in the "Settings" area.

The "Database Installation Wizard" supports you during the installation of the Process

Historian database. By default, the following presettings are made for the segmentationduring installation:

Segment size One week

Total number of segments in runtime Eight

Number of prepared segments Three

Depending on the quantity structure, the amount of data per segment can be very large. Thisapplies to all segments in runtime. When the segments are created, the estimated requiredmemory space is reserved.

The optimum settings for the segmentation are a compromise between the memory space

used and the number of uncompressed data segments to be reserved.The Process Historian database is automatically switched to the "Deactivated" state to allowthe segmentation of the Process Historian to be changed. After the settings have beenmade, the database changes back to the "Active" state automatically.

NoteThe Process Historian database is switched automatically to the "Deactivated" state to allowchanges to the segmentation to be carried out. After the settings have been accepted, thedatabase changes back to the "Active" state automatically.


26/30

Management console

3.8 Changing segment settings


26 System Manual, 04/2012, A5E03916798-02

Procedure1. Select the "Segmentation" dashboard in the navigation of the management console.2. In the "Number of segments" area, select the required number of segments to be

prepared continuously.

3. In the "Number of segments" area, select the required total number of runtime segments.4. Click the "Accept settings" button.

ResultSegmentation of the Process Historian is configured.


27/30

Management console

3.9 Licensing dashboard


System Manual, 04/2012, A5E03916798-02 27

3.9 Licensing dashboardThe "Licensing" dashboard gives you an overview of the licenses used and available in thesystem. The availability of the Process Historian license is displayed.

You also obtain detailed information about the states of the tag licenses:

Available Required FreeWhen you select a project, you receive information on the project-specific license states withthe following information:

Project name Project type Number of tags


28/30

Management console

3.9 Licensing dashboard


28 System Manual, 04/2012, A5E03916798-02


29/30


System Manual, 04/2012, A5E03916798-02 29

Process control messages 4Overview

Process Historian contains process control messages that visualize specific system states.These pre-defined messages only contain information about process control states and donot return process status data.

The following table provides an overview of the process control messages generated inProcess Historian:

Message number Message text1012500 PHRDY: Start recovery for Process Historian

1012501 PHRDY: Recovery for Process Historian is completed

1012502 PHRDY: Communication with Process Historian is not available

1012503 PHRDY: Communication with Process Historian faulty

1012504 PHRDY: Communication with Process Historian reestablished

1012505 PHRDY: Process Historian Server offline since @1%s@

1012600 PH: Data memory occupied by @1%d@%

1012601 PH: System out of resources


30/30

Process control messages


processhistorianprhienus en us

Documents