Uniformance. PHD Server. Specification Sheet R320

Transcription

1 Uniformance PHD Server Specification Sheet R320

2 Copyright, Notices, and Trademarks Honeywell International Inc All Rights Reserved. While this information is presented in good faith and believed to be accurate, Honeywell disclaims the implied warranties of merchantability and fitness for a particular purpose and makes no express warranties except as may be stated in its written agreement with and for its customers. In no event is Honeywell liable to anyone for any indirect, special or consequential damages. The information and specifications in this document are subject to change without notice. Honeywell, Experion, PlantScape, TotalPlant, Uniformance PHD, and Business FLEX are U.S. registered trademarks of Honeywell International Inc. Other brand or product names are trademarks of their respective owners. Honeywell Process Solutions 1860 W. Rose Garden Lane Phoenix, Arizona USA ii Uniformance - PHD Specification Sheet

3 Support and Other Contacts United States and Canada Contact: Honeywell Solution Support Center Phone: Calls are answered by dispatcher between 6:00 A.M. and 4:00 P.M. Mountain Standard Time. Emergency calls outside normal working hours are received by an answering service and returned within one hour. Mail: Honeywell HPS TAC, MS L W Rose Garden Lane Phoenix, Arizona Europe Contact: Honeywell TAC-EMEA Phone: Facsimile: Mail: TAC-BE02 Hermes Plaza Hermeslaan, 1H B-1831 Diegem, Belgium Pacific Contact: Honeywell Global TAC Pacific Phone: (toll free within Australia) (outside Australia) Facsimile: Mail: Honeywell Limited Australia 5 Kitchener Way Burswood 6100, Western Australia GTAC@honeywell.com India Contact: Honeywell Global TAC India Phone: Facsimile: Mail: Honeywell Automation India Ltd. 56 and 57, Hadapsar Industrial Estate Hadapsar, Pune , India Global-TAC-India@honeywell.com iii Uniformance - PHD Specification Sheet

4 Support and Other Contacts Korea Contact: Honeywell Global TAC Korea Phone: (toll free within Korea) Facsimile: Mail: Honeywell Co., Ltd 4F, Sangam IT Tower B4-4 Block 1590, DMC Sangam-dong, Mapo-gu, Seoul, , Korea People s Republic of China Contact: Honeywell Global TAC China Phone: Mail: Honeywell (China) Co., Ltd 33/F, Tower A, City Center, 100 Zunyi Rd. Shanghai , People s Republic of China Global-TAC-China@honeywell.com Singapore Contact: Global TAC South East Asia Phone: Facsimile: Mail: Honeywell Private Limited Honeywell Building 17, Changi Business Park Central 1 Singapore GTAC-SEA@honeywell.com Taiwan Contact: Global TAC Taiwan Phone: Facsimile: Mail: Honeywell Taiwan Ltd. 17F-1, No. 260, Jhongshan 2nd Road. Cianjhen District Kaohsiung, Taiwan, ROC Global-TAC-Taiwan@honeywell.com iv Uniformance - PHD Specification Sheet

5 Support and Other Contacts Japan Contact: Global TAC Japan Phone: Facsimile: Mail: Honeywell Japan Inc. New Pier Takeshiba, South Tower Building, 20th Floor, Kaigan, Minato-ku, Tokyo , Japan Elsewhere Call your nearest Honeywell office. World Wide Web Honeywell Solution Support Online: Training Classes Honeywell Automation College: Uniformance - PHD Specification Sheet v

6 This page is intentionally left blank vi Uniformance - PHD Specification Sheet

7 Contents 1. Architecture Overview...9 Architecture examples Important Considerations in PHD System Sizing Introduction Important Considerations in PHD System Sizing Introduction PHD Server Calculations and Virtual Tags Roles Data Collection and RDI Server Standard RDIs Available Remote Peer Interface PHD OPC Server PHD Applications Consolidated Event Journal (CEJ) EJC RDI for Consolidated Event Journal (CEJ) EPKS RDI for Consolidated Event Journal (CEJ) OPCAE RDI 1.10 for Consolidated Event Journal (CEJ) PHD to Relational Peer Tag Sync Experion Tag Sync Uniformance - PHD Specification Sheet vii

8 Contents Figures Figure 1 - Small scale PHD system... 9 Figure 2 - Medium scale PHD system viii Uniformance - PHD Specification Sheet

9 1. Architecture Overview A PHD implementation may consist of many different integrated hardware and software components depending upon the needs of the customer. The following architecture examples represent two of the many possible topologies that can comprise a PHD implementation. The architecture is highly scalable and not all nodes are necessary or required. In some cases, it may be advisable to combine multiple functions on a single Windows server; while in other cases; distributing functions across multiple servers may provide the best system security and scalability. The following guidelines apply to PHD 310 and subsequent releases. Architecture examples Small scale system Figure 1 - Small scale PHD system Uniformance - PHD Specification Sheet 9

10 1 Architecture Overview 2.1 Introduction Medium scale system Figure 2 - Medium scale PHD system 10 Uniformance - PHD Specification Sheet

11 2. Important Considerations in PHD System Sizing 2.1 Introduction The following tables outline the supported maximums for the PHD system. The ability of a customer to reach one or more of these limits depends on numerous considerations including, but not limited to the following: Server physical memory Processor speed Number of processors Disk space Number of system limits being stressed Network capacity Configuration and system tuning Amount of server load imposed by other applications. This Specification Sheet also identifies the recommended hardware. In the case of heavily loaded systems, it is recommended that Honeywell Services be consulted to plan an appropriate server configuration. As each installation will be uniquely tailored to the site s needs, there may be configurations that exceed specified limits. While these configurations may be acceptable; it is recommended that the site contact Honeywell to review the configuration. Some of the limits may be attained only when using high-end hardware - Honeywell Services should be consulted when in doubt. It is important to remember that PHD has been designed to take full advantage of all available hardware resources (such as number of processors, hyper threading, and memory) to provide maximum performance and capacity. ATTENTION The PHD Sizing Tool, SizePHD, must be used to verify that the proposed hardware configuration is consistent with the limits stated in this specification sheet. Uniformance - PHD Specification Sheet 11

12 This page is intentionally left blank Uniformance - PHD Specification Sheet 12

13 3. Important Considerations in PHD System Sizing 3.1 Introduction The following tables outline the supported maximums for the PHD system. The ability of a customer to reach one or more of these limits depends on numerous considerations including, but not limited to the following: Server physical memory Processor speed Number of processors Disk space Number of system limits being stressed Network capacity Configuration and system tuning Amount of server load imposed by other applications. This Specification Sheet also identifies the recommended hardware. In the case of heavily loaded systems, it is recommended that Honeywell Services be consulted to plan an appropriate server configuration. As each installation will be uniquely tailored to the site s needs, there may be configurations that exceed specified limits. While these configurations may be acceptable; it is recommended that the site contact Honeywell to review the configuration. Some of the limits may be attained only when using high-end hardware - Honeywell Services should be consulted when in doubt. It is important to remember that PHD has been designed to take full advantage of all available hardware resources (such as number of processors, hyper threading, and memory) to provide maximum performance and capacity. ATTENTION The PHD Sizing Tool, SizePHD, must be used to verify that the proposed hardware configuration is consistent with the limits stated in this specification sheet. Uniformance - PHD Specification Sheet 13

14 3 Important Considerations in PHD System Sizing 3.2 PHD Server It is important for all large scale system configurations, that the site validate performance and capability on the target configuration. 3.2 PHD Server Total number of tags 2,000,000 For higher-end systems or if a larger number of tags is required, it is recommended that Honeywell Services be consulted when planning or configuring these system. Data types supported Type I 32-bit Integer Type L 64-bit Integer Type F Single precision Type D Double precision Type C ASCII String Type U Unicode String Type B Binary Data - Maximum BLOB tag size 32,500 Maximum data size is controlled by two PHD parameters: MAX_USEVALLEN which defaults to 255. This controls the maximum amount of memory PHD allocates for each value in processing requests. MAX_ARCRECSIZE which defaults to Uniformance - PHD Specification Sheet

15 3 Important Considerations in PHD System Sizing 3.2 PHD Server This controls the record size within the archive files and must be changed if larger data sizes are required. Maximum string tag size 32,500 characters See above. Number of connected archives 8192 (memory permitting) While PHD permits up to 1024 open archive files, the actual number of open archives is constrained by the available system memory. Maximum archive size 32GB In general, larger archive sizes are recommended for optimal data retrieval response times. Concurrently connected users 10,000 The number of concurrent requests is limited by the system resources and by the number of available pool threads which, by default, is 256 Default limit imposed by APIServer is 100. Uniformance - PHD Specification Sheet 15

16 3 Important Considerations in PHD System Sizing 3.2 PHD Server PHD Server and RDI cross reference table Calculate the number of RDIs times the number of servers running those RDIs. For example, if an RDI is running on dual RDC collectors and two shadow servers, it should be counted four times. If the machine in question is one of the hosts, then subtract one (1). Default maximum is 256, but can be increased using the Registry setting RdiHostTableSize. 16 Uniformance - PHD Specification Sheet

17 3 Important Considerations in PHD System Sizing 3.3 Calculations and Virtual Tags 3.3 Calculations and Virtual Tags Number of functions 128,000 Includes 1D, 2D, and 3D lookup tables Default limit is 100 and is controlled by the PHD parameter MAX_PRCFUNC. Number of modules 128,000 Default limit is 1,000 and is controlled by the PHD parameter MAX_PRCMODULE. Levels of nested virtual tags Number of function arguments 32 for calculations Nested GetData requests are limited to Calculation registers 64 - Number of characters in a virtual tag definition Length of a calculation string 30, Number of input tags Uniformance - PHD Specification Sheet 17

18 3 Important Considerations in PHD System Sizing 3.4 Roles 3.4 Roles Number of PHD roles Maximum roles per user Always uses INTS in Data Collection and RDI Server Number of RDI Servers per physical server 25 - Number of RDIs per RDI Server 25 for Shadow Servers with Active and Standby nodes configured 100 While the default is approximately 25, this number can be fine tuned using system registry settings (with the consultation of Honeywell Services) Fastest collection rate Slowest collection rate 1 second The number of tags that can be collected at this rate is typically constrained by the capacity of the data provider. 1 day - 18 Uniformance - PHD Specification Sheet

19 3 Important Considerations in PHD System Sizing 3.6 Standard RDIs Available Maximum tags per RDI 400,000 Typically 25,000-50,000 While an RDI may be assigned 400,000 tags, it is typically advisable to have more RDIs with a lower tag count and collection offsets to balance load against the data provider. 3.6 Standard RDIs Available Honeywell Model Number Name Comments Type A Interfaces - - TP-RDIN52 Experion Link Used with Experion R310 and later TP-RDIN01 Remote LxS RDI Runs on an APP node, and collects data from a TPS system (LCN) TP-RDIN06 Experion/PlantScape RDI Used with PlantScape and Experion releases. Beginning with PHD 210 and Experion 300, Experion Link is the preferred interface. TP-RDIN12 OPC RDI - TP-RDIN14 OPC RDI for Honeywell systems - TP-RDIN30 File Access/FTP - Uniformance - PHD Specification Sheet 19

20 3 Important Considerations in PHD System Sizing 3.7 Remote Peer Interface Honeywell Model Number TP-RDIN31 Name File Access/FTP for Honeywell systems Comments - Internal RDIs - These interfaces are included in the PHD server license. Gateway RDI - Shadow RDI - Manual Input RDI - Virtual Tag RDI - Test RDI Sine wave simulation interface ATTENTION All RDIs are licensed per area, which is roughly equivalent to a PHD collector and shadow system. Numerous additional RDIs have been developed on a project basis. Contact Honeywell if an interface is required for a system that is not listed here. 3.7 Remote Peer Interface Number of remote peers on a PHD server 20 if run as a specific user 100 if run under the local System account PHD OPC Server 20 Uniformance - PHD Specification Sheet

21 3 Important Considerations in PHD System Sizing 3.8 PHD OPC Server OPC DA versions supported OPC HDA versions supported Number of PHD OPC Servers installed on a Windows server Number of PHD OPC Servers connected to a PHD server Number of OPC clients connected to a single PHD OPC server 1.0a, 2.05, and , and This also depends on if the OPC server is collocated with PHD server or on a standalone box. RDM is assumed not to be installed for this number. Uniformance - PHD Specification Sheet 21

22 3 Important Considerations in PHD System Sizing 3.8 PHD OPC Server Maximum OPC Groups supported Maximum tags per OPC group 80 Based on 'maximum tags per group' (5,000 items per OPC group) and maximum tags (400,000), then 400,000 / 5,000 = 80. 5,000 - HDA server aggregates implemented OPCHDA_INTERPOLATIVE OPCHDA_TOTAL OPCHDA_AVERAGE OPCHDA_TIMEAVERAGE OPCHDA_COUNT OPCHDA_STDEV OPCHDA_MINIMUMACTUALTIME OPCHDA_MINIMUM OPCHDA_MAXIMUMACTUALTIM E OPCHDA_MAXIMUM OPCHDA_START OPCHDA_END OPCHDA_DELTA - 22 Uniformance - PHD Specification Sheet

23 3 Important Considerations in PHD System Sizing 3.8 PHD OPC Server HDA server aggregates implemented OPCHDA_REGSLOPE OPCHDA_REGCONST OPCHDA_REGDEV OPCHDA_VARIANCE OPCHDA_RANGE OPCHDA_DURATIONGOOD OPCHDA_DURATIONBAD OPCHDA_PERCENTGOOD OPCHDA_PERCENTBAD OPCHDA_WORSTQUALITY PHD_INTERPOLATIVE PHD_AVERAGE PHD_TIMEAVERAGE PHD_DELTA PHD_MINIMUMACTUALTIME PHD_MINIMUM PHD_MAXIMUMACTUALTIME PHD_MAXIMUM PHD_STDEV PHD_REGSLOPE PHD_REGCONST PHD_REGDEV PHD_FIRST - Uniformance - PHD Specification Sheet 23

24 3 Important Considerations in PHD System Sizing 3.8 PHD OPC Server PHD_MINIMUMACTUALTIME_CO NF - PHD_MINIMUM_CONF PHD_MAXIMUMACTUALTIME_C ONF PHD_ MAXIMUM_CONF PHD_STDEV_CONF PHD_REGSLOPE_CONF PHD_REGCONST_CONF PHD_REGDEV_CONF PHD_FIRST_CONF PHD_LAST_CONF PHD_LAST PHD_INTERPOLATIVE_CONF PHD_AVERAGE_CONF PHD_TIME_AVERAGE_CONF PHD_DELTA_CONF 24 Uniformance - PHD Specification Sheet

25 3 Important Considerations in PHD System Sizing 3.9 PHD Applications 3.9 PHD Applications Consolidated Event Journal (CEJ) Maximum data retention Maximum records inserted per second 5 years Data can be retained as many years as required depending on memory available space on the hard disk drive. 16 Also refer to LCN for appropriate limitations EJC RDI for Consolidated Event Journal (CEJ) Number of TPS systems connected to a single database 25 - EPKS RDI for Consolidated Event Journal (CEJ) Number of EPKS collectors configured 9 - OPCAE RDI 1.10 for Consolidated Event Journal (CEJ) Number of OPCAE collectors configured 9 - PHD to Relational Number of tasks scheduled 16 - Uniformance - PHD Specification Sheet 25

26 3 Important Considerations in PHD System Sizing 3.9 PHD Applications Number of tags per task 16 - Peer Tag Sync Number of tags 230,000 - Experion Tag Sync Number of tags 50,000 - Number of Experion Servers Uniformance - PHD Specification Sheet

27 This page is intentionally left blank Uniformance - PHD Specification Sheet 27

28 Honeywell International Process Solutions 1860 W Rose Garden Ln Phoenix, AZ This page is intentionally left blank