OM Pro 310 - Honeywell · report on alarm metrics; and to summarize shift handover information....

Specification and Technical Data

Operations Management Pro

OM Pro 310 Specification and Technical Data

OMPro-SPT-310

August 2008

OM Pro 310 Specification and Technical Data 2

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 310 Release date: March 2008 Document number: OMPro-SPT-310

http://www.honeywell.com/


Contents Introduction .................................................................................................................................................. 5

Concepts and Capabilities ............................................................................................................................. 6 Levels in Computer Integrated Manufacturing ......................................................................................... 6 Assets and Equipment ............................................................................................................................... 6 Variables .................................................................................................................................................... 7 Boundary Management ............................................................................................................................ 7 Instructions ............................................................................................................................................... 9 Process Monitoring ................................................................................................................................... 9 Shift Summary and Shift Handover ........................................................................................................... 9 Tasks ........................................................................................................................................................ 10 Alarm Management ................................................................................................................................ 11 Alarm Metrics and Analysis ..................................................................................................................... 11 Reports .................................................................................................................................................... 13

Products ...................................................................................................................................................... 14 Alarm & Event Analysis ........................................................................................................................... 14 Alarm Configuration Manager ................................................................................................................ 15 Event Analyst ........................................................................................................................................... 16 Operating Instructions ............................................................................................................................ 16 Operations Logbook ................................................................................................................................ 17 Operations Monitoring ........................................................................................................................... 18 UserAlert ................................................................................................................................................. 19

Components ................................................................................................................................................ 21 Client Components .................................................................................................................................. 21 Server Components ................................................................................................................................. 22 Experion .................................................................................................................................................. 25

Architecture ................................................................................................................................................ 27 Reference Architecture: Two Servers at Level 4 ..................................................................................... 27 Reference Architecture: DMZ ................................................................................................................. 29 Integration .............................................................................................................................................. 31

Specifications .............................................................................................................................................. 33 Platforms – Client Components .............................................................................................................. 33 Platforms – Server Components ............................................................................................................. 33 Control Systems ...................................................................................................................................... 34 Historians ................................................................................................................................................ 36 Security ................................................................................................................................................... 37 Internationalization ................................................................................................................................. 37 Specifications and Sizing ......................................................................................................................... 38 Migrating from Earlier OM Pro Releases ................................................................................................ 42

Releases, Packaging, and Licensing ............................................................................................................. 44 Releases .................................................................................................................................................. 44 Licensing .................................................................................................................................................. 44 Packaging ................................................................................................................................................ 44 Prerequisites ........................................................................................................................................... 45 Experion .................................................................................................................................................. 45


Business Objects ..................................................................................................................................... 45 Oracle ...................................................................................................................................................... 46 Microsoft SQL Server .............................................................................................................................. 46

Documentation ........................................................................................................................................... 47

Figures

Figure 1. Boundary configuration examples ................................................................................................. 8 Figure 2. Typical shift summary report showing three comment snippets and one table ......................... 10 Figure 3. Typical interactive multi‐dimensional report for alarm metrics .................................................. 12 Figure 4. AEA reports life cycle with user roles .......................................................................................... 15 Figure 5. Typical Event Analyst display ....................................................................................................... 16 Figure 6. Typical operating instruction showing notes and numerical targets........................................... 17 Figure 7. The task capability allows scheduled and ad hoc tasks ............................................................... 18 Figure 8. Operations Monitoring detects limit violations and summaries the violations and impact ....... 19 Figure 9. Experion Alert Summary Display, used to display alerts raised by UserAlert .............................. 20 Figure 10. Reference architecture for two servers at level 4 ..................................................................... 27 Figure 11. ACM communicating through a firewall .................................................................................... 29 Figure 12. Reference architecture for using a DMZ .................................................................................... 30

Tables

Table 1. Levels for Computer Integrated Manufacturing ............................................................................. 6 Table 2. Performance indicator data available in alarm metric reports ..................................................... 11 Table 3. Client components for general use ............................................................................................... 21 Table 4. Client components for configuration and administration ............................................................ 22 Table 5. Central server components ........................................................................................................... 23 Table 6. Distributed server components .................................................................................................... 25 Table 7. Location of server components with two server architecture ...................................................... 28 Table 8. DMZ server configuration ............................................................................................................. 30 Table 9. Control systems supported by ACM and AEA ............................................................................... 35 Table 10. General system specifications ..................................................................................................... 38 Table 11. AEA specifications ....................................................................................................................... 39 Table 12. ACM specifications ...................................................................................................................... 39 Table 13. Operating Instructions specifications .......................................................................................... 40 Table 14. Operations Logbook specifications ............................................................................................. 41 Table 15. Operations Monitoring specifications ......................................................................................... 41 Table 16. UserAlert specifications .............................................................................................................. 41 Table 17. Migration scenarios for upgrading to OM Pro 310 ..................................................................... 42 Table 18. Honeywell product licenses included in OM Pro 310 ................................................................. 44 Table 19. Business Objects product licenses included with OM Pro .......................................................... 45


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

Advanced Alarm Management

Alarm & Event Analysis

Alarm Configuration Manager

UserAlert

Event Analyst

Business FLEX Operating Instructions

Operations Logbook

Operations Monitoring

Event Monitoring

Lab Data Integrator

LIMS

OM Pro can be licensed as a suite, and the individual products within OM Pro can be licensed and installed individually. This document describes the specifications for the OM Pro 310 suite as a whole. Certain components may offer additional capabilities or support different platforms when used individually.

OM Pro supports Experion™ PKS and other control systems. OM Pro makes use of several Experion R310 components and includes a license for their use. These Experion components can be shared with an Experion control system, if OM Pro is used with Experion.


Concepts and Capabilities

This section summarizes important concepts and the main capabilities of OM Pro. Refer to the documentation for individual products for more information.

Levels in Computer Integrated Manufacturing

Five levels are defined for Computer Integrated Manufacturing. 1

Table 1. Levels for Computer Integrated Manufacturing

Level Description

1 The final elements in a distributed control system (DCS) that connect to the actuators and sensors.

2 Distributed control system functions, including operator consoles, regulatory, logic sequential, and basic controls.

3 Control functions that provide unit‐to‐plant level control and optimization, including multivariable control and optimization, remote operators, and model‐based event detection.

4 Plant‐wide functions, including planning and scheduling, production management, non‐critical monitoring, asset management, quality management, analytics, process improvement, and other functions that do not require close connections with the process.

5 Corporate‐wide functions such as supply chain management, business analytics, and enterprise resource management.

“Control domain” refers to level 3 or the combination of levels 2 and 3. “Business domain” refers to the combination of levels 4 and 5.

Assets and Equipment

OM Pro uses an asset (equipment) model to organize information.2 Asset names are up to 40 characters long and must be unique. Assets are organized in a hierarchy that can contain up to 4,000 nodes and be up to 10 levels deep.

ACM and AEA use the asset model in the Experion Enterprise Model. Operating Instructions, Operations Logbook, and Operations Monitoring (OI/OL/OM) can optionally use the Experion asset model, or those three applications can be configured to use a different equipment model. Using the same asset model throughout OM Pro minimizes configuration and ensures that asset names are the same everywhere. In some cases it is useful to configure independent different models, for example, when the operating teams are organized differently than the control systems.

1 Theodore Williams, “A Reference Model for Computer Integrated Manufacturing,” Chapter 3 (ISA, 1989). 2 For the purposes of OM Pro, “assets” and “equipment” are synonymous.


The Experion asset model has both tag names and item names. Asset tag names must be unique, while item names do not need to be unique, as they are qualified by their position in the hierarchy.

The Enterprise Model is usually shared with Experion, if Experion is used, but use of the Enterprise Model does not require an Experion control system. OM Pro supports a single Enterprise Model for the entire system. ACM supports multiple Enterprise Models, for example, if there are multiple Experion control systems, but other products in OM Pro support only a single Enterprise Model. The Experion asset model is normally configured in the Enterprise Model Builder, and then published to the various OM Pro components.

Operating Instructions, Operations Logbook, and Operations Monitoring make use of equipment (assets) and an equipment hierarchy (asset model) defined in the Plant Reference Model, or PRM. When using the Experion asset model throughout OM Pro, the Enterprise Model Builder is used, and the Experion asset model is published to the PRM for use by those three applications. It is also possible to configure equipment (assets) in the PRM configuration tools and export the definitions to the Enterprise Model Builder.

If a site chooses to use the Experion asset model only for ACM and AEA, then the Enterprise Model Builder will still be used for those two applications, the PRM configuration tools will be used to configure the equipment model used by OI, OL, and OM, and the synchronization tools will be turned off. The two models will be maintained independently, and need not be the same.

Variables

A variable refers to the collection of information about a single measurement location in a process plant. A variable entity may include information about the name in the control system, the tag name in the historian, alarm settings, equipment constraints, operating boundaries, links to drawings, consequences of violating limits, procedures to take when limits are violated, and so on. OM Pro reads some variable information from process historians such as PHD, and other information from control systems. OM Pro manages variable information, and allows authorized users to enter and update variable information used throughout OM Pro.

Boundary Management

Constraints are named limits that apply to equipment, such as design, safety, corrosion, and environmental limits. The same constraint can apply to multiple variables, and multiple constraints can apply to the same variable. Constraints are named and are configured with the monitored property name, value (limit), engineering units, the reason for the constraint, the user and role responsible for the constraint, and a link to a document with additional information. Constraints are independent of one another and do not have any inherent meaning or level of importance.


Figure 1. Boundary configuration examples

Boundaries, or operating boundaries, are named limits that have the same meaning or importance throughout the plant. Boundaries are named, may have an alarm type and priority, have a reason for the boundary, a potential impact, information about the consequences of violating the boundary, actions to take when a violation occurs, and other information. Boundaries have a level that specifies how they related to one another. The system does not allow setting limit values for lower priority boundaries outside higher priority boundaries. In the following example, the Target_Hi and Target_Lo boundaries are required to be at or within the Standard_Hi and Standard_Lo boundaries.

Boundaries are used throughout OM Pro and provide two important benefits. One benefit is to apply consistent terminology across different process control and business systems. A second benefit is to enforce limit rules, so that inner, less important boundaries must fall within outer boundaries. ACM supports mapping boundaries to a specific DCS alarm priority (e.g., HIGH) and alarm type (e.g., PVHI). UserAlert and Operations Monitoring can monitor boundary values directly. Operating Instructions uses boundaries to limit planning targets—the default condition is that planning targets for a variable must lie on or within the most limiting boundary. Constraints are useful to manage limits that are best associated with equipment, but are only used when configuring boundaries and variables. Using constraints is optional.

Each plant must define a philosophy for organizing limits. A typical approach is to define three levels of boundaries. The top level boundary is used for critical conditions where it is important that the process not cross those limits, and where an alarm should elicit an immediate response. Limits at this top level usually have safety, health, or environmental consequences. A second boundary level is used for limits related to reliability, where corrective action is expected if a limit is crossed, but the consequences are not as severe as the top level. A third boundary level is used for targets that have an economic impact if violated, such as optimization targets. With this type of organization, alarms might be used for the top two levels but not the third level.


Instructions

Instructions are intended for planners and supervisors to communicate the daily and weekly operating plan to operators and others. Typically instructions are created every week or for mode changes for major process units. An instruction consists of numerical targets and notes, and applies to an asset in the asset hierarchy. Instructions are created, approved (usually by a supervisor), and then activated. Instructions are said to be complete when they are replaced with newer instructions.

An instruction can contain hundreds of numerical targets for variables. These targets can include minimum, maximum, and focus values, and can be calculated from other targets in the same instruction. These numerical targets are validated against the boundary limits stored in the Boundary Manager, so that planners are not allowed to set instruction targets that are outside of the preferred operating ranges. Target values are downloaded to the historian when an instruction is activated.

Instructions can be grouped together in a production order, for example to define a campaign to make a particular product or grade, or all the instructions that should be activated at the same time. Production orders can be imported from ERP and other systems with the aid of other Honeywell products that are not part of OM Pro. An instruction can contain a formulation, which is a list of the materials consumed and produced by an instruction. The formulation can be used to calculate the total quantities of feeds and products over the life of an instruction.

Process Monitoring

Process variables can be monitored in two ways. Operations Monitoring monitors variables and limits configured for the site, records a complete history of all violations in a database, and allows authorized users to optionally enter reasons and annotations about violations. Operations Monitoring is normally used within OM Pro to monitor most boundaries configured in the Boundary Manager, and planning targets defined in Operating Instructions.

UserAlert provides more personal monitoring, along with notifications when violations require more immediate attention. A site can configure public alert sources and end users can configure their own alert sources. Typically UserAlert detects conditions faster than Operations Monitoring and can issue email and pager notifications, but does not provide for extended retention of historical violations, nor the option to enter reasons and annotations.

Shift Summary and Shift Handover

A shift summary report is a collection of information that is put together specifically to show what happened during a shift, and is typically used for shift handover. A shift summary is linked to a particular shift and a particular unit or process area. Shift summaries can be created at different levels in the equipment hierarchy, for example, to allow operators to prepare reports for their units, and supervisors to prepare high level reports for the same shift.


There is a work flow, where shift summaries are created, then submitted, then approved. Once submitted, the content is locked except for the ability to add additional notes. Once approved, the content of a shift summary is completely locked. Shift summaries are stored as PDF files.

Figure 2. Typical shift summary report showing three comment snippets and one table

Tasks

An operating department can set up scheduled and ad hoc tasks to track its own activities. A task is something to be done that has a name, a description of what is to be done, a planned or scheduled due date, a priority, a type, and other information such as a link (a URL) to related information. Users can view tasks assigned to them, and can mark tasks as complete. Authorized users can edit tasks, assign tasks to other people, change the due date, and generally manage tasks for themselves and others.

Users can create ad hoc tasks whenever needed. Recurring tasks can be scheduled with a task scheduler, for example, to collect lab samples every week.


All tasks have a status, such as pending, deferred, overdue, and complete. The system detects when tasks are overdue. Users can update the status.

Tasks can have subtasks, and each subtask can have its own description and status. For instance, collecting lab samples could be a scheduled task, and the individual samples to be collected could be subtasks. When all samples have been collected, then the task as a whole is complete.

Alarm Management

Alarm system documentation is provided in ACM. The system stores information such as the alarm category, the desired trip points, priorities, alarm enable status, links to drawings, consequences of violating an alarm, and the time to respond by an operator before the condition becomes more serious.

Alarm settings are documented and limits entered in ACM. Alarm limits can be enforced, meaning that they are reset to values stored in ACM. Enforcements can be scheduled, for example, every shift at a specified time, executed on demand, for example, when requested by an operator, or when operating modes change. Operators use the Alarm Enforcer Client to review pending and completed enforcements.

Alarm Metrics and Analysis

A performance indicator is a measurement, such as alarm count, maximum alarm rate or number of disabled alarms, used to assess plant performance. A performance target is a standard against which a PI can be evaluated, such as those found in the Engineering Equipment & Materials Users’ Association (EEMUA) guidelines. The EEMUA guidelines are a set of industry alarm performance targets. Reports can be configured to highlight performance indicators that exceed selected performance targets. Alarm metrics can be calculated based on a configured shift schedule.

Table 2. Performance indicator data available in alarm metric reports

Category Description

Alarms Alarm time, return time, duration and time to acknowledge.

Alarm rates Frequency data.

Process changes Operator changes to mode, output, setpoint and other settings.

Standing alarms Active and enabled 30 minutes before end of shift.


Category Description

Standing disabled or inhibited alarms

Active but disabled or inhibited 30 minutes before end of shift.

Stale alarms Not returned to normal before the start of the week after which it occurred.

Standing stale alarms

Not returned to normal for at least 12 hours, as of 30 minutes before the end of shift.

Repeating alarms Occurred 10 or more times in a particular period (hour, shift).

Repeat offenders Exceeded the alarm count threshold one or more times in a particular period (e.g., last four complete weeks).

Journaled alarms Written to the DCS journal, whether displayed to the operator or not.

Configuration DCS point configuration data.

Enforcement ACM enforcement data, such as sessions, exceptions, average exceptions and suspend overrides.

Standard reports are provided that cover the most common plant and operator load performance indicators. In addition, users can interactively create their own multi‐dimensional reports.

Figure 3. Typical interactive multi‐dimensional report for alarm metrics


Reports

OM Pro provides over 50 standard reports, including reports for Standing Alarms, Peak Alarm Rate, Alarms per Hour, Alarm Count, Repeating Alarms, Monitoring Top 10, Monitoring Limit Violations, Instruction Details, and others.

Most reports are developed using Crystal Reports, and can be extended or revised by site staff. Reports can be generated automatically on a time or shift schedule. AEA can notify users by email when alarm metric reports are generated and for some reports can attach the report to the email.


Products

OM Pro includes six core products: Alarm & Event Analysis (AEA), Alarm Configuration Manager (ACM), Operating Instructions, Operations Logbook, Operations Monitoring, and UserAlert, and also some optional products such as Event Analyst. All of these products are licensed software products that can be used individually or as part of the OM Pro suite.

OM Pro requires, but does not include some prerequisite software such as a process historian. A list of prerequisites is given on page 45.

Alarm & Event Analysis

Alarm & Event Analysis (AEA) provides alarm metrics. AEA collects and reports on alarm and event journal data, and configuration data, from Honeywell Experion, TPS History Module (HM) and Event Journal Collection (EJC) data sources. AEA can also report on Alarm Configuration Manager (ACM) enforcement data. It provides dynamic Web reports and static reports in Web, Excel and other formats.

Features:

• Alarm metric collection, calculation, and storage, including the ability to collect from multiple dasources and support for both Honeywell and non‐Honeywell control systems.

ta

• Standard reports such as maximum alarm rates, stale alarms, and repeating alarms.

• Report builder, allowing a site to create its own custom reports.

• Dynamic analysis using OLAP technology in a web browser, allowing users to manipulate the presentation of alarm and event data, to drill into report results, to save their own views, and to export the results to Microsoft Excel.

• Scheduled reports, including the ability to notify recipients by email when reports are read, and attach some reports to the email.3

• Configuration and alarm enforcement analysis, with reports that cover alarm system configuration and enforcement activity handled by ACM.

AEA makes extensive use of products from Business Objects, including Crystal Reports, OLAP Intelligence, and Business Objects Enterprise. (See page 45.)

AEA is organized to support several types of roles for reporting users, including administrators, report builders, and users. The ability to create, modify, or publish new reports is limited to the number of licenses for Crystal Reports and OLAP Intelligence. By default one license for each of these products is included with OM Pro, and more can be purchased. The ability to work interactively with the reports and OLAP cubes is limited to the number of licenses purchased for the Business Objects Enterprise server. By default, five named user licenses are included with OM Pro, and more can be purchased. There are no limits to the number of users who can view scheduled reports.

3 Email notifications are only possible if the AEA Web Server has SMTP server access.


Figure 4. AEA reports life cycle with user roles

Alarm Configuration Manager

Alarm Configuration Manager, or ACM, provides alarm management capabilities. Fundamentally, ACM stores information about desired alarm limits, regularly examines alarm limits, and optionally resets actual alarm limits to reference values.

Features:

• Alarm system documentation, with a central location for alarm settings and related documentation derived from alarm analysis and rationalization.

• Change management , with the ability to detect disabled or modified DCS alarm settings and optionally enforces the rationalized values. Alarm system change can be handled within ACM rather than directly on the DCS.

• Operator performance support, with online help that describes causes and effects of an alarm as well as the recommended response.

• Boundary Manager, for managing constraints and boundaries for the entire OM Pro suite.

• Reporting, including detailed documentation, change management, and enforcement and configuration reports.

• Offline configuration, allowing most alarm system, change management, and configuration to bedone offline.


ACM supports Experion® and other control systems. One ACM system can support several control systems of the same or different types.

Event Analyst

Event Analyst is a tool for analyzing the process history and event data recorded by Uniformance PHD with Event Journal Collection (EJC) from one or more Honeywell TPS control systems. Event Analyst combines trend displays and alarm event displays on a single display to aid the analysis of historical process data.

Features:

• Display process history from PHD and event data on the same trend. Zoom in on a region of interest.

• Save results as data files, for example, to provide a permanent record of good production runs orabnormal operations. Files can be compared with other file and shared with other users.

Figure 5. Typical Event Analyst display

Operating Instructions

Operating Instructions (OI) manages and communicates the operating plan to operators. A planner, supervisor, or engineer prepares detailed instructions for a unit, including numerical targets and notes.


Instructions must be approved and activated. Once activated, the targets are downloaded to the process historian, and Operations Monitoring and UserAlert can monitor using the new targets. Violations are detected and processed by Operations Monitoring and UserAlert much like other violations.

Features:

• Instructions for any node in the asset hierarchy. Each instruction can contain notes, numerical targets for hundreds of process variables, and a formulation that defines feeds and products.

• Group instructions in production orders, starting at the same or different times, and for the saor different assets.

me

• Numerical targets are automatically validated against boundaries configured in the Boundary Manager.

• Import/export production orders and instructions from external systems.

Figure 6. Typical operating instruction showing notes and numerical targets

Operations Logbook

Operations Logbook (OL) is an electronic log to record what happens in a shift. It allows for ad hoc entry of comments and observations, tracks daily to‐do items, and prepares the shift handover report.

Features include:

• Shift summary reports created by operators every shift for selected nodes in the asset hierarchy.


Shift summary reports are created from templates that define standard information to enter every shift, and information pulled from other applications.

• Tasks, a department‐wide to‐do list, with the ability to create scheduled and ad hoc tasks, to define completion times, responsibilities, and procedures.

• Ad hoc entry of comments and observations.

• Search comments entered in Operating Instructions and Operations Monitoring, as well as Operations Logbook.

Figure 7. The task capability allows scheduled and ad hoc tasks

Operations Monitoring

Operations Monitoring (OM) systematically monitors process data against limits, and reports deviations. Limits can be planning targets from Operating Instructions, boundaries, or other limits. Users can see target values that are out of range and can enter comments and reasons why.

Features:

• Monitor thousands of process values every few minutes, detect violations, and store results online for years.

• Enter reasons and comments about violations, enabling reporting and follow‐up on common causes.

• Configure each monitored variable individually, with detection methods, limits, and impact calculations.

• Display boundaries and other variable information.


• Automatically suspend monitoring in process areas when defined equipment are down, for example, if a process unit is shut down.

Figure 8. Operations Monitoring detects limit violations and summaries the violations and impact

UserAlert

UserAlert provides near‐real time alerting and notification for conditions when process data are outside of limits. UserAlert is intended to handle conditions where notifying operators is useful but alarms are not appropriate. UserAlert can be used to monitor any data available through an OPC server that complies with the OPC DA 1.0a or 2.0 specification.

Features:

• Monitor process data from OPC DA data sources, with the ability to connect to multiple OPC servers.

• Simple and combination alerts with a rich set of algorithms and condition types.

• Public and private alert sources, allowing sites to configure common alerts and individual users toconfigure their own alerts.

• Pager and email notifications when alerts are raised.

• Experion integration. UserAlert displays alerts in the Experion Alert Summary Display, which provides a consistent appearance for alarm and alert handling.

UserAlert supports any control system that supports OPC. The operator interface typically runs on a control room GUS for a TPS system and on an Experion Station in an Experion system.


Figure 9. Experion Alert Summary Display, used to display alerts raised by UserAlert


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 use

Component 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.

Provide programmatic access to alarm documentation.



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


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 party historians. Not used when the plant historian is PHD.

Translation Toolkit AEA, ACM, OI, OL, OM, UA

Used to translate the user interface components to languages other than English.

Experion Enterprise Model Builder

AEA, ACM, OI, OL, OM, UA

Configure assets and the asset hierarchy, and distribute the asset model to other systems for use.

Server Components

The server components are divided into two groups. One group is usually installed on one or more central servers. A second group of server components are usually installed closer to the control systems to collect data or take other actions on the control systems. A site with more than one control system will typically install multiple copies of the distributed server components. It is not listed here, but a process historian such as PHD is another central server component.


Table 5. Central server components


Oracle database ACM, OI, OL, OM The Oracle database server is licensed software from Oracle Corporation.

Primary storage location for ACM, OI, OL, and OM, including the Master Boundary Database (MBD), which stores alarm system data as well as boundaries and constraints for all of OM Pro.

One Oracle database instance, called the Business FLEX instance, is used for all OM Pro applications and also for any other Business FLEX applications installed at this site.

AEA does not store data in this database but does read the DCS hierarchy, tag configuration, and enforcement data stored by ACM.

PHD can optionally be used with OM Pro. If used, a second Oracle database instance is installed for PHD, optionally including EJC. One Oracle serve computer can manage both the OM Pro and the PHD Oracle database instances.

SQL Server database AEA, ACM, UserAlert, OI, OL, OM

The SQL Server database server is licensed software from Microsoft Corporation.

Primary storage location for AEA and UserAlert. Stores some information for the other applications, such as security data and shift summary reports.

NOTE: SQL Server can be used as the primary database manager for ACM when ACM is used by itself, but not with OM Pro.

OM Pro uses 7 SQL Server databases:

• EMDB (Experion Enterprise Model) • emsevents (installed by EAS) • OPC Integrator (installed by EAS) • Experion Core Services (installed by EDS) • Base Components (used by OI/OL/OM) • UserAlert • AlarmAnalysis (used by AEA)

Business Objects Enterprise Premium and OLAP Intelligence

AEA Report server for AEA reports and OLAP analysis. The reports are written in Crystal Reports, while the analytics made use of Business Objects’ OLAP Intelligence component.

The Business Objects Enterprise server is licensed software from Business Objects. Business Objects owns Crystal Reports.



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 obtains process data, checks process conditions in each alert source at regular interfaces, and notifies users via the Experion Alert Summary Display when conditions become active.

Business FLEX Application Server

OI, OL, OM Manages scheduled tasks such as the program used in OM to detect deviations, called Variance Monitoring, the program used in OI to schedule instructions, and other services.


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


AEA Data Collector AEA Gathers event data from a control system, such as a TPS HM, and transfer to the AEA Application Server.

ACM Enforcer Server ACM Updates and maintains alarm limits in the control systems. Typically there is one Enforcer Server for each control system, and the Enforcer Servers typically run on computers close to the control system.

Can run on Experion Application Server (EAS), TPS APP Node, and Emersion DeltaV App Station. Not validated to run Experion Process Server or ESVT.

ACM Manager Server Proxy

ACM Stands in for the ACM Manager Server if the Manager Server and Enforcer Server are on opposite sides of a firewall. See page 27.

Experion

OM Pro supports Experion and other control systems. Even when used with other control systems, OM Pro makes use of common components that are shared with the Experion system. These components are packaged with OM Pro and do not need to be ordered separately. See page 45 for a list of the Experion licenses that are included with OM Pro.

Several OM Pro components are supported on selected Experion components, such as Experion Console Station. As a general note, Honeywell does not support installing any OM Pro components on an Experion Process Server.

OM Pro 310 shares components with the Experion 310 release. Sites that use both OM Pro 310 and Experion 310 may find that these components can be shared in production use. OM Pro 310 supports other Experion releases and sites with multiple control systems at different releases, but such sites usually are not able to consolidate servers.

The Experion Application Framework (EAF) consists of two parts, the Experion Application Server (EAS), and the Experion Desktop Server (EDS), and are delivered on the same physical media. (EAS and EDS are listed in the table above as server components for OM Pro.) EAS and EDS both use Microsoft SQL Server to store configuration information. EAS and SQL Server must be installed on the same computer, and EAS databases install only the default SQL Server instance. EDS can be installed on a different computer


than SQL Server and does not require use of the default instance. EDS supports web applications and must be installed on a computer that has Microsoft’s IIS web server enabled.

The Experion Enterprise Model provides the asset or equipment model used in OM Pro, and is included with EAS. The Enterprise Model Builder is a configuration tool used to maintain the asset model, and is installed by the EAF installation program.

The Experion Relational Point Data Client provides the ability to expose data from relational databases through OPC. OM Pro uses this component to expose boundary data stored by ACM in the Oracle database through OPC. The Experion Relational Point Data Client must be installed on the same computer as EAS.


Architecture

There are a number of ways to install the various OM Pro components. Two standard approaches are described here. Other approaches are possible. As a general note, Honeywell does not support installing any OM Pro components on an Experion Process Server.

Reference Architecture: Two Servers at Level 4

The first reference architecture locates most of the server components on two physical servers in the business domain. These servers are called “OM Pro Server 1” and “OM Pro Server 2”. In this architecture the process historian is usually installed on a third server.

Control domain

Business domain

End usersOM Pro Server 2

SQL ServerAAM applications

OM Pro Server 1Oracle

BF applications

DCS ApplicationsHistory collectorAEA collector

DCS ApplicationsEnforcer serverManager proxy

Historian(PHD or PI)

Figure 10. Reference architecture for two servers at level 4

Some server functions require connections to the control system, including the ACM Enforcer Servers and AEA Data Collectors. This architecture allows a firewall between the two main servers and the control systems, as shown in the figure. This architecture is intended to have most end users interact with the system from level 4. The server components are installed on these two physical servers as shown in the table.


Table 7. Location of server components with two server architecture

Server Software

OM Pro Server 1 Windows Server 2003 with IIS, .NET 2.0, .NET 3.0, IE Web Controls, MSXML 6.0, and MDAC 2.8

Oracle 9i or 10g Server with one or two database instances:

• Business FLEX and ACM

• Uniformance Database (optional, and only if PHD is used)


Experion Desktop Server (EDS) with IIS, and with these OM Pro components

• AEA Web Server

• ACM Manager Web Service

• OI/OL/OM web components

Business Objects XI Release 2 products

• Business Objects Enterprise Premium

• OLAP Intelligence

• Crystal Reports Server

ACM Manager Server

ACM Enforcer Proxy

OM Pro Server 2 Windows Server 2003 with .NET 2.0, .NET 3.0, MSXML 6.0, and MDAC 2.8

Oracle 9i or 10g client, Oracle Data Provider for .NET, and Oracle Provider for OLE DB

Microsoft SQL Server 2005 SP2 with seven databases:

• Experion Core Services (installed by EAF)

• EMDB (Experion Enterprise Model)

• emsevents (installed by EAS)

• OPC Integrator (installed by EAS)

• Base Components (installed by OI/OL/OM)

• UserAlert

• AlarmAnalysis (used by AEA)

Microsoft SQL Server 2000 Analysis Services SP4 with one OLAP database for AEA

Experion Application Server (EAS), including the Experion Relational Point Data Client

ACM Point Server

ACM EMI

UserAlert Server

AEA Application Server

In this architecture ACM enforces alarms through a firewall. This is accomplished with proxy and web service components that link the ACM Manager Server on level 4 with the Enforcer Server on level 3, as shown in the diagram.


Figure 11. ACM communicating through a firewall

Reference Architecture: DMZ

The second reference architecture locates the database servers in a DMZ that is accessible to both the business and control domains. The web server is located in the business domain, and the alarm management functions are located in the control domain. End users interact with the system from both level 3 and level 4, as some capabilities are available in each domain.


Figure 12. Reference architecture for using a DMZ

The several servers in this architecture are configured as shown in the following table.

Table 8. DMZ server configuration

Server Software

Oracle Server in DMZ

Windows Server 2003 with .NET 2.0, .NET 3.0, MSXML 6.0, and MDAC 2.8

Oracle 9i or 10g Server with one or two database instances:

• Business FLEX and ACM

• Uniformance Database (optional, and only if PHD is used)

SQL Server in DMZ

Windows Server 2003 with .NET 2.0, MSXML 6.0, and MDAC 2.8

Microsoft SQL Server 2005 SP2 with four databases:


• Base Components (installed by OI/OL/OM)

• UserAlert database

• AlarmAnalysis (used by AEA)

Microsoft SQL Server 2000 Analysis Services with one OLAP database for AEA


Server Software

L4 Web Server Windows Server 2003 with IIS, .NET 2.0, .NET 3.0, IE Web Controls, MSXML 6.0, and MDAC 2.8


Experion Desktop Server (EDS) with IIS, and with these OM Pro components

• AEA Web Server

• ACM Manager Web Service

• OI/OL/OM web components

Business Objects XI Release 2 products

• Business Objects Enterprise Premium

• OLAP Intelligence

• Crystal Reports Server

L4 Application Server








Experion Application Server (EAS)


UserAlert Server

AEA Application Server

L3 Application Server








Experion Application Server (EAS), including the Experion Relational Point Data Client

ACM Point Server

ACM Manager Server

UserAlert Server

Integration

OM Pro provides several types of integration when the components within OM Pro are installed and configured together.


Boundaries. Boundaries and constraints are entered in the Boundary Manager, which is part of ACM and physically stored in the Oracle database. ACM, UserAlert, and AEA get boundary values directly from this database. Operating Instructions and Operations Monitoring get these boundary values through an indirect approach: When boundaries are released in ACM, the system copies those values to the “limit set” component using an internal component called VtSync. OI and OM get boundary values from limit sets, in the same way that they would if a site used limit sets but not OM Pro.

Boundaries are exposed via OPC through the Experion Application Server, where they can be used by other programs.

User interface. Variable information, such as the consequence of deviating, that is entered in the Boundary Manager is available in the Operating Instructions and Operations Monitoring web user interface.

Assets and equipment. The OM Pro suite uses the asset model in the Experion Enterprise Model to organize information. The Experion asset model is required for ACM and AEA, and optional for OI/Ol/OM. The Enterprise Model Builder is normally to configure the asset hierarchy, and then the asset hierarchy is exported as an XML file and imported into the Plant Reference Model (PRM) used by OI/OL/OM. The import utility automatically creates any assets needed in the PRM to match what appears in the Enterprise Model, and builds the complete asset hierarchy. It is also possible to configure the PRM independently, in which case the asset (equipment) model used in ACM and AEA will be different than the model used in OI/OL/OM.

Operator consoles. ACM AlarmHelp can be integrated into, and called from Experion displays. The ACM client components are compatible with SafeView.

Historian tags. OM Pro keeps a list of historian tags that are available from PHD, OSIsoft PI, or another historian. This list of tags is normally updated from the historian at least once a day, and is shared by all OM Pro components that use historian tags.


Specifications

Platforms – Client Components

Note that individual client components may require only some of the platforms listed here.

Operating systems – all of these are supported and can be used at a site in any combination, except as noted

Windows 2000 Professional SP4

Windows XP Professional SP2

Windows Server 2003 SP2 Standard and Enterprise Editions

Windows Vista Business and Enterprise Editions

Other software generally required by most OM Pro client components

Internet Explorer 6.0 or 7.0

Microsoft .NET Framework 2.0 and 3.0

MSXML 6.0

MDAC 2.8

Oracle 9i client 9.2.0.8 or 10g client 10.2.0.3 (not required for web applications)

Adobe Reader version 6 or later

Other software required for selected OM Pro client components, but not required for all end users

Microsoft SQL Server 2000 Analysis Services SP4, client components (needed only for AEA Reporting Building Workstation)

Crystal Reports XI Professional or Developer Release 2 SP2 (needed only for creating or editing reports)

Microsoft Office XP, 2003, or 2007 (used in some cases when importing and exporting data)

Exceptions: The Enterprise Model Builder is formally supported on Windows XP and Server 2003, although workarounds are available to make it work on Windows 2000 and Vista. Event Analyst is only supported on Windows 2000, XP, and Server 2003. UserAlert’s email and pager configuration requires a workaround to work on Vista. Contact product management for the latest information.

Platforms – Server Components

Note that individual server components may require only some of the platforms listed here.


Operating systems Windows Server 2003 SP2 Standard or Enterprise Edition

Database management – all listed software is required

Oracle 9i Server 9.2.0.8 or 10g Server 10.2.0.3: Standard Edition One, Standard Edition, or Enterprise Edition

Microsoft SQL Server 2005 SP2: Standard or Enterprise Edition

Microsoft SQL Server 2000 Analysis Services SP4 (needed only for AEA)4

Reporting – all listed software is required

Business Objects Enterprise Premium XI Release 2 SP25

Business Objects OLAP Intelligence XI Release 2 SP2

Business Objects Crystal Reports Server XI Release 2 SP2

Other software required for at least some OM Pro server components

Internet Explorer 6.0 SP1 or 7.0

Microsoft .NET Framework 2.0 and 3.0

MSXML 6.0

MDAC 2.8

Oracle 9i client 9.2.0.8 or 10g client 10.2.0.3

Adobe Reader version 6 or later

Experion shared component Experion Application Framework (EAF) 310

Exception: Event Analyst has not yet been qualified for use with Oracle 10g. Contact product management for the latest information.

Control Systems

ACM provides native support for some control systems, and generic support for others, as shown in Table 9. A control system with native support has a dedicated ACM interface that is aware of alarm types and parameters for that control system, while generic support requires the site to supply some configuration for alarm types and parameters, alarm limit validation rules, and secondary support. Limited alarm configuration management is possible with generic support using tag templates and variable entitles with offline source tags.

The interface between ACM and the control system is via OPC DA or files. When OPC is used, ACM requires one OPC data access server for each DCS, and this server must support the OPC DA 1.0a or 2.0 specification. Some interfaces support write access, where ACM is able to enforce alarm settings, while others provide only read‐only access, so that ACM can report on differences but cannot enforce alarm settings. When OPC cannot be used, ACM can access alarm configuration data from a formatted text file rather than accessing the control system directly. This allows ACM to document and report on control systems that do not have OPC DA access or that are otherwise not supported fully by ACM.

4 AEA needs Analysis Services 2000, not Analysis Services 2005, for compatibility with Business Objects OLAP

intelligences XI, which does not support Analysis Services 2005. 5 Note that Business Objects XI SP2 is not the same as Business Objects XI Release 2 (R2). Release 2 is a later

release that has enhanced capabilities and different license keys. OM Pro 310 requires Business Objects XI Release 2, and does not support Release 1.


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 except for alarm

priorities

File, specific to Yokogawa

6 Each Experion server requires 1 x EP‐NTAUNS. 7 Each Experion server requires 1 x EP‐NTAUNS. 8 Honeywell TPS R533 and later support is via APP node with APP Base & optionally CL Server, to request ACM

enforcement from TPN. 9 Only if connected via Experion for TPS Server. 10 Foxboro I/A support requires Matrikon’s OPC server, Matrikon.OPC.Foxboro, version 4.0.2.0 GenCS:

foxomsrvr.


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 Documentation only

‐‐

It is possible to deploy ACM offline, without a control system connection, and the components can be networked or installed on a single computer (e.g., a laptop). This is known as an offline or disconnected ACM installation, and it supports almost all aspects of ACM configuration. A typical use is during design stage to capture and analyze the alarm configuration decisions being made or as part of an alarm rationalization project, when the control system is not available.

Event Analyst analyzes events collected from the Honeywell TPS control system, only, and requires Uniformance PHD using the Event Journal Collector (EJC) module.

UserAlert gets data from OPC DA servers and so does not depend on a particular control system. The UserAlert client components are qualified to be installed and used on Experion R301 Station, GUS R341, and standard networked PCs described in the Platforms section.

Operating Instructions, Operations Logbook, and Operations Monitoring work with the process historian, not directly with the control system, and so do not depend on any particular control system or version.

Historians

Many OM Pro components require a process historian. Two options are supported: Uniformance PHD and generic historians using OPC HDA. There is one exception—Event Analyst supports only PHD.


Uniformance PHD R210 and R215 are supported by all OM Pro components.11 When used, PHD can share some server computers with OM Pro, such as the Oracle database server.

Other process historians are supported using OPC HDA version 1.2. OM Pro 310 is qualified with OSIsoft™ PI versions 3.3 and 3.4 using OSIsoft’s OPC server for PI.12 From time to time, Honeywell may qualify other process historians through OPC HDA user interface, such as Yokogawa’s Exaquantum historian. Contact the Honeywell product manager for the latest information.

When a process historian other than PHD is used, OM Pro provides a utility called GETIT that reads the list of tag names from the historian, and stores a copy of the tag names in the Oracle database.

Some OM Pro features require historian tags to be created. For instance, a historian tag will normally need to be created to store each limit in the Boundary Manager or Operating Instructions that is to be monitored by Operations Monitoring.

Example: A site configures 1000 variables in the Boundary Manager and defines two sets of limits for each variable. This same site configures instructions for 10 assets, each setting two targets for 25 variables. This site has 1000*2 + 10*2*25 = 2,500 limits, and therefore will need to create 2,500 tags in the process historian.

Security

OM Pro uses a role‐based security model with Windows authentication. User accounts are required to access the system. Entitlement to perform actions in the OM Pro suite is controlled by roles, in a role‐based security model. There are over 25 predefined roles used by the various OM Pro components.

Each Windows user is granted one or more roles by an administrator using the administration consoles in OM Pro. Roles are independent of one another, not hierarchical. Roles can be assigned to groups, including to Windows groups, so that users can obtain role privileges based on group membership. ACM and UserAlert use Windows local groups on the computer where the Manager Server runs. All the web components can use Windows local groups and/or domain groups on the computer where the web server runs.

Operating Instructions, Operations Logbook, and Operations Monitoring allow linking security to the asset model, so that a user can be granted a role for some assets but not others.

Internationalization

Internationalization refers to the preparing an application to be translated and deployed in an environment that isn’t English. Localization refers to translating an application. Globalization refers to the combination of internationalization and localization.

11 PHD R210 is used with Oracle 9i and PHD R215 with Oracle 10g. The two releases are otherwise the same. 12 In the past OSIsoft has licensed its OPC HDA server as an extra cost option for the PI system, so sites with a PI

license do not necessarily have a license for OSIsoft’s OPC HDA server.


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 unique.



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


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


Control systems No limit Limited by server capacity.

Maximum of one generic control system.

Historians 1 One per ACM system.

Consoles 99 Maximum 99 per control system.



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


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 to the Oracle server.

Mode‐based instructions

Yes Modes are configurable on assets (equipment).

Note that alarm modes configured in ACM are not the same as planning modes configured in Operating Instructions.

Modes per asset No limit

Details (tags) per instructions

No limit Each detail specifies minimum, aim (focus), and/or maximum targets for one variable (historian tag). No limit on the number of details per instruction.

Instruction activation Manual, scheduled, mode change

Each instruction is configured individually for when it is activated.

Boundary checks When activated and ad hoc

All instruction details (proposed limits) are checked against boundary values. Checking is done when an instruction is activated, and on demand when editing proposed instructions.


Table 14. Operations Logbook specifications


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


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


Configured conditions

10,000 Up to 10,000 conditions evaluated every one minute per UserAlert Server.

Monitoring resolution

10 seconds Conditions can be evaluated as often as every 10 seconds. Monitoring more often reduces the number of conditions that can be monitored.

Condition types (algorithms)

9 options Bit pattern, boundary, combination, digital, frozen, group, range, rate of change, timer.



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.

Data source number No limit No limit to the number of OPC sources accessible by one UserAlert server.

Maximum alerts and alarms, Experion server

2,000 Maximum 2,000 unacknowledged alarms and alerts per Experion server. Alarms and alerts occupy the same storage space so there can be a maximum of 2,000 active alarms and alerts in the Alarm and Alert summaries.

Migrating from Earlier OM Pro Releases

OM Pro 310 supports migrating from OM Pro 200 and OM Pro 300. Procedures are documented for the following migration scenarios. Please note that other scenarios are possible but may require advice from Honeywell.

Table 17. Migration scenarios for upgrading to OM Pro 310

Upgrade Supported Migration Scenarios

OM Pro 200 to 310 Migration is performed in steps, with a migration from OM Pro 200 to 300, and then from 300 to 310.

Note: An upgrade of this magnitude will normally require consulting advice from Honeywell. Migrating from OM Pro 200 to 310 will require upgrading from PHD 202 to PHD 210 or 215, upgrading from SQL Server 2000 to 2005, and may require switching the servers from Windows Server 2000 to 2003. It is possible to upgrade the components in place, although there are some benefits for transferring the system from old to new servers since OM Pro 310 can run on a smaller number of servers than OM Pro 200.

OM Pro 300 to 310 The network architecture follows the two server, level 4 design as described on page 27, with no changes made to the network architecture as part of the migration.

Existing servers are upgraded in place.

Servers run Windows Server 2003. (OM Pro 310 does not support Windows 2000 Server.) The system is down while the upgrade is performed.

Oracle 9i continues to be used, not upgraded to Oracle 10g.

SQL Server 2000 is upgraded in place to SQL Server 2005.

Process historian is PHD 210 and is not changed as part of the migration.


Upgrade Supported Migration Scenarios

OM Pro 300 to 310 The network architecture follows the two server, level 4 design as described on page 27, with no changes made to the network architecture as part of the migration.

Two new servers are installed. The two existing servers continue to run in parallel until the new servers are commissioned.

New servers run Windows Server 2003, Oracle 10g, and SQL Server 2005.

Process historian is PI 3.4 and is not changed as part of the migration.


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 310

Product Release Core Optional

Alarm & Event Analysis 310 X

Alarm Configuration Manager (ACM) 310 X

Event Analyst 130.4 13 X

Event Monitoring Business FLEX 220 X

Lab Data Integrator (LDI) Business FLEX 220 X

LIMS Business FLEX 220 X

Operating Instructions Business FLEX 220 X

Operations Logbook Business FLEX 220 X

Operations Monitoring Business FLEX 220 X

UserAlert 310 X

13 Event Analyst 130.4 supports only Oracle 9i, not 10g. An update is planned but not yet released at the time

of this writing.


Earlier releases of OM Pro included ProMenu/ProTrend for use with GUS, however, ProMenu/ProTrend has been incorporated into GUS and is no longer packaged with OM Pro.

Prerequisites

OM Pro has several prerequisites. Note in particular that OM Pro requires, but does not include licenses for Microsoft Windows, Oracle Server, Microsoft SQL Server, or a process historian such as Uniformance PHD or OSIsoft PI. All of those products must be licensed separately.

Experion

OM Pro provides an Experion PKS 310 license for the following:

• DSA

• 40 Experion Application Clients

• OPC Advanced Client

• Experion Relational Point Data Client

• 10 DSA subscriptions

• Alarm pager

No license is required for EDS or other Experion components included in OM Pro.

Business Objects

Each OM Pro license includes licenses for some products from Business Objects (www.businessobjects.com), as follows. These Business Objects licenses are limited to use with Honeywell products. If necessary, additional licenses for the Business Objects products can be purchased from Honeywell.

Table 19. Business Objects product licenses included with OM Pro

Product Quantity

Business Objects Enterprise Premium XI 5 named user license

Crystal Reports Developer version XI 1 license

Crystal Reports Server .NET edition (included with Crystal Reports Developer license)

OLAP Intelligence XI 1 named user license

The Crystal Reports Server is used for all reporting except by AEA. Honeywell supports three options for this component. Crystal Reports Server .NET edition is bundled with Crystal Reports Developer and is the default for all sites. It allows for one (1) concurrent user to generate reports. The second and subsequent users are queued until the report is generated for the first user. A license for Crystal Reports Server Embedded Throttled or Crystal Reports Server Embedded Processor can be purchased at extra cost. Both Crystal Reports Server versions support more than one simultaneous user.

http://www.businessobjects.com/


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.

Microsoft Corporation (www.microsoft.com) offers two editions of SQL Server 2005 that are supported by OM Pro; Enterprise Edition and Standard Edition, with different prices and scalability. Microsoft offers three standard ways to buy licenses: per processor licensing, based on the number of CPUs in the server computer, server plus device CALs (concurrent access licenses), and server plus user CALs. Honeywell’s interpretation of Microsoft’s licensing policies is that all OM Pro users are required to have a SQL Server license, or else the site must choose per processor licensing.

http://www.oracle.com/

http://www.microsoft.com/


Documentation

OMPro310‐SCN OM Pro 310 Software Change Notice

OMPro310‐IG OM Pro 310 Installation and Setup Guide

AAM310‐ST Advanced Alarm Management 310 Specification

OI‐SPT‐220 Operating Instructions Specification and Technical Data

OL‐SPT‐220 Operations Logbook Specification and Technical Data

OM‐CFG‐220 Operations Management Suite Configuration Guide

OM‐USR‐220 Operations Monitoring User Guide

OMPro‐SPT‐310 OM Pro Specification and Technical Data

OM Pro 310 - Honeywell · report on alarm metrics; and to summarize shift handover information....

Documents

Transcript of OM Pro 310 - Honeywell · report on alarm metrics; and to summarize shift handover information....