safety historian – basic version r200.1

8/19/2019 Safety Historian – Basic Version R200.1

http://slidepdf.com/reader/full/safety-historian-basic-version-r2001 1/199

Safety HistorianRelease 200.1

Basic VersionRevision 01 (12/2013)

SH50-200.1



Copyright, Notices, and Trademarks

© 2013 – Honeywell Safety Management Systems a divi sion o f Honeywell Aerospace BV.

Release 200.1 (Basic Version)Revision 01 — 12/2013

While this information is presented in good faith and believed to be accurate,Honeywell Safety Management Systems disclaims the implied warranties ofmerchantability and fitness for a particular purpose and makes no express warrantiesexcept as may be stated in its written agreement with and for its customer.

In no event is Honeywell Safety Management Systems liable to anyone for any indirect,special or consequential damages. The information and specifications in this documentare subject to change without notice.

TotalPlant, TDC 3000 and Universal Control Network are U.S. registered trademarks ofHoneywell International Inc.

Experion PKS and PlantScape are trademarks of Honeywell International Inc.

Safety Manager, Safety Historian, FSC and QMR are trademarks ofHoneywell Safety Management Systems

Other brands or product names are trademarks of their respective holders.

No part of this document may be reproduced or transmitted in any form or by any means,electronic or mechanical, for any purpose, without the express written permission ofHoneywell Safety Management Systems.



Safety Historian R200.1 (Basic Version)

About This Publication


This publication is designed to provide all information required to properly set up, configure, anduse Safety Historian R200.1. Safety Historian is a Windows application that retrieves events

from Event Detecting Devices (e.g. Safety Manager controllers) and allows the user to viewthese events in a large number of user-definable formats.

Depending on the software options you purchased, if any, you may also need the following

document:

• SH51-200.1 (Safety Historian R200.1 - Network option),

Where appropriate, this manual refers to the above mentioned document.




Table of Contents i

TABLE OF CONTENTS

SECTION 1 – INTRODUCTION TO SAFETY HISTORIAN ...................................................................... 1

1.1 Section Overview .............................................................................................................. 1

1.2 About Safety Historian ..................... ......................... ........................ ......................... ........ 2

1.3 Safety Historian Packages ................................................................................................. 4

1.4 Stand-Alone (‘Basic’) versus Network Applications ...................... ......................... ............. 6

1.5

Terminology .....................................................................................................................10

1.6

Using This Manual ............................................................................................................14

SECTION 2 – SETTING UP SAFETY HISTORIAN ................................................................................16

2.1

Section Overview .............................................................................................................16

2.2 Requirements ...................................................................................................................17

2.3

Hardware Connections .....................................................................................................19

2.3.1 Connections Overview ......................................................................................................19

2.3.2 RS-232 Communication ....................... ......................... ........................ ......................... ...21

2.3.3 RS-485 Communication ....................... ......................... ........................ ......................... ...22

2.3.4

Ethernet Communication ..................................................................................................25

2.4

Preparing the Safety Manager System ....................... ......................... ........................ ......29

2.5 Preparing the FSC System ...............................................................................................29

2.6

Installing the Safety Historian Software ....................... ........................ ......................... .....30

2.7

Uninstalling the Safety Historian Software ....................... ......................... ........................ .39

2.8

Keep the Safety Historian computer secure and reliable ............................................ .......41

SECTION 3 – GETTING STARTED .......................................................................................................41

3.1 Section Overview .............................................................................................................41

3.2 Program Basics ................................................................................................................42

3.3 Configuration & Tasks area ..............................................................................................45

3.4

Event Windows area .........................................................................................................48

3.5

Multibox Controls ........................ ......................... ........................ ......................... ............49

3.6

Error Reporting ....................... ........................ ......................... ........................ .................50

3.7

License and Version Information ........................ ........................ ......................... ..............52

3.8

Password Protection ........................ ........................ ......................... ........................ ........53

SECTION 4 – THE NETWORK ARCHITECTURE ..................................................................................57

4.1

Section Overview .............................................................................................................57

4.2

Introduction ......................................................................................................................58

4.3

Network Architecture Basics .............................................................................................59

4.4

Working with Event Detecting Devices (EDDs) .................................................................62




ii Table of Contents

4.4.1

Introduction ...................................................................................................................... 62

4.4.2

Adding an EDD ........................ ......................... ........................ ......................... .............. 64

4.4.3

Reviewing or Editing an EDD .................................. ........................ ......................... ........ 65

4.4.4

EDD Properties ........................ ......................... ........................ ......................... .............. 65

4.4.5 Deleting an EDD .............................................................................................................. 74

4.5

Working with Printers ....................................................................................................... 75

4.5.1

Introduction ...................................................................................................................... 75

4.5.2

Adding a Printer ....................... ......................... ........................ ......................... .............. 76

4.5.3 Reviewing or Editing a Printer ................................. ........................ ......................... ........ 77

4.5.4 Printer Properties ...................... ........................ ......................... ........................ .............. 77

4.5.5

Deleting a Printer ............................................................................................................. 80

4.6 Printing the Network Architecture ............................................ ......................... ................ 81

SECTION 5 – WORKING WITH POINTS ............................................................................................... 85

5.1

Section Overview ...................... ........................ ......................... ........................ .............. 85

5.2

Introduction ...................................................................................................................... 86

5.3

Point Configuration ....................... ......................... ......................... ........................ .......... 87

5.3.1

Introduction ...................................................................................................................... 87

5.3.2

Point Properties................................................................................................................ 88

5.3.3

The Point Browser ........................ ......................... ......................... ........................ .......... 91

5.4

Adding Points ....................... ......................... ........................ ......................... .................. 92

5.5

Editing Point Properties ..................... ......................... ........................ ......................... ..... 94

5.6

Deleting Points ..................... ......................... ........................ ......................... .................. 95

SECTION 6 – IMPORTING AND EXPORTING POINTS ........................................................................ 96

6.1

Section Overview ...................... ........................ ......................... ........................ .............. 96

6.2

Importing Points ....................... ......................... ........................ ......................... .............. 97

SECTION 7 – WORKING WITH EVENTS ............................................................................................ 106

7.1

Section Overview ...................... ........................ ......................... ........................ ............ 106

7.2

Viewing Modes ..................... ......................... ........................ ......................... ................ 107

7.3

Event Message Properties ............................................................................................. 108

7.4

Incoming Events............................................................................................................. 112

7.4.1

Viewing Incoming Events ....................................... ......................... ........................ ....... 112

7.4.2

Continuous Printing of Incoming Events ................... ......................... ........................ ..... 114

7.5

Historical Events ...................... ......................... ........................ ......................... ............ 117

7.5.1

Viewing and Filtering Historical Events ................................. ........................ .................. 117

7.5.2

Exporting Historical Events ......................... ........................ ......................... ................... 121

7.5.3

Automatic Export Of Events..................................... ........................ ......................... ...... 123

SECTION 8 – VISIBILITY AND FILTERING OF EVENTS .................................................................... 130

8.1

Section Overview ...................... ........................ ......................... ........................ ............ 130

8.2 Event Visibility Status ........................ ......................... ........................ ......................... ... 131

8.2.1

Introduction ...................... ........................ ......................... ........................ ..................... 131

8.2.2

At Unit/Subunit Level ..................... ......................... ........................ ......................... ....... 132




Table of Contents iii

8.2.3

At Point Level ......................... ........................ ......................... ........................ ...............134

8.2.4

Overriding the Event Visibility Status...............................................................................135

8.3

Event Filters ...................................................................................................................137

8.3.1

Introduction ....................................................................................................................137

8.3.2

Defining Event Filters .....................................................................................................138

8.3.3

Specifying Filter Criteria ....................... ......................... ........................ ......................... .141

8.3.4

Using Event Filters .........................................................................................................144

SECTION 9 – CUSTOMIZING WINDOW LAYOUTS ............................................................................146

9.1

Section Overview ...........................................................................................................146

9.2 Customizing the Points Window ......................... ........................ ......................... ............147

9.2.1

Introduction ....................................................................................................................147

9.2.2 Resizing the Column Width ....................... ........................ ......................... .....................147

9.2.3

Hiding and Showing Columns .........................................................................................148

9.2.4

Rearranging the Column Order ..................... ......................... ........................ .................151

9.2.5

Setting the Default Status Messages ..............................................................................151

9.3

Customizing the Event Windows ........................ ........................ ......................... ............155

9.3.1

Introduction ....................................................................................................................155

9.3.2

Resizing the Column Width ....................... ........................ ......................... .....................155

9.3.3

Hiding and Showing Columns .........................................................................................156

9.3.4

Rearranging the Column Order ..................... ......................... ........................ .................159

9.3.5 Customizing the default Event Colors .............................................................................160

9.3.6

Showing or Hiding the Grid Lines ....................... ........................ ......................... ............164

9.3.7 Customizing the Event Type Names ...................... ......................... ........................ ........165

9.4

Customizing the Log & Error Messages Window ...................... ......................... ..............167

9.4.1 Introduction ....................................................................................................................167

9.4.2 Resizing the Column Width ....................... ........................ ......................... .....................167

SECTION 10 – PROGRAM MAINTENANCE .......................................................................................168

10.1

Section Overview ...........................................................................................................168

10.2

Program Maintenance and Customization Overview ......................... ........................ ......169

10.3

Setting the Daylight Saving Time ....................... ........................ ......................... ............171

10.4

Defining Work Shifts .......................................................................................................173

10.5 Time Synchronization of Event Detecting Devices ............................................ ..............174

10.6

Backing Up the Configuration .........................................................................................177

10.7

Restoring the Configuration ............................................................................................179

10.8

Password Maintenance ..................................................................................................181

APPENDIX A – ERROR MESSAGES DURING SOFTWARE INSTALLATION ....................................184

APPENDIX B – TROUBLESHOOTING ................................................................................................186

Error Messages ..................... ........................ ......................... ......................... ........................ ........186




iv Table of Contents

FIGURES

Figure 1-1 Safety Historian in stand-alone configuration (example) ..................... ......................... ........... 6

Figure 1-2 Safety Historian in network configuration (example) ...................... ......................... ................ 8 Figure 2-1 Hardware connections for Safety Historian Basic Version ....................... ........................ ..... 20

Figure 2-2 RS-232 communication cable, type FS-CCE232-02/L10 ......................... ........................ ..... 21

Figure 2-3 Jumper settings for the Black Box IC133C 2-Port RS-232/422/485 PCI Host Adapter inRS-422/485 mode ..................... ......................... ........................ ......................... ..... 23

Figure 2-4 Jumper settings for the Black Box IC187C-LP RS-232/422/485 PCI Host Adapter in RS-422/485 mode .......................................................................................................... 23

Figure 2-5 Dip-switch settings for the Black Box IC983C-LP RS-232/422/485 PCIe Host Adapter inRS-422 mode (best mode for RS-485 DS-SOE communications) ...................... ....... 24

Figure 2-6 RS-485 communication cable, type FS-CCE-485-02/Lx for Black-Box IC133C orIC187C-LP PC communication interface ........................ ........................ ................... 25

Figure 2-7 Redundancy options for Ethernet communication at an FSC controller ......................... ....... 27

Figure 2-8 Hard disk Properties window (Write caching) ..................... ......................... ........................ ... 31

Figure 2-9 Software License Agreement window ..................... ......................... ........................ ............ 32

Figure 2-10 Entering user information ........................ ........................ ......................... ........................ . 33

Figure 2-11 Entering license number ...................... ........................ ......................... ........................ ..... 34

Figure 2-12 Choosing the destination folder for Safety Historian ......................... ........................ .......... 35

Figure 2-13 Selecting a program folder................................... ........................ ......................... ............. 36

Figure 2-14 Installation summary window ....................... ......................... ........................ ..................... 37

Figure 2-15 Safety Historian shortcut on desktop ......................... ........................ ......................... ....... 38

Figure 2-16 Uninstalling Safety Historian software ........................ ........................ ......................... ....... 39

Figure 2-17 Confirming uninstall ........................ ........................ ......................... ........................ .......... 40

Figure 3-1 Safety Historian shortcut on desktop ...................... ......................... ........................ ............ 42

Figure 3-2 Main Safety Historian application screen ......................... ........................ ......................... ... 44

Figure 3-3 Multibox controls ......................... ........................ ......................... ........................ ............... 49

Figure 3-4 Standard Safety Historian error message box ...................... ......................... ....................... 50

Figure 3-5 Click Honeywell brand to launch the About box ...................................... ......................... ...... 52

Figure 3-6 License and version information ........................ ......................... ......................... ................ 52

Figure 3-7 Password entry window ........................ ......................... ........................ ......................... ..... 53

Figure 4-1 Network Architecture window ........................ ......................... ........................ ..................... 60

Figure 4-2 Safety Historian network architecture and SM/FSC networks ...................... ........................ . 62

Figure 4-3 Properties for Ethernet EDD ...................... ......................... ........................ ......................... 66

Figure 4-4 Properties for Serial EDD ...................... ........................ ......................... ........................ ..... 66

Figure 4-5 Properties for slave EDD (connected via master EDD to Safety Historian Station) ................. 66

Figure 4-6 Communication settings for an EDD ....................... ......................... ........................ ............ 70

Figure 4-7 Physical view of Safety Historian network in Safety Builder ....................... ........................ ..... 71

Figure 4-8 Properties window showing COM port identification. ........................ ........................ .............. 72

Figure 4-9 Print Setup dialog ........................ ......................... ........................ ......................... .............. 77

Figure 4-10 Previewing printer output of the network architecture ....................... ......................... ......... 82

Figure 5-1 Points window ......................... ........................ ......................... ........................ ................... 88

Figure 5-2 Point Properties window ....................... ......................... ........................ ......................... ..... 92 Figure 6-1 SM to Safety Historian convertor (xls to dBASE) ......................... ........................ ................... 99

Figure 6-2 Security Warning in Excel.......................... ......................... ........................ ......................... .. 99

Figure 6-3 ‘step 1’ of conversion from xls to dBASE format...................... ........................ ..................... 100

Figure 6-4 Setting points import options ....................... ........................ ......................... ....................... 102

Figure 7-1 Viewing incoming events ...................... ......................... ........................ ......................... ... 112

Figure 7-2 Setting up continuous printing ....................... ......................... ........................ ................... 115

Figure 7-3 Filter controls in Historical Events window. ................................ ......................... ................. 117

Figure 7-4 Progress bar ...................... ......................... ........................ ......................... ..................... 118

Figure 7-5 Viewing the Historical Events ........................ ......................... ........................ ................... 119




Table of Contents v

Figure 7-6 Export events dialog ...................... ......................... ........................ ......................... ..........121

Figure 7-7 Defining Automatic export of events ...................... ........................ ......................... ............124

Figure 8-1 Setting the event visibility at unit/subunit level ........................ ......................... ...................133

Figure 8-2 Setting the event visibility at point level ..................... ......................... ........................ ........135

Figure 8-3 Overriding the event visibility status ...................... ......................... ........................ ............136

Figure 8-4 Defining event filters ...................... ......................... ........................ ......................... ..........138

Figure 8-5 Defining the event filter criteria............................................. ......................... .....................140

Figure 8-6 Time-related filter criteria ........................ ......................... ........................ ......................... .141

Figure 8-7 Using the calendar ........................ ......................... ........................ ......................... ..........142

Figure 8-8 Point filter criteria ....................... ........................ ......................... ........................ ...............144

Figure 8-9 Filter controls in Historical Events window............................................................................145

Figure 9-1 Dragging column widths ......................... ........................ ......................... ........................ ..147

Figure 9-2 Defining the layout of the Points window ....................... ......................... ........................ ....149

Figure 9-3 Setting the default status messages (combined with customizing event colors andEvent type names) ..................................................................................................153

Figure 9-4 Dragging column widths ......................... ........................ ......................... ........................ ..155

Figure 9-5 Defining the layout of the events windows.............................. ........................ ....................157

Figure 9-6 Customizing event colors in the event windows (combined with Event type names and

Status Messages) ...................................................................................................162 Figure 9-7 Selecting a color ........................ ........................ ......................... ........................ ...............163

Figure 9-8 Grid lines on and off ...................... ......................... ........................ ......................... ..........164

Figure 9-9 Showing or hiding the grid lines ......................... ......................... ........................ .................165

Figure 9-10 Dragging column widths ....................... ......................... ........................ ......................... .167

Figure 10-1 General program options ...................................................................................................172

Figure 10-2 Backing up the configuration ...................... ........................ ......................... .....................177

Figure 10-3 Specify and locate Backup File Name dialog ...................................... ........................ .......178

Figure 10-4 Restoring the configuration ........................ ........................ ......................... .....................179

Figure 10-5 Locate and select Backup File dialog ....................... ......................... ........................ ........180

Figure 10-6 Passwords window ...................... ......................... ........................ ......................... ..........182

TABLES

Table 2-1 Hardware connections for Safety Historian Basic Version ..................... ......................... .......21

Table 2 Dip-switch Settings ....................................................................................................................24

Table 3 Electrical Interface Modes ......................... ........................ ......................... ........................ ........24

Table 3-1 Safety Historian functions and required authorization levels ...................... ......................... ...55

Table 4-1 Most important functions in Print Preview window ........................ ........................ .................83

Table 6-1 Structure of dBASE point import file ....................... ........................ ......................... ..............97

Table 7-1 Structure of CSV event export file ..................... ......................... ........................ .................122

Table 10-1 Safety Historian maintenance and customization options ........................ ......................... .169

Table B-1 Error messages and their solutions.................................... ........................ .........................186




vi Table of Contents

REFERENCES

PublicationTitle

PublicationNumber

Safety Historian – Basic Version R200.1 SH50-200.1

Safety Historian – Network Option R200.1 SH51-200.1

Safety Manager Software Reference EP-SM.MAN.6285

FSC Software Manual FS80-xxx*

* 'xxx' is the release number. For example, the Software Manual for FSC R700 is referencedas FS80-700



Section 1 – Introduction to Safety Historian

1.1 Section Overview

Section overview This section provides a general overview of the Safety Historian

application and this manual. It covers the following topics:

Subsection Topic See page

1.1 Section Overview ...........................................................................................1

1.2 About Safety Historian ...................................................................................2

1.3 Safety Historian Packages .............................................................................4

1.4

Stand-Alone (‘Basic’) versus Network Applications ......................................... 6

1.5 Terminology................................................................................................. 10

1.6 Using This Manual ....................................................................................... 14



1.2 About Safety Historian

AboutSafety Historian

Safety Historian is part of Honeywell's Safety Manager (SM) and FailSafe Control (FSC) product lines.

This software package records and logs point events, alarm events

and diagnostic events that are detected by the connected SM

controller(s) and/or FSC controller(s). The events are stored in its

event database including detailed time-stamp information. These

events can be displayed, analyzed, printed and exported based on

user-definable selection criteria (filters).

Safety Historian enables users to analyze and monitor (abnormal)

process behavior. Any anomalies in a process may upset the

process as a whole. In order to understand why they occurred andto find the first event that caused the process upset, accurately

time-stamped and archived information is essential. Equally

important is the ability to retrieve and analyze the logged

information. This enables any process anomaly to be reported

rapidly and remedied effectively. This helps the user keep the

process on-line and maximize the plant profitability.

Output Events are displayed at the PC screen, but they can also be printed atany (line) printer configured in Windows.

Communication Safety Historian retrieves the events via:

• Ethernet via the proprietary Experion (SCADA) protocol from

SM controller(s) and FSC controller(s);

• RS-232/RS-485 via the proprietary FSC-DS SOE protocol from

FSC controller(s).

Flexibleconfiguration

In order to achieve maximum flexibility without interrupting plantoperations, all functions that are not safety-related can be configured

by the user, even on-line (i.e. while event recording continues):• Event message configuration and appearance,

• Properties of points,

• Point configuration (adding, importing, exporting, and deleting),

• Diagnostic status message configuration,

• Event type names configuration,

• Default status message configuration, and

• Event colors.

This allows users to tailor the system and its response to their

specific plant needs, without having to interrupt operations or waitfor a scheduled shutdown of the plant.



Supported events The following SM/FSC event types are recorded and stored by Safety

Historian:

• Value events of point types I, O, AI, and AO(point value events),

• Force events of point types I, O, AI, and AO

(point force events),

• Point value reports of point type BO; also known as: BO-SER

(point report events),

• Diagnostic events, Remote IO Diagnostic events, and

• Exception Report events:

− system fault,

−

SOE buffer full event,− All forces cleared event,

− Unknown point force change (forced point without a SOE

ID).

Events can be viewed on-line, while being retrieved from theconnected SM/FSC controller(s), or post-mortem from disk. The

event database can hold a maximum of 2,100,000,000 events(provided sufficient hard disk space is available).



1.3 Safety Historian Packages

Safety Historianpackages

The functionality of the Safety Historian package you purchased isdefined by:

• which module has been chosen, and

• which point limit has been chosen.

Each is discussed in more detail below.

Modules Two module ‘flavors’ of Safety Historian are available:

• Basic

This module provides all basic functionality, but has nonetworking capabilities. It allows you to access events reportedfrom one or more connected SM/FSC controllers. For more

information on stand-alone (‘Basic’) Safety Historian

applications refer to subsection 1.4 on page 6.

• Network

This module provides all basic functionality and has networkingcapabilities which allow it to be used in a sequence-of-event

(SOE) network. The network version of Safety Historian caneither be installed as a client or server. For more information on

Network Safety Historian applications refer to subsection 1.4 on

page 6. Further details on SOE network configurations (including

installation details) can be found in document SH51-200.1

("Safety Historian R200.1 – Network Option").

Point limits The Safety Historian package you purchased will also have a

maximum number of points that it can monitor and process. The

following point limit options are available:

• ≤ 100 points,

• ≤ 500 points,• ≤ 2,500 points,

• ≤ 10,000 points,

• ≤ 50,000 points.

It is possible to upgrade the license at any desired moment in order

to increase the point limit.

Interface By default, the Safety Historian package is supplied with the

Experion (SCADA) and the FSC-DS SOE protocol, which is used

for communication with SM and FSC controllers .



The FSC DS SOE protocol is used exclusively for communication

with FSC systems.

Safety Historian supports simultaneous communication with SM

and FSC controllers and simultaneous use of the two abovementioned communication protocols.

Installation The Safety Historian setup program on the DVD uses the license

code to automatically install the correct package, with the chosen

module and chosen point limit.

Packageinformation

The About Safety Historian window contains detailed informationabout the currently installed module and point limit. For details refer

to subsection 3.9 ‘User and Version Information‘ of this manual.



1.4 Stand-Alone (‘Basic’) versus Network Applications

Safety Historian can be used in both stand-alone configurations andin sequence-of-event network configurations.

Stand-aloneapplications

In stand-alone applications, Safety Historian is directly connected to

one or more SM/FSC controllers (see Figure 1-1 below). It retrieves

events from each connected controller and stores them in a database

on the Safety Historian station for on-line viewing, history analysis,

etc. Configurations like these are served by the Basic version of theSafety Historian software.

Figure 1-1 Safety Historian in stand-alone configuration(example)

Please note the following limitations:

• Regarding SM controllers:

(Ethernet only)The maximum number of SM controllers that can be connected

to a Safety Historian station is 32.



Master-slave configurations

SOE data from a slave SM controller can only be retrieved

directly, so it cannot be retrieved via its master controller.

• Regarding FSC controllers:

EthernetThe maximum supported number of 10018/E/. modules is 32.

RS-232/RS-485

o The maximum number of FSC DS SOE communication

links depends on the number of RS-232/RS-485 COM-ports

at the Safety Historian station.

o The maximum number of FSC controllers that can be

connected to each communication link using multidrop is16, although this number may be less in practice depending

on the length of the communication link, the configured

Baud rate, and the number of events per second that Safety

Historian will process.


SOE data from a slave FSC controller can be retrieved via its

master provided that master and slave are using the FSC DS

SOE protocol.

Networkapplications

Several PCs can be interconnected to form a dedicated sequence-of-event local area network (LAN) (see Figure 1-2 below). In such

configurations, there are a number of Safety Historian servers, which

collect the incoming events from the connected SM/FSC controllers ,

and store them locally in a database for remote viewing, analysis, etc.

The information stored on the servers in an SOE network is accessed

using one or more Safety Historian clients. This allows all events to

be viewed remotely from one or more location(s).



Figure 1-2 Safety Historian in network configuration (example)

Configurations like the one shown in Figure 1-2 are served by the Network version of the Safety Historian software. The networking

capabilities of Safety Historian provide a scalable process historian

environment that can be configured to serve any application'sspecific needs.

Please note the following network considerations:

• The maximum number of servers per network is limited by the

LAN specification.



• Regarding SM controllers:

(Ethernet only)

The maximum supported number of SM controllers per SOEnetwork is 32.


SOE data from a slave SM controller can only be retrieved

directly, so it cannot be retrieved via its master controller.

• Regarding FSC controllers:

Ethernet The maximum supported number of 10018/E/. modules is 32.

RS-232/RS-485

o The maximum number of FSC DS SOE communication

links depends on the number of RS-232/RS-485 COM-ports

at the Safety Historian station.

o The maximum number of FSC controllers that can be

connected to each communication link using multidrop is16, although this number may be less in practice depending

on the length of the communication link, the configuredBaud rate, and the number of events per second that Safety

Historian will process.


SOE data from a slave FSC controller can be retrieved via its

master provided that master and slave are using the FSC DS

SOE protocol.

Note:For details on SOE networking, including configuration

details, refer to document SH51-200.1 ("Safety Historian

R200.1 – Network Option").



1.5 Terminology

Terminology The following terminology is important for a proper understanding ofthe Safety Historian application and this manual:

Client See Safety Historian Client.

Controller Name Alphabetical identification of a SM controller.

For FSC controllers the term System Name is used.

Controller Node Number

Numerical identification of a Safety Manager controller.For FSC controllers the term System Number is used.

Force event The change of state of a point to 'forced' or to 'force cleared' (via a

force or force-clear command initiated at the Safety Manager Station

/ FSC Navigator Station).

Diagnostics event The change of state of a point from healthy to faulty (i.e. detection ofan abnormal situation in a SM/FSC controller by the built-in

diagnostic features).

Event The change of one state to another state at a given moment in time.

See also: User-defined event , force event , and diagnostics event .

Event collecting device An external device that records the event messages transmitted by a

SM/FSC controller. Safety Historian running on a PC is an eventcollecting device.

Event detecting device(EDD)

A device that monitors the process and transmits any detected events

to event collecting devices for further processing. In the context of

Safety Historian, this will normally be one or more connectedSM/FSC controllers.

Event message A message containing information on an event including an

identification of the event, its time stamp, the event status, and other

optional information.

Event reporting Transfer of event messages in chronological order to an event-



collecting device. This event reporting can be on request or

automatically (continuously).

Experion (SCADA)Protocol

Protocol that enables communication between:

- a SM controller and a Safety Historian station (SOE data only);- an FSC controller and a Safety Historian station (SOE data only);

- a SM controller and an Experion PKS station (SOE data &SCADA);

- an FSC controller and an Experion PKS station (SOE data &SCADA).

Acronym SCADA: Supervisory Control and Data Acquisition

Experion PKS Honeywell Process Knowledge System (PKS) is a Honeywellautomation system running on the Experion platform. Experion PKS

unifies people with process, business and assets, drawing its datafrom all resources available on the Experion Platform.

FSC Depending on context either FSC controller or FSC system is meant.

Acronym FSC: Fail-Safe Control.

FSC controller FSC sub-system consisting of one or two Central Parts (respectivelya Non-redundant or Redundant controller architecture).See also FSC system.

FSC-DS SOE protocol Protocol that enables communication between an FSC controller and

a Safety Historian station (SOE data only).

FSC Navigator station PC that runs the FSC Navigator (operating software for the FSC

System).

FSCSOE Predecessor of Safety Historian software package.

FSC system A set of several sub-systems executing the safety functions/strategies,

of which the key sub-systems are:- FSC controller

- FSC Navigator station (that runs the FSC Navigator software)

Point Data point of an EDD (defined in its application) whose process



behavior is monitored and whose events are transmitted to the event

collecting device. (Only points in SM/FSC that are specifically

‘enabled for SOE-recording’ respectively ‘SER-enabled’ are

monitored.)

Process point See Point.

Process variable See Point.

PC Personal computer.

Safety Historian Software Package that is part of Honeywell's Safety Manager (SM)

and Fail-Safe Control (FSC) product lines which records and logs

point events for on-line viewing, history analysis, etc.

Safety Historian Client PC in a sequence-of-event (SOE) network that is used to remotely

view the reported events stored on (a) Safety Historian server PC(s).

Safety Historian Server PC in a sequence-of-event (SOE) network that is used to collect and

store events from the connected SM/FSC controllers to enableremote viewing from the (a) Safety Historian client PC(s).

Safety Historianstation

PC in a stand-alone sequence-of-event (SOE) application that

combines the functions of client and server, i.e. it is used to collect

incoming events from the connected SM/FSC controller(s), and stores

them locally for viewing, analysis, etc.

Safety Manager

controller

See SM controller.

Safety Manager station See SM station.

Safety Managersystem

See SM system.

SER Sequence of Events Recording.



Server See Safety Historian Server.

SM

Depending on context either Safety Manager controller or SafetyManager system is meant.

Acronym SM: Safety Manager.

SM controller SM sub-system consisting of one or two Control Processors(respectively a Non-redundant or Redundant controller architecture).

See also SM system.

SM station PC that runs the Safety Builder (operating software for the Safety

Manager System).

SM system A set of several sub-systems executing the safety functions/strategies,of which the key sub-systems are:

- Safety Manager controller- Safety Manager station (that runs the Safety Builder software)

SOE network A number of PCs that are interconnected via a local area network

(LAN) to form a dedicated sequence-of-event (SOE) network. Such

networks consist of a number of servers, which collect the incoming

events from the connected SM/FSC controllers, and clients, that areused to view the information stored on the servers. This allows all

events in a network to be viewed remotely from one central location.

System Number Numerical identification of an FSC controller.

For SM controllers the term Controller Node Number is used.

System Name Alphabetical identification of an FSC controller.For SM controllers the term Controller Name is used.

Time stamp The recorded current date & time at the moment an event is detected.

User-defined event The change of state of a point that has been ‘enabled for SOE-

recording’ in the Safety Manager Station (or SER-enabled in the FSC

Navigator Station) by the user.



1.6 Using This Manual

Manual scope This manual is intended for users of Safety Historian Release 200.1.It provides all information a user needs to know to properly use the

application.

Where appropriate, this manual may refer to the following

document:

• SH51-200.1: Network option

English versionof Windows

This manual assumes that you use the English version of Microsoft

Windows. This means that all standard Windows components, menu

options, etc. are in English. If you use a Windows version other than

English, the standard Windows dialog boxes shown in this manual

may look slightly different and may contain different text.

This manual also assumes you have a good understanding ofWindows basics and are comfortable using the Windows

environment. If this is not the case, please refer to the Windowsdocumentation for more information on how to use Microsoft

Windows.

Manualorganization

This manual has been divided into a number of sections, each

focusing on different aspects of using Safety Historian:

Section 1: Introduction to Safety Historian

This section provides general information about the

Safety Historian application and this manual.

Section 2: Setting Up Safety Historian

This section describes how to prepare your hardwarefor sequence-of-event recording, and how to install the

Safety Historian application and set it up for initial use.

Section 3: Getting StartedThis section describes the Safety Historian application

in more detail and familiarizes you with the basicoperation of the program.

Section 4: The Network Architecture

This section explains how to configure the networkarchitecture used in the Safety Historian application.

Section 5: Working with PointsThis section explains how to use points in the Safety

Historian application.



Section 6: Importing and Exporting PointsThis section explains how you can use CSV/dBASE

files to define the points in Safety Historian.

Section 7: Working with Events

This section explains how events can be viewed and printed for inspection, analysis and alarming purposes.

Section 8: Visibility and Filtering of Events

This section explains how the visibility of events can

be controlled and how historical events can be filtered

to display only those events that meet certain criteria.

Section 9: Customizing Window Layouts

This section explains how to customize the appearance

of the various Safety Historian windows.

Section 10: Program Maintenance

This section explains how to customize certain SafetyHistorian settings and perform a number of

maintenance tasks.

Appendix A: Error Messages during Software Installation

This appendix describes a number of error messages

that may be displayed while installing the Safety

Historian software.

Appendix B: TroubleshootingThis appendix describes a number of system errors that

may occur and how they can be solved.




16 Section 2: Setting Up Safety Historian

Section 2 – Setting Up Safety Historian


Section overview This section describes how to prepare the hardware for sequence-of-

event recording, and how to install the Safety Historian applicationonto a PC. It covers the following topics:


2.1 Section Overview ........................................................................................ 16

2.2 Requirements ....................... ........................ ......................... ...................... 17

2.3

Hardware Connections ...................... ......................... ........................ ......... 19 2.3.1 Connections Overview ....................... ......................... ........................ ......... 19

2.3.2 RS-232 Communication............................................................................... 21

2.3.3 RS-485 Communication............................................................................... 22

2.3.4 Ethernet Communication ........................ ........................ ......................... .... 25

2.4 Preparing the Safety Manager System...................... ........................ ........... 29

2.5 Preparing the FSC System ......................... ........................ ......................... 29

2.6 Installing the Safety Historian Software ......................... ........................ ....... 30

2.7 Uninstalling the Safety Historian Software......................... ......................... .. 39

2.8 Keep the Safety Historian computer secure and reliable .............................. 41




Section 2: Setting Up Safety Historian 17

2.2 Requirements

Setup The software package of Safety Historian can be obtained via DVD.The package contains a Setup program that installs the Safety

Historian application on your PC.Both Safety Historian and its setup program are Windows

applications, so to enable installation, the PC must already be runningthe Windows operating system. For more details see paragraph

‘Software requirements’ below.The setup program creates folders as needed and installs files to the

PC’s hard disk.

Hardware

requirements

The target PC for the Safety Historian application software should at

least meet the following hardware requirements:• Processor:

o Clock: minimum 1 GHz

recommended Intel Core i7 2,2 GHz or better,

o Architecture: 32-bit or 64-bit (x64);

• Memory

o Type:

Preferably ECC memory to lower the risk of datacorruption;

o Size:

1 GB RAM (32-bit architecture), 2 GB RAM (64-bit architecture);

• Hard disk:

o 20 GB available hard disk space for event database storage

and to generate large print preview reports;

• DVD drive;

• When using a serial communication link:at least one free serial port (COM) with a high-performance16550A buffered-style UART.

Softwarerequirements The software requirements (prior to installation) are as follows:

• Windows 7 Professional (64 or 32 bit)

Safety Historian was specifically developed to run under the abovementioned Windows version. It is not supported by any other

Windows version. Using Safety Historian under any Windows versionother than the version mentioned above is considered improper use of

the software. Honeywell Safety Management Systems cannot be held





liable in any way for any damages that result from using SafetyHistorian under a Windows version other than the version mentioned

above.

Windowsapplications

It is strongly recommended that you use the Safety Historian stationexclusively for sequence-of-event purposes.

Also file sharing should not be done at the station!Other tasks may affect the stability and integrity of the Windows

environment.





2.3 Hardware Connections

Note:More detailed information regarding connections between

Safety Historian (FSCSOE) and FSC controllers can be found in

the Communication Integration Guidelines, PM.IG.8170.

2.3.1 Connections Overview

Communicationlinks

Safety Historian retrieves the events from:

• SM controller(s)

via Ethernet communication links• FSC controllers(s)

via Ethernet communication linksor

via a maximum of four serial (RS-232 or RS-485) communicationlinks.

Communication cables are used to interconnect the Safety Historian

station and the SM/FSC controllers or other devices.





Table 2-1 and Figure 2-1 below provide an overview of the variousconnection options for Safety Historian Basic Version.

Figure 2-1 Hardware connections for Safety Historian Basic Version

For connection details for the network version of Safety Historian refer to document SH51-200.1("Safety Historian R200.1 – Network Option").





Table 2-1 Hardware connections for Safety Historian Basic Version

Connected Device Connection Type Safety Historian StationConnection

Device Connection

SM controller Ethernet Ethernet portSM controller:USI-000 x communicationmodule

FSC controller

Ethernet Ethernet portFSC controller:10018/E/x communicationmodule

RS-485Third-party serial device(e.g. from Black Box)

FSC controller:I-interface on 100 x 4/ x / x communication module

RS-232

Third-party serial device(e.g. from Black Box)

FSC controller:F-interface on 100 x 4/ x / x

communication moduleSerial COM port of PC

Line printer Ethernet / USB / … Ethernet port / USB port /…Ethernet port / USB port/…

2.3.2 RS-232 Communication

RS-232communication

If RS-232 serial communication is used for Safety Historian, thecommunication cable can be connected to any standard serial port

(COM) with a high-performance 16550A buffered-style UART. Mostindustry-standard PCs use such standard serial ports (usually COM1

and COM2). You may also use any third-party interface expansion board that has a standard RS-232 serial port (e.g. Black Box).

Communication cable The pin allocation of the RS-232 communication cable is as follows:

Figure 2-2 RS-232 communication cable, type FS-CCE232-02/L10





Notes:1. The schematic in Figure 2-2 assumes that you use Belden

cable 8103.

2. End-of-line (EOL) resistors are not to be installed.

3. For more information, please refer to CommunicationIntegration Guidelines, PM.IG.8170

4. For systems delivered before 2003 it is possible that old type

of communication cables are used, for details of those cables please refer to Communication Manual, FSC SOLUTION-

020201.

Maximum cable length The maximum cable length for RS-232 communication is 10 m(32.8 ft).

2.3.3 RS-485 Communication

RS-485communication

If RS-485 serial communication is used for Safety Historian, the

communication cable must be connected to an RS-485 serial port. Athird-party RS-485 interface expansion board (e.g. Black Box) must

be used since a standard PC does not support an RS-485 serial port.

Third-partyinterface boards

The following standard third-party interface boards have been found

to be reliable, and work well with Safety Historian:

• Model IC133C from Black Box,

• Model IC187C-LP from Black Box

• Model IC983C-LP from Black Box

You may, of course, also use RS-485 interface boards from othermanufacturers.

Black Box IC133C board jumper settings

Jumper settings are shown in Figure 2-3. Both ports are configured for RS485 Development System SOE

Communication.





Figure 2-3 Jumper settings for the Black Box IC133C 2-Port RS-232/422/485 PCI Host Adapter

in RS-422/485 mode

Black Box IC187C-LPboard jumper settings

Jumper settings are shown in Figure 2-4.

Both ports are configured for RS485 Development System SOECommunication.

Figure 2-4 Jumper settings for the Black Box IC187C-LP RS-232/422/485 PCI Host Adapter in RS-422/485 mode





Black Box IC983C-LPboard jumper settings

Dip-switch settings are shown in Figure 2-5 .Port X is configured in default RS422 mode which is the best mode

for RS485 Development System Communication (both multi-dropand point-to-point connections).

Table 2 and Table 3 show the meaning of the dip-switch settings.

Figure 2-5 Dip-switch settings for the Black Box IC983C-LP RS-

232/422/485 PCIe Host Adapter in RS-422 mode (best mode for RS-485 DS-SOE communications)

Table 2 Dip-switch Settings

Switch Description

M1 Sets the electrical interface mode (with M0)

M0 Sets the electrical interface mode (with M1)

T Adds or removes 120 termination

PU Adds or removes 1K pull-up resistor in RS-422/485 mode

PD Adds or removes 1K pull-down resistor in RS-422/485 mode

L Connects TX– to RX– for RS-485 two-wire operation

L Connects TX+ to RX+ for RS-485 two-wire operation

Table 3 Electrical Interface Modes

M1 M0 Interface

OFF OFF RS-232

OFF ON RS-422 [Default]

ON OFF RS-485 ECHO Enabled

ON ON RS-485 No ECHO

Communication cable If any of the above third-party interface boards are used for RS-485

Safety Historian communication, the pin allocation of the cable is as

follows:





Figure 2-6 RS-485 communication cable, type FS-CCE-485-02/Lx

for Black-Box IC133C or IC187C-LP PC communication interface

Notes:1. The diagram shown in Figure 2-6 assumes that you use

Belden cable 8103.2. For multidrop connection with other FSC systems, please

refer to Communication Integration Guidelines,

PM.IG.8170.3. For systems delivered before 2003 it is possible that old type

of communication cables are used, for details of those cables

please refer to Communication Manual, FSC SOLUTION-

020201.

Important!A 120 Ohm end-of-line (EOL) resistor should be located in the

last FSC system connected (See Communication Integration

Guidelines, PM.IG.8170 for details).

Maximum cable length If any of the above third-party interface boards are used for RS-485Safety Historian communication, the maximum cable length is 750 m

(820 yd).

2.3.4 Ethernet Communication

Ethernetcommunication SOE communication with an SM controller is always done viaEthernet and through USI-000x communication modules.

SOE communication with an FSC controller can be done via

Ethernet and thus through 10018/E/ x communication modules.

Notes on using multiple SOE collectors:

Regarding SM controllers





If Safety Historian and Experion PKS (both SCADA SOEcollectors) are configured at the same USI module, then the

SOE collection functionality of Experion PKS must beswitched off . When two SCADA SOE collectors are desired,

you can configure each collector at a separate USI-module.If Safety Historian and Experion PKS with a CDA-protocol

(non-SCADA) are configured at the same USI module then both SOE collectors can be used simultaneously.

Regarding FSC controllers

If Safety Historian and Experion PKS (SCADA SOE) areconfigured in one FSC controller, then the SOE collection

functionality of Experion PKS (SCADA SOE) must be

switched off .

Network switches Network switches must be configured to allow or block TCP/IP

connections via opening or closing TCP port numbers.

Contact a network administrator to take care for configuring thenetwork switches.

The following TCP port numbers should be opened:

• 51000, but only for those switches that are present between

an SM/FSC controller and Safety Historian Server (disregard

‘Server’ when using the Basic version of Safety Historian);• 51666 and 52666, but only for those switches that are present

between a Safety Historian Server and Safety HistorianClient.





Communicationredundancy at anSM controller

Please refer to Safety Manager Software Reference

(EP-SM.MAN.6285),Appendix A, particularly sub section: ‘Communication via the

Experion (SCADA) protocol’

Communicationredundancy at anFSC controller

Safety Historian supports redundant Ethernet communication. Bothconnection redundancy (dual Ethernet) and Central Part redundancy

are supported. The supported configurations are shown in Figure 2-7 below.

CP1

CP2

A

A

B

3

redundant Central Parts +

redundant Ethernet channels

(using two 10018/E/1 modules)

B

CP

single Central Part +

single Ethernet channel

(using 10018/E/1 module)

A 1A

CP

A

B

2

single Central Part +

redundant Ethernet channels

(using 10018/E/E module)

A B

Figure 2-7 Redundancy options for Ethernet communication at an

FSC controller

Please note that redundancy with two Central Parts, each with

redundant Ethernet channels (using two 10018/E/E modules) is notsupported.





Communication cable The communication cables used for Ethernet communication withSM/FSC controllers are standard UTP cables.

Since the 10018/E/x module of FSC controller has coaxial Ethernet ports, a coax-UTP cable convertor must be used for each coax port.





2.4 Preparing the Safety Manager System

Please refer to Safety Manager Software Reference(EP-SM.MAN.6285),Appendix G, particularly sub section: ‘Configuring SOE’

2.5 Preparing the FSC System

See FSC Software Manual (FS80-xxx*), Appendix B, particularly sub

section: ‘B.2 Sequence-of-Event Recording to SOE Safety Historian’.

* 'xxx' is the release number. For example, the Software Manual for FSC R700 is referencedas FS80-700





2.6 Installing the Safety Historian Software

Notes:1. The installation procedure as described below assumes thatyou use the English version of Windows.

2. You need administrator rights in Windows to be able toinstall the Safety Historian software.

3. As part of the installation process the Windows firewall will be configured to allow incoming connections on TCP ports

51666 and 52666 to cater for Safety Historiancommunication with FSC and SM Controllers.

4. To further harden the system, the Safety Historian databasewill be executed by an account with limited privileges; this

Windows user account SafetyHistorianSRV is also createdduring installation.

Installation To install Safety Historian, do the following:

Important (1):Turn off Write-cachingof hard disk

1. Before starting setup, please first turn off the Write-cachingfeature of the hard disk where the Safety Historian database is

going to be located. This will prevent losing event data and/orcorruption of the database in the event of a power-outage,

equipment failure or abnormal termination of the SafetyHistorian application.

To turn off Write-caching, go to the Windows Start menu,

choose: Control Panel | System | Device Manager | Disk

Drives. Select the hard disk where the event database will be

located, right-click it and select Properties. Choose Policies tab,which will look similar to the window in Figure 2-7.





Figure 2-8 Hard disk Properties window (Write caching)

2. At the Policies tab disable the Write-caching policy.

3. Click the OK button to confirm.

4. If Windows suggests to restart the PC, please do so.

Important (2):When using SMControllers

When you use SM Controllers it is important that an up-to-date list of

diagnostic description text lines is present in the installation folder ofSafety Historian.

The file is called: ‘Fsc_fault.txt’

(Which is a confusing name since in this context it is only used forSM Controllers.)

The installation folder is: ‘\Program Files (x86)\Honeywell\Safety

Historian Client-Server R2xx.x\bin’

So, when your SM Controller(s) are being updated it is needed tocopy the mentioned file from the installation folder of Safety Builder

to the mentioned installation folder of Safety Historian.

Of course this can only be done when Safety Historian has been

installed. If the server (and/or clients) of Safety Historian were





running when the file was copied, please restart the server and/orclient(s).

The file contains specific diagnostic description text lines of which

one will be inserted into the description column when a diagnosticevent is received from an SM Controller.

Starting Setup 1. Put the distribution DVD in the DVD drive.

2. Close all Windows applications that are open.

3. From the Start menu, choose Computer. This will open the

Windows File Explorer. Choose the DVD drive and choose‘setup.exe’ to start the setup program.

Software license 4. A Welcome window will appear, after clicking its Next button,the Software License Agreement window (see Figure 2-9) will

open:

Figure 2-9 Software License Agreement window





Carefully read the license agreement before proceeding. You must accept the license agreement before you can continue. To accept

the license agreement and continue with the installation, click theYes button. If you decline the license agreement, click the No

button, and the setup procedure will be aborted.

User information 6. Click the Next button to open the Customer Information dialog box (see Figure 2-10).

Figure 2-10 Entering user information

Serial number Enter the user name and the company name. In the Serial text

box, enter the serial number that was provided with thedistribution DVD. Enter the number exactly as provided: note

that any letters in the serial number are case-sensitive ('x' is not

the same as 'X'). You must enter a valid serial number before youcan install Safety Historian.Then choose who will be able to launch Safety Historian at this

computer: anyone or only when the user name (the one registeredin Safety Historian) is equal to the user that has logged in at the

PC.After you have successfully completed the User Information

dialog box, click the Next button.





License number 7. A dialog box will appear which prompts you to enter the license

number that was supplied with the distribution DVD (see Figure2-11).

Figure 2-11 Entering license number

The license number determines which Safety Historian packageyou are entitled to use. The Setup program will automaticallyinstall the correct package (including all interface options, if any).

Please enter the license number exactly as provided: note that anyletters in the serial number are case-sensitive ('x' is not the same as

'X'). You must enter a valid license number before you can proceed.





Note:The message “Invalid license number entered” can stillappear, even when you have correctly entered a license

number. This is because the combination of the license

number with the earlier entered serial number is invalid.Please select the right combination of numbers that have

been provided with the distribution DVD.

After you have entered a valid license number, click the Next button.

Destination folder 8. The window as shown in Figure 2-12 will appear. This window

prompts for the folder on the hard disk where the SafetyHistorian application files should be installed. The suggested

destination folder is X:\Safety Historian, where 'X' is the drivethat contains the Windows operating system (usually drive C).

You can accept this default suggestion, or you can use theBrowse button to specify a different folder.

When you are done, click the Next button.

Figure 2-12 Choosing the destination folder for Safety Historian





Program folder 9. The window as shown in Figure 2-13 will appear.

Figure 2-13 Selecting a program folder

This window prompts for the name of the program folder that willcontain the Safety Historian. You can accept the default

suggestion (Honeywell), or you can enter a different programfolder. When you are done, click the Next button.

Note:Please note that the program group of all other Safety

Manager-related software applications will also default to

'Honeywell'.





Summary window 13. The window as shown in Figure 2-14 will appear.

Figure 2-14 Installation summary window

This window presents a brief summary of the installation

parameters before the setup program will start copying the files toyour hard disk. If you want to change any of the parameters, use

the Back button to move to the appropriate window and changethe parameter. Then use the Next button(s) to return to this

window. If you are ready to install Safety Historian, click theNext button in this window. The files will now be copied to hard

disk.

Finalizing Setup 14. As the last step, you will be prompted to restart your computer.Click the Finish button to complete the setup process and restart

your computer.

Note:Safety Historian will only operate correctly after you reboot

your computer.





StartingSafety Historian

If the Safety Historian application has been properly installed on the

Safety Historian station, two items have been added to the Windowsuser interface:

• A shortcut on the Windows desktop called 'Safety Historian Basic'

(see Figure 2-15), and

• An item called 'Safety Historian Basic R200.1' in the Honeywell

program group (under Start / All Programs).

Figure 2-15 Safety Historian shortcut on desktop

You can start Safety Historian by double-clicking the desktopshortcut, or by moving to the 'Honeywell' program group and

choosing the 'Safety Historian Basic R200.1' option.

Important: Before you officially start making use of Safety Historian be sure to

follow the instructions that are written at the beginning of this paragraph at “Important (2):

When using SM Controllers”.





2.7 Uninstalling the Safety Historian Software

Safety Historian has an uninstall facility which allows you tocompletely remove it from your system.

Uninstall procedure To uninstall Safety Historian, do the following:

1. Double-click the Programs and Features icon from Control

Panel. (Please note that in Windows versions other than Englishthese program components are called differently.)

The following window will appear:

Figure 2-16 Uninstalling Safety Historian software

2. From the list of applications that can be automatically removed byWindows, select Safety Historian Basic R200.1, right-click and

select Uninstall. The window as shown in Figure 2-17 willappear.





Figure 2-17 Confirming uninstall

If you want to remove Safety Historian from your system, choose Yes.

All Safety Historian application files and associated shortcuts willnow be removed from your hard disk. During the uninstall operation,you may be asked whether certain files should be removed. If you are

not entirely sure whether they can be removed, it is recommended thatyou leave them on your hard disk.

Note:The Safety Historian event database and configuration files are

not removed. This means that the event history and

configuration settings can be reused.





2.8 Keep the Safety Historian computer secure and reliable

The Safety Historian computer is connected to FSC or SM SafetyControllers. To keep the computer secure and reliable it is highlyrecommended not to install personal applications like movies, games

or music on the Safety Historian computer. Ensure that the SafetyHistorian computer is, and remains, secure and free of viruses.

It is recommended to enable the Windows Firewall. As part of the

installation process the Windows firewall will be configured to allowincoming connections on TCP ports 51666 and 52666 to cater for

Safety Historian communication with FSC and SM Controllers. Tofurther harden the system, the Safety Historian database will be

executed by an account with limited privileges; this Windows useraccount is named SafetyHistorianSRV and is created during

installation. The Safety Historian is started in the user account. Ensurethis user account is configured with the minimal privilege level to

allow normal operation. It is strongly advised not to run the Safety

Historian with Windows Administrator privileges. Safety Historian

utilizes the Firebird database engine.

Note:The installation of software updates, for example Windows or

Anti-Virus software, may require a reboot of the computer.

During a reboot Safety Historian Server is not active and eventsare not retrieved. New events are retained on the FSC and SMcontrollers and will be retrieved when the Safety Historian

Server is back on-line. Check the FSC and SM user

documentation for details on event retention.

To ensure reliable continuous operation of Safety Historian, allcomputer power-saving features must be disabled. Examples of power

saving features are Hard Disk Drive power management, Sleep,Hibernate and Hybrid Sleep.

Note:Screensavers which show pictures, slide shows, random effects

or animated wallpapers may add an unexpected high processorload which may reduce the Safety Historian’s performance. It is

recommended not to activate this type of screensavers. Ascreensaver that switches the monitor off typically does not

affect the computer’s performance and can be enabled.




Section 3: Getting Started 41

Section 3 – Getting Started


Section overview This section describes the Safety Historian application in more detail,

and familiarizes you with the basic operation of the program. Itcovers the following topics:


3.1

Section Overview ........................ ......................... ........................ ................ 41

3.2

Program Basics ...................... ........................ ......................... .................... 42

3.3

Configuration & Tasks area................... ........................ ......................... ...... 45 3.4

Event Windows area ........................ ........................ ......................... ........... 48

3.5

Multibox Controls ........................ ......................... ........................ ................ 49

3.6

Error Reporting ....................... ........................ ......................... .................... 50

3.7

License and Version Information ........................ ........................ .................. 52

3.8

Password Protection ........................ ........................ ......................... ........... 53




42 Section 3: Getting Started

3.2 Program Basics

Note:It is assumed that you have a good understanding of Windows

basics and are comfortable using the Windows environment. Ifthis is not the case, please refer to the Windows documentation

for more information on how to use Microsoft Windows.

About SafetyHistorian

Safety Historian is part of Honeywell's Safety Manager (SM) and FailSafe Control (FSC) product lines.This Windows software package

records and logs process events, alarm events and diagnostic eventsthat are detected by the connected SM controller(s) and/or FSC

controller(s). The events are stored in its event database includingdetailed time-stamp information. These events can be displayed,

analyzed, printed and exported based on user-definable selectioncriteria (filters).

Important!It is strongly recommended that you use the Safety Historianstation exclusively for sequence-of-event purposes.

Also file sharing should not be done at the station!Other tasks may affect the stability and integrity of the Windows

environment.

StartingSafety Historian

If the Safety Historian application has been properly installed on the

Safety Historian station, two items have been added to the Windowsuser interface:

• A shortcut on the Windows desktop called 'Safety Historian Basic'

(see Figure 3-1), and

• An item called 'Safety Historian Basic R200.1' in the Honeywell

program group (under Start / All Programs).

Figure 3-1 Safety Historian shortcut on desktop





You can start Safety Historian by double-clicking the desktopshortcut, or by moving to the 'Honeywell SMS' program group and

choosing the 'Safety Historian R200.1 Basic' option.

It is not possible to run two instances of Safety Historian. If youattempt to start Safety Historian for a second time, the first instance

will open again.

ExitingSafety Historian Safety Historian can be closed in any of the following three ways:

• From the Control menu (which is called up by clicking the Safety

Historian icon in the upper left hand corner of the main applicationscreen), choose Close.

•

With the main application screen active, hold down the Alt key and press F4.

• Click the icon in the upper right hand corner of the main

application screen.

Notes:1. Exiting Safety Historian is password-protected at Operator

level.

2. Before shutting down Windows make sure that you exit

Safety Historian first.

Main screen After Safety Historian has started up successfully, the main screenwill be displayed (see Figure 3-2 on the next page). This screen

contains the following areas:

• Event windows area, with tabs to open the:

(see subsection 3.4 on page 48)

o Incoming Events window

o Historical Events window

o Points window...

• Configuration & Tasks area, used for selecting the functions ofSafety Historian

(see subsection 3.3 on page 45),





Note:The network client version of Safety Historian has an additional‘Safety Historian Servers’ area (right above the Configuration &

Tasks area) to make a connection with an available server.

For details on SOE networking and the network version ofSafety Historian refer to document SH51-200.1 ("Safety

Historian R200.1 – Network Option").

Figure 3-2 Main Safety Historian application screen





3.3 Configuration & Tasks area

Menu bar The Safety Historian application provides a Configuration & Tasks area for easy access to all program functions.

The following program functions can be selected from theConfiguration & Tasks area:

• Network Architecture

• Configuration Options

• Import Points

• Export Events

• Back up or Restore

• Find

Each program functions contains an underlined shortcut character,which allows direct access to that menu by holding down the Alt key

on the keyboard and pressing the shortcut character. For example, the Network Architecture

function can be called up by pressing Alt and n .





Note:

The network server version of Safety Historian does not have a

Configuration & Tasks area since there will generally be littleuser interaction on Safety Historian servers.

For details on SOE networking and the network version ofSafety Historian refer to document SH51-200.1 ("Safety

Historian R200.1 – Network Option").

NetworkArchitecture…

Use this option to view, edit or print the network architecture.The network client version of Safety Historian has additional

functionality in the Network architecture function: Connecting and

Disconnecting to a Server.

(For details refer to section 4 of this manual.)

ConfigurationOptions…

Use this option to configure various features of Safety Historian:(For details refer to sections 9 and 10 of this manual.)

• General…

• Event visibility…

• Customize Display of Events…

Use this option to customize Event Type Names, Default StatusMessages and Event coloring.

•

Column Layout…• Event Filters…Use this option to define filters for viewing the

event history.(For details refer to subsection 8.3 of this manual.)

• Continuous Print Setup…Use this option to set up continuous printing of incoming events.

(For details refer to subsection 7.4.4 of this manual.)

• Change Passwords…Use this option to change any of the

passwords that are used to protect Safety Historian from

unauthorized use.(For details refer to subsections 3.10 and 10.9 of this manual.)

• Automatic Export of Events… Use this option to automatically export new events on a daily,

weekly or monthly basis and to keep the size of your databaselimited.

(For details refer to subsection 7.5.5 of this manual.

Import Points… Use this option to import a dBASE file that contains the pointconfiguration of an existing SM/FSC controller (see section 6 of this





manual).

Export Events… Use this option to export (selected) historical events to a CSVformatted file. (For details refer to subsection 7.5.4 of this manual.)

Back up orRestore…

Back up

Use this option to create a backup of the current Safety Historianconfiguration (network architecture, etc.). (For details refer to

subsection 10.7 of this manual.)

RestoreUse this option to restore the configuration database. The

configuration database will be overwritten with the informationcontained in the backup file. This option can be used to restore the

configuration database after hard-disk failures or PC power downs

that led to a corrupted configuration database.(For details refer to subsection 10.8 of this manual.)

Find… Use this option to find text in the Historical Events or Points window.The Find option can not be used for the Incoming Events window

because its contents might change (due to incoming events) whilesearching is in progress. Use the Historical Events window instead.





3.4 Event Windows area

Event windows area The center of the main Safety Historian application screen containsthree event windows, each of which can be opened by clicking itsassociated tab (see Figure 3-2). The following event windows are

available:

Incoming Events window

Use this window to view the latest events as they are recorded bySafety Historian.

For details on viewing the incoming events refer to subsection 7.4of this manual.

Historical Events window

Use this window to view events that were reported earlier and that

are stored on hard disk.For details on viewing the historical events refer to subsection 7.5

of this manual.

Points window

Use this window to view and edit all points that have been

configured in the Safety Historian program.

Accessing the Editing, Adding and Deleting options of points isdone via right-clicking in the area of the Points window.

For details on configuring points refer to subsection 5.3 of thismanual.





3.5 Multibox Controls

Multibox controls Safety Historian uses "multiboxes", which are used to select one ormore items from a standard list. Multiboxes share features from a list box (selection of more than one item from a list) and a combo box

(showing the selected item or items in an edit control). Figure 3-3 below shows an example of a multibox.

Multibox with open list box Multibox with closed list box

Figure 3-3 Multibox controls

The visibility of the list box is toggled by clicking anywhere at the list box (as it appears in closed form, see right multibox in Figure 3-3).

The list box will then 'unfold'. By default the list box is not visible.To select one option, simply click on the option to highlight it.

To select multiple consecutive options, hold the Shift key and click.To select multiple non-consecutive options, hold the Ctrl key and

click.

The edit control will show all items which you have selected in the list box, separated by a '+' symbol. If the edit control contains more itemsthan can be displayed, you can use the cursor keys to move through

the selected items. This will not affect the selection in any way. If youclose the list box, the edit control is updated to display the selected

items, except in the following cases:

• If you did not select any item from the list box, the edit control

displays ‘None’.

• If all items have been selected, the edit control displays ‘All’.





3.6 Error Reporting

Error conditions There are two conditions in which errors and warnings may occur:1. You are interacting with the program and you make a mistake of

some kind (e.g. entering invalid information), or

2. You are not interacting with the program, but background errorsoccur (e.g. insufficient disk space, communication error, etc.).

Errors and warnings are reported to you via a standard Windows-stylemessage box to draw your immediate attention (see Figure 3-4).

Figure 3-4 Standard Safety Historian error message box

Low disk space When hard disk space reaches 200 Mega Bytes then Windows will

issue a pop-up message that warns about the low disk space. If themessage is ignored and disk space is declining further then no new

events can be retrieved since previously stored events will not beoverwritten.

Not retrieving events from an Event Detecting Device (EDD) meansthat eventually the event buffers in the EDD will overflow and thus

new events cannot be stored.

CorruptedSOE database

In case of a power-outage or abnormal termination of the SafetyHistorian application, the database will not get corrupted if the Write-

caching feature of the hard disk (where the database is located) has

been disabled as instructed during setup of the Safety Historian, seesubsection 2.6 (Installing the Safety Historian software).

If the database gets corrupted for whatever reason it will be repairedautomatically. You may lose a maximum of one event after a repair.

An Uninterruptable Power Supply (UPS) is advised when retrieval

of events is not allowed to be interrupted during a power-outage thataffects the Safety Historian station, client or server.





3.7 License and Version Information

License and VersionInformation

To view detailed License and Version information, launch the About box. The About box (Figure 3-6) is launched when you click at the

Honeywell brand name that is located in the upper left hand corner ofthe main screen (Figure 3-5 ). At the server window of the network

version it is located at the upper right hand corner.

The about box also shows Process Information: the actual amount ofresources that the Safety Historian application is using.

Figure 3-5 Click Honeywell brand to launch the About box

Figure 3-6 License and version information





3.8 Password Protection

Passwordprotection A number of functions in the Safety Historian application are password-protected to prevent unauthorized access to these functions.An authorization hierarchy has been defined, with the following four

authorization levels (in descending order of authority):

• Supervisor,

• Architect,

• Maintenance, and

• Operator.

The Supervisor has the highest authority and has access to all Safety

Historian functions. This means that the Supervisor password isaccepted for all authorization levels. At the authorization levels otherthan Supervisor, only a subset of the Safety Historian functions can be

accessed. For details on password maintenance refer to subsection10.8 of this manual.

Table 3-1 on page 55 outlines which Safety Historian features are

password-protected. If a certain option requires passwordauthorization, a password entry window will appear (see Figure 3-7

below), and you are prompted to enter the password for the specifiedauthorization level (or higher).

Figure 3-7 Password entry window

If you enter an incorrect password, an error message is displayed, and

you can enter the password again. There are two exceptions to this:• the network architecture, and

• the Configuration dialog.

Each of these is explained in more detail below.

Network Accessing the network architecture is password-protected at Architect





architecture level. If you enter an incorrect password or no password at all, andyou choose the OK button (or press the E NTER key), an error message

will appear saying you entered an incorrect password.If you choose the Cancel button (or press the ESCAPE key), no error

message is displayed and the Network Architecture dialog willappear nonetheless. However, all options that you have no

authorization for will be disabled. This means that you will then only be able to view the network architecture, and not modify it in any

way.

Configurationdialog

Entering the Configuration dialog (Options \ Configuration) is password-protected at Maintenance level. If you enter the correct

password, the Configuration dialog will appear, and you can modifyall options without having to enter any password again.

If you enter an incorrect password or no password at all, and youchoose the OK button (or press the E NTER key), an error message

will appear saying you entered an incorrect password.If you choose the Cancel button (or press the ESCAPE key), no error

message is displayed and the Configuration dialog will appearnonetheless. However, the following three options that require the

Maintenance authorization level will be disabled:

Changing the maximum size of the event database,

Overriding the event visibility, and

Enable time synchronization of the SM/FSC controller.

Also, if you want to change the default status messages for points, youwill be prompted to enter the Operator password.

All other configuration items do not require password authorization,and can therefore be modified as you please.

Default passwords The default authorization passwords are as follows:Supervisor password: SUPERVISOR

Architect password: ARCHITECT Maintenance password: MAINTENANCE

Operator password: OPERATOR

Please note that the passwords are all case-sensitive (i.e. 'x' is not the

same as 'X'). The default passwords are all in upper-case characters.

Requiredauthorization levels

Table 3-1 below provides an overview of the minimum required

authorization level to carry out certain functions.





Table 3-1 Safety Historian functions and required authorizationlevels

Minimum requiredauthorization level Action for which authorization is required

Operator Exiting Safety Historian.

Operator Changing the default status messages of points(see subsection 9.2.5 of this manual).

Maintenance Changing the maximum size of the event database(see subsection 10.3 of this manual).

Maintenance Overriding the event visibility(see subsection 8.2.4 of this manual).

Maintenance Importing and exporting points(see section 6 of this manual).

Maintenance Exporting historical events(see subsection 7.5.4 of this manual).

Maintenance Deleting events after exporting them(see subsection 7.5.4 of this manual).

Maintenance Backing up and restoring configurations(see subsections 10.7 and 10.8 of this manual).

Maintenance Defining and editing point properties(see subsections 5.4 and 5.5 of this manual).

Maintenance Deleting points

(see subsection 5.6 of this manual). Architect Defining and editing the network architecture

(see section 4 of this manual).

Supervisor Changing the passwords(see subsection 10.8 of this manual).





Left blank intentionally.




Section 4: The Network Architecture 57

Section 4 – The Network Architecture


Section overview This section explains how to configure the network architecture used

in the Basic version of the Safety Historian application. It covers thefollowing topics:


4.1


4.2

Introduction ................................................................................................. 58

4.3

Network Architecture Basics ............................. ......................... .................. 59 4.4

Working with Event Detecting Devices (EDDs) ......................... .................... 62

4.4.1

Introduction ................................................................................................. 62

4.4.2

Adding an EDD ....................... ........................ ......................... .................... 64

4.4.3

Reviewing or Editing an EDD ........................ ......................... ...................... 65

4.4.4

EDD Properties........................................... ......................... ........................ 65

4.4.5

Deleting an EDD ..................... ......................... ........................ .................... 74

4.5 Working with Printers ....................... ........................ ......................... ........... 75

4.5.1

Introduction ................................................................................................. 75

4.5.2 Adding a Printer ...................... ........................ ......................... .................... 76

4.5.3 Reviewing or Editing a Printer ....................... ......................... ...................... 77

4.5.4

Printer Properties ........................ ......................... ........................ ................ 77

4.5.5

Deleting a Printer ........................ ......................... ........................ ................ 80

4.6

Printing the Network Architecture ....................... ........................ .................. 81




58 Section 4: The Network Architecture

4.2 Introduction

Note:The network architecture of the network client version of Safety

Historian works slightly differently from the Basic version. Fordetails on SOE networking refer to document SH51-200.1

("Safety Historian R200.1 – Network Option").

Configuration ofnetwork and points

The Safety Historian application can only communicate with printersand Event Detecting Devices (EDDs) if the network architecture and

points have been properly configured.

The network architecture defines the devices and their propertiesthat are or will be connected to the Safety Historian station; the

devices being:

• Event Detecting Devices (e.g. SM controllers), and,

• printers.

A point is a data point of an EDD as defined in its application. The process behavior of points is being monitored and their events are

transmitted to Safety Historian which will log these events.The points correspond with the tag numbers as defined in the

application of the Event Detecting Device.

Configuration of network and points must be done in the followingorder:

1. Set up links between the Safety Historian station (), printers and

Event Detecting Devices (EDDs) by defining the Network

Architecture (described in this section).

2. Create the database of points by editing the Point Properties (see

section 5 of this manual). You can also import a dBASE file that

contains the point configuration of an existing SM/FSC controller(see section 6 of this manual).





4.3 Network Architecture Basics

Introduction To set up and configure links between the Safety Historian station, printers and EDDs, choose Network Architecture in the

Configuration & Tasks area. This will open the Network

Architecture window (see Figure 4-1 below).

Note:Accessing the network architecture is password-protected atArchitect level. If you enter an incorrect password or no

password at all, and you choose the OK button (or press theE NTER key), an error message will appear saying you entered an

incorrect password.If you choose the Cancel button (or press the ESCAPE key), no

error message is displayed and the Network Architecture dialog will appear nonetheless. However, all options that you

have no authorization for will be disabled. This means that youwill then only be able to view the network architecture, and not

modify it in any way. (This means that the Add, Delete and

Properties buttons will be disabled.)





Figure 4-1 Network Architecture window

The Safety Historianstation(‘SOE System’)

The Safety Historian station is the workstation (PC) that Safety

Historian is running on. It is always at the top of the list. In the initialstate, it is the only component available in the network. It has no

properties that can be edited, nor can it be deleted. All othercomponents (EDDs and/or printers) are added by the user.

Displaying/hiding"lower-level" items

If any of the items has a (open triangle) in front of it, this means

that one or more network components are connected to it. If you then

click the triangle icon, the branch will unfold and the connectednetwork components will become visible. Conversely, clicking a

(solid triangle) will fold a branch, thus hiding any lower-level

network components.By default, all branches will be unfolded when you open the Network

Architecture window.

Adding network To add Event Detecting Devices (EDDs) or printers to the network





components architecture, do the following:

1. Select the item you wish to add the new network component to

(Safety Historian station or an existing EDD).

2. Choose the Add Device… or Add Printer… button in theNetwork Architecture window,

or right-click and choose one of the Add options from the popup

menu.

Note:In the network version of Safety Historian, first a connection

needs to be made (Connect button) with the server before a

new network component can be added to it.

For details on adding Event Detecting Devices refer to subsection

4.4.2 on page 64. For details on adding printers refer to subsection 4.5.2 on page 76.

Deleting networkcomponents

For details on deleting Event Detecting Devices from the network

architecture refer to subsection 4.4.5 on page 74. For details on deleting printers from the network architecture refer to

subsection 4.5.5 on page 80.

Printing the network

architecture

For details on printing the network architecture refer to subsection 4.6

on page 81.





4.4 Working with Event Detecting Devices (EDDs)

4.4.1 Introduction

Event DetectingDevices (EDDs)

Safety Historian can only communicate with Event Detecting Devices

(e.g. SM/FSC controllers) that are correctly defined in the networkarchitecture. EDDs can be divided into two categories:

• EDDs which are directly connected to the Safety Historian station(the "SOE System"), and

• EDDs which are connected to another EDD (which, in turn, is

directly connected to the Safety Historian station).

EDDs connectedto other EDDs

If one or more EDDs are connected to another EDD in the network

architecture, they will normally form a network of SM/FSCcontrollers, with the SM/FSC controller directly connected to the

Safety Historian station being the network master and the others theslaves.

Consider the network architecture shown in Figure 4-1 on page 60. Figure 4-2 below represents the physical layout of the corresponding

sequence-of-event network. There are basically three separatecommunication links: to controllers A, B and C.

Figure 4-2 Safety Historian network architecture and SM/FSC

networks





Controller A stands on its own. Controller B, D and E together forman FSC network, with controller B being the master. Similarly,

controllers C, F, G and H are a SM network, with controller C beingthe master.

Translated to the Safety Historian network architecture, this meansthat controllers A, B and C are directly connected to the Safety

Historian station. Controllers D and E are connected to controller B,and controllers F, G and H to controller C (see Figure 4-1 on page 60).

Retrieving SOE datafrom slave EDDs

In order to retrieve SOE data from an SM/FSC master/slave network,every SM/FSC controller in the network must be defined in the Safety

Historian network architecture. It is not sufficient to just define themaster controller.

If you do not define a present slave SM/FSC controller in thenetwork, Safety Historian will be able to retrieve its events but will

not recognize them. The status message of the events will then be"Event ID not recognized".

Regarding SM controllers

When SM controllers have been loaded with software versions older

than R160.1: then SOE data from a slave SM controller cannot beretrieved via its master controller.

In this case it is necessary to directly connect Safety Historian to aslave SM controller to be able to retrieve its SOE data.


SOE data from a slave FSC controller can be retrieved via its master

provided that master and slave are using the FSC DS SOE protocol.

EDD Device number Regarding SM controllers

Each SM controller has its own controller node number (assignedusing the Safety Builder software).

In Safety Historian, the device number of an EDD must match thecontroller node number of the corresponding SM controller in the

SM network.


Likewise, each FSC controller has its own system number (assigned

using the FSC Navigator software).In Safety Historian, the device number of an EDD must match thesystem number of the corresponding FSC controller in the FSC

network.





4.4.2 Adding an EDD

Adding an EDD To add an Event Detecting Device (EDD) to the network architecture,

do the following:

1. Open the Network Architecture window.

2. Select the item you wish to add the new EDD to (Safety Historian

station or an existing EDD).

Choose the Add Device… button,orright-click and choose the Add Device… option from the popup

menu.

Note:

In the network version of Safety Historian, first a connectionneeds to be made (Connect button) with the server before a

new Device can be added to it.

3. If you chose to add a new EDD to:

• The Safety Historian station:Then an Event Detecting Device Properties dialog will have

appeared with which you need to specify the complete set ofcommunication properties of the added EDD.

Please continue reading at subsection 4.4.4 EDD Properties on page 65;

•

An existing EDD:(So the added EDD is a slave of the existing EDD.)

In this case a reduced Event Detecting Device Properties dialog will have appeared with which you need to specify only

the Device Name and the Device Number. The SafetyHistorian station does not need the rest of the communication

properties of the added EDD since it is not directly connectedto this added slave EDD. The Safety Historian station will

retrieve SOE data from the slave via the existing EDD (themaster).

Please continue reading at subsection 4.4.4 EDD Properties on

page 65;





4.4.3 Reviewing or Editing an EDD

Reviewing/editingEDD properties

After an Event Detecting Device has been added to the network

architecture, you can always review and/or edit its properties. Thiscan be done in either of two ways:

• Select the appropriate EDD in the Network Architecture window(see Figure 4-1) and choose the Properties… button, or

• Select the appropriate EDD in the Network Architecture window,

right-click and choose the Properties… option from the popupmenu.

4.4.4 EDD Properties

EDD properties Each EDD has a number of properties that need to be specified when

the EDD is added to the network architecture. To set (or edit) the properties of an EDD, choose the Properties… button. The Event

Detecting Device Properties dialog will appear. The propertiesshown depend on whether the EDD is a slave (see Figure 4-5) and

when it is not a slave, the communication type: Ethernet or Serialcommunication (see Figure 4-3 and Figure 4-4 below). The default

setting for new EDDs is Ethernet communication.

Please note that any changes to EDD properties become effective assoon as the Event Detecting Device Properties dialog is closed (bychoosing the OK button).





Figure 4-3 Properties for Ethernet EDD Figure 4-4 Properties for Serial EDD

Figure 4-5 Properties for slave EDD (connected via master EDD to Safety HistorianStation)





The following properties are shared by all EDD dialog windows

shown above:

• Device name

• Device number• Use daylight saving time (Enable for DCF only)

The remaining properties are shared by both Ethernet-based EDDs

and serial-based EDDs dialogs:

• Communication interface, and

• Enable collection of events.

Each of these properties is discussed in more detail below.





Device Name The device name is a unique descriptive name that you assign to theEDD when you add it to the network architecture.

When a device name is typed that has already been given to another

EDD then the OK button will be deactivated.

The device name will typically be equal to the:

• Controller name (regarding SM controllers);

• Project/Application name (regarding FSC controllers).

Device Number You must specify the appropriate device number of the EDD. In the

case of SM/FSC controllers, this number must match the controller

node number / system number ( assigned using the Safety Builder /

FSC Navigator software.

When a device number is typed that has already been given to anotherEDD then the OK button will be deactivated.

• Regarding SM controllers:You can look up / check the ‘controller node number’ via SafetyBuilder by:

- selecting ‘Network Configurator’,- selecting tab ‘Physical View’,

- clicking ‘Expand All’, and thenhover the mouse pointer over a desired controller. A ‘tool tip’

window will then show the ‘controller node number’.

Alternatively: right click the desired SM controller and select‘Properties’. The properties window will then show the ‘controllernode number’

• Regarding FSC controllers:You can look up / check the ‘system number’ via FSC

Navigator by selecting: System Configuration | Install |Configuration | FSC-FSC communication configuration. A screen

will then appear that lists all connected FSC systems together withtheir ‘system numbers’.

Use daylight savingtime

(Enable for DCF only)

Enable this check box when the EDD uses a DCF as clock-source. Note that this is also applicable for a slave EDD which master uses aDCF.





Communicationinterface

This is the type of communication that is used between the SafetyHistorian station and the connected EDD. Two communication types

are supported:

• Ethernet

• Serial (RS-232/485)

Select the communication type that Safety Historian should use.

Serialcommunication

The following property is specific to EDDs with Serial (RS-232/485)

communication:

• COM port PC

COM port PC This is the communication port at the Safety Historian station that is

used to interface with the EDD. Safety Historian supports RS-485and RS-232 communication ports. The ports can be any of the

standard serial communication ports in the Safety Historian station(COM x), as well as the ports on an installed third-party interface

board (e.g. a Black Box board).Please note that the drop-down list may not contain all COM ports if

they have not been defined in Windows (even though the porthardware may be present). For details on how to define ports in

Windows please refer to the Windows documentation.To specify the communication attributes of the selected port, choose

the Settings… button next to the COM Port PC drop-down list (see below).

Communicationsettings

If you choose the Settings… button in the properties dialog forSerial-based EDDs (see Figure 4-4), a new popup window will

appear in which you can modify the communication settings for theselected port:





Figure 4-6 Communication settings for an EDD

By default, the FSC-DS protocol is selected as the protocol for

communication between the Safety Historian station and the EDDs(FSC controllers). The other parameters should be set according to the

communication parameters of the FSC controller. Check theengineering documents or check these settings via FSC Navigator by

selecting:System Configuration | Install | Modules | Central Part |COM.

Note:Depending on the protocol selected, it may be possible that

some properties cannot be modified.

Ethernetcommunication

The following properties are specific to EDDs with Ethernet

communication:

• Redundant channels

• IP address(es)

RedundantChannels

Regarding SM controllers:

Select this checkbox if the connected SM controller has beenconfigured with a redundant architecture.

You then also need to provide the IP address of the second Ethernetcommunication channel.

Regarding FSC controllers:





Select this checkbox if the connected FSC controller has redundantEthernet channels (either dual channels on one 10018/E/E module or

single channels on two 10018/E/1 modules).You then also need to provide the IP address of the second Ethernet

communication channel.

IP Address(es) • Regarding SM controllers:

You need to supply the IP address(es) of the port(s) of the USI-

000x module(s) that have been allocated to the Experion(SCADA) protocol.

You can look up / check the IP address(es) via Safety Builder by:

- selecting ‘Network Configurator’,

- selecting tab ‘Physical View’,- clicking ‘Expand All’, and then- right click the SM controller that is connected to the Safety

Historian icon (see Figure 4-7), and select ‘Properties’.The properties window will then show the used COM port (see

Figure 4-8).

Figure 4-7 Physical view of Safety Historian network in SafetyBuilder





Figure 4-8 Properties window showing COM port identification.

COM ports 1A, 2A, 1B or 2B If the COM port identification starts with a ‘1’ then click the tab

‘COM Module 1’ (otherwise ‘COM Module 2’).

If the COM port identification contains the letter ‘A’ or ‘B’ thenthis tab will show the IP address(es) you will need.

For a certain COM port only one IP address will exist (of CP1)when the SM controller has been configured with a Non

Redundant architecture. Otherwise two IP addresses will exist (for both CP1 and CP2).

COM ports 1C, 2C, 1D or 2D

If the COM port identification contains the letter ‘C’ or ‘D’ thenone or two Black Box converters* (LES301A) are being used of

which the IP addresses are to be configured/retrieved with asoftware tool that has been provided by the Black Box company.

The IP address(es) are thus not present in Safety Builder.One converter is used if the SM controller has been configured

with a Non Redundant architecture. Otherwise two converters areused.





Overview of IP address sources:

SM controller with redundant architecture (CP1 and CP2)

The IP addresses will be those of:

o port 1A of CP1 (using USI module at slot 2) port 1A of CP2 (using USI module at slot 7)

or: o port 2A of CP1 (using USI module at slot 3)

port 2A of CP2 (using USI module at slot 8)

or: o the two Black Box converters* (LES301A) in case ports are

used with a ‘C’ or ‘D’ identification.

SM controller with Non-redundant architecture (CP1 only)

The IP address will be that of:

o port 1A (at CP1 only; using USI module at slot 2)

or:

o port 2A (at CP1 only; using USI module at slot 3)

or: o the Black Box converter* (LES301A) in case a port is used

with a ‘C’ or ‘D’ identification (at CP1 only)

* Note:The Black Box converter (LES301A) is a serial-Ethernet

converter that allows serial ports C/D of a USI-000x to be usedfor an Ethernet protocol.

The IP addresses of these converters are to beconfigured/retrieved with a software tool that has been provided

with the Black Box converter. The IP address(es) are thus not present in Safety Builder.

• Regarding FSC controllers:You need to supply the IP address(es) of the 10018/E/ x Ethernet

interface module(s) in the connected FSC system. These are the IPaddresses that were allocated to the 10018/E/ x module(s) using the

FSC Navigator software. You can use FSC Navigator to look upthe correct IP address(es) by selecting: System Configuration |

Install | Modules | Central Part | COM.

In case of Ethernet channel redundancy, you also need to providethe IP address of the second Ethernet communication channel.





4.4.5 Deleting an EDD

Deleting EDDs EDDs can be deleted from the network architecture in either of twoways:

• Select the appropriate EDD in the Network Architecture window(see Figure 4-1) and choose the Delete button, or

• Select the appropriate EDD in the Network Architecture window

(see Figure 4-1), right-click and choose the Delete option from the popup menu.

In either case, you will be asked to confirm the deletion.

Please note the following considerations:

• The Safety Historian station cannot be deleted.

• Deleting EDDs requires the authorization level Architect.





4.5 Working with Printers

4.5.1 Introduction

Printers It is possible to connect one or more printers to the Safety Historianstation (‘SOE System’). Printers are basically used for two purposes

in Safety Historian:

• Report printing (e.g. printing of the network architecture, points or

the event history), and

• Continuous printing of incoming events.

Report printing Printers that are to be used for printing the network architecture,

points or the event history do not need to be defined in the networkarchitecture. Any printer configured in Windows can be used for

report printing —both local and shared (network) printers. For detailson how to configure printers in Windows refer to the Windows

documentation.

For details on printing the network architecture refer to subsection 4.6on page 81.

For details on printing the point configuration refer to subsection 5.8.

For details on printing historical events refer to subsection 7.5.3.

Continuous printingof incoming events

Printers that are to be used for continuous printing of incoming events

need to be defined in the network architecture (see subsection 4.5.2on page 76). They must be line printers (or substitutes), and should

preferably be directly connected to the Safety Historian station.(Although network printers and shared printers can also be used, thisis not recommended as their job control could mix your events with

output submitted by other users.) Whatever printers are used, theymust be installed in Windows.

Note:In the network version of Safety Historian, printers may only beconnected to servers. For details on SOE networking refer to

document SH51-200.1 ("Safety Historian R200.1 – Network

Option").





4.5.2 Adding a Printer

Adding a printer To add a printer for continuous printing of incoming events to thenetwork architecture, do the following:

1. If the printer of choice has not been installed yet in Windows: please refer to the Windows documentation and install the printer

of choice.

2. Open the Network Architecture window.

3. Select the Safety Historian station item. (Printers cannot be

added to an EDD.)

Choose the Add Printer… button,or

right-click and choose the Add Printer… option from the popup

menu.

Note:

In the network version of Safety Historian, first a connectionneeds to be made (Connect button) with the server before a

Printer can be added to it.

4. The Windows Print Setup dialog Figure 4-9 will appear.See subsection 4.5.4 Printer Properties on page 77.





4.5.3 Reviewing or Editing a Printer

Reviewing/editingprinter properties

After a printer has been added to the network architecture, you canalways review and/or edit its properties. This can be done in either of

two ways:

• Select the appropriate printer in the Network Architecture window(see Figure 4-1) and choose the Properties… button, or

• Select the appropriate printer in the Network Architecture window(see Figure 4-1), right-click and choose the Properties… option

from the popup menu.

4.5.4 Printer Properties

Printer properties Each printer for continuous printing has a number of properties thatneed to be specified when the printer is added to the network

architecture. To set (or edit) the properties of a printer, choose theProperties… button. The Windows Print Setup dialog as shown in

Figure 4-9 below will appear. Please note that any changes to printer properties become effective as soon as the Print Setup dialog is

closed (by choosing the OK button).

Figure 4-9 Print Setup dialog





The following items are discussed in more detail below:

• Printer selection,

• Print width, and

• Left margin

Printer Selection The drop-down list shows all printers configured in Windows (both

local and network printers). Select the line printer (or a substitute)that you wish to use for continuous printing.

Please note that this list will be empty if no printers have been

installed in Windows or if all available printers are already used for

continuous printing. For details on how to install a printer in Windows please refer to the Windows documentation.The line printer should preferably be directly connected to the Safety

Historian station. (Although network printers and shared printers canalso be used, this is not recommended as their job control could mix

your events with output submitted by other users.) Whatever printer isused, it must be installed in Windows.

Detailed printer

properties

To modify detailed printer properties for the selected printer, click the

Properties… button in the Print Setup dialog.

Note:The "look and feel" of the printer properties dialog and the

available options in it depend on the printer model and drivers

installed.

Print Width The number of characters that will be printed per line. The exact printwidth depends on the characters per inch (cpi) of the printer's default

font, which will always be the font used to print incoming events

continuously. The printer's default font is the font that is loaded intothe printer memory after the printer is switched on. For details referto your printer documentation.





Left Margin The number of characters that is used as the left paper margin. Theexact number that should be set depends on the paper width, the

characters per inch (cpi) of the printer's default font, and how wideyou want the margin to be.

Example:

The standard page width for A3 paper with a 10-cpi font is 132characters. You could then set the print width to 120 and the left

margin to 6 (which would also leave a right margin of 6). For detailson other paper and font sizes refer to the documentation that was

supplied with your printer.

Note:Safety Historian does not check whether the sum of thespecified left margin and the print width exceeds the number of

characters the printer can print on one line. If this happens,events may occupy more than one line, thus breaking the

column layout.





4.5.5 Deleting a Printer

Deleting Printers Printers can be deleted from the network architecture in either of twoways:

• Select the appropriate printer in the Network Architecture window(see Figure 4-1) and choose the Delete button, or

• Select the appropriate printer in the Network Architecture window

(see Figure 4-1), right-click and choose the Delete option from the pop-up menu.

In either case, you will be asked to confirm the deletion.

Please note the following considerations:

• The Safety Historian station cannot be deleted.

• Deleting printers requires the authorization level Architect.

• Deleting a printer will delete all references to that printer in the

point properties database.





4.6 Printing the Network Architecture

Printing the networkarchitecture You can print the network architecture to any printer that has beenconfigured in Windows (both local and network printers).Color printing is supported. Before you can print the network

architecture, you must have configured a printer which is not used to print incoming events continuously. If you have not configured such a

printer, the Print

option from the File menu will be disabled.

To print the SOE network architecture, open the Network

Architecture window (see Figure 4-1) and choose the Print button.

Before printing to paper you can preview the output on screen bychoosing the Preview button. See Figure 4-10 for an example.





Figure 4-10 Previewing printer output of the network architecture

Options in Print The Print Preview window has a number of options that allow you to





Preview window further inspect the output before actually printing it. You can alsosave the report to a file on your hard disk and retrieve report files that

were saved earlier. This is very useful if you want to compare twonetwork architectures (e.g. after a modification).

Table 4-1 below lists the most important buttons with their functions:

Table 4-1 Most important functions in Print Preview window

Button Function

Zoom page in/out.

Zoom page to selected percentage (e.g.100%).

Zoom to fit the full page width in the window(= default view).

Go to the first page (if report consists of more than

one page).Go to previous page (if report consists of more thanone page).

Go to entered page number.

Go to next page (if report consists of more than onepage).

Go to last page (if report consists of more than onepage).

Print the current network architecture (first thestandard Windows Printer setup dialog is shown).

Save the current network architecture to aFastReport report (see below).

Load a FastReport file that was saved earlier(see below).

FastReport(fp3) files

The network architecture as shown in the Print Preview window can be saved to a FastReport file for further use later.

If you click the icon in the button bar, a dialog will appear whichallows you to specify the name and location of the FastReport file.

The extension fp3 is assumed and does not need to be entered.

To load an existing FastReport file that was saved to hard disk earlier,click the icon in the button bar. A dialog will then appear which

allows you to select the FastReport file you wish to open.




Section 5: Working with Points 85

Section 5 – Working with Points


Section overview This section explains how to set up, configure and use points in theSafety Historian application. It covers the following topics:


5.1


5.2

Introduction ................................................................................................. 86

5.3

Point Configuration ..................... ......................... ........................ ................ 87

5.3.1

Introduction ................................................................................................. 87

5.3.2

Point Properties ...................... ........................ ......................... .................... 88

5.3.3

The Point Browser ........................................... ........................ .................... 91

5.4

Adding Points ......................... ........................ ......................... .................... 92

5.5

Editing Point Properties ........................... ......................... ........................ ... 94

5.6

Deleting Points ........................................... ......................... ........................ 95




86 Section 5: Working with Points

5.2 Introduction

Configuration ofnetwork and points The Safety Historian application can only communicate with printersand EDDs if points and network architecture have been properlyconfigured.

The network architecture defines the devices and their propertiesthat are or will be connected to the Safety Historian station; thedevices being:

• Event Detecting Devices (e.g. SM controllers), and,

• printers.

A point is a data point of an EDD as defined in its application. The process behavior of points is being monitored and their events aretransmitted to Safety Historian which will log these events.The points correspond with the tag numbers as defined in theapplication of the Event Detecting Device.

Configuration of network and points must be done in the followingorder:

1. Set up links between the Safety Historian station, printers andEvent Detecting Devices (EDDs) by editing the Network

Architecture (see section 4 of this manual).

2. Create the database of points by editing the Point Properties (described in this section). You can also import a dBASE file thatcontains the point configuration of an existing SM/FSC controller(see section 6 of this manual).





5.3 Point Configuration

5.3.1 Introduction

Introduction The Safety Historian application can only access and properly use points if they have been properly configured.To define and/or edit points, select the Points tab from the Eventwindows area and right-click at either an existing Point or at an emptyline. Then a context menu will open with the following options:(double clicking will open the Properties window right away)

• Add Point; Add new points to the configuration (see subsection

5.4),

• Delete points from the configuration (see subsection 5.6),

• Properties; Edit the properties of configured points (see subsection5.5),

The Import Points function is available in the Configuration &Tasks area. It will import points into the configuration, i.e. add new points and change the properties of existing ones with points that arespecified in a file with a specific format (see subsection 6.2 of thismanual).

Please note that some tasks require a certain authorization level inaccordance with table 3-2 in subsection 3.10.

The Points window (see Figure 5-1 on next page) is also referred to asthe 'point browser'.) There must be at least one configured EDD before you can configure any point properties. If no EDD is available,you cannot add any points.





Figure 5-1 Points window

5.3.2 Point Properties

Point properties Each point can have the properties listed below in alphabetical order.(Please note that not all properties may be applicable, depending onthe point type).

Description This attribute specifies a text of up to 64 characters which providesextra information about the point.

EDD This attribute specifies in which Event Detecting Device (EDD) the

point is located.

Analog HealthyMessage

This attribute is only applicable to analog inputs and outputs (AI andAO). It specifies a text of up to 64 characters which will be printed asthe event status message as soon as the point value changes fromalarm low or high to the healthy state.

Analog HealthyMessage Color

This attribute is only applicable to analog inputs and outputs (AI andAO). It specifies the color of the Healthy Message of this point in the





Incoming Events window. The color can be selected from thestandard Windows color palette. If no color is selected, the defaultcolor for the point type is used. This default color can be set in theConfiguration Options menu, see subsection 9.3.5.

Boolean High Message This attribute is only applicable to digital inputs and outputs (DI andDO). It specifies a text of up to 64 characters which will be printed asthe event status message as soon as the point value changes from lowto high.

Boolean High MessageColor

This attribute is only applicable to digital inputs and outputs (DI andDO). It specifies the color of the High Message of this point in theIncoming Events window. The color can be selected from thestandard Windows color palette. If no color is selected, the defaultcolor for the point type is used. This default color can be set in the

Configuration Options menu, see subsection 9.3.5.

Boolean Low Message This attribute is only applicable to digital inputs and outputs (DI andDO). It specifies a text of up to 64 characters which will be printed asthe event status message as soon as the point value changes from highto low.

Boolean Low MessageColor

This attribute is only applicable to digital inputs and outputs (DI andDO). It specifies the color of the Low Message of this point in theIncoming Events window. The color can be selected from thestandard Windows color palette. If no color is selected, the defaultcolor for the point type is used. This default color can be set in the

Configuration Options menu, see subsection 9.3.5.

Analog OverrangeMessage

This attribute is only applicable to analog inputs and outputs (AI andAO). It specifies a text of up to 64 characters which will be printed asthe event status message as soon as the point value changes fromalarm low or healthy to the alarm high state (only applicable for AIand AO type points).

Analog OverrangeMessage Color

This attribute is only applicable to analog inputs and outputs (AI andAO). It specifies the color of the Overrange Message of this point inthe Incoming Events window. The color can be selected from the

standard Windows color palette. If no color is selected, the defaultcolor for the point type is used. This default color can be set in theConfiguration Options menu, see subsection 9.3.5.

Printer 1 This attribute specifies the first printer that will print the eventsrelated to the point if they occur.

Printer 2 This attribute specifies the second printer that will print the eventsrelated to the point if they occur.





SOE ID Sequence-of-Event Identification, also known as: ‘SOE Number’,‘SOE sequence number’ and ‘SERSEQ’.It matches the SOE ID of the corresponding point in the SM/FSC

controller. The SOE ID must be a unique number within an EDD.

Subunit A subunit is part of a unit. It specifies in which subunit the point islocated. The name of a subunit can be a text of up to 20 characters.

Tag Number The Tag Number can be any sequence of up to 32 alphanumericcharacters.The combination of:

• Point Type

• Tag Number and

• EDD

provides a unique identification of a point.

Tag Identification The combination of Point Type + Tag Number is called the TagIdentification.See Tag Number.

Analog UnderrangeMessage

This attribute is only applicable to analog inputs and outputs (AI andAO). It specifies a text of up to 64 characters which will be printed asthe event status message as soon as the point value changes fromalarm high or healthy to the alarm low state.

Analog Underrange

Message Color

This attribute is only applicable to analog inputs and outputs (AI and

AO). It specifies the color of the Underrange Message of this point inthe Incoming Events window. The color can be selected from thestandard Windows color palette. If no color is selected, the defaultcolor for the point type is used. This default color can be set in theConfiguration Options menu, see subsection 9.3.5.

Unit This attribute specifies in which unit the point is located. The name ofa unit can be a text of up to 20 characters.

Value Format This attribute is only applicable to binary outputs (BO). It specifies atext of up to 64 characters which will be printed as the event status

message as soon as the point value must be reported. The text maycontain the variable '$N', which is the current value of the BO value.

Point Type This is the type of the point. The following types are supported:

− DI (digital input) − DO (digital output)

− AI (analog input) − AO (analog output)

− BO (binary output)

Visible This attribute specifies whether events related to the point will be





displayed on screen and included on printer output.For further details refer to subsection 8.2.3 of this manual.

5.3.3 The Point Browser

Browsing throughpoints

The points are displayed in the point window (see Figure 5-1 on page88). This is a table in which each row represents a point and eachcolumn a property of a point. The points are sorted by SOE ID.

If the points cover more than one screen, you can drag the verticalscroll bar on the right of the window to easily scroll through the

points. Alternatively, you can use the ↑/↓ arrow keys,PageUp/PageDown keys, or End/Home keys to move between points.

Not all properties may be visible in the point browser. If not allcolumns fit in the window, a horizontal scroll bar is displayed whichallows you to browse through the column list. The column widths can be easily resized by dragging its edges.

Windowcustomization

The Points window can be customized in a number of ways. Thefollowing customizations are possible:

• Resizing the column widths,• Hiding certain columns,

• Rearranging the column order, and

• Setting the default status messages.

For details refer to section 9 of this manual.





5.4 Adding Points

Addingpoints To add a new point, right click at either an existing Point or at anempty line in the Points Figure 5-1window (see on page 88) andselect Add… from the context menu that pops up. This will open thePoint Properties window (see Figure 5-2 below; the fields will beempty at first).

Figure 5-2 Point Properties window

In the Point Properties

5.3.2

window you can freely edit all fields thatapply to the selected point. For details on the point properties refer tosubsection on page 88. Fields that are not applicable aredisabled. For example, the low message and high message do notapply to analog inputs (as shown in Figure 5-2 above).

In the Unit and Subunit fields, you can make a selection from thedrop-down list or you can enter a new (sub)unit. If the name you enterdoes not yet exist, you will be asked whether this new (sub)unitshould be created.A newly entered point will become effective as soon as the Point

Properties window is closed by choosing the OK button.





In order for a new point to be stored into the configuration database,the following fields must contain valid data:

• Tag Identification (Point Type + Tag Number)

• SOE ID

• Event detecting device (EDD).

Please note that the status message fields contain predefined statusmessages. You can adjust these defaults as required (see subsection9.2.5 of this manual for more details).

Browsing throughpoints

You can quickly browse through the existing points by choosing theNext button (to move to the next point) or the Previous button (tomove to the previous one).If you choose the Next button at the last point, you will go to the first point in the list. Similarly, if you choose the Previous button at thefirst point, you will go to the last point in the list.

Importantconsiderations Please note the following:

• Adding new points or editing existing ones requires theauthorization level Maintenance.

• If you try to change a point's tag identification to the exact tag

identification of another point in the specified EDD, an errormessage will appear.

• If you try to change the SOE ID to an SOE ID which is alreadyused in the EDD, an error message will appear.

• If you try to select an event detecting device, the tag identificationand SOE ID of the point must be unique in this EDD. Otherwisean error message will appear.

• The text in the Value Format field may contain one or more '$N'character sequences. If a report event occurs, this charactersequence will be replaced by the value of the point at the time the

event occurs. If, for instance, the Value Format field contains'value = $N bar', the event status message would be something like'value = 3 bar'.

• In the Unit and Subunit fields, you can select an existing unit orsubunit, but you can also enter a new unit or subunit.





5.5 Editing Point Properties

Reviewing/editingpoint properties

After a point has been added to the configuration database, you canalways review and/or edit its properties. This can be done in either oftwo ways:

• Double-click the appropriate point in the Points window (seeFigure 5-1), or

• Right-click the appropriate point in the Points window (see Figure5-1) and select Properties from the context menu that pops up.

This will open the Point Properties window (see Figure 5-2 on page88), in which you can freely edit all fields that apply to the selected point. Fields that are not applicable will be disabled. Please note that

the SOE ID and EDD cannot be edited.Any changes to a point will become effective as soon as the Point

Properties

window is closed by choosing the OK button.


• Operators can only change status messages.

• If you try to change a point's tag identification to the exact tagidentification of another point in the specified EDD, an errormessage will appear.

• The text in the Value Format field may contain one or more '$N'character sequences. If a report event occurs, this charactersequence will be replaced by the value of the point at the time theevent occurs. If, for instance, the Value Format field contains'value = $N bar', the event status message would be something like'value = 3 bar'.

• In the Unit and Subunit fields, you can select an existing unit orsubunit, but you can also enter a new unit or subunit.





5.6 Deleting Points

Deleting points In the Points window (see Figure 5-1 on page 88), you can delete a point by right-clicking the appropriate point and select Delete Point

from the context menu that pops up.




96 Section 6: Importing and Exporting Points

Section 6 – Importing and Exporting Points


Section overview This section explains how to import points. It covers the following

topics:


6.1 Section Overview ........................................................................................ 96

6.2

Importing Points ....................... ......................... ........................ .................. 97




Section 6: Importing and Exporting Points 97

6.2 Importing Points

dBASE file Besides using thePoints

Table 6-1

window to add and modify points (seeFigure 5-1), you can also use the import function to add points

automatically. The points to be imported should be specified in aspecially formatted import dBASE file.

below shows the required format.

Notes on table fields:

• If a mandatory field value is missing then the record will beignored, i.e. it will not be imported into Safety Historian);

• Unknown fields will be ignored;

• The field order is of no importance.

Important!

The import function will update the configuration data of existing

points without any warning.Existing points in the historical event database will not be updated to

preserve consistency in displaying historical events.

Table 6-1 Structure of dBASE point import file

FIELD NAME MANDATORY TYPE SIZE COMMENTS

TYPE Yes Character 2 SM: ‘Point Type’ / FSC: ‘Variable type’

TAGNUMBER Yes Character 32 Tag NumberSERSEQ Yes Numeric 5 SOE ID

QUALIFICAT No Character 16 Qualification status message:Regarding SM: Defined as field ‘State 1 text’ in the PointConfigurator of Safety Builder;

Regarding FSC:Defined as field ‘Qualification’ in theSystem Configuration of FSC Navigator;

For more information see paragraph:‘Qualification status message’.





Importing pointsfrom SM system

If the Event Detecting Device is an SM controller, you can use the

Safety Builder’s xls export file, convert it to dBASE format and use itas the import file for Safety Historian. Points from the SM system are

then imported into Safety Historian.

Importing pointsfrom FSC system

If the Event Detecting Device is an FSC controller, you can use theFSC Navigator’s dBASE export file as the import file for Safety

Historian. Points from the FSC system are then imported into SafetyHistorian.

SOE-enabling ofSM points

/

SER-enabling ofFSC points

Before you can import SM/FSC points into Safety Historian, youmust make sure that the points are prepared for sequence-of-event

recording, in other words, they must be set to ‘SOE-enabled’ (or

‘SER-enabled’ in FSC terminology. Also, they must be providedwith a sequence number.

Regarding Safety Manager For details on how to set SM points to ‘SOE-enabled’ and provide

them with sequence numbers, please refer to Safety ManagerSoftware Reference (EP-SM.MAN.6285), Appendix G, particularly

sub section: ‘Configuring SOE’.

Regarding FSC For details on how to set FSC points to ‘SER-enabled’ and provide

them with sequence numbers, please refer to FSC Software Manual(FS80-xxx*), Appendix B, particularly sub section: ‘B.2 Sequence-

of-Event Recording to SOE Safety Historian’.* 'xxx' is the release number. For example, the Software Manual for FSC R700 is referenced

as FS80-700

Creating dBASE file After setting the desired SM/FSC points to SOE/SER-enabled, you

need to create a dBASE export file that can be used as the import filefor Safety Historian.

Note:

The dBASE file will contain more SM/FSC points than just theones that are SOE/SER-enabled. However, when importing the

SM/FSC points, Safety Historian will only import those that are

SOE/SER-enabled.





Regarding Safety Manager

In order to create a dBASE export file regarding Safety Manager

systems it is required that the following software has been installed atyour PC:

• Microsoft Office Excel 2007 or higher.

First create the xls export file in Safety Builder:

• Select Point Configurator,

• Click the button Export Points,

• You will be prompted to enter the path and file name of the xls file.

The file extension will be ‘.xls’.

Then convert the xls export file to a dBASE file:

• Launch the tool ‘SM2SafetyHistorianConverter.xls’ (part of the

SM software package). Now Excel will be launched and runs the

tool as shown in Figure 6-1;

Figure 6-1 SM to Safety Historian convertor (xls to dBASE)

• When a security warning (Figure 6-2) appears right above thespreadsheet, click Options…and choose ‘Enable this content’;

Figure 6-2 Security Warning in Excel





• At Step 1, ‘Select SOE points’ (Figure 6-3), you can decide if you

want a subset of the whole collection of SOE points. To be able toselect between the two options please click at the right rectangle

that contains either the text “All points having a SOE ID” or “Only

SOE Enabled points”. Now a small pull-down icon appears(encircled in red, see Figure 6-3). Click the icon and make yourselection;

Figure 6-3 ‘step 1’ of conversion from xls to dBASE format

• At Step 2, click the SELECT- button; a window will pop-up with

which you can navigate to the location of your xls export file.

First, please check if the xls file name has a maximum of 8characters; if it is longer it must be shortened by renaming it. Thenselect the file and click the Open- button.

Now the path and name of the xls file is visible in the rectangleright below the SELECT- button;

• Step 3: ‘Select the SOE device’ and ‘Select USI module’.

SOE device (SOE collector) You can decide if you want a further subset of the SOE points by

clicking at the upper rectangle of step 3; then a small pull-down

icon appears, click the icon and make your selection.

USI moduleSelecting the USI module is not needed, this information is

ignored during the import process at Safety Historian;

• At Step 4, click the GENERATE- button. The dBASE file willnow be generated from the xls file. The path and name of the xlsfile is visible in the rectangle right below the GENERATE-

button. The file extension will be ‘.DBF’. If you want to view theresulting dBASE file in Excel, just click at the Open- button that is

located at the right of the mentioned rectangle;

Regarding FSC

In order to create a dBASE export file regarding FSC systems, do thefollowing in FSC Navigator:

• Choose System Configuration;

• Choose Signal Specs. The I/O specification window will appear;





• Choose Write dBASE;

• You will be prompted to enter the path and file name of the dBASE

file. Also add the file extension .dbf.Please note that in FSC Navigator the maximum length of file and

directory names is 8 characters. The file extension length is 3characters.





Importing dBASEfile into SafetyHistorian

To import an SM/FSC export file into Safety Historian, do thefollowing:

1. In Safety Historian, choose Import Points in the Configuration& Tasks area.

2. This selection will, after entering the correct password, launch the

standard open file dialog of Windows.

3. Locate and select the dBASE file to be imported.

4. The Points Import Options window will appear (Figure 6-4). Inthe Event Detecting Device drop-down list, you must select the

EDD from which the dBASE file was exported. Also in thisdialog, you can select the continuous printer(s) that should print

the events of the points and/or decide to interpret the

Qualification status message field in the dBASE file (see paragraph ‘Qualification status message’).

Figure 6-4 Setting points import options

5. Choose the OK

button to start the import operation.

The import operation will add new points to the configuration andexisting points will be modified to the property settings found in theimport file. If the import of the points is successful, the point browser

will be updated to include all imported points.





Qualificationstatus message

Regarding SM, the Qualification status message is defined as field

‘State 1 text’ in the Point Configurator of Safety Builder; Regarding

FSC, it is defined as field ‘Qualification’ in the System Configuration

of FSC Navigator

The Qualification status message (contained in QUALIFICAT fieldin the dBASE file) will only be ‘interpreted’/used if the check box is

selected (see Figure 6-4) and the imported point is of typea DI or DO.If this field is to be used then:

its contents are copied to the High and Low Status Message fields ofthe Point configuration.

The Low Status Message fields will be preceded with the specifiednegation string (see Figure 6-4) ('Not' by default). If the Low Status

Message field then starts with the negation string twice (e.g. 'Not Not'), then these characters will be erased to make the phrase positive

again. The comparison is case-sensitive.

If the Qualification status message field is not to be used then thedefault status messages will be used.


• Importing points requires the authorization level Maintenance.

• Safety Historian will only import SM/FSC points that are

SOE/SER-enabled.• Safety Historian demands that the file to be imported is in dBASE

III format (with file extension .dbf).





Important Please note the following:

• The TYPE, TAGNUMBER and the SERSEQ fields must be

defined in the dBASE file (the EDD will be selected at the start ofthe import operation of the dBASE file). Otherwise the dBASE

record cannot be uniquely linked to a point. Linking records to points is based on the unique combination of the SOE ID and the

Device number of the device identified by the EDD.

• To be able to process a point, Safety Historian requires that the

TYPE, TAGNUMBER and SERSEQ fields contain valid data. If adBASE record contains invalid data (i.e. undefined types, unknown

device name or SOE ID out of range), the point will be ignored.




106 Section 7: Working with Events

Section 7 – Working with Events


Section overview This section explains how to view, print and perform other tasks withevents. It covers the following topics:


7.1

Section Overview ...................................................................................... 106

7.2

Viewing Modes ..................... ......................... ........................ .................... 107

7.3

Event Message Properties ...................... ........................ ......................... .. 108

7.4

Incoming Events ....................... ......................... ........................ ................ 112 7.4.1

Viewing Incoming Events ........................ ........................ ......................... .. 112

7.4.2

Continuous Printing of Incoming Events ........................ ........................ ..... 114

7.5

Historical Events........................................................................................ 117

7.5.1

Viewing and Filtering Historical Events ..................... ........................ ......... 117

7.5.2

Exporting Historical Events ..................... ......................... ........................ .. 121

7.5.3

Automatic Export Of Events ........................ ......................... ...................... 123




Section 7: Working with Events 107

7.2 Viewing Modes

Viewing modes Safety Historian has four different viewing modes:

• Incoming Events (continuous mode)

Viewing incoming events as they are detected by the EDDs.(see subsection 7.4).

• Historical Events (historical mode) (see Figure 7-5 below)

Viewing logged events that were detected in the past(see subsection 7.5).

• Points... Use this option to view points.

Note:The default viewing mode when Safety Historian is started iscontinuous mode (incoming events).

Switching betweenviewing modes

Switching between the viewing modes is done by clicking theappropriate tab in the main Safety Historian application window.

Event visibility All recorded events are stored in the event database. Whether or notan event is actually displayed in the Incoming Events window andHistorical Events window can be controlled by setting its eventvisibility. For details refer to subsection 8.2 of this manual

Event filtering All recorded events are stored in the event database. This allowshistorical event data to be viewed for later analysis. It may be usefulto view only those events that meet certain criteria, e.g. from a certainunit or within a certain time frame. Safety Historian has extensiveevent filtering capabilities. For details refer to section 8.3 of thismanual.

Windowcustomization

The layout of the three event windows can be customized in a numberof ways. For example, the column width and layout can easily bemodified. For details refer to section 9 of this manual.





7.3 Event Message Properties

Event messageproperties Each event takes up one line in the Incoming Events window and theHistorical Events window. The following list describes the properties of each event (in alphabetical order).

Date The date that the event occurred. The format of the displayed datedepends on the settings in the Region and Language dialog box ofthe Windows Control Panel.

Description The event's descriptive name.

EDD / Device Name The Event Detecting Device (EDD) where the event occurred (same

as point's EDD).

Event Type The type name of the event (which is customizable).There are a number of types:

• Point Value Event that occurs if a point value changes.

• Point Force Event that occurs if a point is forced or when the forcing is cleared.

• Diagnostic Event that occurs if a diagnostic error on an EDD or an EDD’slocal IO module is detected.

• Remote IO Diagnostic Event that occurs if a diagnostic error on an EDD’s remote IOmodule is detected.





• Report

o Point Report message (used by FSC only)

Event that occurs if a value report must be given of a BO point.

o Exception Report message Event that occurs if an exception report must be given:

A Point Force without a SOE ID (used by FSC only)

State of the EDD(Used by FSC only, SM uses Boolean Point Valueevents for these state events):e.g. EDD system fault, SOE buffer full, All forcescleared.

Status Message Holds the customizable points'/EDD’s status messages, which dependon the event type:

Point Value event:

• DI, DO:the Boolean point's High message or Low message, dependingon the value of the point.

• AI, AO:the Analog point's Healthy message, Overrange message orUnderrange message, depending on the value of the point.

Point Force

• DI, DO, AI, AO, BO, BI: The point’s Force set or Force cleared message.

Point report (used by FSC only):

• BO:the Binary point's report message in which a message variable($N) will be replaced with the point's value.

Exception report (used by FSC only, SM uses Boolean Point Value

events for these state events):• The EDD’s exception report message.

Diagnostic:

• The EDD’s diagnostic message in which the message variables$N, $C and $S will be replaced with the respective references tothe physical location in the device where the diagnostic refersto:





SM controller Controller number, Chassis number and Slot number.

FSC controller System number, Rack number and Position number.

Remote IO Diagnostic (used by FSC only):

• The EDD’s remote IO diagnostic message in which the messagevariables $N, $I and $S will be replaced with respectivereferences to the physical location of the remote IO modulewhere the diagnostic refers to:RUSIO Network, IOTA Address and Slot Number.

Subunit This is the subunit where the event occurred (same as point'ssubunit).

Tag Number This is the Tag Number of the point for which the event occurred.

Time This is the time at the moment the event occurred. The format of thedisplayed time depends on the settings in the Region and Language dialog box of the Windows Control Panel.

Unit This is the unit where the event occurred (same as point's unit).

Point Type This is the type of the point for which the event occurred. Thefollowing types are supported:

• DI (digital input) • DO (digital output)

• AI (analog input) • AO (analog output)

• BO (binary output)

Diagnostic eventsand Report events

If events occur for points which are fully configured in SafetyHistorian, the event properties will be filled as described above. If,however, an event occurs which is not related to a point, the eventcontents will be slightly different for some properties. This is the casefor Diagnostic events and Report events:

• The Tag Number, Description, Unit and Subunit fields are left blank.

• The Event Type field contains the proper event type name.

The contents of the Status Message of Point and Exception reportevents and Diagnostic and Remote IO Diagnostic events areaccording to the configured messages.For more information see the descriptions in the above paragraph





about the Status Message for the mentioned diagnostic en reportevents.

Unknown SOE ID orpoint not fullyconfigured

If Safety Historian receives:

• an event with an unknown SOE ID,

• an event of which a matching point has not (yet) been fullyconfigured,

then the event will be logged in the database and its contents will bedisplayed slightly different for some properties:

• The Tag Number field contains the SOE ID as available in theevent message coming from the EDD.

• The Status Message field contains the text ’Unknown DataType(5)' in case the ‘DataType’ field of the event message contains anumber that is out of range (or a similar text with another field).Otherwise it will contain the value of the field ‘EventValue’.

• The EDD field can contain the text ‘Unknown EDD’.

• The Description, Point Type, Unit and Subunit fields are all left blank.

An unknown SOE ID can be resolved by entering the point that belongs to the event into the Safety Historian point database. This can be done by :

− manually defining them (see subsection 5.4), or

− importing them from a dBASE file (see subsection 6.2).





7.4 Incoming Events

7.4.1 Viewing Incoming Events

Viewingincoming events

To continuously view events the moment they are detected by theEDDs, click the Incoming Events tab in the main Safety Historianapplication window. This will open the Incoming Events window,see Figure 7-1. You can also print the incoming events continuously (see subsection7.4.2).

Figure 7-1 Viewing incoming events





Presentationof events

Events are presented in table format. Each row represents an eventshown in its specific color. Each column is a property of the event.Events are presented in descending time order: the event that

occurred last is always displayed at the top row of the window.If not all columns fit in the window, a horizontal scroll bar isdisplayed which allows you to browse through the column list. Thecolumn widths can be easily resized by dragging its edges.

Note:The date and time format used in the window depends on thesettings in the Region and Language dialog box of theWindows Control Panel.

Event visibility All recorded events are stored in the event database. Whether or notan event is actually displayed in the Incoming Events window can becontrolled by setting its event visibility. For details refer to subsection8.2 of this manual.

Windowcustomization

The Incoming Events window layout can be customized in a numberof ways. The following customizations are possible:

• Resizing the column widths,

• Hiding certain columns,

• Rearranging the column order,

• Customizing the event colors,

• Showing or hiding the grid lines, and

• Customizing the event type names.

For details refer to subsection 9.3 of this manual.





7.4.2 Continuous Printing of Incoming Events

Continuous printingof incoming events

You can set up a line printer in such a way that it continuously printsthe incoming events for certain points as they are detected by theEDDs (and appear in the Incoming Events window).Only events of points that have been specifically assigned to that printer will be printed. This means that the Printer 1 and/or Printer 2 properties of the points should be set to the printer used for continuous printing. Otherwise the events will not be printed continuously.

Notes:1. A printer used for continuous printing of incoming events

must be a line printer (or a substitute). It should preferably

be directly connected to the Safety Historian Station.(Although network printers and shared printers can also beused, this is not recommended as their job control could mixyour events with output submitted by other users.) Whatever printer is used, it must be installed in Windows.

2. A printer used for continuous printing of incoming events

must be defined in the network architecture.

Setting upcontinuous printing To set up a printer for continuous event printing, do the following:

1. Choose Configuration Options in the Configuration & Tasks

area. This will open the Configuration Options window.

2. The Configuration Options window will by default open withthe General Options screen. Now choose the Continuous

Printing Setup option from the list on the left of the window.This will show the dialog in the window as shown in Figure 7-2on the next page.

3. In the Continuous Printing Properties box at the top, select theline printer you wish to enable/disable for continuous event printing. (The drop-down list will only show printers you haveconfigured in the network architecture.) After selection of the

printer, the current continuous printing properties of this printerwill be shown.

4. Enable or disable continuous printing by selecting or unselectingthe Print Incoming Events Continuously check box.Please note that this option is password-protected at Operatorlevel.

5. The Column Details box of the dialog allows you to specify howthings should be printed. You can specify the order of the columns





(i.e. event attributes) to be printed, as well their heading title,width (in characters). The items in the Column Order box are printed left to right (i.e. the top item is printed leftmost on the paper).

Figure 7-2 Setting up continuous printing

You can use the Move Up and Move Down buttons to rearrange

the column order on the paper.





Note:If the width of all columns exceeds the width of the paper, thecolumns that "fall off" the page will not be printed. You canthen rearrange the column order in such a way that the

desired columns are printed. You can also change the paperorientation from Portrait to Landscape or decrease the fontsize to make all columns fit the paper width.

6. Choose the OK button to make the settings effective. Theconfigured settings will be activated immediately and SafetyHistorian will start printing the incoming events as they arereported (providing the Print Incoming Events Continuously check box has been selected).





7.5 Historical Events

7.5.1 Viewing and Filtering Historical Events

Viewing thehistory of events

To view the history of events, click the Historical Events tab in themain Safety Historian application window. This will open theHistorical Events window.

In its initial state, the Historical Events window is empty. You must firstselect or define a filter to specify the criteria that events should meet to bedisplayed (e.g. all events from a particular unit or in a particular timeframe).

Predefined filter To select a predefined filter (either a standard or user-defined filter), clickthe filter drop-down box at the top of the Historical Events window (longrectangle in Figure 7-3) and then click the Apply Filter (F5) buttonlocated next to the drop-down box.

Figure 7-3 Filter controls in Historical Events window.

Custom filter (ad hoc) To define a new filter that is only to be used once and thus does not haveto be saved, click the Custom Filter… button at the top of the Historical

Events window (Figure 7-3). A Filter Criteria dialog will then appear withthe fixed filter name ‘Custom filter‘. For further details on defining eventfilters refer to paragraph Event Filters in Section 8 of this manual.

New filter (to become part of the predefined filters)To define a new filter that is to be used several times and thus must besaved, it is needed to define a new filter via the Configuration Options (located in the Configuration & Tasks area). For further details ondefining event filters please refer to paragraph Event Filters in Section 8of this manual.When the New filter has been defined, this filter will have become part ofthe list of predefined filters. You can now select this newly made filter inthe filter drop-down box at the top of the Historical Events window (long





rectangle inFigure 7-3) and then click the Apply Filter (F5) buttonlocated next to the drop-down box.

After a predefined filter has been selected or defined with the Custom

Filter feature, the Historical Events window is filled with all eventsthat meet the specified criteria (see Figure 7-5 on the next page). Thismay take some time, depending on the size of the event database andthe filter criteria. A progress bar and percentage indicator at the bottom of the Safety Historian application window show how thefiltering process is progressing:

Figure 7-4 Progress bar

If the filtering process takes too long, you can abort it by clicking theAbort button that is located at the right side of the progress bar. Thefiltering process will then be stopped immediately, and the Historical

Events window will display all events that were found until then.This means that not all events that meet the selection criteria may bedisplayed.

Note:You can only abort the filtering process if some historical eventsare already displayed on screen.





Figure 7-5 Viewing the Historical Events

The tasks you can perform with regard to the Historical Events are:

• exporting historical events to a CSV file (see subsection 7.5.2), and

• apply a filter to select and inspect a range of historical events(see subsection 8.3 of this manual).

Presentationof events

Events are presented in table format. Each row represents an eventshown in its specific color. Each column is a property of the event.Events are presented in descending time order: the event thatoccurred last is always displayed at the top row of the window.If not all columns fit in the window, a horizontal scroll bar isdisplayed which allows you to browse through the column list. Thecolumn widths can be easily resized by dragging its edges.





Note:The date and time format used in the window depends on thesettings in the Region and Language dialog box of the

Windows Control Panel.

Event visibilityand filtering

All recorded events are stored in the event database. Whether or notan event is actually displayed in the Historical Events window can be controlled by setting its event visibility. Safety Historian also hasextensive event filtering capabilities that allow you to view only thoseevents in the Historical Events window that meet certain selectioncriteria. For details refer to section 8 of this manual

Windowcustomization

The Historical Events window layout can be customized in a numberof ways. The following customizations are possible:

• Resizing the column widths,

• Hiding certain columns,

• Rearranging the column order,

• Customizing the event colors,

• Showing or hiding the grid lines, and

• Customizing the event type names.

For details refer to subsection 9.3 of this manual.





7.5.2 Exporting Historical Events

Exporting events Historical events can be exported to a CSV compatible file format,which allows you to inspect them using any third-party tool capableof working with this database.To export (selected) historical events, do the following:

1. Choose Export Events in the Configuration & Tasks area. Thiswill open the Export Events window as shown in Figure 7-6.

Figure 7-6 Export events dialog

2. The default file name is Events.csv, located in: C:\Users\<username>\Documents. Use the Browse button to change the exportfile name and/or location.

3. Select a filter (predefined or user-defined) to limit the number ofevents to be exported. For further details on defining event filters please refer to paragraph Event Filters in Section 8 of thismanual.

4. To start exporting the events, choose the OK button in the Export

Events window.Safety Historian will now export to file all Historical events thatmeet the selected filter. At the end of the export process a messagewill be displayed indicating the number of events that have beenexported.





Notes:1. The file name will always get the extension .csv, even if you

enter a different extension.

2. Select a storage device that has sufficient free storage space.3. Overwriting an existing file is password-protected at

Maintenance level.

Export filestructure

The exported CSV file has the format as shown in the table below.The fields are of string type and do not have fixed nor maximumsizes.

Table 7-1 Structure of CSV event export file

Field Name Description

TimeStamp Time Stamp in number of milliseconds that havepassed since January 1

st

Date

1970, 00:00:00 hours.(This is used for calculation and sorting purposes.)

Date part of Time Stamp.Format is according to settings in the Region andLanguage dialog box of the Windows Control Panel.

Time Time part of Time Stamp.Format is according to settings in the Region andLanguage dialog box of the Windows Control Panel.

Point Type Point type

Tag Number Tag number

Event Type Event type

Status Message Status message

EDD Name of Event Detecting Device

Description Description of point

Unit Unit name

Subunit Subunit name

SOE ID SOE ID

Device # EDD Device numberMessage Color Color in HTML Color Format





7.5.3 Automatic Export Of Events

Exporting events Events can be exported to a CSV compatible file which allows you toinspect them using any third-party tool capable of working with thisdatabase.Automatic Export Of Events differs from Exporting Historical Events.With Automatic Export Of Events Safety Historian will periodicallyexport all

1. Choose Configuration Options in the Configuration & Tasksarea. This will open the Configuration Options window.

events (Auto-Export) according to the selected options.Event files will be stored in the auto-export folder.

2. The Configuration Options window will by default open with

the General Options screen. Now choose the Automatic Exportof Events option from the list. This will show the dialog in thewindow as shown in Figure 7-7 below:





Figure 7-7 Defining Automatic export of events

3. The default setting is Automatically Export Events unchecked.Check ‘Automatically export events’ to enable Automatic exportof events.

4. The events will be exported as a .csv file. For details on theexport file refer to Table 7-1 on page 122.

5. Choose the pattern of creating automatic exports (daily, weekly ormonthly).

With the Weekly setting (default), automatic exports are doneevery Sunday morning. Check the Daily box, or the Monthly boxif automatic exports should be done or every 24 hours, or everyfirst of the month.The export file will be created at 05:00 AM at the selected pattern.The export file will only contain events that have not beenautomatically exported before.

6. To start automatic export of events, choose the OK button in theAutomatic Export Events window. Safety Historian will now





periodically export all events (Auto-Export) according to theselected options. Event files will be stored in the Auto-exportfolder.

Notes:1. All automatically exported events are filed in the "auto-

export" folder. The "auto-export" folder is located in thefolder where Safety Historian basic or Safety Historian Network has been installed. If the "auto-export" folder is not present it will be created.

2. Automatically exported files are named"Events_<date> <time>", where <date> and <time> are dateand time of export.

3. The file name will always get the extension .csv.




130 Section 8: Visibility and Filtering of Events

Section 8 – Visibility and Filtering of Events


Section overview This section explains how event visibility can be controlled, and how

events can be filtered to display or print only those events that meetcertain selection criteria. It covers the following topics:


8.1


8.2

Event Visibility Status ........................ ......................... ........................ ....... 131

8.2.1

Introduction ............................................................................................... 131

8.2.2

At Unit/Subunit Level ......................... ......................... ........................ ....... 132

8.2.3

At Point Level ....................... ........................ ......................... .................... 134

8.2.4

Overriding the Event Visibility Status ................................ ........................ . 135

8.3 Event Filters ......................... ........................ ......................... .................... 137

8.3.1

Introduction ............................................................................................... 137

8.3.2

Defining Event Filters ........................ ......................... ........................ ....... 138

8.3.3 Specifying Filter Criteria..................... ......................... ........................ ....... 141

8.3.4 Using Event Filters ........................ ........................ ......................... ........... 144




Section 8: Visibility and Filtering of Events 131

8.2 Event Visibility Status

8.2.1 Introduction

Enabling/disablingevent visibility

All events are stored in the event database, which is located on theSafety Historian station. Whether or not an event is actually displayed

in the Incoming Events window or Historical Events window (and printed) can be controlled by setting its event visibility.

You can set the event visibility at two different levels:

At the unit and subunit level (see subsection 8.2.2), or

At the point level (see subsection 8.2.3).

Notes:1. For events to be displayed on screen and output to printer,

their visibility must be turned on at both point level andunit/subunit level. This means that if the visibility status of a

point is turned on and the corresponding unit/subunit isturned off (or vice versa), the events related to that point

will not be displayed.2. The visibility status of an event at its moment of collection

determines whether the event will be visible in the Incoming

Events window.





8.2.2 At Unit/Subunit Level

Event visibility atunit/subunit level

Event visibility can be controlled at unit/subunit level. This allowsyou to prevent events from certain units and/or subunits from being

displayed in the Incoming Events window and the Historical Events window. They will also not be printed.

Note:Please note that all events are logged in the event database,

regardless of their visibility status in the event windows.

To set the event visibility at unit/subunit level, do the following:



2. The Configuration Options window will by default open with

the General Options screen. Now choose the Event Visibility option from the list on the left of the window. This will show the

dialog in the window as shown in Figure 8-1 on the next page.





Figure 8-1 Setting the event visibility at unit/subunit level





3. The Event Visibility tab dialog has two boxes. The box on the leftlists the units that are defined in the configuration database. If a

unit is selected in the left box and this unit has subunits, then theright box shows these subunits. Each item in the left and right

boxes has a checkbox in front of it. If you want events from a unitor subunit to be displayed, make sure its checkbox is selected ( ).

In the example shown in Figure 8-1 on the previous page, SafetyHistorian will display all events from Unit 01, as well as the

events from subunits 03a and 03b of Unit 03.To show or hide all events of a subunit, first select the unit which

contains the subunit (in the left box). Then select the appropriatesubunit in the right box and check or uncheck the checkbox.

Please note that you can only select a subunit if its correspondingunit is 'visible'.

4. Choose the OK button to make the changes effective, or Cancel to abort the operation and discard any changes you made.

Note:For events to be displayed on screen and output to printer, theirvisibility must be turned on at both point level and the

corresponding unit/subunit level.

8.2.3 At Point Level

Event visibility atpoint level

Event visibility can also be controlled at point level. This allows youto prevent events from specific points from being displayed in the

Incoming Events window and the Historical Events window. Theywill also not be printed.

Note:

Please note that all events are logged in the event database,

regardless of their visibility status in the event windows.

To set the event visibility at point level, do the following:

1. Select the Points tab in the main Safety Historian applicationwindow. This will open the Points window (see Figure 5-1 insubsection 5.3.1).





2. Select the point whose event visibility you wish to edit, right clickand select Properties or double-click the point.

This will open the Point Properties window.

3. The Point Properties window has a Visible checkbox in the bottom left corner (see Figure 8-2 below). To display events

related to the selected point, make sure the Visible checkbox isselected ( ).

Figure 8-2 Setting the event visibility at point level


Note:For events to be displayed on screen and output to printer, their

visibility must be turned on at both point level and the

corresponding unit/subunit level.

8.2.4 Overriding the Event Visibility Status

Overriding theevent visibility status

If required, you can override the visibility status of events. All eventswill then be displayed on screen and printed even if the event

visibility status has been turned off (either at point level orunit/subunit level).

To override the event visibility status, do the following:


2. The Configuration Options window will by default open withthe General Options screen. Now choose the Event Visibility

option from the list on the left of the window. This will show thedialog in the window as shown in Figure 8-1 on page 133.





8.3 Event Filters

8.3.1 Introduction

Event filters All events that are recorded are stored in the event database, whichcan contain a maximum of 200,000 events. This allows historical

event data to be viewed for later analysis. It may be useful to viewonly those events in the Event History window that meet certain

criteria, e.g. from a certain unit or within a certain time frame. SafetyHistorian supports filtering of historical events in order to limit the

range of events to be viewed. There are two types of event filters:

Predefined filters, and

User-defined filters.

Predefined filters There are a number of fixed, predefined filters which allow you to

retrieve all events from a certain time period. These filters cannot beedited. The following predefined filters are available:

• All events of the current shift,

• All events of the last shift,

•

All events of the shift before last shift,• All events of the last 30 minutes,

• All events of the last 60 minutes,

• All events of the last 120 minutes, and

• All events.

User-defined filters It is also possible to define filters that are geared to specific

situations. You can specify a number of criteria that events shouldmeet to be displayed. Such user-defined filters can be saved for later

use and can be edited.

For details on defining event filters refer to subsection 8.3.2 on page138.

For details on using event filters refer to subsection 8.3.4 on page 144.





8.3.2 Defining Event Filters

Definingevent filters

You can define event filters to limit the range of historical eventsdisplayed in the Event History window.

To define event filters, do the following:


2. The Configuration Options window will by default open withthe General Options screen. Now choose the Selection Filter option from the list on the left of the window. This will show the

dialog in the window as shown in Figure 8-4.

Figure 8-4 Defining event filters





4. The Selection Filter Name box lists all the user-defined eventfilters that are available (i.e. that were defined earlier).

5. To create a new filter, choose the New button.To edit an existing filter, select the filter in the Selection Filter

Name box, and choose the Edit button. (This button will not beavailable if nothing has been selected.)





6. The Filter Criteria window will now open (see Figure 8-5 below). Here you can specify the criteria that events should meet

to be displayed in the Historical Events window. (For details onspecifying the filter criteria refer to subsection 8.3.3 on page 141).

Figure 8-5 Defining the event filter criteria

7. Once you have specified all the filter criteria, type the filter namein the Filter Name entry box, and choose the OK button. The

new filter will now be added to the selection filter list.If you were editing an existing event filter, you can choose the

OK button to make the changes effective, or you can save themodified event filter under a new name (thus creating a new

filter).





8.3.3 Specifying Filter Criteria

Specifyingfilter criteria

You can specify a number of criteria that events should meet to be

displayed in the Historical Events window. Events are onlydisplayed if they meet all specified criteria. There are basically two

types of criteria:

• Time criteria (from-to range), and

• Point criteria.

Each of these is discussed in more detail below.

Time criteria The Time box in the Filter Criteria window allows you to specifytime-related filter criteria (see Figure 8-6 below).

Figure 8-6 Time-related filter criteria

There are several options to choose from:

• Time filter,

• Predefined time filter, or

• User-defined time filter.

No time filter Select the Timestamp check box ( ) to enable event filtering basedon time criteria (i.e. select events with regard to their timestamp).

Predefined time filter Select the Predefined check box ( ) to enable event filtering basedon one of the predefined time filters. Select the predefined filter from

the drop-down list to the right of the check box.

The following predefined filters are available:

• All events of the current shift,

• All events of the last shift,

• All events of the shift before last shift,







• All events of the last 120 minutes, and

• All events.Please note that predefined time filters cannot be edited.

User-defined time filter To define your own time filter, make sure that the Timestamp check box is selected and the Predefined check box is not selected.This allows you to define the time period in which events need to

occur to be displayed. You can use the From and To fields to specifythe date/time limits.

The default date/time limit for the 'To'-field is the current date andtime (based on the local computer date), and the default for the 'From'-

field is one hour before the current time.

Notes:1. Since the current date and time are based on the local

computer date and time, you should make sure they are setcorrectly. Otherwise the default date and time shown will beincorrect.

2. The date and time format depends on the settings in theRegion and Language dialog box of the Windows Control

Panel.

Setting the date You can manually enter a date (make sure you use the correct

format), or you can click on the drop-down arrow to the right of thedate entry box. This will display a calendar that you can use to select

the 'From'-date (see Figure 8-7 below).

Figure 8-7 Using the calendar

There are a number of ways to select the date you want:

If you click the symbol, the current date is selected (based on the

local computer date).

You can use the and buttons to browse through months.





If you click the month/year in the window title, a drop-down list willappear which you can use to choose a month.

If you then click the year indication in the window title, you canchoose from a number of displayed years or first browse through

other sets of years by using the and buttons.

Note:Since the current date is based on the local computer date, you

should make sure it is set correctly.

Setting the time You can manually enter a time (hours, minutes, seconds) (make sure

you use the correct format), or you can select either the hour, minuteor second counter and then use the spin buttons to increment ordecrement the selected counter.

Note:

Since the current time is based on the local computer time, youshould make sure it is set correctly. Otherwise the default time

will be incorrect.

Point criteria In addition to time-related criteria, you can also specify Point-related

filter criteria (see Figure 8-8 below). You can define which EDD(s)and/or unit(s) and/or subunit(s) the events should relate to. In

addition, you can make selections based on the point type and/or tagnumber.

For the tag number field you may use a wildcard '*'. For example, if

you want to filter events for all points whose tag number starts with'ABC', you should specify the filter as 'ABC*'. Omitting the '*' would

only select events from points with the exact tag number 'ABC'.





Figure 8-8 Point filter criteria

Notes:1. You can only choose subunits if their related units are

selected.2. The subunits in the displayed list include references to their

corresponding units.

8.3.4 Using Event Filters

Using event filters There are basically two ways to view historical event data using an

event filter:

• Selecting a predefined filter (either a standard or user-defined

filter) with the filter drop-down box at the top of the

Historical Events window (long rectangle in Figure 8-9).

Clicking the Apply Filter (F5) button starts the filtering process;

• Using the Custom filter… button at the top of the Historical

Events window (Figure 8-9).It is used to define a new filter that is only to be used once and

thus does not have to be saved (ad hoc filter).After clicking the button a Filter Criteria dialog appears to

define the quick filter. Closing the dialog with the OK buttonstarts the filtering process.





Figure 8-9 Filter controls in Historical Events window.

Further details on:

• specifying the filter criteria: refer to subsection 8.3 Event Filters;

• using event filters: refer to subsection 7.5.1 Viewing and

Filtering Historical Events.




146 Section 9: Customizing Window Layouts

Section 9 – Customizing Window Layouts


Section overview This section explains how to customize the appearance of the variousSafety Historian windows. It covers the following topics:


9.1


9.2

Customizing the Points Window...................................... ........................ ... 147

9.2.1

Introduction ............................................................................................... 147

9.2.2

Resizing the Column Width..................................... ......................... .......... 147

9.2.3

Hiding and Showing Columns ..................... ......................... ...................... 148

9.2.4

Rearranging the Column Order ....................... ......................... .................. 151

9.2.5

Setting the Default Status Messages .................................... ..................... 151

9.3

Customizing the Event Windows ...................... ........................ .................. 155

9.3.1

Introduction ............................................................................................... 155

9.3.2


9.3.3 Hiding and Showing Columns ..................... ......................... ...................... 156

9.3.4 Rearranging the Column Order ....................... ......................... .................. 159

9.3.5

Customizing the default Event Colors ................................... ..................... 160

9.3.6 Showing or Hiding the Grid Lines ......................... ........................ .............. 164

9.3.7 Customizing the Event Type Names ......................... ........................ ......... 165

9.4

Customizing the Log & Error Messages Window ........................ ................ 167

9.4.1

Introduction ............................................................................................... 167

9.4.2


Windowcustomization

The appearance of the following Safety Historian windows can becustomized by the user:

• the Points window (see subsection 9.2),

• the Incoming Events window (see subsection 9.3),

• the Historical Events window (see subsection 9.3), and

•

the Log & Error Messages window (see subsection 9.4).




Section 9: Customizing Window Layouts 147

9.2 Customizing the Points Window

9.2.1 Introduction

Points window The point properties are displayed in the Points window (see Figure5-1 in subsection 5.3.1). Each row represents a point and each property uses a separate column.The following customizations are possible in this window:

• Resizing the column widths (see subsection 9.2.2 on page 147),

• Hiding and showing columns (see subsection 9.2.3 on page 148),

• Rearranging the column order (see subsection 9.2.4 on page 148),and

• Setting the default status messages (see subsection 9.2.5 on page 151).

9.2.2 Resizing the Column Width

Resizingthe column widths

The width of a column can be easily resized by dragging the edges ofthe column header to the desired width. Please note that only the rightedge of a column can be dragged (see Figure 9-1 below).

Figure 9-1 Dragging column widths





9.2.3 Hiding and Showing Columns

Hiding/showingcolumns

By default, a total of sixteen attributes are shown for each point (i.e.sixteen columns). It may be useful to hide certain columns, e.g. inorder to prevent a "cluttered" display.To define which columns are shown in the Points window, do thefollowing:


2. The Configuration Options window will by default open withthe General Options screen. Now choose the Column Layout

option from the list on the left of the window. This will show thedialog in the window as shown in Figure 9-2.

3. In the Select Display drop-down list, select the Points option (asshown in Figure 9-2).





Figure 9-2 Defining the layout of the Points window





4. Two boxes will now appear. The box on the right lists thecolumns (i.e. point attributes) that are displayed in the Points

window, and the box on the left those that are not. In the exampleshown in Figure 9-2, the attribute Subunit is hidden.

6. To hide a column, select the appropriate column in the right box,and choose the < button. The column name will be moved fromthe right to the left box, and the point attribute will no longer bedisplayed in the Points window.To display a column, select the appropriate column in the left box,and choose the > button. The column name will be moved fromthe left to the right box, and the point attribute will be displayedagain in the Points window.

Notes:

1. You can select multiple list items by holding down theCTRL key while selecting them.To select a group of items that are next to each other,hold down the SHIFT key and click the first and last listitem you want to select.

2. Items that are moved from the left to the right box arealways added to the bottom of the list, and will therefore be displayed as the rightmost column on screen. Fordetails on rearranging the column order refer tosubsection 9.2.4 below.)

3. To remove or add all columns, choose the << or >>

button, respectively.






9.2.4 Rearranging the Column Order

Rearrangingthe column order

By default, all columns (point properties) are shown in a particularorder. It may be useful to change the order of the columns.To change the column order, do the following:



option from the list on the left of the window. This will show thedialog in the window as shown in Figure 9-2.

3. In the Select Display drop-down list, select the Points option (asshown in Figure 9-2 on page 149).

4. Two boxes will now appear. The box on the right lists thecolumns (i.e. point attributes) that are displayed in the Points window, in left-to-right order (i.e. the topmost item in the list isshown as the leftmost column on screen, etc.).

6. To change the column order, select the item from the Displayed

Columns box you wish to move, and use the Up and Down buttons to rearrange its position in the column list.

7. After you are done, choose the OK button to make the changeseffective, or Cancel to abort the operation and discard anychanges you made.

9.2.5 Setting the Default Status Messages

Default statusmessages

When you add a new point to the configuration, its status message properties are set to their default values. These defaults can becustomized. To edit the default status messages, do the following:


area. This will open the Configuration Options window.2. The Configuration Options window will by default open with

the General Options screen. Now choose the Customize Display

of Events option from the list on the left of the window. This willshow the dialog in the window as shown in Figure 9-3.

3. Choose the tab with the event type of which you wish to set theDefault Status Message. Figure 9-3 shows the Point Value tab.





4. You can freely edit any of the fields. Some fields on some tabsshow a $-variable, for details on these variables refer to page 153.






Figure 9-3 Setting the default status messages (combined withcustomizing event colors and Event type names)

$-variables Some Event Types can contain $-variables in their Default StatusMessage field. In the Status message displayed in one of the eventwindows, this $-variable will be replaced by a numerical value:

• Report event type, Report message

SM controllers

Not applicable for SM controllers.





FSC controllers

o $N: current value of a certain BO point.

• Diagnostic event type

For diagnostic events, the Default Status Message can hold areference with $-variables to the physical location in the devicewhere the diagnostic refers toIt is not required to use any or all of the $-variables in thediagnostic status message.

SM controllers

o $N: Controller number,

o $C: Chassis number,

o $S: Slot number.

The same $-variables are used for:

FSC controllers

o $N: System number,

o $C: Rack number,

o $S: Position number.

• Remote IO Diagnostic event type

The status message for these is like the message for Diagnostic event types with the exception that different $-variables areused:

SM controllers

o N: RUSIO Network,

o I: IOTA Address,

o S: Slot number.

FSC controllers

Not applicable for FSC controllers.





9.3 Customizing the Event Windows

9.3.1 Introduction

Events windows The appearance of the Safety Historian event windows (i.e. Incoming

Events window and Historical Events window) is user-definable.The following customizations are possible in these windows:


• Hiding and showing columns (see subsection 9.3.3 on page 156),

• Rearranging the column order (see subsection 9.3.4 on page 159),

• Customizing the event colors (see subsection 9.3.5 on page 160),

• Showing or hiding grid lines (see subsection 9.3.6 on page 164), and

• Customizing the event type names (see subsection 9.3.7 on page 165).


Resizingthe column widths The width of a column can be easily resized by dragging the edges ofthe column header to the desired width. Please note that only the rightedge of a column can be dragged (see Figure 9-4 below).






9.3.3 Hiding and Showing Columns

Hiding/showingcolumns

By default, a total of ten attributes are shown for each event (i.e. tencolumns). It may be useful to hide certain columns, e.g. in order to prevent a "cluttered" display.To define which columns are shown in the event windows, do thefollowing:


2. The Configuration Options window will by default open with theGeneral Options screen. Now choose the Column Layout optionfrom the list on the left of the window. This will show the dialogin the window as shown in Figure 9-5.

3. In the Select Display drop-down list, select the Incoming Events & Historical Events option (see Figure 9-5).





Figure 9-5 Defining the layout of the events windows





4. Two boxes will now appear. The box on the right lists the columns(i.e. event attributes) that are displayed in the selected eventwindow, and the box on the left those that are not. In the exampleshown in Figure 9-5, the attribute Subunit is hidden.

6. To hide a column, select the appropriate column in the right box,and choose the < button. The column name will be moved fromthe right to the left box, and the event attribute will no longer bedisplayed in the selected event window.To display a column, select the appropriate column in the left box,and choose the > button. The column name will be moved fromthe left to the right box, and the event attribute will be displayedagain in the selected event window.

Notes:

1. You can select multiple list items by holding down theCTRL key while selecting them.To select a group of items that are next to each other, holddown the SHIFT key and click the first and last list item youwant to select.

2. Items that are moved from the left to the right box arealways added to the bottom of the list, and will therefore bedisplayed as the rightmost column on screen. For details onrearranging the column order refer to subsection 9.3.4 below.)

3. To remove or add all columns, choose the << or >> button,

respectively.






9.3.4 Rearranging the Column Order

Rearrangingthe column order

By default, all columns (event properties) are shown in a particularorder. It may be useful to change the order of the columns.To change the column order, do the following:



option from the list on the left of the window.

3. In the Select Display drop-down list, select the Incoming Events &Historical Events option.

4. Two boxes will now appear. The box on the right lists thecolumns (i.e. event attributes) that are displayed in the selectedevent window, in left-to-right order (i.e. the topmost item in thelist is shown as the leftmost column on screen, etc.).

6. To change the column order, select the item from the Displayed

Columns box you wish to move, and use the Up and Down buttons to rearrange its position in the column list.

7. After you are done, choose the OK button to make the changeseffective, or Cancel to abort the operation and discard anychanges you made.





State of the EDD

All Forces Cleared*

indicates that all current forces have been released,

SOE Buffer Full*

indicates that the event buffer has reached itsmaximum number of events,

EDD System Fault*,

• Diagnostic

indicates that a diagnostic error on an EDD or an EDD’s local IOmodule has been detected , and

• Remote IO Diagnostic

indicates that a diagnostic error on an EDD’s remote module has

been detected

*Note: Only FSC uses a Report event for this EDD state, other

controllers use a Point Value (Boolean High/Low) event.

Setting

the colors

To set the colors of the events displayed in the Incoming Events

window and Historical Events window, do the following:1. Choose Configuration Options in the Configuration & Tasks


2. The Configuration Options window will by default open withthe General Options screen. Now choose the Customize Display

of Events option from the list on the left of the window. This willshow the dialog in the window as shown in Figure 9-6.

3. Select the tab of the event type, , and click at the Color button ofthe desired Default Status Message. The color selection windowwill appear (see Figure 9-7 on the next page).

4. Choose one of the 48 basic colors, or define your own color.5. Choose the OK button to make the changes effective, or Cancel

to abort the operation and discard any changes you made.

6. By selecting the Override per tag coloring option, the defaultcolors will override the coloring per tag (see paragraph Coloring

per Tag below).(this only applies to new incoming events)





Figure 9-6 Customizing event colors in the event windows (combined withEvent type names and Status Messages)





Figure 9-7 Selecting a color

Coloring per Tag If required, customized colors can be defined per event for each point(see paragraph 5.3.2 Point Properties) in the Incoming Events window and Historical Events window. This is called 'Per TagColoring'. To activate this specific coloring per point, make sure thatthe Override per Tag Coloring checkbox in the dialog as shown inFigure 9-6 is de-selected.Selecting the Override per tag coloring checkbox will activate thedefault colors as defined with the Customize Display of Events

dialogs.





Figure 9-9 Showing or hiding the grid lines

9.3.7 Customizing the Event Type Names

Event type names The names of the events displayed in the Safety Historian eventwindow are user-definable. These event types will appear in the eventmessages displayed by Safety Historian.To set the names of the event types displayed in the Incoming Events window and Historical Events window, do the following:


2. The Configuration Options window will by default open withthe General Options screen. Now choose the Customize Display

of Events option from the list on the left of the window. This willshow the dialog in the window as shown in Figure 9-6 on page162.

3. Select the tab of the desired event type. You can now edit thename of the selected event type. The maximum number of





characters allowed for each event type name is 20. The next timean event occurs, the event type of the event message will containthe new name. Also, all event messages that contain the 'old' namewill automatically be modified to match the new event type name.






9.4 Customizing the Log & Error Messages Window

9.4.1 Introduction

Log & ErrorMessages window

If any errors occur, they are displayed in the Log & Error Messages window (see figure 7-10 on page 129). Each row represents an errorwhile two columns are used: one for the date and time and one forthe message description.The following customization is possible in this window:



Resizingthe column widths

The width of a column can be easily resized by dragging the edges ofthe column header to the desired width. Please note that only the rightedge of a column can be dragged (see Figure 9-10 below).





168 Section 10: Program Maintenance

Section 10 – Program Maintenance


Section overview This section explains how to perform a number of general

maintenance tasks. It covers the following topics:


10.1


10.2

Program Maintenance and Customization Overview ....................... ........... 169

10.3

Setting the Daylight Saving Time ......................... ........................ .............. 171

10.4

Defining Work Shifts ...................... ........................ ......................... ........... 173

10.5

Time Synchronization of Event Detecting Devices ..................................... 174

10.6 Backing Up the Configuration ..................... ......................... ...................... 177

10.7

Restoring the Configuration ............................................. ........................ .. 179

10.8 Password Maintenance ..................... ......................... ........................ ....... 181




Section 10: Program Maintenance 169

10.2 Program Maintenance and Customization Overview

Programmaintenanceoptions

Safety Historian can be customized in a number of ways to suit your

specific needs. Table 10-1 below lists the program maintenance andcustomization options that are possible.

Table 10-1 Safety Historian maintenance and customization options

Customizationcategory

Customization itemSelection in Configuration

& Tasks areaFor detailsrefer to...

General

Setting daylight saving time

Configuration Options

Subsection 10.3

Defining work shifts Subsection 10.4

Activating time synchronization of SM/FSC controllers Subsection 10.5

Showing or hiding the grid lines in the Safety Historian eventwindows

Subsection 9.3.6

Event VisibilityDefining the event visibility perunit/subunit

Configuration Options Subsection 8.2.2

CustomizeDisplay of

Events

Setting the Default StatusMessages for points

Configuration Options

Subsection 9.2.5

Setting the Event Type names Subsection 9.3.7

Defining the colors of theevents displayed in the eventwindows

Subsection 9.3.5

Column LayoutDefining the column layout ofthe event windows and errorwindow

Configuration OptionsSubsections

9.2.3, 9.3.3, 9.4.3

Event Filters

Defining event filters to limit therange of historical eventsdisplayed in the Historical Eventswindow

Configuration Options Subsection 8.3

Working withbackups

Making a backup of the

configuration database Back up / Restore

Subsection 10.6

Restoring a backup of theconfiguration database

Subsection 10.7

Passwordmaintenance

Modifying the passwords thatprotect certain Safety Historianoptions

Configuration Options Subsection 10.8





Passwordprotection

Most of the maintenance and customization options listed in Table

10-1 on the previous page are password-protected.

Options /Configuration

Entering the Configuration Options window (Configuration &Tasks area) is password-protected at Maintenance level. When the

Configuration Options window appears you can modify all optionswithout having to enter any password again.

If you enter an incorrect password or no password at all, and youchoose the OK button (or press the E NTER key), an error message will

appear saying you entered an incorrect password.If you do not enter any password and choose the Cancel button (or

press the ESCAPE key), no error message is displayed and theConfiguration Options window will appear nonetheless. However,

the following three options that require the Maintenance authorization

level will be disabled:• Changing the maximum size of the event database,

• Overriding the event visibility, and

• Enable time synchronization of SM/FSC controller.

Also, if you want to change the default status messages for points, youwill be prompted to enter the Operator password.

All other configuration items do not require password authorization,and can therefore be modified as you please.

Backing up the

configuration database

Backing up the configuration database as such is not password-

protected, but overwriting an existing backup file requiresauthorization level Maintenance.

Restoring theconfiguration database

Restoring a configuration database is password-protected at

Maintenance level.

Changing passwords Changing passwords is password-protected at Supervisor level.





10.3 Setting the Daylight Saving Time

Setting daylightsaving time Safety Historian supports daylight saving time.

To set the daylight saving time, do the following:


2. The Configuration Options window will by default open withthe General Options screen that contains the dialog for setting thedaylight saving time, see Figure 10-1.

3. Use the fields in the Daylight Saving Time box to define the startand end date and time of the period in which daylight saving timeshould be observed.






Figure 10-1 General program options

Using daylightsaving time

If at least one of the configured Event Detecting Devices uses a DCFsignal for event time stamping (usually an FSC controller), then you

should use daylight saving time in Safety Historian. This will ensurethat the time stamps of events displayed in the event windows

(Incoming Events and Historical Events) reflect daylight savingtime correctly, and that event selections produce the correct results.

Notes:

1. If none of the configured EDDs uses a DCF signal, then thisoption is not applicable.2. It is essential that the daylight saving time period as specified

in Safety Historian is the same as the time period as defined by the DCF signal. If these time periods do not match, there

may be a discrepancy between the events that you expect to

see and the ones that are actually displayed.





10.4 Defining Work Shifts

Definingwork shifts Safety Historian can show the events that were recorded duringearlier shifts. For that to be done correctly, you need to specify thecharacteristics of the shifts. To set the work shifts, do the following:


2. The Configuration Options window will by default open withthe General Options screen that contains the dialog for setting thework shifts, see Figure 10-1.

3. Specify when the first shift starts in the Start Time field. In theNumber of shifts per day field, specify how many shifts thereare per day (24 hours). Safety Historian will then calculate

automatically when each shift starts and ends. In the exampleshown in Figure 10-1, there are three shifts. The first shift is from

6:00 am to 2:00 pm, the second from 2:00 pm to 10:00 pm, andthe third from 10:00 pm to 6:00 am.






10.5 Time Synchronization of Event Detecting Devices

Timesynchronization Safety Historian can synchronize the date and time of all connectedEvent Detecting Devices (e.g. SM/FSC controllers) to the system dateand time of the Safety Historian station.

Please note that the sources of time synchronization of SM/FSC

controllers are prioritized.Only if no higher priority time source is available or configured will

the SM/FSC controller accept time synchronization commands fromthe Safety Historian station.

If time synchronization of SM/FSC controllers has been activated,

Safety Historian sends the system date and time of the SafetyHistorian station to all connected SM/FSC controllers at startup of

Safety Historian and once every hour. If no other higher prioritysource of time synchronization is available or configured, the SM/FSC

controllers will then use this information to synchronize their real-time clocks.

Regarding SM:

An SM controller uses a configurable priority of its sources of timesynchronization.

Normally a DCF-77 time source would get the highest priority;Safenet or PTP or NTP or any DCS the second highest and Safety

Historian the lowest.

To configure the sources of time synchronization and their priority please refer to:

Safety Manager Software Reference (EP-SM.MAN.6285),Safety Builder configuration tools, sub section: ‘SM Controller

properties (physical) - tab: Clock Source’.

Regarding FSC: An FSC controller uses a fixed priority for its sources of time

synchronization.A DCF-77 time source will always have the highest priority, any DCS

the second highest and Safety Historian will always have the lowest.For more information on time synchronization please refer to:

FSC Software Manual (FS80-xxx*),Appendix ‘F.13 Real-Time Clock Synchronization’.

* 'xxx' is the release number. For example, the Software Manual for FSC R700 is referenced

as FS80-700





Note:The current date and time sent by Safety Historian are based onthe date and time of the PC where Safety Historian is running at,

you should make sure that the PC date and time are set

correctly!

Activating timesynchronization To activate time synchronization via Safety Historian, do the

following:


2. The Configuration Options window will by default open withthe General Options screen that contains the dialog for activate

time synchronization, see Figure 10-1. 3. Make sure the Enable time synchronization of Event Detecting

Devices checkbox is selected ( ). Safety Historian will now issuetime synchronization commands at startup of Safety Historian

and once every hour. Please note that the SM/FSC controllerswill only use these commands if no other source of time

synchronization is available.

For more information on (configuring) sources of timesynchronization please refer to the previous paragraph.

Timesynchronization inEthernet networks

All computers in an Ethernet-based SOE network can be configuredto use a time synchronization command to receive the date and time

from a designated time source. You can use the site server or anyother designated computer as the time source by using the following

command:

net time \\[computername] /set /y

The time synchronization command can be placed in a logon script so

that it can be activated each time a user logs on.One of the problems with synchronizing the time on Windows Server

computers is that these computers can often go for weeks or evenmonths at a time without anyone logging on to them. Windows

computers include an optional service called the Scheduler, which can be configured to start specified commands at a predetermined time.

One of the things you can do with the Scheduler is to configure it torun the time synchronization command on a regular basis by creating





a repeating task. For details on how to create a Scheduler script(*.cmd) refer to the Windows documentation.





10.6 Backing Up the Configuration

Backing up theconfiguration

To prevent data loss in case of system failure it is advised to back upthe configuration database after modifications have been made to the

configuration.Backups should be made to a drive that is located at another storage

device or another PC, since otherwise a system failure could alsodestroy a backup.

The backup function of Safety Historian creates a .shb (SafetyHistorian Backup) file which contains the point properties and

network configuration. If required, the configuration data can bereconstructed using the restore function (see page 179).

To make a backup, do the following:

1. Choose Back up or Restore in the Configuration & Tasks area.This will show the dialog window as shown in Figure 10-2 (with

having the tab Back up Configuration opened).

2. Choose the button Select File Name. This will open the window

as shown in Figure 10-3 below.

Figure 10-2 Backing up the configuration





Figure 10-3 Specify and locate Backup File Name dialog

3. Specify the backup file name (or accept the suggested name) andselect the drive and directory where the file should be saved.

Remember to choose a drive that is located at another storage

device or another PC!

4. Choose the Save button. Now the backup dialog window (Figure10-2) will return to allow you to enter an optional description of

the backup.5. Choose the Back up button to start the actual backing up process.

A bar will indicate the backing up progress .

Notes:1. The file name will always get the extension .shb, even if you

enter a different extension.2. Remember to select a drive that has sufficient free disk

space and located at least at another storage device or better yet, at another PC..

3. Overwriting an existing file is password-protected at

Maintenance level.





Figure 10-5 Locate and select Backup File dialog

2. Locate and select or specify the file name of the backup file whichshould be restored.

3. Choose the Open button. Now the backup dialog window (Figure10-4) will return to allow you to enter an optional description of

the restore operation.

4.

Choose the Restore button to start the actual restore process. A

bar will indicate the backing up progress.

Notes:1. Restoring the configuration is only possible if the

Configuration database was backed up using the currentSafety Historian version. For example, you should not

restore a Configuration database of Safety Historian R200.1into (a future release of) Safety Historian R210.

2. Restoring a Configuration database is password-protected at

Maintenance level.





10.8 Password Maintenance

Passwords Some functions of the Safety Historian application are password-

protected. This means that they can only be accessed if the user hasthe correct authorization level. There are four authorization levels in

total: Operator, Maintenance, Architect and Supervisor. For details onthe use of passwords refer to section 3.10.

The password for each authorization level can be modified. Changing passwords requires the authorization level Supervisor. As a minimum,

you should change the default passwords in order to get any protectionat all. To change a password, choose the Change Passwords option

from the Configuration Options menu. The Supervisor needs toauthorize by clicking the lock symbol in the lower left corner of the

dialog. This will show a password entry dialog in order to verify theSupervisor status of the user. If the correct password is entered, the

following window will appear:





Figure 10-6 Passwords window

To change a password, you must first select the desired authorization

level (Authorization Role). Next, type twice the new password. Tocomplete the change of password, click the Change Password button.

You can close the window and return to the main application window by choosing the Close button. (If you choose the Close button without

clicking the Change Password button first, any changes you madewill be discarded.)

If the password change is completed successfully, the program will

return to the initial state of the Passwords window (see Figure 10-6).

A number of errors may occur:

• You have entered the wrong old password.

• You have entered an invalid new password.

• You have entered another role’s existing password.

• You have entered the new password twice, but these do not match.

If any of these situations occur, an error message will be displayed.





A valid password is either:

• empty (i.e. no password) or,

• consists of at least four characters and

• is not already used by one of the other roles.

Please note that Safety Historian passwords are case-sensitive (i.e. the

password 'sample' differs from the password 'SAMPLE' or 'Sample').






.




184 Appendix A: Error Messages during Software Installation

Appendix A – Error Messages during Software Installation

Error messagesduring Setup

This appendix describes the error messages that may appear while

installing the Safety Historian software on your system.If you install the network option, a number of specific network-related

error messages may appear. These are described in Appendix A of thedocument FS51-200.1 ("Safety Historian R200.1 – Network Option").

Safety Historian requires Windows <version>. Setup will be

aborted.This message appears if you attempt to install Safety Historian on a

PC that runs a Windows version other than the one that is

prescribed at section 2.2 ‘Requirements’. The setup process will beterminated.

You cannot install server and client in the same directory.This message appears if you attempt to install the Safety Historian

client, server or basic version into the same directory, which is notallowed. You must install them into different directories.

The server package can only be installed on top of another server package, and the client package on top of another client package.




Appendix A: Error Messages during Software Installation 185





186 Appendix B: Troubleshooting

Appendix B – Troubleshooting

Error Messages

Error messages Table B-1 below describes the error messages that may appear in theErrors window, and how they can be solved. The error messages are

listed in alphabetical order.

Table B-1 Error messages and their solutions

Issue / Error Message Solutions

No connections at all can be madebetween a SM/FSC controller and SafetyHistorian server.

Check if the following TCP-port numbersare opened in the firewall at the switches that are in between an SM/FSC controllerand the Safety Historian station:51000.

Cannot access database. • Close any applications that are open.

• Quit Safety Historian and restart PC.

Communication device already open. • Close any applications that are open.


Communication device cannot be closed. • Close any applications that are open.


Communication device in use by anotherapplication.

• Close any applications that are open.


Communication device not open. • Close any applications that are open.


Low disk space (warning from Windows). • Free hard disk space by removingunnecessary files from the hard disk.

System did not respond. • Check cabling.

• Check SM/FSC controllercommunication settings (see alsosection 2.3 of this manual).

Unknown communication error. • Check cabling.

• Check baud rate settings.

• Check protocol settings in SM/FSCcontroller.




Appendix B: Troubleshooting 187



READER COMMENTS

Honeywell Safety Management Systems welcomes your comments and suggestions to improve future editions of this

and other documents.

You can communicate your thoughts to us by fax or mail using this form, or by sending an e-mail message. We wouldlike to acknowledge your comments — please include your complete name, address and telephone number.

BY FAX: Use this form and fax to us at +31 (0)73-6219125 (attn. Worldwide Marketing dept.)

BY E-MAIL: Send an e-mail message to [email protected]

BY MAIL: Use this form and mail to us at:Honeywell Safety Management Systems

Attn. Worldwide Marketing DepartmentP.O. Box 1165201 AC 's-HertogenboschThe Netherlands

Title of Document: Safety Manager Issue Date: 12/2013Safety Historian R200.1 (Basic Version)Revision 01

Document Number: SH50-200.1 Writer: HSMS Product Marketing

COMMENTS:

RECOMMENDATIONS:

Name: Date:

Position:

Company:

Address:

Country:

Telephone: Fax:

E-mail address:



.