PI System Architecture, Planning and Implementation Workbook
Comments
Description
PI System Architecture, Planning andImplementation Version 2010 PI System Basics OSIsoft, LLC 777 Davis St., Suite 250 San Leandro, CA 94577 USA Tel: (01) 510-297-5800 Fax: (01) 510-357-8136 Web: http://learning.osisoft.com OSIsoft Australia P/L• Sydney, Australia OSIsoft Europe GmbH • Frankfurt, Germany OSIsoft Asia Pte Ltd. • Singapore OSIsoft Canada ULC • Montreal & Calgary, Canada OSIsoft, LLC Representative Office • Shanghai, People’s Republic of China OSIsoft Japan KK • Tokyo, Japan OSIsoft Mexico S. De R.L. De C.V. • Mexico City, Mexico OSIsoft do Brasil Sistemas Ltda. • Sao Paulo, Brazil OSIsoft France EURL • Paris, France Copyright: © 1992-2012 OSIsoft, LLC. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, mechanical, photocopying, recording, or otherwise, without the prior written permission of OSIsoft, LLC. OSIsoft, the OSIsoft logo and logotype, PI Analytics, PI ProcessBook, PI DataLink, ProcessPoint, PI Asset Framework (PI AF), IT Monitor, MCN Health Monitor, PI System, PI ActiveView, PI ACE, PI AlarmView, PI BatchView, PI Data Services, PI Event Frames, PI Manual Logger, PI ProfileView, PI WebParts, ProTRAQ, RLINK, RtAnalytics, RtBaseline, RtPortal, RtPM, RtReports and RtWebParts are all trademarks of OSIsoft, LLC. All other trademarks or trade names used herein are the property of their respective owners. U.S. GOVERNMENT RIGHTS Use, duplication or disclosure by the U.S. Government is subject to restrictions set forth in the OSIsoft, LLC license agreement and as provided in DFARS 227.7202, DFARS 252.227-7013, FAR 12.212, FAR 52.227, as applicable. OSIsoft, LLC. Page 1 PI System Architecture, Planning and Implementation Table of Contents 1. PI System Basics................................................................................................. 9 1.1 Course structure ........................................................................................ 9 1.2 Why PI? (What problem are you trying to solve?)................................... 9 1.3 What is a PI System? ............................................................................... 10 1.4 Assets and PI Points – The Basic Building Blocks in the PI System .... 12 1.5 Directed Exercise – Assets Defined ........................................................ 13 1.6 Directed Exercise – Data Types .............................................................. 15 1.7 Data Flow through the PI Server ............................................................. 16 1.8 Data Flow: From The Source To The PI Archives................................... 18 1.9 Data Flow: Block Diagram From Interface To PI Server ......................... 19 1.10 Data Flow on the Interface Computers.................................................... 20 1.11 Reporting by Exception ........................................................................... 20 1.12 Directed Exercise – PI Snapshot Values................................................. 22 1.13 Snapshot .................................................................................................. 24 1.14 Compression............................................................................................ 24 1.15 Cumulative Impact and Defaults ............................................................. 26 2. PI System Environment Architecture ............................................................... 28 2.1 What is PI? ............................................................................................... 28 2.3 Group Exercise – Categorize Your Users ............................................... 30 2.4 Data Sources............................................................................................ 31 2.5 Interface Computers ................................................................................ 31 2.6 Parts is Parts............................................................................................ 32 2.7 Group Exercise – Discover the PI System .............................................. 32 2.8 PI Server + AF Server = PI System .......................................................... 34 2.9 Back to the Data - What Do Your Users Require? .................................. 36 2.10 Group Exercise – Know Your Users, Their Data..................................... 37 2.11 Combining Different Types Of Data ........................................................ 38 2.12 Directed Activity – Viewing Your Data .................................................... 40 2.13 Directed Activity – Critical Data .............................................................. 42 2.14 Group Questions...................................................................................... 43 3. Page 2 PI Server Requirements .................................................................................... 44 3.1 Minimum Operating System .................................................................... 44 3.2 Prerequisite Kits ...................................................................................... 44 3.3 Hardware Sizing ....................................................................................... 46 3.4 Virtualization ............................................................................................ 47 81 7...8 Solo / Group Exercise – Install the PI Server ......................................................................5 Group Exercise ....................................2 Interface Failover .................... 70 6.................................................... 49 4.......................PI System Basics 4............................................................................................. 71 6.............................9 Directed Exercise – Explore the PI Server Directory Structure ................................4 Gathering........................ 6.................3 Directed Exercise – More PI SMT Plug-ins............................4 Time and the PI Server..................................................................................................................................9 Find Points using Tag Search .......2 Directed Exercise – Connect to a PI Server ........ 73 7.......................................1 Pre-installation Checks................. 55 PI System Combinations... 63 6............................... 49 4...........10 Directed Exercise – Point Search..................1 PI Server High Availability .................................................................................. 82 7. 5.......... 52 4......... PI System Navigation ..........3 PI Server Installation.................................................................................. 57 5.....8 Group Recap Questions ................................................. 57 5.....4 Group Questions –Planning and Preparation Stages: Wrap Up ................................................... 53 4... 66 6.................................... 67 6..........6 Directed Activity –PI ProcessBook ...............................7 Solo / Group Exercise – Install the PI AF Server ....... 49 4................6 Directed Activity – Active Directory Roles..7 Daylight Savings Time ............7 What about Ports? ........An Exploration of the PI Server Subsystems .................1 PI System Navigation basics ........3 Routing Time-Series Data through a Firewall ........ 83 7......................................................... PI System Planning ......................................................................................................................8 Calculation Options ........5 Directed Activity – Viewing Your Data ......... 59 5............... 82 7........................ 78 7................... 87 7. 64 6............................... 65 6..................................................................... 90 Page 3 ........................... 51 4...................................................... 50 4.............................2 License File Activation ........................... 68 6................1 A Simple PI System....... 69 6.................3 When You Need To Bet Your Business On PI.................................................. 62 Installing the Servers ............ 78 7.................6 Solo / Group Exercise – Explore the AF documentation................................................. 63 6...................................................... 84 7........................................4 Security Part 1: Planning ........HA Step 1: Planning and Hardware ...............5 Securing the Environment and the Server...................... 88 7...................................... 54 4..........................................2 Adding components as needed............. 58 5.......................................................................10 Solo / Group Exercise ............................................. 79 7................................................. ................................................2 What is OPC? ....................................6 Managing PI Users.................... 94 7........ 125 10............................... 93 7............ 10............. 95 7.......................... 123 10........................................................................... 131 10............. 135 11..................8 Working on the PI Server...... 131 10....... 9........................7 Exercise – Create IO Rate Tags (Optional/Time permitted)...................5 PI Tag Configurator.......................................................................................... 108 8.... 114 9........ 109 8.................3 Directed Activity – Preparing to Install the OPC Interface ................. 107 8..............................15 Solo / Group Exercise – Manage Archives .......................................... 100 7..2 Point Edits Timing..... 124 10................................. 111 Creating and Managing Points ...................7 PI Trust .......................................................PI System Architecture............9 The Database Security Table..................1 PI Point Attributes and Interfaces ...................................................... 136 Page 4 ......... 119 9.......................................... 107 8........ 101 7......... 127 10.......... Planning and Implementation 7.................................... 132 11.................. 120 PI Security ................12 What is the Event Queue? .......... 96 7.................................................................. 103 8.......................................... Understanding the Common Setup of PI Interfaces . 117 9................ Installing and Configuring an OPC Interface .........................................................................13 Directed Activity – Examine the Event Queue ............10 The “Security Slider” ........................................................ 102 7..16 The AF Link Mechanism......................................2 PI Firewall ...................... 122 10......................................1 The Interface Defined......................................................... 128 10........... 116 9...................................... 133 11.................................................... 113 9........................................................11 Exercise – Data Section in the PI System Management Tools................................................. 129 10.....3 The PI License Subsystem ......................................................... PI Groups and PI Identities and Mappings.......................................................................1 The PI Server Conundrum ............................3 Digital State Sets........... 112 9..............................................................2 Directed Activity – What’s Installed ................4 Exercise – Create a Digital State Set / Point ............................... Advise and Event Points.......................................... 133 11............ 114 9..........................................................3 Interface Installation Considerations .....18 Common Tuning Parameters.............................14 PI Archives Defined ............................. 125 10.............6 Exercise – PI Tag Configurator ................................1 A Word About Polling.........................................5 Granting Access .............................4 Connection Logic.....17 Directed Activity – Validate the PI AFLink Mechanism ................................................... ..4 Directed Activity – Interface Syntax Dissected......................................... .....5 Directed Activity – HA Pre-Installation Concerns....6 Pre-Installation Concerns .. 173 13.......3 PI Server Replication ..........................HA Step 5: Configure N-Way Buffering ...........................3 The Buffering Mechanism........... 158 13.................................................................................7 Group Exercise ................................................................................................................................ 163 13... 162 13.. 151 12........11 Group Exercise .........5 Directed Activity – Configure Buffering ......PI System Basics 11......................... 164 13....4 Directed Activity – Mapping Data in PI Buffering .................... 167 13........ High Availability ................................................................................... 183 14.... 150 12........... 148 12..2 Disconnected Startup .......................................2 Directed Activity – The Two Faces of Buffering ..................................HA Step 4: Form the Collective.............. Buffering .............................. 161 13.................................................................3 Changing the Collective Hierarchy ................. 160 13..................... 149 12....................12 Collective Manager .........1 What is PI Buffering? ............... 184 14.................17 Group Recap Question ... 166 13............................................. 169 13......High Availability Debriefing .4 Validating communication between the PI Server and the PI Interface138 11......................... 158 13............9 Exercise – OPC Points...........2 Directed Activity – Components of PI High Availability ...................................... 178 13.........................7 Solo / Group Exercise – The PI Buffer Subsystem ........... 142 11.......................................................HA Step 2: Second Interface Machine ........................... 161 13...............................6 A Note About Load Balancing a Large Number of PI Tags .10 Interface Failover Defined................. 152 12........................................................ 181 13..................................................... High Availability and Complex Architectures .................... 188 Page 5 ....................................8 The Second Interface .......................... 155 12..........................14 Buffering Mechanisms and Data Replication ......................... 156 13.............................................. 148 12..... 139 11.................... 141 11..................15 Group Exercise ...........4 Limitations.........9 Group Exercise .... 146 12....................... 175 13.........................................HA Final Step: The Road Test................ 141 11...........16 Group Exercise ......5 Directed Activity – PI OPC Interface Install & Configuration .................... 172 13..............1 Managing Archives on Replicated Servers.. 165 13......................................................................................... 186 14...................................... 186 14...............6 Validating Data Buffering.............................1 High Availability Defined ..............13 Group Exercise ...................................HA Step 3: Implement Interface Failover......7 PI Interface Configuration Utility ......8 Directed Exercise – Explore PI ICU .....................................................................HA Step 1: Revisit Planning and Hardware. ... 190 14...........................................................1 To Push or To Pull .......................... 197 Page 6 ....2 What Kind of Data Collection? ...............................................................PI System Architecture................................ Planning and Implementation 14.................................. 189 14..................... 195 15........................................ 194 15.. 194 15.......................................5 Untrusted Domain Issues ............................. 195 Appendix A – Ports ..6 Exercise – Add a Local User to a Secondary Node ..................................... 193 15.................................................................. The PI to PI Interface ...................................4 Exercise – Change the Primary PI Server ........... Identical Points?.............................................3 Identical Data........ like exercises. User manuals.osisoft. or documentation references. and other materials used in class can be downloaded from http://techsupport. either in small groups or on your own. Your objectives are skills you can expect to learn in this segment. Throughout the class you will be presented with questions and challenges to help you learn. New concepts are presented as level 2 headings.com . Learning workbooks. Login to an OSIsoft technical support account is required. tips. Page 7 . Icons help you identify themes.PI System Basics How to Use this Workbook Each Main Heading describes a highlevel valuable learning topic. The majority of your time will be spent learning new skills via handson exercises. tools. 77) PI OPC interface 2.8 Page 8 .4.PI System Architecture.385.3.17.18 SMT 2010 SP1 PI AF Server 2010 R3 ICU 1. Planning and Implementation Software Versions Used in this Document Described below are the software versions used in this version of the course.4. Software Version PI Server 2010 SP1 (3. PI System Basics 1. many businesses have realised there is a need to take better control of their production processes. and in a timely manner.1 Course structure The course consists of instructor lead training with individual student exercises. maintenance engineers. You will need to be familiar with your own corporate network topology. including where the data originates and who can best take advantage of the dissemination of this data. Install and configure a simple PI System. easily. During the course.operators. Your site will be used as a pilot and. Modify this system to form a High Availability PI System architecture. Why PI? (What problem are you trying to solve?) With the continuing global financial crisis.PI System Basics 1.2 Sketch the PI System environment topology for your company. Before going too much further you must decide exactly what type of data the stakeholders need and just where it can be found in your organisation. All too often. planning and analysis reports are created with static and inconsistent sources of information – commonly known as silos of information. CEO’s are now requesting timely situation reports so that efficiencies can be introduced to ensure the profitability of the company. This course will lead you into an examination of your users’ data requirements and will examine the infrastructure required to meet those requirements. and the real-time data environment. process engineers. Instead of weekly reports rolled up monthly. your solution will be rolled out across the enterprise. Any solution must address the needs of all stakeholders . site management and enterprise management – as efficiently as possible. you will: 1. You need to unlock the source of this data and present it to all. The current SCADA system operator stations are too expensive to roll out to non-operations employees. Data may be currently locked in spreadsheets or a customized application interface or is on the SCADA system and is not easily accessible by mere mortals. Page 9 . You will then install components of the PI system that will demonstrate the way those pieces interact to provide you with a model for the way to proceed in your own environment. You have been selected for the task of getting the key performance indicators and process data to the CEO in a timelier manner than is currently the case. when proven. Page 10 . Planning and Implementation 1.PI System Architecture.3 What is a PI System? Objectives 1.1 Define the components of a PI System Draw a diagram of the architecture of a PI System The PI System Described The PI System collects. These are generally the parts involved in a PI System: Data is collected from the source by the PI Interface program hosted by the Interface Node. You connect your data sources to one or more PI Interface Nodes. It is read from the PI/AF Servers by the Client tools.3. The Interface Nodes get the data from your data sources and send it to the PI Server. stores. and manages data from your plant or process. Users get data from the PI Server and display it with client tools. The data is sent to the PI Server (Asset data can be contained in the PI AF Server). PI System Basics 1. The PI Server = PI Data Archive + PI Asset Framework In many cases there are many PI Servers in an organization. Page 11 .3. Some customers have as few as one or two interfaces feeding data to a PI Server.2 Architecture of a Typical PI System Sometimes the architecture can be very simple. Everyone reads that PI Server for their data. aggregating data from lower levels. 1 Define an AF Asset and its components . Formula.4 Assets and PI Points – The Basic Building Blocks in the PI System Objectives 1. Define the different data types that can be stored in PI Points What is an Asset? The PI Asset Framework (AF) Server is a part of the PI System. they can find the data they need without understanding the technical details of each piece of equipment. Points Page 12 Assets .4. and Point Source. Assets can be helpful to users of the PI System who do not know or are not familiar with points.PI System Architecture. Using assets.the element and the element attributes Define the four attribute types: Static (None). Planning and Implementation 1. Assets are also helpful in finding all of the points associated with a specific piece of equipment. PI Point. and Table Lookup Define a Point and the attributes Tag Name. Descriptor. It contains asset or “metadata” that is usually organized according to the assets containing the points being monitored. PI System Basics 1. Problem Description Identify the type of objects in the PI AF Server. list them here: Page 13 . There are four types of Attributes.5 Directed Exercise – Assets Defined You are invited to watch what the instructor is doing or perform the same steps at the same time to explore the different concepts presented in this chapter or section. 5. It has been the traditional unit in the PI Server. (Default) Float64 Floating Point number. 16 bits (scaled. Red/Black/Green) Int16 Integer value.2 So What Types of Data Can PI Store? (Point Types) The answer is pretty much everything. 64 bits (double precision) String Text value up to 976 characters Blob Binary large object up to 976 bytes Timestamp Any Time/Date in the range 1-Jan-1970 to 1-Jan-2038 Page 14 . It is simply a single point of measurement. 0 to 32767. 16 bits (1/32767 times range) Float32 Floating Point number.1 What is a PI point? It is a unique storage point for data in the PI Data Archive. 1.5. Planning and Implementation 1. acc: 1/32767) Int32 Integer value. 32 bits (single precision). Below are the valid data types: Digital Discrete value (On/Off.PI System Architecture. (7/8 Digits). 32 bits (-2147450880 to 2147483647) Float16 Scaled Floating Point number. PI System Basics 1.6 Directed Exercise – Data Types You are invited to watch what the instructor is doing or perform the same steps at the same time to explore the different concepts presented in this chapter or section. Problem Description Identify the type of data that might be associated with each of the following: Example: a Temperature Sensor ___a floating point value___ A switch position: _____________________________________ A Batch ID: _____________________________________ Operator comments: _____________________________________ The results of a calculation: _____________________________________ Memory available on a server: _____________________________________ Current phase of the reaction: _____________________________________ Current product count: _____________________________________ Page 15 . and then into the PI Server. through an interface. Client tools are able to view the data from either the PI Server.PI System Architecture. The first mechanism to be described is the data flow through the PI Server.7 Data Flow through the PI Server As previously described. Page 16 . This mechanism is highlighted in the figure below. data moves from a data source. Planning and Implementation 1. If the tag value passes exception. The raw value is assigned a time stamp by the interface and exception. the second type of filtering. The PI User is then able to retrieve either the snapshot value or the archive values for each tag. If the tag value passes compression. compression. Under normal operation. the first type of filtering. including details on exception and compression are described later. it then goes into the buffer queues. Page 17 . The data gets passed from node to node on a per tag basis. is applied. The value of each specific tag is taken from its data source. it then goes into an event queue and then right into the archive for permanent storage. A more in-depth look on this data flow. From the snapshot. that tag value is immediately sent to the PI server where it enters the snapshot.PI System Basics The specific functions of each node is noted in the next figure. below. is applied. Compression Data Source Reporting by Exception Event Queue PI Interface Buffering Snapshot Archives Page 18 .PI System Architecture.8 Data Flow: From The Source To The PI Archives In order to determine if you have installed and set everything up correctly (and in the future to check for proper function). If the interface node cannot connect to the PI Server. If the buffering service is configured on the interface node. The PI interfaces collect data from the data sources and typically use exception reporting. it is essential that you understand the various data structures or “touch points” that the data encounters along the way. then the events go through the buffering service. Planning and Implementation 1. the buffering service holds the data until the PI Server connection is restored. This slide is a good illustration: The PI Server stores data in the form of events. Each event has a value and a timestamp that indicates what time the value was collected. meaning that they pass significant events on to the PI Server and discard the rest. PI System Basics 1.9 Data Flow: Block Diagram From Interface To PI Server Page 19 PI System Architecture, Planning and Implementation 1.10 Data Flow on the Interface Computers As described earlier, the PI Interface has three basic functions: 1. 2. 3. Collect data Timestamp the data (or validate that a timestamp is provided by the device) Apply the Exception Deviation Applying the exception parameters is referred to as “Reporting by Exception.” 1.11 Reporting by Exception The object of exception reporting is to simply reduce noise. In other words, for the interface to send you the data you are interested in, rather than taxing the network connection by sending a lot of data that is not meaningful. Exception reporting uses a simple dead band algorithm to determine whether to send events to the PI Server. For each point, you can set exception reporting specifications that create the dead band. The interface ignores values that fall inside the dead band. The width of the dead band can either be defined by explicitly specifying a number (ExcDev) or by setting a percentage of the span attribute (ExcDevPercent) of the tag. This is normally based on what the user considers a significant change. A maximum elapsed time to run without sending a new value is also specified to be sure the tag’s current value updates even if it not encountering a significant change. This is set in the ExcMax tag attribute. Page 20 Temperature PI System Basics ExMax ExDev C A D B E ExDev F Time In the preceding illustration, values A, E, and F are reported to the PI Server. Value A is the last reported value, values B, C, D and E fall within the exception dead band, but value F falls outside the dead band, so the interface reports value F and the previous value, in this case, value E. All Exception Attributes are set on a per tag basis. Note 1: Some interfaces do not support exception reporting. See the documentation for your interface to determine whether it supports this capability. Note 2: ExcMin is by default set to 0. It is very rarely used. Page 21 PI System Architecture, Planning and Implementation 1.12 Directed Exercise – PI Snapshot Values You are invited to watch what the instructor is doing or perform the same steps at the same time to explore the different concepts presented in this chapter or section. Activity Objectives Determine which events for a PI interface will make it to the PI Server. Approach Consider the following attribute values for a PI tag: ExcDevPercent: 2 ExcMax: 180 Span: 200 The current snapshot received in the PI Server for this tag is: Value: 70.3 Timestamp: 10:00:00 Which of the following values collected by the PI interface pass the exception test? Page 22 3 10:01:00 67.4 10:03:00 70.1 10:02:00 71.2 10:08:00 60.2 10:05:00 66.0 10:06:00 65.PI System Basics PI Interface Node Time Value 10:00:00 70.1 PI Server Node Snapshot Time 10:00:00 Current Snapshot 70.1 10:04:00 68.0 10:09:00 63.8 10:07:00 64.3 Page 23 . Planning and Implementation 1. 1.14 Compression The point of Compression Testing is to remove extraneous data and keep only what is needed to reproduce the original data from the data source. In a simple case like this. When a new value is received it is compared to the previous value. In the following illustration all the events fall on the same straight line. there is no need to store all the points on the line. Page 24 . If you store just two points. If that value indicates that the previous value fails compression then the previous value is discarded and the new value is retained as the new “current” value.13 Snapshot The Snapshot Table is simply the “Current” or most recent value for each tag in the PI Server. The Compression process applies a deviation in a similar manner to exception except that it takes into account he slope of the trending data. within the limits of accuracy required. The Snapshot subsystem populates this table and also performs the Compression Algorithm Calculation. If that value indicates that the previous value passes compression then the previous value is sent on and the new value is retained as the new “current” value. you can exactly recreate the point value for any other time.PI System Architecture. The CompDev and CompMax attributes allow you to control the granularity of the compression algorithm. The PI Server uses a sophisticated compression algorithm to determine which events it needs to keep in order to provide an accurate data history. An animation explains the process: Page 25 . All Compression Attributes are set on a per tag basis.PI System Basics C E Temperature D v De p om v De p m Co F C B A CompMax Time The same principle applies to compressing real-world data. the default values will be used.2 would be missed because it does not meet the default threshold of 1 engineering unit (or 1 percent of a span set to 100). The latency due to spinning of the hard disk and network bandwidth limitations can impede performance. as you will adversely affect the performance of the system by archiving many more values than are necessary. The default values for exception and compression are as follow: ExcDevPercent = 1 (% of span) ExcMax = 600 (10 minutes) CompDevPercent = 2 (% of span) CompMax = 28800 (8 hours) Zero = 0 Span = 100 It is not advisable to use the tag defaults for excdev and compdev. If left to the defaults. it is possible to miss significant changes due to the exception test removing these events. An exception value of 0.PI System Architecture. Page 26 . This should be avoided because the exception and compression values for each tag should correctly reflect the desired tag values. With no exception or compression. we would record the value of OPEN to disk thousands and thousands of times unnecessarily. It is just as bad to turn exception and compression off. While hard disk space is become cheaper. This is illustrated in the slide shown below: Tip If you create a tag in the PI Server and do not specify values for exception and compression. and if the tag normally moves through a very small range of values. An example might be a frequency sensor. Planning and Implementation 1.15 Cumulative Impact and Defaults There is a cumulative impact of the exception and compression process. the more limiting factor is the speed of retrieval. where a change of 0. An example of this would be a valve scanned every few seconds.1 might be more appropriate (or an adjustment to the span). it is advisable to turn off exception and compression entirely. The exception deviation (ExcDev) should be set to half of the compression deviation. In some cases. we recommend setting the compression deviation (CompDev) to the minimum change measurable by the instrument.2 CompDev 100 to 500 0. without wasting space on duplicating values or losing meaningful values. It is important to note that these are only starting point recommendations and you should be sure to inspect your data for the desired resolution.PI System Basics As a starting point recommendation for these settings. although it is recommend leaving compression on. the PI Server will archive values that reflect an accurate change in the device. You can turn off compression directly. Tip An easy-to-use starting point for exception and compression can be found below: Span CompDevPercent ≤ 100 0.2 > 500 0.5 ExcDev(percent) = 50% of CompDev(percent) Page 27 . If set properly. To do this. set the exception deviation (ExcDev) and the exception maximum (ExcMax) to 0. by setting the Compressing attribute to 0 (Off). 1 What is PI? At its simplest.PI System Architecture. Page 28 . 2. A simple PI system consists of the data source. and an appropriate visualization tool on a PC. PI is a data infrastructure. and develop an understanding of the IT network topology required to support them. the data collector for that data source (they may be on the same computer). Planning and Implementation 2. a PI Historian combined with its Asset Framework server. PI System Environment Architecture Objectives Categorize your users Describe the PI System components Compare and contrast the PI Server and the PI AF Server Explain where each component can fit into your Enterprise List the pros and cons of the various client tools In this section. you will investigate your users and the data they require. PI System Environment Architecture The PI environment may be expanded to become a system represented below: However, the PI environment doesn’t start with the system – it starts with people, and what they need from their data. Page 29 PI System Architecture, Planning and Implementation 2.3 Group Exercise – Categorize Your Users This group activity is designed to maximize learning in a specific topic area. Your instructor will have instructions, and will coach you if you need assistance during the activity. Activity Objectives Users are a diverse group of individuals with differing requirements from the same set of data. There are operations’ managers, engineering managers, CEOs, engineers, chemists, operators and accountants who all require data from the various databases within the organisation. These people may exist in different places to each other necessitating a multiplicity of methods of communicating data around the network. Approach Your instructor will ask you to list potential users of PI Data, and where they “live” in the Enterprise. Write some answers here: Page 30 PI System Environment Architecture 2.4 Data Sources Data sources can be the any measuring devices generating asset data. They can be almost anything, and they can connect to the interface data collection computers in a variety of ways. Examples of data sources are: Distributed Control Systems (DCSs) Programmable Logic Controllers (PLCs) Laboratory information systems (LIMs) Supervisory Control and Data Acquisition systems (SCADA) Manual loggers EPA data loggers Network devices Business Information (BI) systems. To acquire data from these sources it is necessary to utilize a PI interface. The interface may be simple such as a file reader or complex such as the interface that uses the OPC protocol. For more information on OPC, see www.opcfoundation.org. PI Performance Equations, PI ACE, and the Totalizer subsystem (discussed later) are also considered data sources, even though they may be hosted on the PI Server computer. 2.5 Interface Computers Interface computers (also known as nodes or data collectors) run one or more PI interfaces. PI interfaces collect data from the targeted data source and send it to the PI Server. Each different data source needs a PI interface that can interpret the protocol used by the source. OSIsoft has over 450 different interfaces. To collect data from a source, the PI System must be configured appropriately. The interface itself must be configured, as must the points where the data is going to be stored in the PI Server, i.e. the data point, aka point, or more properly, the data stream. There is a correspondence between the metadata (attributes) of the point in the PI Server database and the point’s attributes in the data source. Matching the two sets of point attributes is crucial to sustainable and timely data collection by the interface. Necessary steps in collecting data are: • ensure the network between the data source to the PI server is configured • ensure the data source is working • install and configure the appropriate PI interface • create and configure points as required on the PI server • check that the points are receiving data This will be covered in detail tomorrow. Page 31 PI System Architecture, Planning and Implementation 2.6 Parts is Parts The PI System is not just one application. It is a collection of many applications that makeup the infrastructure we call the PI System. It is important in your planning phases that you understand what these parts are and what they do. 2.7 Group Exercise – Discover the PI System This group activity is designed to maximize learning in a specific topic area. Your instructor will have instructions, and will coach you if you need assistance during the activity. Exercise Objectives Describe the PI System components Define the purpose of each component Problem Description You need to understand the function of each of the main PI System Application Components. Approach From the discussion so far, do your best to answer the name of the product according to each of their description. For example: This graphics package allows users to create dynamic, interactive trends featuring realtime PI data. Answer: PI ProcessBook This powerful, easy-to-use spreadsheet add-in is used for gathering, analyzing, and reporting PI data. Answer: Page 32 Answer: Page 33 . easy. web-based tool delivers fast. Answer: This programmatic. Answer: This robust tool lets you define a consistent representation of your assets and provide a structure for your information. fault-tolerant data to the PI System. which are reusable on similar sets of data. Answer: This real-time data collection.PI System Environment Architecture This web-based application allows users to build and share views of data for reporting and analysis. providing real-time. with minimal effort. archiving. Answer: These applications provide high-speed links to external data sources. and distribution engine powers the PI System. powerful analytic tool allows users to write equations. Answer: This intuitive. and secure access to all your PI System data. we will look at the database technologies in our servers. but are computed by applying relational operations to other relations. -source: Wikipedia This type of database is perfect for storing hierarchies and metadata. two server database applications? Because of the truth: Use the right tool for the right job.1 PI AF Server Core Technology The PI AF Server is based on Microsoft SQL Server. Data can be indexed in many ways. and in implementations are called "tables". This is why we base our PI Asset Framework Server on this application. only to provide an explanation of why we use each technology to store data. It is called a relational database because the data is stored in flexible small pieces (tables) that can be assembled in many ways to give different results. Page 34 . Relations that store data are called "base relations". and large structures can be stored efficiently. Planning and Implementation 2. In a relational database. In implementations these are called "views" or "queries". These relations are sometimes called "derived relations". We have two servers not only because the PI System is based on access to real-time and historical data. Other relations do not store data. one of the world’s most advanced relational databases. all data are stored and accessed via relations. To understand this better. 2.PI System Architecture. Note: This information is not required to be memorized in detail. Derived relations are convenient in that though they may grab information from several relations. at its core. they act as a single relation.8 PI Server + AF Server = PI System Why does the PI System have. but also because data is only useful if it is seen in some sort of context.8. The records are small so we can pack the archive efficiently. and exactly where in that file to start reading data. At a higher level. This design is still the most powerful in the world for time series data. we write the “next” record at the end of the archive file and move “backwards.2 PI Data Server Core Technology When the PI Server was first developed. Page 35 . each archive is a fixed size and therefore contains a finite time span. Start End Start End Start End Start End To respond to a data request.” Why? So we can maintain a contiguous Primary Record range. This archive is broken into 1K records.8. Each 1K record at the beginning is associated with the Record Number of each point. as some points will fill quickly and some may not change often at all. 2. These times are stored in an Archive Index. When a user asks for point data. Each database table in the PI Server is called an Archive. When a primary record fills.PI System Environment Architecture The only problem with a relational database is that it is an awful structure for time series data. the system translates that into the RecNo and can find the data start without searching – it knows exactly where in the file to start reading. RecNo Overflow Each record contains a pointer to the next record. the PI Server knows exactly what archive file to jump to. we used our own design for the database because we wanted the best performance. These are called Primary Records and serve as a natural index. Slow changing or static data may be better stored in relational databases structures. text or enumerated data. Page 36 .What Do Your Users Require? Users’ data is any data associated with the diverse equipment required found in the modern business environment. Because of the differences in the rate of change of data. the CPU temperature of a server. or the memory requirements of a monitored business application. AF data can be stored in the associated relational database.9 Back to the Data . All data stored in the PI Server is kept in archives. fast retrieval and automatic compression such as the PI time series archives. shift production limits.3 Where Do the Servers Belong in Your Enterprise? The storage of this data may be disseminated throughout your company. 2.8. derived (calculated) data or grouped (relational) data. derived as required from attributes and elements or passed through from the PI Server. production totals and cost of production to name a few types of data. the date the pump had its impellor changed.PI System Architecture. Planning and Implementation 2. running hours of the pump. This data can be categorised as real-time data. in-stream analysis. or the asset centric elements found in the Asset Framework (AF) database. the serial number of the pump. It can also record the ping time between two computers in corporate network. it is appropriate to store the data in different ways. Both the AF and PI servers can store numeric (floating point or integer). Real time data is best stored in a database that allows for fast storage. the structure of the archives facilitates the rapid retrieval of data. Numeric data stored in the PI Server may be compressed to compact the historian and to facilitate data retrieval. This can be data such as the speed of a pump. Calculated data may be stored in the PI Server. or efficiency of the pump. When the CEO requests data. Users may also require mill shutdown time. or derived as required in the AF database. For each of these groups produce a list of the types of data they need. Classify whether this data as real-time or not. Approach As a group create a list of the types (e. and will coach you if you need assistance during the activity. This group activity is designed to maximize learning in a specific topic area.g. Your instructor will have instructions.PI System Environment Architecture 2. Page 37 .) of user that will need PI. operator. IT network engineer.10 Group Exercise – Know Your Users. engineer. Their Data. etc. CEO. Activity Objectives To understand who the users are and what their data requirements may be. depending on your application. Start with a manageable area. OSIsoft recommends the use of one PI AF database for your entire asset framework. such as a particular type of equipment. non-real time data according to objects with which the users are familiar. configured data. access to data from systems other than PI. allowing users to organise and search for PI information across multiple PI servers. constants. AF supports SQL Server Express editions. In most cases. transformers. SQL Express comes with a free license. consider the following questions: How will you map your company’s assets to AF elements? What attributes are required for each element? Are these attributes PI data. A company with a database that handles current operations may have a second database for staging purposes. PI WebParts.11 Combining Different Types Of Data The AF server provides a number of functions that are useful for building applications upon PI data and other data. together with AF and/or PI Server software. You do not have to configure your entire AF installation at once. grinding mills. Planning and Implementation 2. as well as other. However. which can be installed on a shared computer. AF requires Microsoft SQL Server and that there is a SQL Server instance available at the time of installation. or calculations? Will you use templates to speed definition of these elements? How will the asset hierarchy be structured? Do you need data from other databases as well as real-time (PI) data? What security is required? Are alerts (PI Notifications) needed? PI System Explorer is one tool used to see AF data and connects to one AF database at a time. you may need multiple databases: Within a single company. and expand the model over time. searches. PI OLEDB Enterprise and PI Web Services. The element is a user-oriented object that contains attributes. The most significant is asset centric and allows users to organise and structure PI data. Page 38 . even CPU temperatures. but scalability limitations make it more suitable for small to medium-size installations. Other features of AF that allow users to leverage PI data include object-level security. or part of a process. These can be physical objects in their production processes like pumps. and data from other. An important aspect of AF asset elements is that their data can span PI servers. Modifications to be implemented in the future are made and tested on a staging database before transferring the structure to the operational database. which reference PI data. and the ability to scale to 100 million element attributes or more. The AF also provides an underlying infrastructure for OSIsoft products such as PI Notifications. disparate systems. These asset elements are flexible and allow hierarchical modes. different departments may prefer to have their own unique databases to handle their needs. When planning an AF installation.PI System Architecture. PI System Environment Architecture Please consult the PI Server Installation and Upgrade Guide for details. and must be installed and available prior to the PI Server installation. The PI Server automatically installs AF Client binaries but the PI Server 2010 setup kit does not include AF Server. AF 2010 is a required component of PI Server 2010. Page 39 . Planning and Implementation 2.12 Directed Activity – Viewing Your Data In this part of the class. you will perform a learning activity to explore the different concepts presented in this chapter or section. Your instructor will have directions. Approach Discuss with the instructor.PI System Architecture. the pros and cons of the 4 major client tools. Use the table on the next page to record your ideas: Page 40 . You may be invited to watch what the instructor is doing or perform the same steps at the same time. Activity Objectives Discover the best ways to view data under different circumstances. PI System Environment Architecture Pros Cons Page 41 . Your instructor will have directions. Approach Previously you listed types of data – real-time and otherwise. How big a part will AF play in your environment? The instructor will facilitate the discussion. Page 42 . Planning and Implementation 2. You may be invited to watch what the instructor is doing or perform the same steps at the same time. you will perform a learning activity to explore the different concepts presented in this chapter or section. Activity Objectives To understand the places data can be stored in the PI System environment.PI System Architecture. Decide where this data will be stored and why.13 Directed Activity – Critical Data In this part of the class. Questions 1. What is the difference between a PI System and a PI Server? 2. or to discover a new insight.14 Group Questions The following questions are intended to reinforce key information.PI System Environment Architecture 2. What is the difference between a smart client and thin client? Page 43 . Planning and Implementation 3. OSIsoft products verify that the minimum operating system components are Page 44 . install a standard windows system. testing as you go.2 Prerequisite Kits OSIsoft has removed Microsoft Windows redistributables from the OSIsoft installation kits in order to reduce installation kit size. and Windows Server 2008 R2.1 Minimum Operating System PI Server 2010 runs on the following versions of Microsoft Windows.PI System Architecture. PI Server Requirements Objectives: Describe the Prerequisite Kits Define the hardware requirements of the PI Server Define the hardware requirements of the PI AF Server Describe the virtualization support for the PI System List the steps required to obtain the PI Server license file 3. Most companies have some form of Standard Operating Environment (SOE) that is applied to a computer as the operating system is installed. 64-bit (recommended for production environments): o Windows Server 2008 R2 o Windows Server 2008 SP2 o Windows Server 2003 SP2 or later 32-bit: o Windows Server 2008 SP2 o Windows Server 2003 SP2 or later PI Server 2010 is supported on both the Full and Server Core installations of Windows Server 2008 64bit. Note: While Microsoft client operating systems such as Windows XP and Microsoft Windows 7 may be employed to test and evaluate PI Server. 3. and eliminate download of distributed files common across setup kits. then apply the SOE post PI install. Windows Server 2008. OSIsoft does not support these operating systems for production environments. If this occurs. Be aware that the SOE may interfere with the installation of PI. however if the requirements are missing from the operating system. There are different prerequisite install kits available for download and only one should be used for installation depending on the environment and preference: Online: For installation on a computer connected to the internet. This kit connects to Microsoft sites in order to download . The Microsoft operating system requirements are available as separate Prerequisite Kits.NET Framework 3.5 for the operating system on which it is run. This is a bootstrapper kit that is much smaller than the Standalone kit. the setup kit will no longer automatically install the missing components. Legacy: This kit should only be used for installation on older operating systems where the OSIsoft products do not require .NET Framework 3. Page 45 . or if such connection is not desirable. Standalone (Recommended): For installation on a computer that cannot connect to Microsoft sites.PI Server Requirements installed.5. This is a full redistributable kit that is much larger than the Online kit. in the pi\log directory. one or more Microsoft Windows compatible computers. small system will have the PI Server. For best performance and improved security. preferably with a 64-bit operating system is required. also downloadable from the OSIsoft Technical Support web site. OSIsoft recommends at least two physical drives on the PI Server computer. PI AF servers connected to a mirrored SQL Server. The number of required computers depends on the size and complexity of the PI System. or meters or whatever else you have added into the asset database).3 Hardware Sizing Included in the files distributed with the course is the “Hardware and Systems Sizing Recommendations Spreadsheet”. below to calculate the necessary disk space. Rollback backup (upgrade only) Size of PI Server databases + primary archive The PI Server setup program performs a minimal backup during the upgrade. PI Archive files 10 MB per 1000 points PI event queue 5 MB per 1000 points OSIsoft recommends that you place the event queue on a different physical drive from the PI archive files. and Microsoft SQL Server. or PI AF servers connected to clustered SQL Servers). A simple. Page 46 . OSIsoft recommends that you install SQL Server on a different computer from PI Server. The PI AF server and PI Server must be installed on different computers if: PI AF server will use time-series data from multiple PI Servers or PI AF collectives (a distributed system). the computer would not have the benefits of 64-bit Windows operating systems.PI System Architecture. tanks. For PI Server. such as more than 2GB of RAM per process. It is possible to install a 32-bit version of Windows on a 64-bit computer. Planning and Implementation 3. Message log files 10 MB Located on the same computer as PI Server. PI Server Component Space Requirement Notes PI Server 2010 and PI Software Development Kit (PI SDK) 160 MB 100 MB temporary disk space for installation PI SDK includes the PI API. the PI AF Server and SQL Server (the free SQL Server Express may be used) installed on the same hardware (or virtualised) server. PI AF server. PI AF server is configured for high availability (such as a PI AF collective. However. The size of a PI System depends on the number of PI points and the number of units (elements) of equipment (such as mixers. load balanced PI AF servers. as shown below. The amount of disk space required depends primarily on the number of PI points that the PI system will collect. PI Server databases 11 MB per 1000 points + 1 MB Located on the same computer as the PI Server. Page 47 . A PI System that is sized using the “PI Server Installation and Upgrade Guide” and “Hardware and System Sizing Recommendations Spreadsheet” will operate on a virtualized platform when using the recommended configurations. PI AF collectives. OSIsoft recommends that you install PI Server collectives.PI Server Requirements For distributed systems with large workloads and point counts. redundant computers to achieve the best level of performance and scalability. and with multiple PI Servers or PI Server collectives that link to a central AF database. there are five core principles that should be noted when implementing the PI System on a virtualized platform. 3. This type of system is depicted below.4 Virtualization OSIsoft supports the virtualisation of the PI System on the virtualization platforms of Microsoft Hyper-V and VMWare ESX Server. and Microsoft SQL Server on separate. In addition to the recommended architectures. For more information see “Virtualization and the PI System 1.” Page 48 .PI System Architecture. using a custom configuration should be undertaken. Principle 4 – Ensure qualified support of the virtual environment. Planning and Implementation Principle 1 – A Virtual Machine is just another brand of machine. Principle 3 – Do not mix virtual and physical implementations on the same host. Principle 2 – Enterprise solutions must use enterprise class virtualization and hardware.2. Principle 5 – Thorough testing of the PI System on both physical and virtual platforms. the redundant interface automatically starts collecting and buffering data to send to the PI Server. Depending on the data source. 4. PI Server Replication enables alternate data sources by synchronizing the configuration of multiple servers. Each interface manual has comprehensive details of how to implement interface failover. Page 49 . PI System Planning Objectives: Discuss Highly Available Systems How to get through firewalls Understand your calculation options To ensure the integrity of your PI environment steps must be taken to implement backups. an interface can automatically switch between redundant copies of the interface run on separate interface computers. or network failure causes one interface to become unavailable.PI System Planning 4. Depending on the pace of the course. 4. it receives updates to the list of points and their parameters and writes the information— including the point scan list—to a local disk file. Subsequent starts of the interface can use the local copy of the point information to start up without a connection to the PI Server. you will be implementing a highly available architecture on Day 3 or Day 4. This allows interfaces to buffer data to multiple servers with the same point configuration. Please consult the PI Server Installation and Upgrade Guide for details. PI clients can retrieve data from any of the servers without changing data references. This provides uninterrupted collection of process data even when one of the interfaces is unable to collect data for any reason. hardware failure.1 PI Server High Availability PI Server High Availability (HA) enhances the reliability of the PI Server by providing alternate sources of the same time-series data for users. When maintenance. redundancy and high availability of the all components.2 Interface Failover PI Interfaces based on standard interface template (UniInt) can potentially support interface failover. UniInt interfaces can also restart without a connection to the PI Server. As the interface runs. Any client workstations on the protected LAN are configured to connect to the PI Servers on the protected LAN. This reduces the diversity of traffic and number of data sources that would flow through the firewall from the protected LAN to the widely available LAN if n-way buffering sent time-series data to all of the secondary PI Servers. The PItoPI interface copies point data from one PI server to another. The client workstations on the widely available LAN are configured to connect only to the PI Server(s) on the widely available LAN. The primary PI Server receives all configuration changes.PI System Architecture. Page 50 . and could be configured to connect to the PI Servers on the widely available LAN as well. Data is moved in one direction. You may employ a primary PI Server on the protected LAN inside the firewall and a secondary server(s) with a large group of users outside the firewall on the widely available LAN.3 Routing Time-Series Data through a Firewall A firewall that isolates the PI Servers on a protected LAN from a large number of users on a widely available LAN may be deemed necessary. Planning and Implementation 4. The interfaces send time-series data to the PI Servers on the protected LAN via n-way buffering. One or more PI to PI interfaces running on the protected LAN may forward time-series data from the primary server to the PI Servers on the widely available LAN. The interfaces receive configuration information from the primary PI Server. meaning data is copied from the source to the receiving PI server. PI System Planning 4. easy to configure. In order to connect to the AF database OSIsoft recommends that you use Windows authentication because it is more secure than SQL Server authentication.1 What is Security? Computer security has two parts: Authentication Authorization Who is the user. Objects and their effective permissions are based on the Windows user identity. and can easily accommodate the PI System.4 Security Part 1: Planning Objectives • Introduce PI security • Understand how network and environment affect PI Security. • Discuss Mappings • Discuss the applicability of Trusts 4. and provide for minimal Maintenance.4. and how do we confirm that the user is really whom he or she says? What is that user allowed to do? Security is always a balance. It’s something that you probably have now in your domains. That is why we suggest using Windows Active Directory security. Page 51 . You want to use what is most secure. We call this Windows Integrated Security. The permission sets for all users are stored as Windows security descriptors associated with certain types of objects and collections within AF. which locks out idle sessions and requires password re-entry. PI can stand alone. Have unique passwords for both the local administrator and the piadmin PI user. download the required files on another computer and transfer them by flash drive or other media. Do not put client software (Microsoft Office. This will encourage the servers use as a client. Have a screen saver. Page 52 . Instead. This access can be provided by remote terminal client services.) on your server. sharing no files and inaccessible by anyone except the local computer administrator and users. This usually includes: Domain security for users. Although PI is usually implemented in domains and all data communications to PI are through TCP/IP response packets. and applications Router security including router based firewalls Antivirus programs and regular operating system patches Controlled access by remote parties Fixed IP addresses are usually applied to interface computers and server computers. PI ProcessBook. directories.PI System Architecture. etc. Planning and Implementation 4. Install the server in a secured area with a locked door. uninterruptible power supply and air conditioning. implementation in a corporate network secured computing environment. and best supported by. PI can be implemented without joining the domain since. while DHCP IP addresses is the norm for user clients. PI’s lookup server name can be entered into the Domain Name Server associated with its fixed IP address. file access to the PI Server from any remote computer is unnecessary.5 Securing the Environment and the Server PI is consistent with. Do not use the PI Server computer to access the Internet via a browser. 6 Directed Activity – Active Directory Roles In this part of the class. Page 53 . Your instructor will have directions. you will perform a learning activity to explore the different concepts presented in this chapter or section.PI System Planning 4. Approach Spend two minutes listing the benefits of a good security model using Windows Integrated Security and Active Directory: List the roles you would find useful in your organization. Tip You should take this list to your IT Department a good deal of time before an installation of the PI System in order for you to take advantage of the best security from Day One. Activity Objectives Create your roles you might find useful. You may be invited to watch what the instructor is doing or perform the same steps at the same time. a firewall has holes only in the server-bound direction. Note: There is a list of the Ports the PI System uses in Appendix A. nothing is allowed to pass except return connections on ephemeral ports. and may be optional. or temporary.org/wiki/Ephemeral_port The default ephemeral port range for Windows is 1024-5000. but others have configuration were the automatic reversedirection port opening is called “keeping state” or a “stateful firewall”.wikipedia. Planning and Implementation 4. A common misconception is that port 5450 should be opened bi-directionally. Page 54 .7 What about Ports? You cannot discuss security without talking about network ports. A complete list of ports that may need configuring can be found in Appendix A.PI System Architecture. port. The return connection is on an arbitrarily selected “ephemeral”. in the opposite direction. The old school way to do this is to leave the entire range open for the return connection. See http://en. Many firewall software packages just do it whether you want it or not. Ideally. but in the 21st century this is normally handled automatically by the firewall. and real-time cost accounting). and counting. The main difference between a Performance Equations point and a Totalizer point calculating the same summary is that Totalizer calculates based on Snapshot events while the Performance Equation Scheduler calculates based on Archive events. and the calculation results are stored in the PI Archive as a PE point.2 Performance Equations The Performance Equation (PE) Subsystem provides an equation syntax and library of built-in functions that allow you to perform a wide variety of calculations on the data stored in PI points.Net for details.1 ACE The PI Advanced Computing Engine (ACE) allows programming of complex calculations (for example.8 Calculation Options There are varied options for performing calculations in the PI environment.PI System Planning 4. communication applications (for example. called event-based scheduling. 4. heat and material balances. data reconciliation. and any other application that does not require user intervention. minimum and maximum values. Please consult the PI ACE 2010 User Guide for Visual Basic . Each PE is associated with a PI point. You can configure a PE point to be evaluated periodically by the Performance Equation Scheduler on a time-based basis. Output of a calculation is stored in a PI point. standard deviations.8.3 Totalizer The PI Totalizer Subsystem performs common calculations such as totals. consequently Totalizer points may have more accurate results. averages. For those people interested in Steam Functions there is also an applicable section in the manual mentioned below.8. Please consult the PI Performance Equations Syntax and Functions Reference section in the PI Server Applications User Guide for details. Page 55 . alarming. 4. or when an event is received on a specified trigger point. ACE provides a fault-tolerant and redundant architecture to ensure these real time calculations. 4. data transfer programs.8. emailing. and paging). The calculations can be one formula or a sequence of calculations and can have many input attributes. For more information see the PI System Explorer section of %PIHOME%\pipc\help\AF. 4.8.chm. You should review the PI Server Applications User Guide for material on PI Real-Time SQC and the PI Alarm Subsystem. Planning and Implementation Please consult the PI Totalizer Subsystem section in the PI Server Applications User Guide for details. Calculations may be derived that use PI point data. as well as static attribute data. Page 56 .PI System Architecture.4 AF Calculations As indicated previously the Asset Framework can be used for asset-based calculations. In the AF Help file is a list of Data Reference Functions that can be utilised. or type ‘calculation’ in the Search tab. and both internal and external table data. it is transferred in a timely manner to the PI Server. There is no need for manual refreshing of the displays. the PI interface is running as a service on the same computer as the source of the data.PI System Combinations 5. PI System Combinations Further information on complex systems. Objectives Reiterate the components of a small PI system Develop complex PI environments 5. Page 57 .1 A Simple PI System In addition to the users’ PCs. a computer to run the PI interface collecting the real time data CEO’s desk PI Interface with data source AF Server with PI Server Above. Tools such as ProcessBook. The users then request data from the AF and/or PI Server as required. As the data is collected. PI WebParts or Coresight will sign up for updates so that any new data arriving at the PI server is displayed on the client as it is received. the simplest recommended PI System consists of just two computers: a computer for the AF and PI Servers. 2 Adding components as needed As the needs of the PI environment grow. This may result in a PI system configuration as shown below. the AF server may be moved to a separate server. an Advanced Calculation Engine (ACE) can be added to the existing server or may be located on a separate server. The arrows indicate the direction of data flow. Planning and Implementation 5. multiple components are added to expand the capabilities of the systems. Page 58 CEO AF Server . If the AF server becomes a bottleneck for the system because of its extensive size. PI ACE PI Server PI Interface with data source . When sophisticated calculations (requiring programming) become necessary.PI System Architecture. These include the ability to conduct online backups. Please consult the PI AF 2010 R3 Overview Guide for details.3.3 When You Need To Bet Your Business On PI There may come a time when the PI environment is vital to the running of the company. The PI environment has been designed to provide fault tolerance via server replication and interface failover. 5. and switch to the next appropriate PI AF server. each acting as an independent storage for the time series data. load distribution. the distributed nature of data collection within the PI System. On failure. These servers automatically adopt configuration changes made on the primary. A collective has two types of servers: Primary . 5.1 PI Server Replication The PI High Availability (HA) design provides for multiple PI Servers. Each PI AF server must know its server role (primary or secondary).2 PI AF Collective A PI AF collective is a set of PI AF servers that acts as the logical PI AF server in a PI System to provide high availability (HA).the remaining servers in a collective. The failover and load balancing logic is implemented at the level of the PI AF SDK.3. uses a PI AF collective. compatibility with Microsoft Clustering technology. disaster recovery. and each secondary server must know where the primary server is located in order to send its status to the primary. Page 59 . At such a time. each primary server must know where the secondary servers are located to allow for replication. and increased scalability. SQL Server replication enables the secondary database server(s) to contact the primary database server and replicate metadata and data. Each PI AF server / PI AF SQL database pair can be on the same computer or on different computers. but receive data from the data source individually via a technique called n-way buffering that will be explained later. Secondary . implemented with PI AF. the PI AF SDK will select the appropriate PI AF server. The PI System includes features that facilitate making data highly available.PI System Combinations 5. it may be necessary to evaluate a Highly Available PI system.the main server in a collective where configuration changes are made. The high availability (HA) feature. These PI Servers function as a unit called a collective. and the availability of fault-tolerant third-party solutions that provide redundant hardware solutions. By adding the necessary components to satisfy the users’ requirements for redundancy and replication you may end up with a PI environment as shown below.3. If one copy of the interface shuts down then another will take over the data collection. This mechanism assures that time-series data stored in each current archive is an exact duplicate of the other current archives in the collective. PI ProcessBook.3. Many interfaces incorporate failover mechanisms that allow for redundant data collectors.3 Interface Buffering and Failover The interface buffering service writes time-series data directly to all members of the collective. and on day 3 you will explore implementing interface failover. 5.4 Clients PI clients (for example.3. and PI AF are all capable of redundancy or replication. PI DataLink) can automatically switch from the primary PI Server to any of the replicated servers in the event connection to the primary is unavailable. 5. buffering data temporarily for those unable to receive data for a period.5 Other Components The remaining major components in the PI environment such as PI ACE. On day 2 you will be exploring interface buffering. PI WebParts. Process Control Network Primary PI AF Server ACE Secondary PI AF Server Primary PI Server Secondary PI Server ACE Interface Interface SharePoint with PI WebParts data source Page 60 .PI System Architecture. PI OPC Server. assuring that all clients always have read-access to PI data. Planning and Implementation 5. The ARC Advisory Group is a leading research and advisory firm for automation technology in industry. then required site data (such as KPIs) can be presented (with history) at the corporate level. The file can be found in the training materials or obtained from the ARC Advisory Group. Page 61 . The PItoPI interface allows the rollup of this data by copying data from one server and making it available on another server. When a corporate PI server is connected via the PItoPI interface to remote site PI Servers. Dissemination of selected data from the remote sites via the corporate PI system to the corporate users becomes possible. it is possible to combine data from widely distributed PI sites to a corporate PI System. 5.PI System Combinations In addition to the complex scenario presented above.6 Various Historical Options Please take a few moments to review Fault Tolerant Platforms for Manufacturing Applications (filename \DVD\Documentation\2001-038M&E.3. This paper was published by the ARC Advisory Group in September 2001. This allows corporate access to designated data on the distributed site PI collectives without interfering with the site servers.pdf). infrastructure and enterprise solutions. Planning and Implementation 5. When do you use 64bit vs. Questions 1. What method of visualization is NOT recommended? 5. or to discover a new insight.4 Group Questions –Planning and Preparation Stages: Wrap Up The following questions are intended to reinforce key information. Your instructor may choose to have you try to answer the questions on your own or have the group answer them together out loud. List the PI software components that make up the PI System 2010 server. What software platforms are supported? 2. 3. When would you install the PI Server and PI AF Server on different computers? Page 62 .PI System Architecture. 32bit kits? 4. If you require any prerequisite applications. Log on as Administrator (or with administrative privileges). Obtain your PI Server License File. The version you use is up to you. You now should know the pros and cons of each. Installing the Servers Objectives 6. the account must have write permission on the AF server. Changing the clock after installation will cause problems. Validate that the user has the correct permissions. In some cases you will get an error.1 Review pre-installation check list Describe the steps to obtain a License File Know the steps for installation the PI/AF servers Identify the directory structure of PI Start and stop the PI Server Pre-installation Checks It is critical that you perform the pre-installation checks. all clocks should be synchronised from a network time source.Installing the Servers 6. Always check the PI Server operating system clock when installing any PI Server. Update Windows. The appropriate OSI pre-requisites file must be installed on the computer before the AF server is installed Install Microsoft SQL Server. and in others the installation will stop. Page 63 . you will need to install them before the installation proceeds. A properly updated Windows Operating System will have the prerequisites. In your work environment. The installer must be either the administrator or member of the local administrators group. In addition. You get this from the tech support site. Ensure the clock on each machine has the correct time and it is in the correct time zone. view the PI Server Manifest to verify the server details and then download the Machine Signature File (MSF) Generator Utility to create a signature file that identifies some characteristics of the computer for licensing purposes. you must copy the generator utility (MSFWinGen. for example) then the license activation file will match the laptop Page 64 . If you generate the MSF on the wrong computer (on your laptop. To generate the Machine Signature File (MSF). run the utility on the VM.exe or MSCmdGen. This license file controls which applications can run on the PI Server and displays running parameters.Machine Signature File (MSF) generated When the license activation file is generated. 1 – Download Generator Utility 3– Upload MSF 4 – License File Download 2 .exe) to a local disk on the PI Server computer and then run the utility. If the PI Server is on a virtual machine (VM).PI System Architecture. Planning and Implementation 6. such as the point count limit.2 License File Activation A license activation file must be generated before the PI Server is installed. The OSIsoft Technical Support Web site provides an online tool called My License Activations (MLA) that allows you to generate your site-specific PI Server license activation file. the server will not run as expected. Page 65 . CD. This “conditions” the server ready for installation of the PI software. If you install PI Server on a different computer or VM. refer to the various installation and user manuals for the specifics. It can be on a flash drive.3 PI Server Installation The OSI prerequisite software needs to be installed first. The license file must be present during the installation. The general steps involved in the PI System installation and configuration are as follows. You will of course. 6. or any media that can be read by PI Server during installation. The setup program copies the license file to the PI\dat directory during installation and the original file will no longer be used. Consult the PI Server License Activation Files section of the PI Server 2010 SP1 Installation and Upgrade Guide for full details.Installing the Servers computer. The SQLexpress software has been installed ready for the AF Server. if your PI Server will have 5. If you have more than 50. and (RAM / 3) for 64-bit is a safe upper limit for archive files.4 Gathering The following information will be requested during the installation: Location of the PI server license file – ask your instructor. Therefore. run the 64-bit PI Server on 64-bit Windows OS and set the archive size to 4-8 KB x the total number of points. 256MB for 32-bit systems. but can use all of the RAM on 64-bit systems. It is important to note that the defaults are rarely used in a typical installation. and an archive size cannot exceed 2 TB.PI System Architecture. since most installations are not on the C drive. The FSC is capped at approximately 1GB on 32-bit systems. or site. the PI Server will write to and/or read from the 2-3 most recent archive files.000 points or less then you can safely use the default value (currently 256MB). This is because at most times. As a rule is thumb your Snapshot Event Queue should be set to half of the archive size. with the following consideration on memory resources. Page 66 .000 points. Planning and Implementation 6. You should select a size so that at least 2 archive files can fit in the Windows File System Cache (FSC). User.4. and company name PI SDK path (default: c:\Program Files\PIPC) PI server path (default: c:\Program Files\PI) Data archive path (default: c:\Program Files\PI\dat – use C:\Program Files\PI\ARCHIVES) Default archive size (see below). Tip Many people size their archives based on a size that is convenient to use with their desired backup media. However.1 Archive Sizing Your archives must be sized with at least 2KB for each point in the system. 6. please take a few moments to note the computer names for each computer. Primary: Secondary: PI Servers: Note:For the purposes of this course the AF will be installed here. The AF server used will be the one installed on the same computer as the primary PI Server. The PI OPC DA Interface will be configured on two interface computers and an OPC Simulator will be installed on one of the interface machines. OPC Interfaces: OPC Simulator: Page 67 . Depending on the size of the class.HA Step 1: Planning and Hardware This solo or group activity is designed to maximize learning in a specific topic area. Problem Description You need to organise your Collective. Two (2) computers will be used to establish the PI Server collective and two (2) computers will be used as the data collector computers.5 Group Exercise .Installing the Servers 6. so you will need to work in pairs. Your instructor will have instructions. Exercise Objectives Understand the computers involved in the Collective. In the table below. Approach This exercise makes use of four (4) computers. the students may be divided into teams. and will coach you if you need assistance during the activity. Find the correct guide and answer the following questions. Exercise Objective To read the AF installation manual in preparation for its installation. One of the guides contains the answers to the following questions.6 Solo / Group Exercise – Explore the AF documentation This solo or group activity is designed to maximize learning in a specific topic area. Problem Description Find the necessary information in order to install PI AF Server. Your instructor will have instructions. Approach The AF manuals are PI Asset Framework 2010 R3 Installation and Maintenance Guide PI Asset Framework 2010 R3 Overview Guide These guides are available in the documentation folder of the supplied files. 1. List the supported SQL Server versions. 2. Can the AF SQL database be created manually? 3. and will coach you if you need assistance during the activity. Planning and Implementation 6. Do end users connect to the SQL Server? Page 68 .PI System Architecture. Page 69 . Your instructor will have instructions. Note: The installation process may install . and done all of the computer checks (clock.) Approach In the installation folder you will find the PI AF Server installation kit.Net Framework 4 then require a reboot. gathered the install kits and license file. You should have validated the prerequisites and Microsoft SQL Server. Make sure the SQL Server is started after installation (some people reboot after running installation kits as a matter of practice).Installing the Servers 6. You may have to use " Run the PI AF Server Setup Program" in PI AF 2010 R3 Installation Guide.7 Solo / Group Exercise – Install the PI AF Server This solo or group activity is designed to maximize learning in a specific topic area. and will coach you if you need assistance during the activity. Exercise Objectives Install the PI AF Server Problem Description You are ready to begin the PI System installation. etc. Install the PI AF Server. . you will find the PI Server installation kit. You may have to use "Install PI Server on a Single Computer" in PI Server 2010 Installation and Upgrade Guide. Edit this file to include your interfaces on the PI Server and any other commands you want to execute on start.bat. Your instructor will have instructions. It’s time to install your PI Server.bat Tip Page 70 This file calls the script pisrvsitestart. Planning and Implementation 6. start the PI Server using the following batch file: \PI\adm\pisrvstart. which contains commands for all of the interfaces and other site-specific applications. Note: The PI Server install is not complete until the PI Server is started for the first time! Some “run-once” functions are accomplished on the first start. Approach In the installation folder. Exercise Objectives Install the PI Server Problem Description Your PI AF Server is installed. Install the PI Server. and will coach you if you need assistance during the activity.PI System Architecture.8 Solo / Group Exercise – Install the PI Server This solo or group activity is designed to maximize learning in a specific topic area. If the PI server is not running. Installing the Servers 6.9 Directed Exercise – Explore the PI Server Directory Structure In this part of the class, you will perform a learning activity to explore the different concepts presented in this chapter or section. You may be invited to watch what the instructor is doing or perform the same steps at the same time. Your instructor will have directions. Activity Objectives Become familiar with the PI directory structure. Approach Examine the directories under \PI, \PIPC x(86) and \PIPC. ADM - administration tools BIN - program files DAT - data files (point DB, etc.) LOG - message log files SETUP -additional install kits 1. Where are the start and stop files for the PI Server? 2. Where is the license file? 3. Where is piartool.exe (a most useful command line tool)? Page 71 PI System Architecture, Planning and Implementation Within the PI SDK Installation Paths, there will be many of the following directories in both the 64-bit directory and the 32-bit directory. Which ones you have specifically will depend on what is installed on the machine and the license details. INTERFACES - PI interfaces DAT - configuration and log files BIN - PI API program files and tools ProcessBook, DataLink, etc. 4. What is in the \SMT directory? The following PI interfaces (data collectors) are installed on the PI Server: PI Random data simulator interface. PI Ramp Soak data simulator interface. PI Performance Monitor interface (basic version is limited to 512 points). PI SNMP interface (basic version is limited to 32 points). PI Ping interface (basic version is limited to 32 points). The last three are not configured. Page 72 Installing the Servers 6.10 Solo / Group Exercise - An Exploration of the PI Server Subsystems This group activity is designed to maximize learning in a specific topic area. Your instructor will lead you through an explanation of the services, as well as your first look at SMT. Exercise Objectives Become familiar with the PI services. Problem Description You want to discover the make-up of the PI Server. Remember, the PI Server is not one application running, but a concatenation of many applications that all operate in harmony. Use SMT to check the PI system services. Approach Navigate to Start > All Programs > PI System > PI System Management Tools Then select PI Services as shown above. This will show: Page 73 PI System Architecture, Planning and Implementation Some the subsystems have a red icon. Why? Tip An alternative way of checking the subsystems is Start – Run.. then type services.msc and press Enter. Under normal operation of the PI Server, The PI Shutdown Subsystem should not be started even if the start-up type is set to automatic. This service automatically starts and stops when the PI server is launched and when it is shutdown. What other services installed by default with a manual start-up type and not started? Page 74 Installing the Servers In the space below. PI Network Manager PI Message Subsystem PI License Manager Page 75 . describe the function of the subsystems. You will have to reference "Introduction to the PI Server" in PI Server 2010 Introduction to System Management. PI System Architecture. Planning and Implementation PI Update Manager PI Base Subsystem PI Snapshot Subsystem PI Archive Subsystem Page 76 . Installing the Servers PI Backup Subsystem Page 77 . 1 PI System Navigation basics Objectives 7. It maintains a list of known PI Server(s) with which the machine can communicate. PI System Navigation 7. Planning and Implementation 7. test the connection to the PI Server.1.PI System Architecture. Page 78 .1 Understand how to connect to different PI Servers Become familiar with the PI SMT console Understand PI Time Format Find PI Points using the Tag (Point) Search View and edit data Connect to PI and Manage the SDK Known Servers Table Now that we have confirmed that PI is started. The PI Connection Manager is included in the PI SDK and as such is common to most applications that connect to a PI Server. This is why. Your instructor will have directions. change your default server.PI System Navigation 7. even if you have never configured a PI Server. at least one should appear in your PI Connection Manager. or change the PI user you are trying to log in as. To add a PI Server. Click in the checkbox next to your PI Server to connect and validate your connection. In this dialogue box you can add and remove connections to PI Servers. select Server > Add Server… Page 79 . it will display all of the PI Servers that have been configured in the Known Servers Table (KST). Activity Objectives Show new users a method of connecting to the corporate PI Server. You may be invited to watch what the instructor is doing or perform the same steps at the same time. Note: The first time the PI SDK is installed a default PI Server is requested. you will perform a learning activity to explore the different concepts presented in this chapter or section. When the dialogue box is invoked.2 Directed Exercise – Connect to a PI Server In this part of the class. Approach Navigate to Start > All Programs > PI System > About PI-SDK Click on Connections in the PI-SDK branch. connected PI client. Although most PI SMT plug-ins can be run remotely and will perform these server functions from any authorized.PI System Architecture. It is recommended that your download the current version of the tools as they change regularly and are included with your OSIsoft Software Reliability Program (SRP). some PI SMT plug-ins require local access to the server’s registry and some will require an access to the Windows services of the remote PI Server. and are included with every PI Server.2. Page 80 .1 More on PI System Management Tools (PI SMT) The PI System Management Tools (PI SMT) are a set of Microsoft Windows-based graphical applications used to manage the PI System from client PCs. 7. Planning and Implementation You will need to know the following when creating a new PI Server connection: Network Path: either the PI Server IP address or hostname Confirm: validates the connection at creation time Connection Type: PI3 Port Number: 5450. security related messages and other server level activity. PI Ping. Verify the license file.PI System Navigation 7. Page 81 . You may be invited to watch what the instructor is doing or perform the same steps at the same time. interfaces. PI Random Simulator and PI Ramp Soak Simulator interfaces.3 Directed Exercise – More PI SMT Plug-ins In this part of the class. Use this to view start-ups and shutdowns of the whole PI Server and parts of the PI Server. Your instructor will have directions. Find the number of PI Points you are licensed for using the Licensing SMT plug-in. and users connecting to the PI Server’s PI Network Manager. View the server logs for the first time. Browse the recent PI Server message logs using the Message Logs plug-in. These include messages from the PI Performance Equation Scheduler. The Message Logs plug-in shows messages written by the PI Server subsystems and messages specifically written back to the server by PI API and PI SDK applications. Approach Check the version of your PI Server by using the PI Version SMT plug-in. to identify systems. PI Performance Monitor. Activity Objectives Check the version of the PI Server.log includes messages from any PI interfaces running locally on the PI server machine as well as the PI Server applications. you will perform a learning activity to explore the different concepts presented in this chapter or section. The PI Server’s pipc. Your instructor will have directions. go to the Data – Current Values area and show all point values and time stamps.5 Directed Activity – Viewing Your Data You are invited to perform the same steps at the same time. Activity Objectives Observer current values in SMT Approach In SMT. Each event has a value and a timestamp that indicates the collection time of the value.4 Time and the PI Server The PI Server stores data in the form of events. Page 82 . 7.PI System Architecture. Planning and Implementation 7. you may be prompted for the default PI Server. Your instructor will have directions.PI System Navigation 7. you should find the installation kit for PI ProcessBook. your instructor will show you how to validate a connection to the PI Server. as discussed in the next few sections. Page 83 . discuss PI time and perform a tag search. interactive graphical displays featuring real-time PI data. Activity Objectives Install PI ProcessBook Create a simple trend to examine a tag’s data Approach In the same location that your instructor directed you to earlier. you will not have to configure security.6 Directed Activity –PI ProcessBook You are invited to perform the same steps at the same time. You will create a simple trend with a “Random” tag. In this and later activities / exercises we will use PI ProcessBook to examine our tags for proper function. If you install the application on the PI Server. PI ProcessBook is an easy-to-use graphics package that allows users to create dynamic. It is often used in control rooms to monitor a process in real-time. After the installation. During the installation. The displayed time is interpreted by looking at the time zone on the client or server and re-converting this data time into a local time. only the current DST transitions are known. By default. To make sure that past transitions between daylight savings times are correct. Any adjustments for time.PI System Architecture. Note: It is important that all of the computers involved in collecting data (PI Server. PI stores timestamps as the number of seconds expired since January 1. Interfaces normally synchronize their timestamps to the server time basis and then post the time as UTC when stored. such as time zone or Daylight Saving Time (DST). interface computers.7 Daylight Savings Time The PI Server stores all values with a time that is converted to UTC (Universal Coordinated Time). Page 84 . and client computers should all have their time zones and times set correctly and synchronized. Note: Situations where some computers change their clocks when others do not can cause data loss. etc. the PI Server cannot handle the time difference and discards the data. all computers either change their clocks twice a year at the same time or they do not. If the PI interface time is more than ten minutes ahead of the PI Server.tz file on your PI Server. as it is considered a future event. For most current interfaces. (was Greenwich Mean Time (GMT)). This is determined by a setting in the client tool. 1970 GMT. you need to update the localhost. Automatic DST changes will not cause a problem when all computers observe the same rules.) have their operating system clocks set correctly. That is. As the PI clients and PI Server know what time zone they are in. They are provided by the operating system. are made by the local machine clock of the user looking at the data. DST and time zone differences are properly considered when storing data on the PI Server. Planning and Implementation 7. Display sequencing and math operations are performed on the UTC basis. PI servers. This means that each day of the year has exactly 24 hours. As a result. so data can be viewed in either Server Time or Client Time. events are sent to the server with UTC timestamps. The PI Server automatically adjusts data according to daylight savings time transitions. interface computers. If the time part is omitted. 7.PI System Navigation To verify that the DST rules. Midnight is at the start of the day.1 PI Time Syntax Absolute Time (a specific point in time) * : (NOW) t : 00:00:00 on the current day (TODAY) 18-Jun-12 16:00:00 Using the full PI Time format (dd-mmm-yy HH:mm:ss.0000). if the date part is omitted. Expression Meaning 13 00:00:00 on the 13th of the current month of the current year 13-Aug-12 00:00:00 on that date 8: 08:00:00 on the current date 25 8 08:00:00 on the 25th of the current month of the current year 21:30:01.02 9:30:01. You can also run pidiag -tz -dump -brief in the \PI\dat folder to list all transition times. it will default to the current day.7. it will default to midnight.0200 PM on the current date Page 85 . run pidiag -tz in the \PI\adm folder to check the time zone and DST transitions table of your PI Server. Saturday. Sunday 00:00:00 on the most recent occurrence of that day of the week Relative Time (time is offset from another time) + 11h : + 11 hours Combined Time (using Absolute and Relative Times together) t + 11h : today + 11 hours Relative Time Units of Measure Hours (h) Minutes (m) Seconds (s) Weeks (w) Days (d) Years (y) Months (mo) There is no default time unit. Thursday. For example +2. Page 86 .5m. Minute and Second intervals can use fractions.osisoft. Only Hour. go to techsupport. For more information on DST.PI System Architecture. Tuesday.com and look for Daylight Saving Time under the System Managers Resources section. Wednesday. see the PI Server 2010 Reference Guide.5h or -0. Friday. Planning and Implementation Common Abbreviations: Symbol Meaning * Current time (NOW) t 00:00:00 on the current day (TODAY) y 00:00:00 on the previous day (YESTERDAY) Monday. For more information on time and PI. PI System Navigation 7. Express the following times in valid PI combined time: a. Questions 1. Wednesday-2d b. The 4th of the current month at 16:00 c. 12 hours ago Page 87 . 1 6: c. *-30m 2. Determine the “real” dates and times indicated by the PI Times: a.8 Group Recap Questions The following questions are intended to reinforce key information. or to discover a new insight. Today at 6:00 AM b. Your instructor may choose to have you try to answer the questions on your own or have the group answer them together aloud. y+8h d. These people will have to use some other way of finding the required points.PI System Architecture. BA:Phase. Planning and Implementation 7. we opted to install the default points. First. CDEP158. we will need to learn to find points using the Tag Search tool. BA:Level. In order to be sure that all parts of the server are working correctly we would like to see both current and historical data.9 Find Points using Tag Search Perhaps the best way to verify that the PI Server is working is to look at data. Most of the point searches will be filtered in one of three ways: Tag Mask This is a mask for the point name. Page 88 .1 Basic Search A point search is one of the most common functions that users will perform. however.1. CDT158. BA:Temp. Look at data from these points to verify that the server is up and running correctly. 7. then you are all set.1. The following 10 simulator points were then created during the install.1. BA:Active. When we installed the PI Server.9.1. Most data that is displayed in a display.1. BA:Conc. CDM158. SINUSOIDU We can use these points to test PI and not affect any real data. report or web part will come from a PI point. If your organization has a convenient naming convention or you are very familiar with the points in your plant. However. SINUSOID. people unfamiliar with the point nomenclature may not have that luxury. So if you know what PI interface you want data from. but it requires some knowledge of the PI System and how the interfaces have been set up. This is of more use to the PI System Manager. but not flow_down_under.PV but the descriptor might helpfully be Reactor 65 Operating Temp. but you are not sure what the point names are.bat file) of an interface. or in the interfaces section of %OSI in the module database. The downside to searching by descriptor is that it compares text strings and can be compute intensive. 7. Note 1: Search criteria are not case sensitive. Page 89 . in the PI ICU. You can find the point source of a specific PI interface by looking at the start up script file (. Hopefully a descriptive phrase has been used in the point descriptor attribute when defining the point. a temperature point might be named TC365674A.. flow_meter2 and flow_down_under. Use * to replace any number of characters like in this example using the point mask search criteria: flow* will return points flow_meter1.9. Point Source PointSource can be helpful.2 Tag Search Strategies Wildcards can be used in any of the above searches. Use ? to replace one character as in this example using the point mask search criteria: flow_meter? will return points flow_meter1 and flow_meter2. you can bring up a list of all of the points that are associated with that PI interface. E. but it is a most useful attribute for finding the appropriate points when used.PI System Navigation Descriptor Descriptor is not a required point attribute. searching with tag mask = flow* and point source = OPC. For example. Each PI interface will be labelled with a specific point source.g. Note 2: Search criteria can be combined. g. all points with point source of R. Approach Try some point searches using different criteria (e.10 Directed Exercise – Point Search In this part of the class. all point names that begin with BA. etc. Page 90 . Activity Objectives You need to familiarize yourself with the principles of point searching. Use Advanced Search to find any points with the attributes Zero > 0 and Span > 100. you will perform a learning activity to explore the different concepts presented in this chapter or section. Planning and Implementation 7..).PI System Architecture. You may be invited to watch what the instructor is doing or perform the same steps at the same time. Your instructor will have directions. 10. From the Tag Search window.PI System Navigation 7.10. 7. Page 91 . if a measurement needs to be read from a particular device in a network.2 Use PI SMT to View and Edit Data To look at point data you may use PI SMT. Current Values: displays the snapshot value of multiple points in a real time screen. and other attributes can be used to store character string information. such as the name (or tag) of the point. Certain point attributes can be used to define data type information such as integers and floating-point numbers. You can also get the current values of any point by clicking the Pt. you can access all the attributes of a point as well as the current value by clicking the Pt Attr… button. This brings up a window updated in real time with the current values of the selected points in the Tag Search windows. The Data section in the PI SMT console contains 3 plug-ins to view the data from PI points and identify points that are not working properly. For example. Values… button. the IP address may be stored in a point attribute. Archive Editor: displays and allows you to edit historical data for a point.1 Point Attributes / Point Values All of the information that is required to gather data from a particular data source is stored within the context of a PI point by means of point attributes. Stale and Bad Points: displays points that have not received updates in a specified time range or are in an error state. Calc Failed. etc. Page 92 . Planning and Implementation The Current Value plug-in allows the system manager to look at the current value for any points they have access to on any PI Server to which they can connect. The plug-in also allows the user to choose whether they will have those values updated as new values come in to the PI Server. The Stale and Bad Points plug-in allows you to identify points that are not working properly. such as any states from the System digital state set (PtCreated. Shutdown. I/O Timeout.PI System Architecture.). You can search for points that have not received any snapshot values for a certain period of time and points that have a bad snapshot value. Approach Use the PI SMT data plug-ins section to examine point values. Problem Description You want to look at the values for a production point and you have no client tools (PI ProcessBook or PI DataLink) available on your machine. Page 93 . Find the current value for point CDT158. Exercise Objectives Display the current value for the point CDT158. and the archived values for the last 3 hours. Your instructor will have instructions. and will coach you if you need assistance during the activity.11 Exercise – Data Section in the PI System Management Tools This solo or group activity is designed to maximize learning in a specific topic area.PI System Navigation 7. This indicates a problem with the Archives. It performs a similar action as a clutch in an automobile. the Snapshot Event Queue preserves that data. Planning and Implementation 7. Tip Page 94 Because it is a buffer. It is analogous to the Buffering mechanism. In the case of the PI Server. This behavior repeats until the available drive space is exhausted. Tip The files created by the PI Buffer Subsystem are the same format. the Snapshot Event Queue will contain data at any time but it should not slowly build. it is a good idea to configure the Event Queue to reside on a different physical drive than the Archives. meaning that when one fills another is created. when the Archive is busy or cannot accept data for any reason. and can even be moved manually to the PI Server and processed like an Event Queue. separating the engine and transmission when they are at odds. . There is no tool for viewing the contents of the file.PI System Architecture. Under normal operation. The Event Queue is a rolling file. only that there are events present.12 What is the Event Queue? The Snapshot Event Queue is located logically after the Snapshot and before the Archive. Stop the Archive Subsystem simulating a failure. Activity Objectives Monitor the Event Queue for problems Approach Open PI SMT.PI System Navigation 7. Your instructor will have directions.13 Directed Activity – Examine the Event Queue In this part of the class. Page 95 . You may be invited to watch what the instructor is doing or perform the same steps at the same time. you will perform a learning activity to explore the different concepts presented in this chapter or section. Observe the changes. 2 There is only one Primary Archive Each archive has a start and an end time.” Archives have the following characteristics: They are fixed sized files The PI Server only writes current values to one file at a time Each archive has an associated Annotation file 7. If no empty archive exists. Dynamic Archives should only be used for troubleshooting and reprocessing of archives. In the example shown below.PI System Architecture. Therefore. Older “full” archive files are used less frequently and can be migrated to a storage device.14 PI Archives Defined The data tables that the PI System stored data within are called “Archives.14. an empty archive will be selected to be the new primary. The process of initializing a new primary archive is called “shifting. Planning and Implementation 7. they are created at a fixed size and the entire file is allocated upon creation to minimize the potential of fragmentation on disk. Tip The Primary Archive should always live on the PI Server. Dynamic archives are files that grow as they are filled.14.” The next primary archive is determined by: If automatic archive creation is enabled. When it is approximately 98% full.1 Fixed Files When you create archives. the archives are separated by time seams. When an archive is initialized the timestamp of the first value sets the start time. You have the option of creating dynamic archives. you will notice that this means your data will be overwritten if you do not create sufficient new archives or enable automatic archive creation. When automatic archive creation is disabled: If it exists. then the oldest archive will become the primary and its existing data will be overwritten. These seams are transparent to the user. 7. a new file is initialised (in case some data comes in late). All of the data between those two points in time is contained in that file. Page 96 . the PI Server will create a new PI archive and use it as the new primary archive. empty archives.PI System Navigation Using the PI SMT Archive Manager.3 The Annotation File Each Archive has an associated annotation file. 7. you can set an archive to not be “shiftable.4 Setting Up An Archiving Strategy The most important rule about Archives is to have a strategy for how you manage your data.” Tip To prevent overwriting archives: Turn on automatic archive creation or keep adding new. This file is important to keep with the archive file. Page 97 . Have plenty of disk space. Since the PI System will either create an archive file as needed. or use an existing empty archive.14. you have to determine which method you will use: Auto Archive Creation Create Empty Reserves You can use PI SMT to create and manage archive files. Set the archive as non-shiftable 7.14. It contains non-time series data. 7. Planning and Implementation Piartool is a command line tool to manage archives in the PI system. Page 98 . They will be the same size as the primary archive.14. You enable automatic archive creation with the Archive_AutoArchiveFileRoot parameter in the Archive tab of the Tuning Parameters PI SMT plug-in.5 Automatic Archive Creation Archives can be created automatically. You simply enter a valid file path and file name prefix and the parameter is turned on. This feature is not enabled by default.PI System Architecture. ext] Ex: auto_1210260306.arc • 1: [root]_YYYY-MM-DD_HH-MM-SS[. Force an archive shift. Possible values are: • 0: [root]_D_Mon_YY_H_M_S[.ext] Ex: auto_2008-05-08_11-03-52. Create a new empty PI archive with the desired size. fixed size archives that have been created. The default is . you need to: 1.ext] Ex: auto_8_May_08_11_23_17. To change the size of the automatic archives that are created. The default value is 1. You must monitor your disk space if you use this feature. 4. as this will keep the function enabled. The extension of the archive file can be changed with the Archive_AutoArchiveFileExt tuning parameter.arc. Disable automatic archive creation by setting the Archive_AutoArchiveFileRoot parameter to a blank value 2.arc • 2: [root]_UTCSECONDS[. To disable the automatic archive creation. The system will return to the old behaviour if you run out of available disk space or if the path does not exist for the automatic file creation. the PI Server will no longer use any empty.PI System Navigation Once this parameter is set. Do not set to the default value of zero (0). 3. clear the value and save the entry. This will shift into the newly created archive with the desired size. Re-enable automatic archive creation by resetting the Archive_AutoArchiveFileRoot parameter.arc Page 99 . The format of the archive file suffix can also be changed with the Archive_AutoArchiveFileFormat tuning parameter. PI System Architecture. Planning and Implementation 7. empty archive Configure Auto Archiving Force an archive shift Problem Description You need to learn to use the PI SMT Archive manager to manage your archive files. Your instructor will have instructions. What is the name of the current Primary? 3. Force a shift to test. Approach Open PI SMT and connect to your PI Server.15 Solo / Group Exercise – Manage Archives This solo or group activity is designed to maximize learning in a specific topic area. Exercise Objectives Determine the predicted date for the next regular archive shift Create a new. How many archives are there? 2. Which will be the next archive to be Primary? Create a new. and will coach you if you need assistance during the activity. Configure Auto Archiving in the Tuning Parameters to automatically create new archive files in the C:\PI_Data\Archives\ folder (remember to create the folder first). empty archive of the same size as the current primary. Examine the archive statistics for the existing archives and answer the following questions: 1. Page 100 . What are the start and the end times? 4. PI System Navigation 7. It is possible for someone in a role on the SQL Server.1 Security The security models may be different. 7. not to be identified as having write access in the PI Module Database. The AF Link mechanism keeps the PI Module Database and the PI AF data structures in sync with each other. PI AF uses the Active Directory objects and the security roles as defined in the Microsoft SQL Server.16.16 The AF Link Mechanism. It is possible to create an Element Attribute in PI AF that is not valid in the PI MDB (only in the sync-ed Element). There is one main reason for this: Applications that use the PI Module Database for structure but we want people to build those structures in PI AF (not to use the PI Module Database anymore) This is sometimes and issue for two reasons: 7.16. The PI Server has piusers and pigroups and can have mappings to the Active Directory. You should get into the habit of using the PI AF database only. In these cases they are labeled as such: Tip The PI Module Database is being deprecated. Page 101 .2 Data Types The PI AF has data structures that do not exist in the PI Module Database. These cannot be used in applications that use the PI MDB. Planning and Implementation 7. Activity Objectives Check your functioning of the PI Module Database .PI System Architecture. Page 102 . . From the information displayed in the tool. You may be invited to watch what the instructor is doing or perform the same steps at the same time. determine how often the sync check is made. Determine if the servers are currently in sync. you will perform a learning activity to explore the different concepts presented in this chapter or section.17 Directed Activity – Validate the PI AFLink Mechanism In this part of the class. Your instructor will have directions.AF Link Approach Open PI SMT. If you have any questions please contact OSIsoft Technical Support! The Tuning Parameters are found and can be adjusted in PI SMT.2 Archive_LowDiskSpaceMB If your PI Server is installed on the same drive as your Operating System or you have a very limited drive space available for your archives. You must have write access to the PI TUNING table. Turning Auditing ON is as easy as setting the EnableAudit value to a negative one (-1) and then restarting the following subsystems: Snapshot Archive Base 7. and most of our early customers did not need the feature. what they do.18. The defaults are all set to the “most common” PI System but in most cases. If you want auditing you have to turn it ON. and how they are often adjusted.PI System Navigation 7. The tuning parameters in this section are defined in PI Server 2010 System Management Guide. 7. What follows are the most common tuning parameters. yours will be unique in some way. you can protect your system from running out of hard drive space by setting this parameter.18. but it is not enabled automatically.18 Common Tuning Parameters Tuning Parameters are similar to adjustment dials for the PI System. Tip In general you should not lower or reduce a value unless you have a good reason.1 EnableAudit The PI Server has a robust audit mechanism. This could negatively impact user access. Page 103 . It is not enabled because the process does take a certain amount of computer resources. version 2010. This parameter prevents automatic archive creation when free space is less than the specified value.4 Archive_MaxQueryExecutionSec and ArcMaxCollect If you have very expensive queries you may need to limit either. 7.18. Example: E:\PIArchives\SYD_PRI (where SYD is the site abbreviation and this was the primary of the collective). 7. This is the minimum amount of free disk space to leave on the volume of the primary archive. . The calculation is as follows: Archive_LowDiskSpaceMB = (‘Archive Size’ x 3 ) + 2.18.PI System Architecture. The integer value set is the number of seconds allowed for a query. You would only use these if you were having performance problems due to excessive or expensive queries. the time allowed for a query to execute. it must be added manually. There are also tuning parameters to set the file name and extension but these are not often used. In that case. Planning and Implementation In a PI Server with ample disk space. You must specify a valid path where the archives will be created and the file name prefix.000 Where the result reserves 3 times the archive size plus 2GB Tip This parameter is not shown by default in System Management Tools. Tip We recommend you use a name that identifies the PI server name and primary or secondary (if HA). For example: Archive_MaxQueryExecutionSec = 300 Page 104 would limit a query to 5 minutes. Archive_MaxQueryExecutionSec has no default value. this is not necessary. or the amount of data that can be returned to the user.3 Archive_AutoArchiveFileRoot This tuning parameter does two things: it enables Auto Archive Creation and defines the path for the archives. the PI Server will begin writing data to queues. 7. This parameter determines if that idle connections are closed after a specific time in seconds. You will have to restart the Snaphot Subsystem to change the location or size.6 Snapshot_EventQueuePath By default.7 Snapshot_EventQueueSize The recommended size is one-half of your archive size. but truncates them.5 MaxConnIdleTime By default.18. 7. especially if the scan time is longer.18. the Snapshot Event Queue is installed in the same folder as your archives. This number can be far greater than other applications like PI ProcessBook or other client tool. This can be dangerous.8 TotalUpdateQueue and MaxUpdateQueue These are common parameters adjusted when the PI Server is the source server for a PItoPI interface. For example: MaxConnIdleTime = 86. In this situation the source PI Server can queue up a great number of events.PI System Navigation Tip Instead of limiting queries try to work with your users to write more efficient or better queries! ArcMaxCollect has a default value of 1.400 would disconnect idle connections after 24 hours. If you change your archive size you should change your Queue size as well.18. Tip The Snapshot Event Queue setting only takes effect on startup. It will be easier to manage the files if they are not mixed in with the many archive files. Page 105 .5 million events (this was lower in earlier versions). It is best to set this to something reasonable. 7. because dropped connections will stay open the on the server indefinitely. 7.18. This does not prevent the more expensive queries. there is no limit to how long an idle connection will be kept open. Adjust the MaxUpdateQueue if think you will have more than 50.PI System Architecture. Planning and Implementation This parameter adjusts the maximum number of events in Update Manager for each and all consumers. Tip Page 106 Some have used the following formula: (20 + 2 * ‘Number of Interfaces’ ) * (‘MaxUpdateQueue’) . Adjust the TotalUpdateQueue if think you will have more than one million events queued up at any time.000 events queued up between interface reads. 1 Define a PI Interface Identify the basic components of an interface installation Discuss the variety of architecture possibilities Describe how to connect interfaces in a secure way Install and configure an interface Configure the basic interface parameters The Interface Defined The PI Interface plays a critical role in the PI System. Connects to the data source Timestamps the data (or ensures the data received is stamped at the source) Formats the data correctly Send the data to the PI Server PI ICU Data Source Interface Buffer PI SMT Tag Configurator PI Server Page 107 . Understanding the Common Setup of PI Interfaces Objectives: 8. 3.Understanding the Common Setup of PI Interfaces 8. 2. It performs the following tasks: 1. 4. PI System Architecture, Planning and Implementation 8.2 Directed Activity – What’s Installed In this part of the class, you will perform a learning activity to explore the different concepts presented in this chapter or section. You may be invited to watch what the instructor is doing or perform the same steps at the same time. Your instructor will have directions. Activity Objectives Identify the PI interface components. Approach Every Interface has at least four components that are installed on the interface computer (many interfaces have additional files – refer to the manual for details). The image below illustrates the basic components for the PI Random Interface. Write the functions next to the icons. Page 108 Understanding the Common Setup of PI Interfaces 8.3 Interface Installation Considerations 8.3.1 Where do you install the Interface? Several architectures are possible with interfaces. Examples are shown below: Having seen the above recommendations, what would you say was the least difficult configuration? Page 109 PI System Architecture, Planning and Implementation 8.3.2 Interface Node Clock Before you install and configure the interface, make sure that the clocks on the Interface machine and PI Server machine are relatively close. They do not have to be exact. Tip 8.3.3 An interface that is more than 30 minutes “off” the server clock will not run, and data that is sent more than 10 minutes into the future will be discarded! DST Rules It does not matter so much that your computers obey DST, as long as the servers and your interfaces are configured the same way and observe the same rules! Page 110 Understanding the Common Setup of PI Interfaces 8.4 Directed Activity – Interface Syntax Dissected In this part of the class, you will perform a learning activity to explore the different concepts presented in this chapter or section. You may be invited to watch what the instructor is doing or perform the same steps at the same time. Your instructor will have directions. Activity Objectives Learn the interface startup file syntaxes Approach As a class, navigate to one of the startup batch files for the default Random interface. Edit the file to open it. The elements in the startup file are called “switches.” You are allowed and encouraged to open an interface manual to answer the questions. Parse the file to answer the following questions: 1. What does /HOST mean? What formats are acceptable? 2. What does the switch /ID do? 3. What does the switch /PS refer to? 4. What is the connection between /ID and /PS? 5. What is the /F switch used for? What formats are acceptable? What is an “offset” and what is it used for? Page 111 It is possible to rename a point while preserving the historical data associated with it. There are many ways to create points in the PI Server. in which case archived data is no longer accessible. Throughout the course. Some attributes are system assigned and cannot be changed. This tool allows the system manager to set the attributes for each point individually during PI point creation.PI System Architecture. we will show you the most common. The Point Builder plug-in for PI SMT is a graphical tool that allows the user to create and edit PI points. Creating and Managing Points Objectives Build and edit points with Point Builder Describe a digital state set Create a digital state set Create digital state points Build and edit points with the PI Tag Configurator add-in to Excel. Now we will dive deeper into them. One tool often used to build and edit tags is Point Builder in PI SMT. Planning and Implementation 9. Understand use and building of IO Rate Tags Earlier in the course. and allows you to edit them afterward. It is also possible to delete a point. we defined a PI Point. Page 112 . Tip Instrument Tags are sometimes case sensitive! Copy and paste this information directly into PI SMT or PI point Configurator from the PI OPC Client Tool if possible.Creating and Managing Points 9. the Location1 field is used for the interface instance number (/ID) Location4 Typically the field is the scan class number. See the /PS parameter in the interface start-up file. Page 113 . That is why each interface documentation notes what point attributes are used and how. Often it must match the data source exactly! Extended Descriptor Place for detailed query instructions (uncommon). Tip It is a good idea to print out the interface manual and keep it as a hard copy. Point Source Must match the value set in the interface configuration. It is a Microsoft Word document and it is likely you will have to configure an interface on a machine that does not have that application installed! Listed below are the common point attributes and how they are commonly used. Exception Specifications Defines a significant change in value. ALAWAYS consult the interface manual.1 PI Point Attributes and Interfaces Do you remember what was said about always reading the documentation manual? Each interface can use point attributes in a different manner. Instrument Tag Name of the point/location in the source data system. Location 1 Typically. 3. it could be some time to reload the points. This means that depending on the scan class and the number of points that are affected. modified or deleted. Digital Sets are kept in a common table for multiple points to access. You will then use the DigitalSet attribute to store the associated Digital Set name. 9. This is a preventative measure so as to not overload an interface. to make sure they are set according to the parameters in the interface start-up file. interfaces check for point updates. and then presents the text value. If points were added. a Digital Set containing the states of On and Off can be accessed by multiple points in the PI Server. so you can refer to them with upper and lower case. There is a large default set called System. can receive from the PI Server and archive a state from the System Page 114 . These are typically states such as Open/Closed for a valve or On/Off for a switch. check the Point Source and Location1 point attributes. which is a grouping of these states. The Digital State Set must exist prior to the creation of the digital point. If those do check out. This integer is then associated with a Digital State Set. the interface will reload points at a rate of 25 points per 30 second. All points.PI System Architecture. The digital states are case preserving. If the points are not loaded. Planning and Implementation 9.3 Digital State Sets 9.1 Usage of digital state sets Digital points are used to store data sources that have discrete states as can be seen above. double check that you have a valid PI Trust to the PI Server and that it grants write privileges to the desired point(s). does a lookup in the Digital State Set. The log will indicate if the points were loaded by the interface with or without error. While the user is interested in the actual state. including non-digital points. which contains the system error messages and other information. but not case sensitive. but it will display the configured upper or lower case.2 Point Edits Timing Every 2 minutes. For example. PI retrieves the integer value. Whenever the value is requested. PI stores this information as an integer. To create a new Digital Set. so if you would like to have the same Digital Sets on multiple PI Servers.3. 9. PtCreated. will cache the Digital Sets. although is a facility for importing digital states. I/O Timeout.Creating and Managing Points digital states set (Shutdown. select the New icon in the menu bar. copy and paste existing Digital states. you will need to export and import the list of sets and states as a . This field is populated automatically. starting at a value of 0 and increasing by 1 from there. These columns are State Number and State Name. and edit or delete existing Digital States. However. Digital Sets are local to the PI Server. A new table will appear with two columns. The State Number field corresponds to the integer that PI will store in the archive for that digital state. including PI SMT. Under Range. The State Name field corresponds to the states of the data source and is manually entered. most client applications. etc. save the new digital states by clicking on the Save icon in the toolbar. Additions and edits to Digital Sets are immediately available on the PI Server.2 Creating digital state sets You can create Digital States with the Digital States plug-in under the Points section in PI SMT. This means that you may have to exit and restart for any changes to be visible.). This allows you to create new Digital States. You can also right click and select Add Set from the pop-up menu. Once you have fully entered all of your digital states. Over Range. Page 115 . It is not recommended to use or edit the System Digital Set on your PI Server.csv file or copy / paste the state sets from one server to another by opening multiple PI Servers connection inside the plug-in. Descriptor. you are producing paint of different colors. Pointtype=Digital Page 116 .PI System Architecture. Problem Description In one of your plants. Exercise Objectives Create a digital state set and point based on the data source. You are given the following translations: Red 0 Green 1 Yellow 2 Black 3 Blue 4 Use the above information above to build the point with the proper attributes. Pointsource=R. Location4=1.4 Exercise – Create a Digital State Set / Point In this part of the class. Note the important tag attributes and use the following values: Tag. Planning and Implementation 9. You are invited to perform the same steps at the same time. you will perform a learning activity to explore the different concepts presented in this chapter or section. Location5=1. A set point in your DCS holds the information regarding which color at a particular point in time should be produced. Then use PI SMT Point Builder to create an appropriate digital point for the set point information. Location2=3. That information is in the form of digital status and you want to capture it in the PI Server. Digitalset. Approach Open the PI SMT Digital States plug-in and create a Digital State Set on your PI Server. Be Careful! Enabling Delete You may notice that the Delete action is not enabled by default.Creating and Managing Points 9. you can’t get them back. In addition. only export the tags (rows) that you actually changed or are new. It is recommended that you only enable Delete when you need it and be extremely careful when using it.1 Like every powerful tool.5 PI Tag Configurator PI Tag Configurator is an add-in to Microsoft Excel. one point per row. Each point has its attributes listed under the headings in the top row. Your instructor will show you examples. Import or export operations are performed on these selected points only. If you delete a tag(s) by accident. 9. you may need such a set of templates for each interface type. Tip 9. with a row for each tag and a column for each attribute.2 Export only What Matters OSIsoft recommends that you build templates. That is because there is no “undelete” for a tag. PI Tag Configurator requires the spreadsheet to have the following layout: • • • • The attributes are listed in the top row.5. which include only the necessary attributes for that type of tag. Tag Configurator can save you a lot of time or do a lot of damage if not used carefully. Select a point row by putting X in the first column. Moreover.5. The tool best suited to bulk build and edit tags is PI Tag Configurator. People have accidentally wiped out their entire systems by accident. All of the history is inaccessible or lost. The spreadsheet format is convenient when viewing and editing in bulk. The point names are listed in the second column. Page 117 . Page 118 . In that case.5. the CompDev will be reset accordingly. Planning and Implementation 9. If you change the CompDev attribute. the CompDev will be reset accordingly.PI System Architecture.3 The Deviation versus Percent Issue The compression / exception deviation is actually determined by the following logic: Deviation Percent/100 * Span = Deviation So the following three are true: If you change the CompDevPercent attribute. If you export a line where two or three are changed or one is changed but you export all of the fields then the system has to make a guess as to which change you really want. the CompDevPercent (and the Span if it changes) will take precedence. the CompDevPercent will be reset accordingly. If you change the Span. Exercise Objectives Create points from a spreadsheet with the PI Tag Configurator How to work with the Interface Manuals Configure Interface startup files Problem Description You should create two sinusoidal tags for the random interface without doing so individually in the PI SMT Point Builder Tool. you might to create new scan classes in the interface startup file to accommodate new scan frequencies. The first tag should show a one-hour Sinus wave with a scan class of 5 seconds. which starts on the full minute. when creating new tags. 3 and 5. Please build useful tags. for instance). You are invited to perform the same steps at the same time. Tip Usually. validate that the tags are working properly (collecting data).6 Exercise – PI Tag Configurator In this part of the class. Approach Use the Tag Configurator to build one line for each new tag and export the definitions to the PI Server. Both tags have a scale from zero to 100.Creating and Managing Points 9. when configuring each new tags. you will perform a learning activity to explore the different concepts presented in this chapter or section. take note of the tag attributes whose purposes are unique to each interface (Location 2. In PI ProcessBook. Page 119 . The second tag should show a ten-minute Sinus wave with a scan class of 1 second. Also. you will perform a learning activity to explore the different concepts presented in this chapter or section.PI System Architecture. You are invited to perform the same steps at the same time.7 Exercise – Create IO Rate Tags (Optional/Time permitted) In this part of the class. Planning and Implementation 9. Page 120 . Creating and Managing Points Page 121 . 380.XX and later.380. people have to be able to get critical data to make decisions. In this chapter.PI System Architecture.4.XX security) Describe the ACL syntax and how access is granted Create and manage PI identities Configure PI mappings Configure PI point security Create and configure PI Trusts Configure PI database security Configure PI security settings slider Tip OSIsoft recommends you reserve Trusts for unattended applications like Interfaces. we will address the methods and best practices for allowing users proper access to their data. For the PI System to be useful. Planning and Implementation 10. PI Security Objectives Describe the function of the PI Firewall in the connecting logic Describe the function of the PI License in the connecting logic Describe how users connect Describe the security implications of working on the server box Describe pisusers and pigroups (pre 3. You should NOT use them for user access for PI Servers version3.4. Page 122 . PI AF Server Active Directory PI Server However. we create mappings to objects for which we want to control access. In the PI Server. In the PI AF Server. you can tie Active Directory entities to objects.1 The PI Server Conundrum The PI System has two parts: PI Server and PI AF Server. We call these mapped things PI Identities.PI Security 10. the PI Server does not have the ability to tie Active Directory entities directly to objects like points or data tables. PI AF Server Active Directory Mapping PI Server Page 123 . Page 124 . Having logged into the computer via her corporate windows account.*.PI System Architecture. Corporate firewalls and routers protect most PI installations. This is accomplished by the PI system manager mapping the users’ active directory group to a PI Identity. the PI Firewall contains one entry configured with an IP address mask of *. 10. Any IP address or subnet may be allowed or disallowed access.com Disallow Although the PI Firewall can be very useful for a few customers. It provides a rudimentary control based on the incoming IP Address or hostname. the maintenance of a separate firewall database in PI is rarely advisable.55 Disallow 192.168.* Allow Bobcat. There are only two functions: ALLOW DISALLOW HostMask Tip Value 192. Use the Firewall PI SMT plug-in in the security section to configure the PI Firewall. Planning and Implementation Tip Caution: We do not recommend using native PI Server security (piusers and pigroups) as they are. by definition. Most implementations control access through network infrastructure. This provides access to all incoming connections.*.177.168.* and a value of Allow. the user is automatically authenticated on the PI server. By default.somewhere. less secure.149.2 PI Firewall The PI Firewall is the first level of access security to your PI Server. The identity specifies the read/write permissions for accessing the database. Tip You should avoid using the native piusers and pigroups in your security scheme.exe(5676) ID: 51 You do not need to respond in any way – these are informational. You can use the License plug in in PI SMT to view your license statistics. Applications may generate messages such as: 0 pinetmgr 20-Oct-05 11:34:07 >> License Warning (non-fatal): [-12221] Not licensed to use this client application. However. Level: 3 Process name: PointBuilder.3 The PI License Subsystem The PI License subsystem has the capability to determine what applications are allowed. 10. 10. Page 125 . They are inherently insecure and are included for legacy systems. as of the current version the only element that is actually metered is the point count.4 Connection Logic The diagram on the following page illustrates the connection logic.PI Security Tip More specific host masks will override ones that are more general. Planning and Implementation ` PI User Firewall License Not Often Used Trust Windows Users piuser/ pigroup Mapping to PI Identity PI Point Page 126 DBSecurity .PI System Architecture. Choices are “read” and/or “write. Page 127 .5 Granting Access Each connecting user is associated with a PI Identity (or piuser or pigroup) and that PI Identity has permissions explicitly granted by an ACL.5. 10.w) | Identity2:A(r) Where Identity1 can read and write and Identity2 can only read. In the DBSecurity Table you grant access to data structures on a global level.1 Granting Access – the ACL An Access Control List (ACL) string defines the access permissions for that entry.” The syntax is: Identity1:A(r.Application You will apply the ACL in general in one of two places: the DBSecurity or PI Point attributes (point configuration access and point data access). Tip You can give only “write” permissions but it is not recommended for users.5. 10.PI Security 10.2 Granting Access . You can also apply access permissions on a tag by tag basis. PI System Architecture. It is more flexible to use AD Groups and not try to micro-manage AD User mappings. PI Groups and PI Identities and Mappings The Identities. & Groups plug-in in PI SMT allows you to create and manage PI Identities.6 Managing PI Users. When configured. Several entries are created by default during installation. PI Users and PI Groups. including PI databases security and PI point security. Planning and Implementation 10. . Tip Page 128 Ideally you will have one Identity for each Active Directory Group you will use to access the PI System. Users. you can use the security entries to specify security settings throughout the PI Server. The application cannot log in so it must rely on a mechanism called a “trust” to gain access.7 PI Trust For obvious reasons. A trust simply maps a connecting application to a user. You can use either the Wizard or the Advanced options to create a trust – they perform the exact same function. The best way to verify this is to start the interface and watch the connection that is denied on the PI Server using the Message Log plug in of the PI SMT.1 Create Trusts Trusts are easy to create. Then look at the PI Server Message Logs in PI SMT for the denied connection. Tip You can map an application to the piadmins group for convenience in setting up the trusts. 10. so it is best to base trusts only on those parameters. the Random interface will use the phrase RandE. Page 129 . but do not leave that trust in place. The message for the connection will have the information you need to form a trust.7. Always use specific Identities in your trusts that have only the necessary permissions. The application name used in the connection for most interfaces is an encoded phrase that takes the first four letters of the interface name and the capital letter “E”. Tip PI Interfaces almost all use a protocol that only sends the IP Address and an encoded application name in it communication (PI API). the interface needs to connect to the PI Server. The PI Server checks all incoming connections for a trust as a first step. Use the PI SMT Mappings and Trusts plug in. You will probably have to create three trusts: PI Interface PI Buffer (Subsystem or Server) PI ICU (if you are using this tool to configure) A good tool to view connections on the PI Server is the PI Network Manager Statistics plug in in the PI SMT. For example.PI Security 10. Page 130 .PI System Architecture. Some people find the Wizard confusing because understanding when to use a “PI API Application” or “PI SDK application on a Windows NT based OS” might not be intuitive. Do not map trusts to the piadmin user. That is. Most people should simply select Advanced. This simply presents all of the options in one dialog box. Planning and Implementation Tip Trusts should follow the “2+” Convention. You want to create Trusts SPECIFIC to the executable that is connecting to PI. a trust to the interface based on IP Address AND the executable name. Note: You must have write access to the PIPOINT database to create new points. each object has their own security control settings. pidiag. The table below lists the common database tables used for user access: Database Controls… PIDS Access to Digital States and Digital Sets. no login is required to use the command prompt utilities on the PI Server (piconfig. For the change to take effect. version 2010. 10. Page 131 . These are shown in the Database Security plugin in PI SMT.PI Security 10. This is an important option as many programs and users may require PI Module Database access. and all of the database tables are collected in one place. You do not need this privilege to edit the configuration or data of the points once created. like Microsoft SQL Server. piartool. That access is controlled by PI point security. Points Classes and Attribute Sets. There is the same concept in the PI Server. Editing existing PI points can be provided through the PI point security configuration on a point-bypoint basis.9 The Database Security Table In other applications.8 Working on the PI Server A default loopback PI Trust exists on the PI Server that grants piadmin access to all applications running locally on the PI Server machine. PIPOINT top-level access to Points. By default. the PI Server must be restarted. For more information see PI Server 2010 Configuring Security. PIModules Access to the Modules. You can force a login by modifying the CheckUtilitylogin tuning parameter on the PI Server.). etc. This should not impact you at all if you avoid using piusers and pigroups. . Most of your interfaces will fail to connect if you disable API Trusts.10 The “Security Slider” You have the ability to disallow types of logins to your PI Sever. Planning and Implementation 10. This is controlled by the Security Settings plug-in in PI SMT. In a good security environment you will set the slider to a minimum of explicit logins disabled.PI System Architecture. Tip Page 132 While it may seem ideal to set the “slider” to the top level of security this is not a possibility in today’s PI System. These are described below: Polled For polled points.. advise and event retrieval Discuss OPC Tasks to install an OPC Interface Learn how to work with ICU Configure OPC Tags 11. Not all interfaces support the Advise method. Installing and Configuring an OPC Interface Objectives Discuss polling. the PI Server informs the interface when the trigger point has a new event (not necessarily a change in value) and the interface sends an asynchronous read call for the event points attached to that trigger. This is often the most common method for reading data. and is supported by virtually every interface. For advise points (referred to as read on change in the OPC Standard). Not all interfaces support bi-directional data. the data source sends data whenever a new value is read into the server’s cache. Event (Trigger) For event reads. Page 133 . Advise and Event Points Many interfaces have different methods of retrieving data. All three read types of points are read asynchronously by the interface and the same data routines process all updates. Tip Often the Advise method of reading data is the most efficient and best performing. Advise Advise tags “listen” for new events. The method is often set in a Location Code. Output Output tags read a separate PI Tag and write the value out to the data source.1 A Word About Polling. the interface sends an asynchronous refresh call for the group (tags of the same scan class). These often reference Performance Equation (calculation) tags that are performing a calculation that cannot be performed on the data source.Installing and Configuring an OPC Interface 11. Planning and Implementation Caution: Do not mix advised points and polled points in the same group (i.PI System Architecture. scan class). Some interfaces do not tolerate and will not function correctly. Page 134 .e. opcfoundation. Originally based on Microsoft's OLE COM (component object model) and DCOM (distributed component object model) technologies. There are now hundreds of OPC Data Access servers and clients. The COM/DCOM technologies provided the framework for software products to be developed.2 What is OPC? From http://www. Because of this abstraction. Most OSIsoft Interfaces connect directly to the data source. The first standard (originally called simply the OPC Specification and now called the Data Access Specification) resulted from the collaboration of a number of leading worldwide automation suppliers working in cooperation with Microsoft. and some use one for the scan classes. the specification defined a standard set of objects. where the OPC Interface connects to an OPC Server which in turn is connected to a data source. Check your OPC Server documentation for details. Scan Rate PI Server Tip Interface Update Rate OPC Server Device You never want to set your update rate slower than the fastest scan class! Page 135 . Some OPC Servers use a separate switch for that. The PI OPC Interface is like any other interface.Installing and Configuring an OPC Interface 11. you must be mindful of the “Update Rate”.org OPC is a series of standards specifications. interfaces and methods for use in process control and manufacturing automation applications to facilitate interoperability. with one notable exception: it provides a layer of abstraction between the interface and data source. Search for "OPC DA Sample Binaries." Please consult the OPC Foundation web site for details if you wish to obtain a copy. you will perform a learning activity to explore the different concepts presented in this chapter or section.00 Binaries".3 Directed Activity – Preparing to Install the OPC Interface In this part of the class. These files are available at http://www.opcfoundation. In this situation we will install the Interface on the same computer as the data source – in this case the OPC Server Simulator. Planning and Implementation 11. Page 136 . Since we are in a training environment we will use an OPC Simulator. Activity Objectives Prepare to install an interface Approach Normally before you begin an interface installation you would identify your data source. .PI System Architecture. Process Controls DCS / PLC OPC Server and PI Interface PI Server The OPC server we use is made available by the OPC Foundation as the download "OPC Data Access 3. It has been configured to generate a set of sample data such as a wind farm or pumps. You are invited to perform the same steps at the same time.org/. and vice versa. it is recommended to use the FQDN whenever possible. If using hostname. If you use IP Address in the interface hostname then make sure to use IP Address in the PI Buffering configuration.Installing and Configuring an OPC Interface Fill in the following architecture diagram with the Hostnames and IP Addresses of your machines: Tip It is a good idea to stick with the same configuration credential when setting up the interface and buffering. Page 137 . You will need to get them working before proceeding. Page 138 .4 Validating communication between the PI Server and the PI Interface Verify that the data collector computer can communicate with the PI Server. If these tests do not work.PI System Architecture. The apisnap (\pipc\bin) utility validates the PI Interface connection to the PI server (remember PI Interfaces use the PI API to connect). The PI Connection Manager validates the PI SDK connection to a PI Server. Planning and Implementation 11. you may need to try simpler tests such as pinging the PI Server from the interface computer. you can display the snapshot. status and the last archived value for a point as shown below. Once connected. It is accessible with the PISDKUtility in Start -> All Programs -> PI System. On the PI Server. Install the PI OPC interface. then look at the connection characteristics. You are invited to perform the same steps at the same time. Use PI Interface Configuration Utility to configure the PI OPC interface: Set the host PI server to the PI server to which you will send data. Tip Why use the piadmin User when we earlier said that was bad practice?!? Because it is often simpler to use that all-powerful group to get the interface running.exe) granting it access as the “piadmin” PI User. Install the software: Install the OSIsoft prerequisites kit. Exercise Objectives Install the PI OPC Interface on the data collector computer. Set the OPC server name to the OPC Data Access server simulator.Installing and Configuring an OPC Interface 11. An OPC Data Simulator will be installed on your computers. Page 139 . Install the PI ICU. use PI System Management Tools (PI SMT) to: Build a PI Trust for the PI ICU application (PI-ICU. Start the PI OPC Interface as a Windows service.5 Directed Activity – PI OPC Interface Install & Configuration In this part of the class. Build the three PI Trust for the PI OPC interface computer with IP address. Problem Description You need to set up the OPC Interface to collect data. you will perform a learning activity to explore the different concepts presented in this chapter or section. Host name and FQDN granting it access as the “piadmin” PI User. and build the appropriate security models. Approach Install Log into the computer designated as the PI Interface Computer. Configure the PI OPC Interface with PI ICU. Get it Going Setup your trusts. but you have to navigate to the OPC Interface folder and run it. Restart the Interface and validate that the interface is using the correct trust and PI Identity (not the piadmin User). Tighten Security Page 140 In PI SMT. Create a new new PI Identity called “PI OPC Interface. use the Network Manager Statistics plug-in to validate that the interface is connected to the PI Server.” Create a new trust with the PI OPC Interface PI Identity. Start the interface interactively to confirm operation. . Planning and Implementation Tip You can get the name of the OPC Server Name by using the PI OPC Tool. Start the interface as a Windows service and confirm proper start-up by using the PISDKUtility to monitor the message log. The PI OPC Tool is installed with the OPC Interface. It will not be in the Programs menu. Use PI Interface Configuration Utility (PI ICU) to create the Windows service for the interface.PI System Architecture. Look for connection to both the PI Server and the OPC server. bat Tip If you use the PI ICU to edit an interface startup file do not edit it manually again – your changes will be lost the next time someone uses the PI ICU.6 A Note About Load Balancing a Large Number of PI Tags Most PI interface will allow you to put large number of PI tags per scan class. then some scans may occur late or be skipped entirely. The ICU can only configure interfaces that run on the same computer as the ICU. 11. It automatically stores needed information in the PI Module Database on the server. If the interface is under a large load.bat). and in the interface start-up file (. Page 141 . OSIsoft recommends putting the tags into another scan class with an offset. An alternative would be to create multiple instances of the PI Interface to split the tag load.7 PI Interface Configuration Utility PI ICU allows system managers to easily configure and maintain interfaces.Installing and Configuring an OPC Interface 11. The PI Interface Configuration Utility (PI ICU) is simply a GUI for editing the startup batch file! The one thing you must keep in mind is that the PI ICU READS from the PI Module Database but WRITES to the interface startup batch file. The amount of tags per scan class depends how often the tags are getting updated. PI Interface Configuration Utility READ IT WR PI Module Database E Interface Computer Interface. 11. and scan classes (/f). the General section of PI ICU allows the user to configure the main start-up parameters of an interface. The PI ICU should open the appropriate folder by default. such as the point source (/PS).bat file in the appropriate interface folder. It is reusable code integrated in many of OSIsoft’s interfaces to include generic functions such as establishing a connection to the PI Server computer and monitoring the PI Point database for changes. Tip Import the .PI System Architecture. Add 2 new scan classes. All OSIsoft Interfaces are installed in a single local folder labeled “Interfaces. Import a new interface start-up file (for instance. you may have to browse your file system.8.1 The PI ICU General Section Once the . one scanning every 1 minute with a 15-second offset and a second one scanning every minute with a 45 second offset.bat. Activity Description Use the PI ICU to import the sample batch file that comes with the interface. Note the new .bat_new file has been imported. 11.new file into PI ICU and then save the file. Page 142 .” If the person running the installation kit selected a different location. Planning and Implementation This also means you will need a trust to the PI Server for the PI ICU because it needs write access to the PI Module Database.2 The PI ICU UniInt Section UniInt is short for Universal Interface. Approach Open PI ICU. 11.8. the interface id number (/ID). Note the features on the General tab. OPC interface) into PI ICU.8 Directed Exercise – Explore PI ICU You are invited to watch what the instructor is doing or perform the same steps at the same time. and more. stop time. Page 143 . Doing will provide a clear indication of a gap in the data collection.Installing and Configuring an OPC Interface For more information see the “UniInt Interface User Manual” This section presents the UniInt-based interfaces parameters. It uses a separate switch in the interface specific section (opcint) of the ICU. debug level. You can configure the interface to write a shutdown state when the interface stops by using the Write status to points on shutdown option. such as scan performance summary. Note: The PI OPC interface does not use this Write status to points on shutdown option in the UniInt section of ICU. Page 144 .8. Configuration of a service includes display name.3 The PI ICU Interface Specific Section In addition to generic parameters. Before you click the Create button. 11. but especially useful in getting services to work in Workgroup environments. interfaces have interface-specific parameters. you will want the interface to be dependent on the PI Buffer Subsystem (PIBuffss). This will assure that the buffer starts before the interface. You do not need to buffer interfaces running locally on the PI Server.8. The interface section will display either an interface specific PI ICU control that aids in configuring parameters specific to the current interface or be blank. Planning and Implementation 11. start-up type and dependencies. log on as a specific user.4 The PI ICU Service Section The Service section allows the user to configure the interface as a service.PI System Architecture.default Dependencies: recommended PIBufss when buffering runs – tcpip is default Log on as: some interfaces require the service to run as a specific account (consult interface-specific documentation) . The contents of this section of the PI ICU will change according to the interface. On buffered interface computers. configure: Display name: name displayed in the Services window – populated by default Start-up type: recommended automatic . Validate in the log file there are no errors.log file or the PI SDK logs) You will create points collected by this interface in the next chapter.8. The most common cause of malfunctioning new tags is some incorrect mapping of PI tag attributes to the data source or the interface configuration. Start your Interface.5 Start the Interface There are two ways to start the interface: Interactive (you run the interface manually as your currently logged in Windows user) Non-Interactive (you start the Windows Service) Tip You must validate that the interface can be started by the Windows service before you consider your configuration complete. Page 145 .Installing and Configuring an OPC Interface 11. It is possible that you can start the interface interactively using your permissions but the Windows service not have the correct permissions and fail. There are two ways to view the log file: Interactively (run pigetmsg –f) View the log file (the pipc. You need to create tags in the PI System. For more information see "PI Point Configuration" in PI OPC DA Interface Manual. Tip Open a command prompt and run pigetmsg –f It will show if the tag was picked up properly by the Interface.PI System Architecture. You should notice that there are a series of pumps. Validate PI OPC points are collecting data from an OPC server. Problem Description You have a set of pumps connected to your PI OPC Server and generating data. You are invited to perform the same steps at the same time.9 Exercise – OPC Points In this part of the class. Approach Use the PI OPC Tool (installed with the PI OPC Interface) to examine your OPC Server. Planning and Implementation 11. Use the PI OPC Manual and the information contained in the PI ICU to configure tags. (You have already configured your PI OPC Interface). These pumps each have some tags associated with them. Stop after building the tags for ONE PUMP only! Page 146 . Exercise Objectives Build PI OPC Points. you will perform a learning activity to explore the different concepts presented in this chapter or section. and they should be generating data. Pay particular attention to the Location Codes and the ItemID. Installing and Configuring an OPC Interface Page 147 . When the buffering process is shut down. Tip Unless you have a specific reason why you do not want to preserve your data. Buffering Objectives Describe PI Buffering Define the two different buffering mechanisms and pros / cons of each Configure PI Buffering Validate the function of the buffer Throughout this section you will refer to various sections in the PI Buffer Subsystem User Guide. Multiple interfaces on a single data acquisition computer share the same buffering process and store data in the same buffer. using FIFO (first-in. Page 148 . the memory buffers and file buffers are combined into a new file that contains all data not yet sent to the server. 12.PI System Architecture. When buffering is on. you should always configure buffering for an interface! Normally buffering is run as an automatic system service to ensure it is always running. Data is then stored in a file. Data is stored initially in memory until the allocated buffers are filled. version 3. first-out).375/PR1. The size of the file and the memory buffers are configurable. which stores and forwards events to the home node.4.1 What is PI Buffering? Data sent from the interface to the PI Server is redirected to the buffering process. Planning and Implementation 12. Please open this document. all calls that send data to the default home computer are buffered. you will perform a learning activity to explore the different concepts presented in this chapter or section. The instructor will then ask each team to present why you would want to use their mechanism. Each team will use the Buffering user guide to research their buffer. Each side of the room will be given one of the buffering mechanisms. The room will have 5 minutes. You may be invited to watch what the instructor is doing or perform the same steps at the same time. Element API Buffer Server PI Buffer Subsystem Supported Platforms Supported PI Servers Compression Algorithm Maximum Buffering Capacity Maximum Throughput Page 149 . version 3.375/PR1. Your instructor will have directions. See " PI Buffer Subsystem vs. Activity Objectives Describe the pros / cons of each buffering mechanism Approach The instructor will divide the room in half.2 Directed Activity – The Two Faces of Buffering In this part of the class. BufServ” in PI Buffer Subsystem User Guide.4. .Buffering 12. The PI Buffer Subsystem consumes data from the buffers as soon as they are detected.PI System Architecture. overflows to the buffer file on disk (APIBUF_<servername>. it switches to using dual memory buffers and a file. it switches to using dual memory buffers. or if already full. it uses a single memory buffer. the buffering mechanism intercepts the data as the interface sends it and the buffering application manages the communication between the interface computer and the PI Server.dat). the buffering process can be in one of three states. events are marked as Snapshot Only or To Be Archived. 12. There are three buffers used to process events: two memory buffers and a file buffer. Initially. Once validated and marked for compression. Timestamps and values are validated and if point-level compression is enabled. When that fills. When these buffers become full. all events are stored in as many queues as there are replicated nodes in the target PI Collective (pibufq_<servername>. Planning and Implementation 12. Page 150 .3. A non-replicated PI Server requires only a single queue.1 Buffer File Data is copied into shared memory buffers.dat). Depending on the amount of data being buffered.3 The Buffering Mechanism How does it work? Very simply. Approach The group will track data as it leaves the interface and finishes up in the Snapshot on the PI Server. You can monitor the status of your buffer in real-time. Your instructor has instructions. Your instructor will have directions. You may be invited to watch what the instructor is doing or perform the same steps at the same time. Activity Objectives Describe the path complexities data takes when buffered.4 Directed Activity – Mapping Data in PI Buffering In this part of the class.Buffering 12. whether it is currently able to pass data to the PI Server. you will perform a learning activity to explore the different concepts presented in this chapter or section. To do this. or not. use the \pipc\bin\pibufss. Page 151 . in a command prompt. Activity Objectives Configure Buffering Validate data is being buffered Approach There are a couple of ways to configure buffering. follow these steps in PI ICU. but in this course we will use the PI Interface Configuration Utility. (Buffering is configured through entries in the piclient. Your instructor will have directions. You will need write access to the PI Module Database. Page 152 . Tip Remember you will need a trust to use the PI ICU. The PI Interface Configuration Utility (PI ICU) is the preferred way to configure both the Interface and PI Buffering.) Select Buffering from the Tools menu in PI ICU.5 Directed Activity – Configure Buffering In this part of the class. You may be invited to watch what the instructor is doing or perform the same steps at the same time. you will perform a learning activity to explore the different concepts presented in this chapter or section.PI System Architecture. Planning and Implementation 12. To enable buffering on a data collector.ini file. Page 153 . and start the buffer service in Service. Select the buffered and replicated PI Servers in the Buffered Servers list.Buffering Select your desired buffer from Choose Buffer Type. Change the default settings as necessary in Buffering Settings. create. Configure. Make sure you set the dependency. Page 154 .PI System Architecture. and it will prompt you to set the dependency. The PI ICU will recognise if an interface does not have a dependency set for the buffering service when it is enabled. Planning and Implementation Tip Caution: the Buffering mechanism will NOT collect data unless it starts BEFORE the interface. Make sure the PI Interface is dependent on the buffer service. Buffering 12. Run the PI Buffer Subsystem in interactive mode to see the queue statistics: pibufss -qs The image above shows a non-working buffer – notice all of the zeros in the columns. Page 155 .6 Validating Data Buffering It is critical that you not only check the buffering when you configure it but it is recommended that you periodically check the buffering to make sure it remains doing its job. To validate the PI API Buffer Service: Open a command prompt window and navigate to the pipc\bin folder: Bufutil To validate the PI Buffer Subsystem: Open a command prompt window and navigate to the pipc\bin folder. The only way to validate buffering is to run a command prompt on the interface machine. and will coach you if you need assistance during the activity. Your instructor will have instructions. Disconnect the interface computer from the network. Approach On the PI Server: Create a PI ProcessBook display showing the data from one of your OPC points for the last one hour. Problem Description In the event that the PI server is shut down or disconnected from the network. On the data collector: • • • • • Validate that you are buffering data from the previous Directed Activity. Exercise Objectives Configure and verify buffering on a data acquisition node. Watch the command prompt as it builds values. you need to have data buffering installed and configured on the data acquisition computer to avoid data loss.PI System Architecture. Planning and Implementation 12.7 Solo / Group Exercise – The PI Buffer Subsystem This solo or group activity is designed to maximize learning in a specific topic area. Wait a couple minutes (you can check your PI ProcessBook display for a “flat line”) Reconnect the interface. . On the PI Server: Page 156 Verify the data is recovered from the buffer. Buffering Page 157 . they can be performed with the proper planning and care. 13. the urgency to repair a failed system is reduced.1. your calculations are not getting the data required. 13. High Availability ensures the data is there when you need it. There is no need to rush to get your only source of data up and running. even though there was no data loss. High Availability Objectives: Describe the purpose of High Availability Describe the components of High Availability Create a High Availability PI Collective Implement PI Interface Failover List the limitations of PI High Availability Discuss complex architecture scenarios 13. run with the wrong data. most notably the Buffering process.2 Less Urgent Downtime If you have redundant systems. When you need data to make a decision today and you cannot get your data until tomorrow. In the stand-alone PI System there are already precautions against data loss. the data is more likely to be available when it is critically needed.PI System Architecture. leading to Page 158 . the system has failed you. the data is available via an alternate path. When repairs or upgrades are required. The calculations may fail. If one component fails.1 Reliability When you have multiple data paths between the data source and the user.1. or worse. Planning and Implementation 13.1.1 High Availability Defined High Availability (HA) is not designed specifically to prevent data loss. If a situation is critical to your business. the fact that data will get to you sometime soon is of no help in real time decision making.3 Important Calculations Remain Current If you have calculations being performed constantly and your system is down. What High Availability does give you are the following: • • • • Reliability Less urgent downtime Sustainable calculations Disaster recovery 13. Your professionals have the time they need to properly diagnose and implement a solution for a problem. it is easy to replicate it using one of the working partners. When data that is always available.High Availability inaccurate results. your applications that use PI data run uninterrupted. There is no need for a complete rebuild and migration of data. Page 159 .4 Disaster Recovery When one of your redundant servers fails.1. 13. 2. PI Client application failover. 06-16.2 PI Server Collective (redundancy) Redundant PI Servers are together replicating configurations. feeding all PI servers with the same data.2 Directed Activity – Components of PI High Availability In this part of the class.2. Your instructor will have directions.2. These options can be combined to use AF Collectives with Clustered and / or Mirrored SQL Servers. and providing identical data to analysis and client tools. pp. Activity Objectives Define the components of PI High Availability Approach High Availability requires three (3) components all working together to function properly. Planning and Implementation 13.PI System Architecture. receiving data from interfaces. 13. For more information. PI Server collective.2. see "AF Deployment Scenarios" in PI AF 2010 User's Guide. version 2. These components are: • • • Interface failover and/or N-Way buffering. you will perform a learning activity to explore the different concepts presented in this chapter or section.1 Interface Failover coupled with N-Way Buffering One interface of the set is always running. We will not discuss AF collectives in this class. You may be invited to watch what the instructor is doing or perform the same steps at the same time. 13. including the use of AF Collectives for the AF Server and Clustered or Mirrored SQL Servers for the AF SQL Database.3 PI AF Server HA AF supports multiple High Availability options. 13. Page 160 . 13.2.4 Client Application Failover Clients can connect to any PI Server in the Collective and seamlessly failover to another server if necessary. In addition. PI HA has separate paths for the same time series data for true replication. we are implying a functioning domain controller with reliable DNS resolution. By coherent structure. Currently these include: Performance Equations. This is accomplished by replicating the data as it is collected and distributing the data to each server in the collective. to have proper initialization of the secondary nodes. Message logs are not replicated because the messages are inherent to the specific machine. and that the domain has a coherent structure. Consult Appendix A to get more details. The same situation arises with applications designed to read and write to a single server. configuration data (point definitions. Open the related TCP ports.3 PI Server Replication PI Servers replicate by initially cloning the primary source server. A replication service keeps static. Any Custom manual data entry applications that do not use the PI SDK. All server metadata is replicated except: The Tuning Parameters Table Message Logs PI Firewall Tuning parameters are not replicated because they have configurations that can vary by server machine and thus are not appropriate to propagate. Firewall settings are not replicated because Collective members can be in separate domains and require separate settings. Totalizer points.) synchronized between the primary and the clones (referred to as secondary nodes).4 Limitations The PI HA mechanism was designed to function in a situation where the servers and interfaces are all contained within the same domain. there needs to be Windows file copy access between the servers. 13. only written to a single server. and so on.High Availability 13. PI Batch Generator. data is replicated. PI SDK applications can take advantage of PI SDK buffering. Data replication is achieved in the buffering mechanism. Page 161 . Any data sent to the PI Server from a source other than a buffer mechanism is not replicated. digital state sets. At the buffering level. Planning and Implementation 13. you will perform a learning activity to explore the different concepts presented in this chapter or section. You may be invited to watch what the instructor is doing or perform the same steps at the same time. However.PI System Architecture. Review the section on pre-installation and discuss the differences for the Secondary PI Servers. version 2010. Open the book to "Checklist for Installing PI Collectives" in PI Server 2010 Installation and Upgrade Guide. Your instructor will give you a couple minutes to scan the docs. Your instructor will have directions. Activity Objectives Describe the specifics of the HA Installation Approach You have many of the same installation concerns as you would a stand-alone PI System. Answer the following questions: Do you need another PI AF Server install? How do you get a License file for the Secondary? What version of the PI Server do I use? Page 162 .5 Directed Activity – HA Pre-Installation Concerns In this part of the class. there are differences. Use the PI Collective Manager to initialize each secondary. The license must be obtained against the Primary PI Server. 13.1 PI AF Server PI Server 2010 requires an AF server to be available before the installation. then add the secondary to primary server’s PI Connection Manager. Make sure the PI license supports collectives. The Amount Left should be greater than 0. Validate this be checking the license information in PI SMT under Operation > License > Resources. Page 163 .High Availability 13.6 Pre-Installation Concerns 13. Install the same version of the PI Server software on the secondary PI Server machine. It can be installed on the same machine as the primary PI server or on a different machine.6.2 License A license file will be required. Only the primary PI server will be synchronized with AF server.6. Start the secondary server. The license file will have to acknowledge at least one secondary server. Approach This exercise makes use of four (4) computers. OPC Interfaces: OPC Simulator: Page 164 Secondary: . In the table below. The AF server used will be the one installed on the same computer as the primary PI Server. Depending on the size of the class. the students may be divided into teams. please take a few moments to note the computer names or IP addresses for each computer. Planning and Implementation 13. Two (2) computers will be used to establish the PI Server collective and two (2) computers will be used as the data collector computers.HA Step 1: Revisit Planning and Hardware This solo or group activity is designed to maximize learning in a specific topic area. Problem Description You need to organise your Collective. Your instructor will have instructions.7 Group Exercise .PI System Architecture. and will coach you if you need assistance during the activity. Primary: PI Servers: Note:For the purposes of this course the AF will be installed here. The PI OPC DA Interface will be configured on two interface computers and an OPC Simulator will be installed on one of the interface machines. so you will need to work in pairs. Exercise Objectives Understand the computers involved in the Collective. So when the applications are running on different machines they must use DCOM – in this instance COM over TCP/IP. Thus DCOM is an architecture that enables components (processes) to communicate across a network. COM defines how components interact and is an architecture for simple interprocess communication. but supports distributed interprocess communication. Tip Many people feel that DCOM is inherently unsecure. Because of these security concerns OSIsoft recommends installing the OPC Interface on the same computer as the OPC Server. 13. Configure the second interface (on the other persons interface machine) exactly as the first interface. using the same data source. is a COM application. The OPC Interface communicates with the OPC Server (data source) through the COM layer. DCOM supports the same model of component interaction.High Availability 13. This will require the configuration of DCOM.1 What is DCOM? From What is DCOM? By Rosemary Rock-Evans Microsoft's DCOM (Distributed Component Object Model) is based on Microsoft's own COM (Component Object Model). like many applications.8. The PI OPC Interface. Of course you cannot avoid this in an HA situation.8 The Second Interface The primary interface will be the one originally used by the person with the Primary server. Ensure it is working and that data is going to the primary server before proceeding any further. Page 165 . It defines a basic model of communication using Microsoft's equivalent of objects components. Note: This often involves the following two steps: 1. and will coach you if you need assistance during the activity. Your instructor will have instructions. Problem Description You need a second. There is an extensive manual on setting up DCOM that you may refer to: See the “DCOM Configuration Guide” for more information on DCOM setup. On the second interface. On the identity tab configure to use the administrator user as you did on the remote interface.9 Group Exercise . Page 166 . Exercise Objectives Preparation for failover exercise. On the second interface machine. Use a client tool to verify that you are collecting data for all of the OPC points (Hint: search for points with a pointsource of OPC). Change the Authentication Level to Connect on the General tab.HA Step 2: Second Interface Machine This solo or group activity is designed to maximize learning in a specific topic area. The configuration will be identical except for the OPC Server input on the opcint tab. but as networks become complicated and security gets tighter more care needs to be taken in configuration. you will use: the name of the first interface computer. Approach Repeat the process with identical settings for the second interface machine (of course you will not have to build trusts or points as they are already built). For this. 2. Note that DCOM configuration can get rather complicated. In that list will be the OPC Sample Server (OPCSample.OpcDa20Server). identical interface for the failover scenario. Once you verify that data is being transmitted to the PI Server STOP THE INTERFACE. you will need to configure DCOM. Open the Properties of the interface service and set the user to be the administrator. Planning and Implementation 13.PI System Architecture. On the interface machine without the OPC Server: change the log on user for the Interface Service. you may need to configure the identity OPC Simulator process and the logon rights of each interface. The two steps listed above work in some cases. On the interface machine with the OPC Server: Open Start > Administrative Tools > Component Services and browse to your DCOM Config. many OSIsoft interfaces provide two failover schemes: Phase One: synchronization through the data source Phase Two: synchronization through a shared file. Additionally. For this option. no data loss solution when a single point of failure occurs. the data source must be able to communicate with and provide data to two interfaces simultaneously.10 Interface Failover Defined To minimise data loss during a single point of failure within a system.10. Page 167 .1 Phase One Phase 1 UniInt Failover uses the data source itself to synchronize failover operations and provides a hot failover.High Availability 13. This is something that many SCADA people view with apprehension. the failover configuration requires the interface to support outputs – data is written back to the data source. Tip Phase 1 is appropriate in two situations: (1) if performance degradation occurs using the shared file or (2) read/write permissions for the shared file cannot be granted to both interfaces. 13. Planning and Implementation 13. Page 168 .PI System Architecture. warm. you can expect a small period of data loss during a single point of failure transition.2 Phase 2 Phase 2 UniInt Failover uses a shared file to synchronize failover operations and provides for hot. However. The Phase 2 hot failover configuration provides a no data loss solution for a single point of failure similar to Phase 1. in warm and cold failover configurations. or cold failover.10. The Failover ID for each interface must be unique and each interface must know the Failover ID of its backup interface. You need to make them work together so when one fails the other takes over. Configure the Shared File 1. Note: The first interface to start will create the file. In this classroom. Ensure that the user name assigned in the Log on as: parameter in the Service section of the ICU is a user that has read and write access to the folder where the shared file will reside.11 Group Exercise . it will be simplest to put it on one of the interface computers. Setup a file share folder and assign the permissions so that both primary and backup interfaces have read and write access to the file. and will coach you if you need assistance during the activity. Your instructor will have instructions. 1. Configure The Interface Parameters 1. Choose a location for the shared file. · The Failover ID number for its backup interface. The file can reside on one of the interface nodes but OSIsoft strongly recommends that you put the file on a dedicated file server that has no other role in data collection. Page 169 . 1. Select the HOT type of failover. Exercise Description You have a working interface and a backup interface. Use the Failover section of the Interface Configuration Utility (ICU) to enable failover and create two (2) parameters for each interface: · A Failover ID number for the interface.High Availability 13. Select The Synchronization File Path And File To Use For Failover. 2. 2. All other command line parameters for the primary and secondary interfaces must be identical. Exercise Objectives Implement interface failover.HA Step 3: Implement Interface Failover This solo or group activity is designed to maximize learning in a specific topic area. 2. Approach Note: There are multiple steps in this approach. Device Status 1. you must point the primary and secondary interfaces to different members of the collective by setting the SDK Member under the PI Host Information section of the ICU. Page 170 . Device Status 2. You will not have to recreate the digital state set or failover points. Right-click on the points and select Create all points (UFO Phase 2) to create seven (7) PI points for the interface: the Active ID. Heartbeat1. Test it Before you start testing start the Interactive message logging: pigetmsg –f This file is in \PIPC\ADM folder. Interface 1 State.PI System Architecture. Planning and Implementation 2. Repeat for the second interface. Heartbeat2. Configure the Digital State Set / PI points 1. 2. If you use a PI Collective. Right-click on the Digital State point and select Create UFO_State Digital State Set on Server … to create the required digital state set. and Interface 2 State. You should see that interface start and become the “Backup.High Availability In order to test that failover is working correctly you will have to have a properly running interface and then start the second. Page 171 . Tip If you have PI ProcessBook you can watch the data on each server and see that it should not get interrupted.” Then you can stop the “primary” interface and you should see the change reflected in each log file. A yellow warning icon indicates that the server is available but has errors. Planning and Implementation 13.12 Collective Manager Use the Collective Manager to create new PI collectives.PI System Architecture. Page 172 . A red X indicates that the server is unavailable. An icon in the diagram represents each server in the collective. Status and Connection Status show the associated errors. A green check mark on the icon indicates that the server is communicating properly. configure existing collectives and their servers. and view the status of collectives. Approach Install the same version of the PI Server software on the secondary PI Server machine. select “A newly installed PI Server”. use Connection Manager in the PISDKUtility tool to add the PI Servers by their hostnames or IP Addresses. Select the secondary server from the list the collective manager displays. Exercise Objectives Learn how to create a collective using the PI Collective Manager Exercise Description You need to form a Collective by combining two existing PI Servers. Once the PI Servers are established.13 Group Exercise .HA Step 4: Form the Collective This solo or group activity is designed to maximize learning in a specific topic area. Use the PI Collective Manager to initialize the secondary. Page 173 . you should see two PI Servers with green check icons. When you are finished. When this process is complete. Create New Collective. The Collective Manager will: • • • • • code the collective formation backup the primary server shutdown the secondary server replicate to the secondary server from the primary server backup and then restart the secondary server.High Availability 13. Run the Collective Manager in Start. and answer the questions. and will coach you if you need assistance during the activity. open the PI Collective Manager and establish the collective based upon your two PI Servers. Whichever PI Server is to become the secondary server will lose all its data and databases. When asked if the primary is an existing server or a newly installed server. Select the archives from the primary that you want to replicate to the secondary. Start the secondary server. On each PI Server. You will have to perform the following: • • • Name your collective. and how fast the network is. PI System. Collective creation may take some time depending on how many archives you elected to copy. then add the secondary to primary server’s PI Connection Manager. Make sure you can see both servers in the SMT and use your PI SMT to validate that the servers are running. Your instructor will have instructions. each PI Server should have both PI Servers in their respective Connection Manager. Go to File. All Programs. Build the trusts on the primary PI Server. . Planning and Implementation If you do not see these icons. try to Reinitialize the Collective.PI System Architecture. Tip Page 174 Create trusts for both primary and secondary PI Server to be able to use PI-SMT from both machines. You should use the PI Connection Manager to verify that you have a Collective and not two individual PI Servers. The list must be in numerical order (that is. we learned about the two buffering mechanisms. Pibufss renames it to [REPLICATEDSERVERLIST_SAVED] the first time it runs.1 PI Buffer Subsystem These server strings are entered as a numbered list in the PICLIENT. Regardless of settings. The strings are case insensitive. if there is a BUFSERV2. Otherwise.INI file. the Buffer Subsystem automatically detects the PI Collective configuration. The server names must comply with the following rules: All strings must represent a valid network path. the PI Servers must all be part of the same PI Collective. IP addresses are accepted. The PI ICU is simply configuring the piclient.ini file. The exact order of the entries does not matter as long as the numbers are continuous. there must be a BUFSERV1).INI The most important parameter is the list of PI Servers that need PI API buffering. In the case of PI Buffer Subsystem.INI file under the [BUFFEREDSERVERLIST] section.14. The easiest way to configure the buffering is to use the PI ICU. use Fully Qualified Domain Names (FQDN). If forward name lookups are provided by a DNS. Note: Pibufss does not require the [REPLICATEDSERVERLIST] section in PICLIENT.14 Buffering Mechanisms and Data Replication Earlier in the course. If a section [REPLICATEDSERVERLIST] exists in the PICLIENT. The strings must exactly match the string specified in the /HOST= command-line parameter of PI Interfaces (usually found in a batch command file). so it does not matter if you choose to use that tool or manually edit the file. 13. The configuration parameters for both buffering mechanisms are shared in a single file and use similar formats. The minimum number of entries necessary depends on how many different PI Servers are defined Page 175 . Buffering is critical to the HA process because it is the mechanism that “fans” or replicates the data for each PI Server in the PI Collective. The Buffer Subsystem does not need all PI Servers to be specified in the [BUFFEREDSERVERLIST] section. The PI Buffer Subsystem does not support buffering to multiple PI Collectives and only a single Pibufss instance can run on one machine. All changes require a restart of the buffering subsystem. The entries are of the form: BUFSERVN = PIServerName where N is an integer starting at 1.High Availability 13. The PI Buffer Subsystem configuration is achieved through entries in the file: \PIPC\DAT\PICLIENT.INI file. This behavior is accomplished by setting AUTOCONFIG to 1 in the PIBUFSS section of the .domain.INT BUFSERV2= S2.DOMAIN.PI System Architecture.PIbufss Interactive Mode.2 Testing Run the command: pibufss -cfg from the PI ICU or from a command prompt window.INT).INT 2 S2. regardless of how many are defined in the [BUFFEREDSERVERLIST] section.DOMAIN.DOMAIN.replicated hosts: 2 1 hostname: s1 (bsl: S1.DOMAIN.INT *** Cached PI server configuration.DOMAIN. Planning and Implementation after the /HOST= parameter of PI Interfaces (or PI API applications) that require buffering. The error is: -11419 Buffering is supported for only one PI Server or Collective. status: [0] Success *** Validated API servers (bufferedserverlist). select Tools > Buffer Subsystem > Run pibufss -cfg.ini file. With the default settings.int. Pibufss detects the PI Collective configuration and sets up N-Way buffering to all replicated PI Servers. role: 1 fqdn: s1. select Tools > Buffering and in the Buffering dialog. Time: 20-Nov-08 15:54:06 Configuration Query. id: 209d6f49-8d3d-470d- Page 176 .INT For a complete list of the switches used in each section consult the PI Buffer Subsystem User Guide. count: 1 server/collective: HASRV (last update: 20-Nov-08 15:47:05) serverid: dbe4d7ca-7a9c-4d5d-9b35-14618c0127fe . count: 2 1 S1. Below is an example: [APIBUFFER] BUFFERING= 1 [PIBUFSS] AUTOCONFIG= 1 [BUFFEREDSERVERLIST] BUFSERV1= S1.14. Caution: Specifying extra PI Servers in the [BUFFEREDSERVERLIST] that are not part of the target PI Collective results in a fatal error from Pibufss and prevents proper startup. PI ICU automates this key step of API buffering configuration. In PI ICU. The following output shows the activity on each buffering queue: --. 13. or most likely.int. regid: 1 events sent: 0. A state of Disconnected indicates a failure to connect. queued events: 0 2 [s2] state: Registered. A state of Connected could be a transient. and successfully registered with the PI Snapshot Subsystem. authenticated. successful connections: 1 firstcon: 20-Nov-08 15:46:54.INT). snapshot posts: 0. successful connections: 1 firstcon: 20-Nov-08 15:46:51. lastreg: 20-Nov-08 15:46:52.High Availability a23e-18a3ebcbb92b 2 hostname: s2 (bsl: S2.DOMAIN. a failure to authenticate. snapshot posts: 0. count: 2 1 [s1] state: Registered. queued events: 0 Each buffer session should be in the Registered state. Check the PI Trust definition if necessary. id: 98a80524-9d57-48e48b0e-be9abc28df1d *** Current buffer sessions. role: 2 fqdn: s2. lastreg: 20-Nov-08 15:46:55. regid: 1 events sent: 0. Page 177 . which indicates the PI Buffer Subsystem is connected.domain. Make sure all the servers in your collective are Page 178 .PI System Architecture. 3. 4. On this interface machine. Your instructor will have instructions. configure the PI Buffer Subsystem.HA Step 5: Configure N-Way Buffering This solo or group activity is designed to maximize learning in a specific topic area. Once the mechanism has restarted the service and finished. Exercise Objectives Learn how to configure and test n-way buffering. Approach 1. using the PI ICU and selecting Tools>Buffering…. You need to have the data replicated across your PI Servers in the Collective. Exercise Description You have a working interface writing data to a single PI Server. Does it connect to the collective? 2. Start the interface on the first machine. Enable buffering with the PI Buffer Subsystem. and will coach you if you need assistance during the activity. and then select your collective from the drop-down menu. Planning and Implementation 13. select Buffered Servers.15 Group Exercise . Verify that data is being collected. Page 179 . stop them. At this point make sure that the PI OPC Interface has a dependency set for Pibufss. 5. The points should be generating data. Start the PI Buffer Subsystem and then start the PI OPC interface Note: Remember.High Availability listed and checked. Only proceed once you can validate that each PI OPC Interface and PI Buffer Subsystem combination are working correctly. the buffer mechanism must start before the interface. Check the log files for any errors or problems. Stop the interface and repeat the process on the second interface machine. 8. 6. 7. Open a command prompt and navigate to the \PIPC\bin\ folder and enter: pibufss -qs This will give you statistics on the Buffer Subsystem. If either the PI Buffer Subsystem or the interface is running. PI System Architecture. Planning and Implementation Page 180 . Exercise Description You think you have everything running correctly. add a random point to the collective by copying CDT158 to CDT69 on the primary server. Can you do it? · Check your Collective Manager on the secondary server – what does it show? · Restart the Primary PI Server 5. Returning to PI ProcessBook. 2. 4. Be sure to use your OPC points. Create another trend and add these points to it.bat).High Availability 13. Exercise Objectives Test your High Availability PI System. Can you do it? · Page 181 . Using the connections box reset your PI ProcessBook session to use the Primary PI server. Shutdown the Secondary PI Server Is your PI ProcessBook trend active? Did it switch connections again? Did the Primary PI Server lose data while it was down. Test the system to make sure all of the failover and redundancy solutions are working. Verify that both PI Servers are broadcasting live data for the same point. Prove it.HA Final Step: The Road Test This solo or group activity is designed to maximize learning in a specific topic area. You may also want to add the heartbeat points. Force a failover in the Connection Manager in PI Processbook.16 Group Exercise . Use PI Tag search to verify that CDT69 exists on your secondary server. One of the interface active points (INTF_1_State) should have a value of primary and the other (INTF_2_State) should have a value of backup. · Is your PI ProcessBook trend active? Did it switch connections? · Check \PIPC\bin\pibufss -qs on the primary interface computer (the one that has that status in the active points) – is the data for the Primary Server queuing? · Try to add another Random point. Using the PI SMT tool. 3. or did the buffer work? · Check \PIPC\bin\pibufss -qs on the primary interface computer (the one that has that status in the active points) – is the data for the Secondary Server queuing? · Try to add another Random point. Approach Perform any or all of the following actions: 1. Install PI ProcessBook (if it is not already installed) and create a trend against the collective. Shut down the Primary PI Server (using \pi\adm\pisrvstop. and will coach you if you need assistance during the activity. Your instructor will have instructions. failover as necessary until you are connected to the secondary server. Is it processing data for both servers? Restart the Primary Interface and check for a good start. Stop the Primary Interface (with the ICU or System Services Applet) · Did the other interface pick up data collection properly? Do you have updates in PI ProcessBook? · Do the Interface Status and Heartbeat points look appropriate? · Check the PI Message logs on the interface computers using the PISDKUtility · Check pibufss -qs on the secondary Interface (now with the primary status). restart the Backup Interface. · · · Stop the Backup Interface (with the ICU or System Services Applet) Did the other interface pick up data collection properly? Do you have updates in PI ProcessBook? Do the Interface Status and Heartbeat points look appropriate? Lastly. Planning and Implementation · Check the Collective Manager on the primary server – what does it show? Restart the Secondary PI Server Switch PI ProcessBook back to the secondary server or use PI SMT – did the Secondary Server pickup your new Random point? Did the buffer work for the Secondary PI server such that you did not lose data? · 6. · 7. Page 182 .PI System Architecture. Validate that both PI Servers and both interfaces are running correctly. Review the components of High Availability.High Availability 13. Using PI ProcessBook. how would you validate that replication is occurring? 3.High Availability Debriefing The following questions are intended to reinforce key information presented in this chapter or section. Page 183 . On the PI Server. Explain the difference between UniInt Failover Phase 1 and Phase 2. how would you determine if all PI Servers in your collective are up and functioning properly? 2. Answer the following: 1.17 Group Recap Question . How would you test that N-Way buffering is working? 4. High Availability and Complex Architectures Servers in a collective can reside on different networks and communicate through firewalls. There are no issues with name resolution or security authentication. Planning and Implementation 14. including the PI Server and interfaces. both domains trust each other.PI System Architecture. Page 184 . Some scenarios are: • • • Server Farms Process Control Network / Corporate Network Geographical Process Control Network PI AF Server Secondary PI Server Primary PI Server ` Client PC Interface Interface Active Directory The ideal situation is where there is one domain (or trusted domains) where all of the machines in the domain. If PI AF Server is in the office/corporate network. can “see” each other. The firewalls will have to be set correctly and perhaps host files set in the Process Control network so the machines can access the Primary PI Server. The PI System uses N-Way buffering to send data outside that structure to a Primary PI Server on a Corporate Domain. the Secondary PI Server and the Interfaces are in a Process Control Domain / Workgroup. This situation will present issues of authentication between the PI Servers for replication and issues for the interfaces and N-way buffering.High Availability and Complex Architectures Process Control Network ` Secondary PI Server Primary PI Server Client PC PI AF Server Interface Interface Active Directory In a more complex example. Page 185 . The users can see the Primary PI Server and PI AF but cannot see the Secondary PI Server or interfaces. Users may not be able to be resolved across PI Server members. the PI Servers will have to be synchronized manually.2 Disconnected Startup UniInt Interfaces include the functionality to take advantage of the Disconnected Startup operation. Planning and Implementation Process Control Network ` Primary PI AF Server Secondary PI AF Server ` Client PC Client PC Primary PI Server Secondary PI Server Interface Interface Active Directory Active Directory Above. However when a Secondary PI Server has archives in a different location. they should be on a read-only partition. you must register them manually to make them available. Archive shifts on different PI Servers are not synchronized. The registration of the archives moves with the files that are part of the initializing or reinitializing. This will present significant routing and security challenges. 14. One side effect of this is that an archive cannot be moved from one server to another server easily. It is maybe required to have PI AF Collective so that every client will have access. If multiple PI Servers mount the archives. This can be useful if you have many old archives and you wish to allow multiple servers in the collective access to them. In the worst-case scenario. Archive Shifts can and do happen at different times on each PI Server in the collective. in the more complex example. there are multiple domains involved. These topics are discussed below. 14. It is possible to place archive files on a Storage-Area Network (SAN) drive.1 Managing Archives on Replicated Servers Secondary PI Servers that have archives in the same directory structure as the Primary PI Server are easy to manage. Disconnected startup allows the interface to start from a local cache file with or without a valid Page 186 .PI System Architecture. and none of them can “see” each other. This increases the availability of the archive data because a shift that takes a long time or fails on one PI Server still leaves the other servers available to receive and serve data. which in turn delays the ability of the interface to begin data collection from the Data Source. especially when large point counts are being used. Using the disconnected startup feature when a PI Server connection is available bypasses potentially long delays caused by the latency in network calls required to gather point information from the PI Server. and Digital State information needed to start the interface. PI point configuration. They contain the required PI Server version. The first time the interface is started with the disconnected startup parameter set. Using disconnected startup will improve interface startup time.High Availability and Complex Architectures connection to the host PI Server. This prevents data loss when an interface needs to start up and it does not have a connection to the PI Server. The time to startup will be delayed while the cache files are created. the interface can actively collect and buffer data retrieved from the Data Source when no connection to the host PI Server is available. Once started. a connection to the PI Server is required to populate the cache files with the necessary data to support the disconnected startup feature on subsequent interface restarts. Page 187 . PI System Architecture. Planning and Implementation 14. Each server knows of its place in a collective because of its role. The PI Collective Manager is used to write these parameters into the internal databases of each PI Server in the collective. Page 188 .3 Changing the Collective Hierarchy The PI Collective hierarchy is simply an entry in the PISERVER and PICOLLECTIVE tables within each of the PI Server internal databases forming the collective. 2 = Secondary PI Server. 1 = Primary PI Server. There are three possible roles: • • • 0 = stand-alone PI Server. You need to be able to promote a secondary computer to Primary. Promote the secondary computer with the console command: piartool -sys -promote 3.High Availability and Complex Architectures 14.bat. In the Collective Manager on the new Primary. since PI AF Server lives on the same machine.exe on each server. Exercise Objectives Learn to reconfigure the Collective Problem Description You want to be prepared if you Primary PI Server is ever destroyed. You must use the command line utility piartool. Your instructor will have instructions. 2. Stop the Primary PI Server by running pisrvstop. confirm the new configuration. Approach Note: You cannot do this exercise using Collective Manager. DO NOT shutdown the machine.4 Exercise – Change the Primary PI Server This solo or group activity is designed to maximize learning in a specific topic area. and will coach you if you need assistance during the activity. Page 189 . 1. 5. Page 190 . Note: You will need to clear your Know Servers table.5 Untrusted Domain Issues The PI HA Collective is designed to operate with a single domain or trusted domains where fully qualified name resolution functions across domains. 3.PI System Architecture. Backup the Primary PI Server. Copy all of the files to the Secondary. Planning and Implementation Start you old Primary PI Server and re-initialise from the new Primary PI Server. To initialize manually: 1. For the case of untrusted domains. 14. form the collective manually on each PI Server manually by using the piconfig command. Issues arise when PI Collective members are in different.1 Collective Creation and Initialization The Collective Manager has to have Windows file copy access and FQDN resolution between members of a Collective to function. untrusted domains. 2. Restore the Secondary. What is the best way to do this? Hint: Recreate? 14. then the only behavior you will observe is that a User SID will appear in the Security tables on secondary nodes.5. It will show an error (yellow text box background) until you get the full name complete and correct. You will have to enter it into the name field. then tell the server and the members that cannot resolve the name to ignore that user. This commonly occurs when one of the PI Servers has a local user or the Collective members are in different domains. Note: This tuning parameter is not exposed by default.High Availability and Complex Architectures This process must be repeated each time a change is made to the Primary PI Server. If the user is known to the Primary PI Server.2 Security Usually all Collective members have a common user database – the domain(s) Active Directory. then simply add that user and let it replicate. Note: This must be done on each member because tuning parameters are not replicated between servers. This change requires restarting the PI Base Subsystems on each member. One solution is to create the user on the Primary PI Server. users may be desired on a PI Server in a Collective that are not exposed to all members of the Collective. 14. In some cases. Tell the members to ignore that user by setting the tuning parameter Base_AllowSIDLookupFailureForMapping to 1 on each Collective member. If you set the tuning parameters correctly. Page 191 . perhaps the easiest is to use the Sysinternals command line utility psGetSID. you must add an identity to the Primary PI Server that is that SID. When this is replicated to the proper secondary node.microsoft.PI System Architecture.com and search for the phrase sysinternals. Planning and Implementation If the user is not known to the Primary PI Server. Page 192 . the user or group name should appear in the list of identities. Visit http://technet. This can be accomplished in a number of ways. determine the User SID on the Secondary. Once you have the SID for the user or group. Note: Windows Sysinternals suite of tools is a free Microsoft Technet suite of utilities that can be downloaded from the technet site. 2. Validate on the secondary PI Server that the Identity is resolved correctly. Approach 1. Your instructor will have instructions.High Availability and Complex Architectures 14. 3. and will coach you if you need assistance during the activity.6 Exercise – Add a Local User to a Secondary Node This solo or group activity is designed to maximize learning in a specific topic area. Problem Description Your servers are in different domains. . 4. the Principal is the User SID. add the mapping for the local user to the Primary Security Configuration in PI SMT.exe application to determine the SID of that user on the secondary PI Server. and PIIdent is the name of the PI Identity you want to map to. Principal. Add the user to the Primary and let it replicate. Page 193 . Add a local Windows user account to your secondary PI Server. Exercise Objectives Learn to add local (non-domain or cross-domain) users. Set your tuning parameters to ignore name lookup failure (Base_AllowSIDLookupFailureforMapping). add that SID to the PIIdentMap table using piconfig: @mode create @tabl PIIdentMap @istr IdentMap. Do one of the following: On the Primary PI Server. but adding users to the secondary server in a Collective is not allowed. You need to add users to a secondary server. PIIdent <<Data goes here>> Where IdentMap is the name of the mapping (example: MyMapping1).OR On the Secondary PI Server. Handle the fact that the primary computer will complain that is it not a valid or irresolvable user. Use the Sysinternals psGetSID. Restart pibasess on the servers. PI System Architecture.1 To Push or To Pull The PI to PI interface is said to “push” or to “pull” data based on whether you run the interface on the Source PI Server or the Target PI Server. The PI to PI Interface The PI to PI interface copies point data from one PI Server to another. meaning data is copied from the source to the receiving PI Server (also referred to as target PI Server). Page 194 Target PI Server . Planning and Implementation 15. Source Interface PI Server The PI to PI Interface in a “Push” configuration. 15. Interface Source PI Server Target PI Server The PI to PI Interface in a “Pull” configuration. Data is moved in one direction. and signs up with the Source PI Server. see "PI Point Configuration" in PI to PI TCP/IP Interface.5.The PI to PI Interface 15. version 3. For more information. In normal (Snapshot) mode. the interface acts much like PI ProcessBook or any other client would. What’s the big difference between the two? Compression.5. This is primarily: Point Source Location Codes InstrumentTag For more information. the interface will periodically (based on the scan rate) read the values for the points from the archive on the Source PI Server and send those values to the Target PI Server.3 Identical Data. and all new values are queued and sent to the Target PI Server. Page 195 . see "Data Collection" in PI to PI TCP/IP Interface. 15.2 What Kind of Data Collection? The PI to PI Interface has the capability of running in a history recovery only mode (Archive Data) or the live tag data as it is received on the Source PI Server (Snapshot Data). In history recovery only mode (Archive). This means that any of the interface specific point attributes will have to be adjusted accordingly. the Source PI Server is collecting the data from the device and the Target is not. version 3.8. Identical Points? While the data is identical for the points.8. PI System Architecture. Planning and Implementation This page intentionally left blank. Page 196 . Port: Service . possibly for iViews and PI Page 197 . HTTPS. for clock synchronization ---------------------------------------------------------------------------------------135: DCOM port mapper . SharePoint .Name resolution ---------------------------------------------------------------------------------------80: HTTP. iViews.Ports 137:139 are considered high-risk and are usually blocked.Windows authentication. 1434: MS SQL Server (From: http://technet.Appendix A – Ports Appendix A – Ports You will of course.Time protocol.Windows name resolution ---------------------------------------------------------------------------------------53: DNS .Ports 137:139 are considered high-risk and are usually blocked. other Microsoft resources. Ports 137:139 are considered high-risk and are usually blocked. This information is found under OSIsoft Technical Support Knowledge Base article # 2820OSI8. services.microsoft.Windows 2000. PI Coresight ---------------------------------------------------------------------------------------88: Kerberos .microsoft. ---------------------------------------------------------------------------------------636: LDAP SSL.com/en-us/library/cc646023. ---------------------------------------------------------------------------------------138: NETBIOS Datagram Service .Comments: ---------------------------------------------------------------------------------------44: WINS . and for initialising a collective.aspx and see Configuring the Windows Firewall to Allow SQL Server Access from: http://msdn.for PI WebParts. Port is high risk and is usually blocked ---------------------------------------------------------------------------------------137: NETBIOS Name Service .aspx. ---------------------------------------------------------------------------------------1433. ---------------------------------------------------------------------------------------389: LDAP ---------------------------------------------------------------------------------------443: HTTPS and SSL for websites running for PI WebParts ---------------------------------------------------------------------------------------445: MS Windows port for accessing administration shares. The following ports may need to be opened on a firewall to allow access to PI or other associated services. have to open certain network ports for the applications to communicate. ---------------------------------------------------------------------------------------139: NETBIOS Session Service . XP authentication ---------------------------------------------------------------------------------------123: NTPNetwork . DCOM applications including OPC.com/enus/library/ms175483.NetBIOS name resolution.). PI System Architecture. for iViews and PI WebParts ---------------------------------------------------------------------------------------3268: LDAP GC ---------------------------------------------------------------------------------------3268: LDAP GC SSL ---------------------------------------------------------------------------------------3389: Windows Remote desktop . Planning and Implementation WebParts.Used by PI ACE 2 scheduler to allow connections from the PI ACE Web Service ---------------------------------------------------------------------------------------5457: PI PI Asset Framework (PI AF) ---------------------------------------------------------------------------------------5458: PI Notifications ---------------------------------------------------------------------------------------5459: PI OLEDB Enterprise.Used by to allow connections to the PI SQL Data Access Server April 2012 Page 198 . PI JDBC Driver ---------------------------------------------------------------------------------------5459: PI AF 2.x HA Collective status. and PI Web Services.Remote desktop for PI server administration ---------------------------------------------------------------------------------------5450: PI Network Manager (subsystem of the PI Server) ---------------------------------------------------------------------------------------5454. PI WebParts. PI Coresight ---------------------------------------------------------------------------------------5461: PI JDBC Driver . 5455: PI Analysis Framework (PI AF 1. ---------------------------------------------------------------------------------------1521: Oracle SQL*Net.x) ---------------------------------------------------------------------------------------5456: PI ACE .
Copyright © 2024 DOKUMEN.SITE Inc.