pptph 6 0 technical presentation

1、GE Intelligent Platforms Proficy Historian Technical Information and 6.0 updateScott Duhaime Senior Product Manager June 2015Imagination at work.GE privileged and confidential2Presentation Details Product Overview High level Solution Architecture Overview Component Description Product Packaging & In

2、stallation New 6.0 Components Troubleshooting Tips Appendix Details on Mirroring“Proficy Historian is the mostefficient storage model for timeseries data on the planet”3Eric Pool, Consulting Engineer & Chief Architect, Atlanta M&D CenterAre you getting these results? 30,000 hours of operating data 1

3、,600 global assets 50 terabytes of data 100 million fleet operating hours$100 million cost savings for customers in one yearAtlanta M&D Center is With Proficy Historian. Let us help you.4What is Proficy Historian? Collect, store and distribute time series process dataCollectStoreDistribute Time seri

4、es process data Native collectors & toolkit Expressions 20 million tags HighAvailability Data compression PHA/PKC Excel-add in Native API Big data on- ramp Proprietary data archiving and compression technique Native collectors and APIs to easily get data in and out of Historian Foundation of the Ind

5、ustrial InternetGE Chairman Jeff Immelt at GE IPUser Conference: “Industrial Internet is about business outcomes.”Data SourcesHistorian Solution ArchitectureHTML5 Based Clients Historian Admin Console PHA / PKCClient Access APIOLEDBSDKOPC HDA ServerExcel Add-inHistorian Windows Admin iFIX/CIMPLICITY

6、RTIPClientsOther ComponentsHistorianCollectorCollectorProgramTag CacheME CollectorOPC CollectorOPC A&E CollectoriFIX CollectorFile CollectorOSI PI CollectorDataBufferHistorianAPICalc CollectorPerfMon CollectorSim CollectorS2S CollectorExpressionEngineCollector ToolkitS2S Distributor Proficy REST Ser

7、vicesHistorian APIHistorian APINetworkHistorian APIHistorian APIPort 14000Port 14000Config MgrData ArchiverMirror NodeDiag MgrClient MgrAlarm ArchiverData StoreData StoreData StoreArchives (*.iha)Client MgrData ArchiverMirror NodeDiag MgrAlarm ArchiverData StoreData StoreData StoreArchives (*.iha)En

8、terprise HistorianStored ProceduresAEDB (SQL)Data CollectionProficy HistorianSCADAPLCsOther HistoriansProficy HistorianCollector Framework7Historian Server OverviewProficy Historian is a high performance data archiving system designed to collect, store, and retrieve time-based information at extreme

9、ly high speed efficiently. The system architecture consists of the following:Historian ServerThe Historian server is the central point for managing all of the client and collector interfaces, storing and (optionally) compressing data and retrieving data. All tag data (numbers, strings, BLOBs) are st

10、ored in a proprietary format in the archive database. The Archive Database consists of several files, each of which represents a specific time period of historical data.The Historian Archive indexes all information by Tagname and Timestamp. The Tagname is, a unique identifier for a specific measurem

11、ent attribute. For iFIX users, an Historian Tagname normally represents a Node.Tag.Field (NTF). Searching by Tagname and Time Range is a common and convenient way to retrieve data from Historian. If you use this technique to retrieve data from the Archiver, you do not need to know which archive file

12、 on the Historian Server contains the data. You can also retrieve data using a filter tag.Historian is capable of storing many different data types, such as Float, Integer, Strings, Byte, Boolean, Scaled, and BLOB (undetermined binary data type). The source of the data defines the ability of Histori

13、an to collect specific data types.If licensed for the ”Alarm and Event” option then the server also manages the storage and retrieval of OPC alarms and events in a SQL Server database.Pictured: Historian Enterprise Server NodeHistorian Data Storage and ArchivingHistorian features a patented and prop

14、rietary data storage format, that provides nearly 10-to-1 compression over other standard data storage mechanisms, and is stored in binary format.Data StoresA logical collection of tags used to store, organize, and manage tags according to the data source and storage requirements. Includes logical a

15、nd physical storage definitions.ArchiveHistorian archives are stored as data files, each of which contains data gathered during a specific period of time. A Data Store can have multiple archive files (*.iha).The ihArchives table contains Historian archive configuration information and performance st

16、atistics for each archive, which include: archive name and status, file size information, start and end time, row count, data store name, and more.Historian Collector OverviewCollectorsData Collector gathers data from a data source on a schedule or event basis, processes it, and forwards it to the H

17、istorian Server for archiving. The following figure shows the data flow in a typical Historian system from a data source to the archive.Each collector performs some functions common to all types of collectors (except the File Collector). These functions are: Maintains a local cache of tag informatio

18、n to sustain collection while the server connection is down. Automatically discovers available tags from a data source and presents them to the Historian Administrator. Buffers data during loss of connection to the server and forwards it to the server when the connection is restored. Automatically a

19、djusts timestamps, if enabled, for synchronizing collector and archiver timestamps. Supports both collector and device time stamping, where applicable. Schedules data polling for polled collection. Performs first level of data compression (collector compression). Responds to control requests, such a

20、s pause/resume collectionMain Components of Data Collector Software Data Collector Program the executable data collection program for the type ofcollector. For example, ihFileCollector.exe. Local Tag Cache a cache of configuration information that permits the collector to perform collection even whe

21、n the archiver is not present at start-up (*.cfg). Local Outgoing Data Buffer a buffer of the data sent to the server that the server has not yet confirmed receiving. Historian API an interface that connects the collector to the Historian Server for configuration, data flow, and control functions. E

22、xpressions Engine Use Python expressions to pre-process raw data before the result is stored in Proficy Historian. A library of functions and modules is available for use, or you can use a valid expression, construct the JSON, and add the expression in the File Collector or Excel Add-in.Other Profic

23、y Historian ComponentsComponentDescriptionHistorian APIAll client applications retrieve archived data through the Historian API. The Historian API is a client/server programming interface that maintains connectivity to the Historian Server and provides functions for data storage and retrieval in a d

24、istributed network environment.User APIThe Historian User API is intended to provide high speed read/write access to Historian data and read access to Historian tags. There is no access to alarms, events, or messages. Use the API to develop applications in C or C+, which read and write data to the H

25、istorian server when the Historian SDK and Historian OLEDB do not meet your project requirements for performance or programming language. Proficy Historian allows you to develop both 32-bit and 64-bit User API programs.Client Access APIMost applications today rely on .NET based development platforms

26、 from Microsoft. To enable easier integration with Proficy Historian, a .NET API is provided. The Client Access API supports both 32-bit and 64- bit Windows Operating Systems.REST APIProficy Historian now allows you to use REST APIs built on Predix Web server platform. This allows programs written i

27、n Java to connect to Proficy Historian and to read and write data.OLEDBOLE DB is a collection of standard COM-based interfaces, defined by Microsoft, which abstract standard SQL commands into native API access for any data source. The Historian OLE DB Provider is a data access mechanism that allows

28、Historian data to be directly queried using Structured Query Language (SQL) statements.SDKThe Software Development Kit (SDK) is designed for writing Visual Basic (VB) or Visual Basic for Applications (VBA) Scripts. Using the SDK, you can develop your own scripts to perform selected repetitive or com

29、plex tasks or to make your own custom user interface.Collector ToolkitThe Collector Toolkit lets you write programs that integrate tightly with Proficy Historian and let you leverage the same configuration tools, redundancy schemes, and health monitoring as collectors that ship with Proficy Historia

30、n. A custom collector is a collector developed using the Collector Toolkit. It collects data and messages from a data source and writes them to a Data Archiver.OPC HDAThe Proficy Historian OPC HDA Server reads the raw data stored in Proficy Historian and sends it to the interested OPC HDA clients. O

31、PC HDA compliant clients can connect to the Proficy Historian HDA Server to 11acquire and analyze data.Proficy Historian TablesTableDescriptionihTagsContains the set of tag names and the properties of each tag. This data is mostly the information that the administrator enters through the Tag Mainten

32、ance screen in the Historian Administrator application. Each row in the table represents one tag.ihArchivesHistorian archives are stored as data files, each of which contains data gathered during a specific period of time. The ihArchives table contains Historian archive configuration information and

33、 performance statistics for each archive. Each row in this table represents one archive.ihCollectorsContains the configuration and status information for each collector connected to the Historian Server. Each row in this table represents acollector that is connected to the archiver.ihMessagesContain

34、s Historian messages such as alerts, informational topics, and connection information contained in the audit log. Each row in this table represents a message.ihRawDataContains any collected data for each tag contained in the Historian Server. It contains not just raw data, but also calculated data a

35、nd interpolated data. This table is the one typically used for reporting. There is one row in the ihRawData table for each combination of tagname and timestamp.ihCommentsContains the annotations associated with the collected data. There is a separate row of data in the ihComments table for each comm

36、ent associated with a tag. It is possible to have different data types of annotations. Comments are most often strings, but can be binary numbers or BLOBs. Only string comments are returned in the ihComments tableihTrendAllows you to compare multiple tags for the same timestamp. It contains a row of

37、 data for each unique timestamp, but with columns from one or more tags. The column names are dynamic and determined by the returned tag names. The ihTrend table is similar to a pivot table or, for instance, a cross-tab report. The ihTrend table can store up to 100 columns in a returned set.ihQuery

38、SettingsContains the current session settings. These settings get applied to all queries you make in a session, unless overridden with a WHERE clause. This table displays settings stored in the provider; it has nothing to do with the data stored in the archives. The ihQuerySettings table provides a

39、convenient way to display all of your session settings. You cannot, however, write or update settings in this table. This table only contains one row with the settings for the current session only. The only way to change these parameters is by using the SET statement.ihCalculation Dependenciescontai

40、ns the Calculation and Server-to-Server tags and their triggers.ihAlarmscontains the collected alarm and event data12Commercial Offer: Product Packaging and Installation13How Proficy Historian is soldStandard Edition Single node configuration without the Distributed services Same architecture as 5.5

41、 (Calc Collector and Server to Server Collector NOT AVAILABLE)Enterprise Edition Includes the REST Service Include the new HTML5 based Admin Console Supports up to three mirrors (primary + two additional nodes) on a single license Collector Expression feature comes enabledLink to documentation in Hi

42、storian Electronic BooksGetting Started Guide-Overview of Historian-Standard and Enterprise Offering14Historian 6.0 Enterprise Install New Integrated installer that chains allthe necessary components Enterprise installer supports multiple topologies “Install Historian” link only installs theserver c

43、omponents Separate installers & links for the components (Collectors, Clients) Same install experience as other PMAS2.0 products.Link to documentation in Historian Electronic BooksInformation: Getting Started Guide-Overview of Historian-Standard and Enterprise OfferingPre-Requisites: Getting Started

44、 Guide-Setting up the Historian Environment-Pre-requisite software and set for Enterprise HistorianInstall Guide: Getting Started Guide-Installing Enterprise Historian SoftwareThere is also a link to the Getting Started Guide in the Release Notes link on the DVD, under Release Notes -Installing Prof

45、icy Historian6.0 and in the additional documentation link15Historian 6.0 Standard Install The install is very similar to the 5.5 Install Have to ability to install all the Historiancomponents. Separate Installers for the components Same install experience as other PMAS2.0 products.Links to documenta

46、tion in Historian Electronic Books:Information: Getting Started Guide-Overview of Historian-Standard and Enterprise OfferingPre-Requisites: Getting Started Guide-Setting up the Historian Environment-Pre-requisite software and set for Standard HistorianInstall Guide: Getting Started Guide-Installing

47、Standard Historian SoftwareThere is also a link to the Getting Started Guide in the Release Notes link on the DVD, under Release Notes -Installing Proficy Historian6.016Proficy HistorianNew Features with 6.017Proficy Historian 6.0Enterprise Class Data ManagementNew Features and Improvements in Profi

48、cy Historian 6.0Mirror StorageMirroring and RedundancyHistorian 1(Enterprise)Historian 2(Enterprise) Mirroring and Distributed Services (Data Redundancy, Scale and Availability) Multiple HA solutions Improved Read PerformanceImproved UI Diagnostic Dashboard and New Administration Console Central Adm

49、in across Enterprise Other Features Smart Collection (Expressions in Collectors) New REST based interface to Historian Enhancements to the PI Collector Improved integrated Enterprise Installer18Data Mirroring and Redundancy No longer bound by single server (Historian Data Archiver) Distributes Servi

50、ces nodes (Historian Client Manager, *Historian Configuration Manager, Historian Diagnostics Manager, Historian Data Archiver and Historian Alarm Archiver) All nodes are active, automatic switch over on failure for data and alarms Distributes load across mirrored nodes Reads are distributed across t

51、he nodes Collectors and clients can be distributed among the nodes Increased read performance, 1.5X faster with 2 nodesGE Confidential Distribute to Authorized Individuals Only Data Redundancy in a mirrored solution Mirrors are independent and can be used for disaster recovery strategy19* Config Man

52、ager can not be distributed in 6.0Data Mirroring and Redundancy Single config manager service, server will function in RO config mode on failure Multiple HA solutions Standard and Enterprise Single node supports Windows Clustering Mirrored solution supports failover and data redundancy solution Supp

53、ort up to 3 mirrors, also support single node. Data is written independently to each mirrorRead More on Mirroring in the Appendix! Can sync individual archives from the admin console. Mirroring needs time based archives Buffering mechanism available on failure Auto node replication for small data se

54、t Manual node replication for large data setsDocumentation available in Historian Admin Console Help20Historian REST Services Java based REST Service on the Predix Kernel framework Uses Predix STS based authentication, Impersonates to use the authorization on the server Uses the Historian System API

55、 to connect to the Historian Server Support all data operations, does not support alarmsavailable in Complete documented interface Historian eBooks21New Historian Enterprise ComponentsHistorian Client ManagerThe Historian Client Manager acts as the client connection manager and message router for the system. The Client Manager will examine messages and forward them to the correct DataArchiver or to Configuration Manager.Historian Configuration ManagerThe Historian Config