Operations Management Pro
OM Pro 310
Specification and Technical Data
Copyright, Notices, and Trademarks
© Honeywell International Inc. 1998 – 2008. 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 customer.
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, Uniformance, Business FLEX, Process Knowledge Solution and PKS are registered trademarks of Honeywell International Inc.
Microsoft, Microsoft Access, Visual Basic, Visual C++, Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
All other brand and product names shown are trademarks of their respective owners.
About Advanced Applications
Business FLEX® and Advanced Alarm Management products provides Process Knowledge Solutions® that improve the planning process, systematically measure, monitor, and assess plant performance, and help process plants collect and analyze data. To learn more about Operations Management Pro and other Honeywell software solutions, contact your Honeywell account manager.
Visit www.honeywell.com/ps, or call: U.S. and Canada (877) 466-3993 or +1 602 313-6665 ● Latin America +58-2-235-6301 ● Europe/Middle East/Africa +44-1344-656-898 ● Asia Pacific +65-6355-2828 or +612-9353-7000. Honeywell Process Solutions, 2500 West Union Hills Drive, Phoenix, AZ 85027, USA
Release Information
OM Pro release 310Release date: March 2008
Introduction
Operations Management Pro, or OM Pro, provides comprehensive limit management for process plants. Features include the ability to manage a master set of limits; to apply those limits to alarm enforcement; to set economic and other targets that lie within the master limits; to monitor violations of limits; to report on alarm metrics; and to summarize shift handover information. Operations Management Pro release 310, or OM Pro 310, was released in March 2008. The OM Pro suite includes products from the Business FLEX® and Advanced Alarm Management product lines. There is a set of six core products that work together, plus some additional products that are included in the suite but not required for OM Pro functionality.Product Line Core Products Additional Products
Components
The OM Pro products are composed of many components that run on client computers or server computers. Some of these components are shared, and some are optional. This section summarizes the components found in OM Pro by the type of system. As a general note, Honeywell does not support installing any OM Pro components on an Experion Process Server. Client Components Client components are divided into components that are primarily used by end users, and components that are primarily used by people responsible for system administration and configuration. A few components fall into both categories. In general, users need access to whatever client components are necessary to perform their job; users do not necessarily need access to all client components. Table 3. Client components for general useComponent Product Description
Web client AEA, ACM, OI, OL, OM Used by desktop users.
Main user interface for AEA, Operating Instructions, Operations Logbook, Operations Monitoring, and parts of ACM.
UserAlert Explorer UserAlert Used by desktop users. Configure alert sources. Experion Alert Summary
Display
UserAlert Used by desktop users and console operators. View and acknowledge alerts.
Alarm Enforcer client ACM Used by console operators.
Display and direct alarm enforcements and other alarm management operations. This is the main user interface for operators to interact with ACM. Can run on Experion Console Station, Experion Flex Station, GUS, Yokogawa Human Interface Stations, and Emerson DeltaV Operator Station, provided the operating system is supported by ACM.
Alarm Help Client ACM Used by console operators.
Component Product Description AEA Report Building Workstation AEA Used by power users, typically just 1 or 2 people at a site. Create and modify reports, and publish them to the web server for general access. System administrators and people responsible for configuring the applications will often use the enter user components as well as the more specialized components used for configuration and administration tasks. Table 4. Client components for configuration and administration
Component Product Description
Web client AEA, ACM, OI, OL, OM Main user interface for AEA, Operating Instructions, Operations Logbook, Operations Monitoring, and parts of ACM. Also used for some administration and configuration tasks, especially configuring user accounts and roles for web access, and Operations Logbook shift summary reports.
ACM Administrator Client ACM Configure ACM for a particular site.
ACM Manager Client ACM Configure alarm system data and boundaries
and constraints.
TPI OI, OL, OM Configure use of the equipment model after it is
defined in the Enterprise Model Builder, configure monitoring targets and instruction templates.
GETIT OI, OL, OM Import tag configuration from PI and other third
Table 5. Central server components
Component Product Description
Component Product Description
Crystal Reports Server OI, OL, OM Report server for OI, OL, and OM reports, which are all written in Crystal Reports. The Crystal Reports Server is licensed software from Business Objects. Business Objects owns Crystal Reports. Experion Application Server (EAS) ACM, UserAlert Server components for applications that run in the control domain. Handles pager and email notifications, logs events, exposes boundaries as OPC items, and typically acts as the OPC server when used with Experion control systems. EDS and EAS together are called the Experion Application Framework, or EAF. Experion Desktop Server (EDS) AEA, ACM, OI, OL, OM Web server for the web‐enabled parts of AEA, ACM, OI, OL, OM, and some other Honeywell products. EDS is installed on Windows Server with IIS enabled. NOTE: This server must have SMTP server access for AEA’s email notification to work. EDS and EAS together are called the Experion Application Framework, or EAF. Experion Relational Point Data Client ACM Exposes boundary data stored by ACM in the Oracle database through OPC. This component is installed on top of EAS.
AEA Application Server AEA Collects alarm and event data, and stores processed data in the database server. ACM Manager Server ACM Manages all the interactions with the Master
Boundary Database from the other ACM components, and reads the Enterprise Model from the Experion Server. ACM Enforcer Server Proxy ACM Stands in for the ACM Enforcer Server if the Manager Server and Enforcer Server are on opposite sides of a firewall. See page 27. UserAlert Server UserAlert Connect to one or more OPC servers and
Typically one copy of the distributed server components will be installed for each control system connected to OM Pro. It is not listed here, but PHD buffers are another example of distributed server components.
Table 6. Distributed server components
Component Product Description
AEA Data Collector AEA Gathers event data from a control system, such as a TPS HM, and transfer to the AEA
Application Server.
The ACM client components can run on Experion Console Station, Experion Flex Station, GUS, Yokogawa Human Interface Stations, and Emerson DeltaV Operator Station. The ACM clients are compatible with SafeView. The ACM Enforcer server can run on Experion Application Server (EAS), TPS APP Node, and Emersion DeltaV App Station, but is not validated to run Experion Process Server or Experion for TPS Server (ESVT). AEA provides native support for some control systems, and generic support for others. Many of the interfaces are files using a defined file format. Other control systems can be supported if events can be written to this file format. Table 9 summarizes the control systems supported by ACM and AEA. Table 9. Control systems supported by ACM and AEA ACM AEA
Control system Type Interface Read/Write Type
Honeywell Experion PKS 30x and 31x including CEE, SCADA, EHG, TPS, and BMA tags
Native OPC DA Read/Write Native6
Honeywell Experion PKS 21x including CEE, SCADA & EHG tags
Native OPC DA Read/Write Native7
Honeywell TPS R533 through R6708 Native OPC DA Read/Write Native9, HM or EJC Honeywell TDC3000 R400 through
R532
Generic File Read only File, generic
Honeywell PMX Native OPC DA Read/Write ‐‐
Emerson DeltaV (7.3) Native OPC DA Read only ‐‐
Foxboro I/A 6.5 Generic OPC DA10 Read only File, specific
to Foxboro
IBM Advanced Control System (ACS) Native OPC DA Read/Write ‐‐
Siemens PCS 7 (5.1) Generic OPC DA Read only File, specific
to Siemens Yokogawa Centum CS3000, 2.10 and
above
Native OPC DA Read/Write
ACM AEA Control system Type Interface Read/Write Type
Yokogawa Centum CS, 2.09 and above Native OPC DA Read/Write except for
alarm priorities
File, specific to Yokogawa
Yokogawa CS 1000 Generic OPC DA Read only File, specific
to Yokogawa
Yokogawa Centum XL (24) Generic OPC DA Read only File, specific
to Yokogawa
Yokogawa Centum µXL Generic File Read only File, specific
to Yokogawa
Yokogawa COPS V (22.5) Generic File Read only File, specific
to Yokogawa
Generic ‐ unknown Generic File Read only File, generic
format
Ronan EHAS N/A N/A Documentati
The OM Pro core products are internationalized, which includes support for local conventions such as dates, running client software components on international versions of Windows, the ability to store Unicode characters in the database, and the ability to translate the user interface. Note that OM Pro client components are supported on international versions of Windows, but server components are supported only on English versions of Windows, Oracle, and SQL Server. Some additional products— Event Analyst, Event Monitoring, Lab Data Integrator, and LIMS—are not internationalized, or have limitations. Internationalized products have been tested and are supported with French, German, and Spanish character sets and the client versions of Windows for those same languages. The Business FLEX products (Operating Instructions, Operations Logbook, and Operations Monitoring) also support Chinese. Client software components can be translated to languages other than English using the translation toolkit, which is included with the OM Pro media. Translations are not provided with the OM Pro media. Specifications and Sizing Table 10. General system specifications
Item Specification Comments
Users No limit No limit to number of named users.
Number of simultaneous or concurrent users for most components is limited by server capacity.
Number of simultaneous or concurrent users for reporting may be limited by the Business Objects licenses.
User account names 20 characters Maximum 20 characters combined length of a Windows user account name plus domain name. Maximum 20 characters length for Oracle account names. Asset models 1 Maximum one asset hierarchy for the entire system. ACM 310 supports multiple asset hierarchies, allowing one asset hierarchy per control system, but OM Pro 310 is limited to a single asset hierarchy. Assets 4,000 Maximum 4,000 nodes in one asset hierarchy. The web applications will display up to 500 nodes at one time. Assignable assets 1,000 Alerts in UserAlert can only be members of assignable assets. They cannot be members of un‐assignable assets. The number of assignable assets is a subset of the total number of assets. In Experion, assignable assets provide a way to assign assets to an operator’s scope of responsibility. Asset names 40 characters Asset names can be up to 40 characters long and must be
Item Specification Comments
Asset model depth 10 levels The fully qualified name includes the asset’s name and all parents, and is limited to a maximum of 255 characters. Variables 65,000 Maximum 65,000 variables in Boundary Manager. Note that this is a testing limit, and the total number of tags in the process historian can be much larger than this number. Historians 1 One per OM Pro system, either PHD or PI with OPC HDA. Notes and comments – number and retention No limit No limit on the number of notes or retention period, except as limited by physical storage space available to the Oracle server. Notes and comments – each note 4,000 bytes per note Maximum 4,000 bytes per note, including white space and optional rich text formatting. This limit corresponds to 4000 characters for single byte languages such as English when no formatting is used, less when Unicode or formatting are used. Exception: notes entered in ACM have a limit of 2000 characters regardless of language.
Shift rotation Configurable Shifts up to 12 hours long. No limit on the number of teams or the length of the rotation cycle. Multiple shift rotations can be configured per site, with different shift lengths. AEA requires that shift length must split evenly into 24 hours, for instance 2 x 12 hours, 3 x 8 hours, etc. Table 11. AEA specifications
Item Specification Comments
Events and alarm metric storage
Not specified Limited by server capacity. Control systems No limit Limited by server capacity. Data sources per
control limit
No limit For example, for one Experion control system there could be multiple Experion servers. AEA connects individually to each Experion server.
Reports 38 standard No limit on additional custom reports
Table 12. ACM specifications
Item Specification Comments
Control systems No limit Limited by server capacity.
Maximum of one generic control system.
Historians 1 One per ACM system.
Item Specification Comments Alarm settings Trip point, priority and alarm enable state Enforcement schedules By shift or time Per console Alarm enforcement actions Must enforce Report only Ignore Conditional Individually available for alarm Trip point, priority and alarm enable state. Mode‐based alarm settings Yes Modes are configurable on assets. Note that alarm modes configured in ACM are not the same as planning modes configured in Operating Instructions. Modes per asset 20 Testing limit Table 13. Operating Instructions specifications
Item Specification Comments
Active instructions 1 per asset (equipment)
Maximum one (1) instruction active at the same time per node in the asset hierarchy, hence limited by the number of assets. Historical instructions No limit No limit, except as limited by physical storage space available
Table 14. Operations Logbook specifications
Item Specification Comments
Shift summary reports 1 per user per asset per shift Maximum one shift summary report per authorized user per node in the asset hierarchy per shift. Shift summary reports – history retention No limit No limit on historical retention of shift summary reports other than available disk space. Shift summary reports – each report Configurable No limit on number of comment or table snippets per report, except as limited by time required to render table snippets. Maximum one Excel or one Word snippet per shift summary report. Table 15. Operations Monitoring specifications
Item Specification Comments
Configured targets (conditions) 10,000 Limited by server capacity, especially the capacity of the process historian. Note: Monitoring 5,000 or more targets is considered a big system that may require advice on performance tuning. Monitoring resolution 1 minute Deviations (limit violations) can be detected as often as every 1 minute, with start and end times recorded to the nearest minute. Deviation duration 1 minute – 12 hours Minimum 1 minute, maximum 12 hours or shift length. Assignable reasons per deviation 100 Maximum 100 reasons per deviation. Reasons – configuration limit No limit No limit on the number of reasons that can be configured; limited in practice to ~500 reasons to provide acceptable performance in the user interface. Table 16. UserAlert specifications
Item Specification Comments
Item Specification Comments Data source type OPC DA server(s) One or more required to provide data. Must be compliant with OPC DA 1.0a or 2.0. Tested with Experion R301, APP R240, PHD R210, and OSIsoft OPC Server for PI 3.3 and 3.4.
Releases, Packaging, and Licensing
Releases OM Pro release 310, or OM Pro 310, was released in March 2008. OM Pro 310 combines the Advanced Alarm Management (AAM) release 310 with the Operations Management products from Business FLEX release 220, and Event Analyst release 130.4. Maintenance patches may be available from time to time. Licensing OM Pro is licensed for a site based on the total number of people who use the system. There are four size classes: Size A for up to 18 named users, size B for up to 120 named users, size C for up to 330 named users, and size D for an unlimited number of users at one location. Packaging The OM Pro suite includes licenses for the Honeywell software products listed in Table 18. The products listed as “core” products are the ones that make use of the OM Pro integration, and which are commonly used together. As shown in the table, some products in the OM Pro suite are optional, and do not have any special integration with the core products. These optional products are licensed with OM Pro, but there is no requirement to install or use them. All OM Pro products can be licensed together as part of the OM Pro suite, or individually. Table 18. Honeywell product licenses included in OM Pro 310Product Release Core Optional
Oracle
Please note that this section describes Honeywell’s interpretation of licensing policies by Oracle Corporation. Please refer to Oracle Corporation for definitive answers.
OM Pro requires Oracle Database Server, but does not include licenses for it. Oracle can be licensed from Honeywell or acquired through other channels.
Oracle Corporation (www.oracle.com) offers three editions of the Oracle Database that are supported by OM Pro: Enterprise Edition, Standard Edition, and Standard Edition One, with different prices and scalability. Oracle Corporation offers two standard ways to buy licenses: per processor licensing, based on the number of CPUs in the server computer, and per user licensing. Honeywell’s interpretation of Oracle’s licensing policies is that all OM Pro users are required to have an Oracle license, or else the site must choose per processor licensing. Microsoft SQL Server Please note that this section describes Honeywell’s interpretation of licensing policies by Microsoft Corporation. Please refer to Microsoft for definitive answers. OM Pro requires Microsoft SQL Server 2005, but does not include licenses for it. SQL Server can be licensed from Honeywell or acquired through other channels.