blend performance monitor - honeywell performance monitor installation guide iii contents 1 about...

Advanced Solutions

Profit Blending and Movement R500.1

Blend Performance Monitor

Installation Guide

Release: 5.0.1

Document ID: BPM-INS-500

Revision Date: Sep 2016

© Honeywell International Sarl 2016. All Rights Reserved.

This document is the confidential and proprietary information of Honeywell. Reproduction and distribution of these

materials without the express written consent of Honeywell is strictly forbidden.

While this information is presented in good faith and believed to be accurate, Honeywell disclaims the implied

warranties of merchantability and fitness for a 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 direct, special, or consequential damages. The information and

specifications in this document are subject to change without notice.

These commodities, technology, or software were exported from the United States in accordance with the Export

Administration Regulations. Diversion contrary to U.S. law prohibited.

This product may contain or be derived from materials, including software, of third parties. The third party materials

may be subject to licenses, notices, restrictions and obligations imposed by the licensor. The licenses, notices,

restrictions and obligations, if any, may be found in the materials accompanying the product, in the documents or files

accompanying such third party materials, in a file named third_party_licenses on the media containing the product.

Honeywell, Experion, Profit, Business FLEX, and TotalPlant are US registered trademarks of Honeywell International

Inc.

Other brand or product names are trademarks of their respective owners.

Blend Performance Monitor Installation Guide iii

Contents 1 ABOUT THIS DOCUMENT .................................................................................................................. 5

1.1 Overview .............................................................................................................................. 5 1.1.1 Product Name Changes ......................................................................................... 5

1.2 About This Guide ................................................................................................................ 5 1.3 Before You Begin ................................................................................................................ 5 1.4 Related Documents ............................................................................................................. 6

2 INSTALLATION OVERVIEW................................................................................................................ 7 2.1 System Requirements ......................................................................................................... 7 2.2 Prerequisites ....................................................................................................................... 8

2.2.1 Adding SQL Server Reporting Services, and Business Intelligence Development Studio or SQL Server Data Tools, to an Existing SQL Server Installation ...................... 12 2.2.2 Configure SQL Reporting Services ....................................................................... 20

2.3 Installation and Configuration Steps ................................................................................ 27

3 BPM INSTALLATION......................................................................................................................... 29 3.1 Advanced Preparation ...................................................................................................... 29 3.2 Install the BPM Software ................................................................................................... 29 3.3 Post Installation Instructions ............................................................................................ 33

3.3.1 Install the Microsoft Security Updates................................................................... 33

4 CONFIGURE SITE SPECIFIC DATA.................................................................................................. 34 4.1 Overview ............................................................................................................................ 34 4.2 BPM Database Configuration Using the Excel Configuration Template ......................... 34 4.3 Import from the PBM Database......................................................................................... 36

4.3.1 Advance Preparation ........................................................................................... 37 4.3.2 Importing AmmDB Data into BPM ........................................................................ 39

4.4 BPM Configuration Utility ................................................................................................. 46 4.4.1 Common Utility Features ...................................................................................... 46 4.4.2 Products Tab ....................................................................................................... 47 4.4.3 Tanks Tab ........................................................................................................... 50 4.4.4 Properties Tab ..................................................................................................... 52 4.4.5 Giveaway Reporting Tab ...................................................................................... 53 4.4.6 Reblend Rule Tab ................................................................................................ 53 4.4.7 Spec Seasons Tab............................................................................................... 54 4.4.8 Custom Reports Tab ............................................................................................ 54

5 CONFIGURE CUSTOM/EXTENDED DATA COLLECTION ................................................................ 55 5.1 Background ....................................................................................................................... 55 5.2 Standard Data vs. Extended Data ..................................................................................... 56

5.2.1 Data Collected by BPM ........................................................................................ 56 5.2.2 Standard vs. Extended Keywords......................................................................... 57 5.2.3 BPM Changes for Heel Property Data Collection .................................................. 58

5.3 Adding the Extended Keyword Data to BPM Reports ..................................................... 58 5.3.1 BpmDb Stored Procedures .................................................................................. 58 5.3.2 GetBmBlnd Stored Procedure Details .................................................................. 59 5.3.3 BPMBlendComponentsExtended Report .............................................................. 61

5.4 Custom Data ...................................................................................................................... 62 5.4.1 Blend Plan File Custom Data ............................................................................... 62 5.4.2 Blend Target and Actual File Custom Data ........................................................... 62

Blend Performance Monitor Installation Guide iv

6 CONFIGURE SQL SERVER BASED CUSTOM REPORTS................................................................ 63 6.1 Using Report Manager ...................................................................................................... 63 6.2 Create Custom Reports Using SQL Server Reporting Services ..................................... 64

6.2.1 In Report Builder .................................................................................................. 64 6.2.2 In Business Intelligence Development Studio or SQL Server Data Tools .............. 66 6.2.3 Deploy the Reports .............................................................................................. 68

7 PHD/LAB DATA INTERFACE ............................................................................................................ 69 7.1 Overview ............................................................................................................................ 69 7.2 Lab Service Configuration ................................................................................................ 70

7.2.1 Update the Lab Service Configuration Settings .................................................... 70 7.2.2 Create Scheduled Tasks to Stop and Start the Honeywell BPM Lab Service ........ 71 7.2.3 Start the Lab Service ........................................................................................... 76

APPENDIX A - BPM FILE PROCESSOR AND SERVICE SETTINGS ................................................... 77 A.1 BPM Event Log ................................................................................................................. 77 A.2 BPM Configuration File .................................................................................................... 77

A.2.1 BPM Configuration Codes ................................................................................... 77 A.3 Plan, Target and Actual File Processor Settings............................................................. 79

A.3.1 Plan, Target and Actual File Folder Structure ....................................................... 79 A.3.2 Console Application and Web Service Configuration Settings .............................. 80 A.3.3 BPM Schedule Service ........................................................................................ 81

APPENDIX B - BPM PLAN PROCESSOR ............................................................................................ 82 B.1 Overview ........................................................................................................................... 82 B.2 Processing Details ............................................................................................................ 82

APPENDIX C - BPM TARGET PROCESSOR ....................................................................................... 86 C.1 Overview ........................................................................................................................... 86 C.2 Processing Details ............................................................................................................ 86 C.3 BPM Keyword Mapping for the Target File ...................................................................... 87

APPENDIX D - BPM ACTUAL PROCESSOR ....................................................................................... 90 D.1 Overview ........................................................................................................................... 90 D.2 Processing Details ............................................................................................................ 90 D.3 BPM Keyword Mapping .................................................................................................... 92

APPENDIX E - BPM LAB DATA SERVICE ........................................................................................... 95 E.1 Overview ........................................................................................................................... 95 E.2 Processing Details ............................................................................................................ 95

APPENDIX F - BPM DATABASE .......................................................................................................... 97 F.1 BPM Database Tables ....................................................................................................... 97 F.2 PBM Database Migration Tool .......................................................................................... 98

F.2.1 Prerequisites ....................................................................................................... 99 F.2.2 Update Procedure ............................................................................................... 99

APPENDIX G - TROUBLESHOOTING TIPS ....................................................................................... 102 G.1 Picture Printing Not Available ........................................................................................ 102 G.2 SQL Server Reporting Services Encryption Key Loss ................................................. 103

Blend Performance Monitor Installation Guide 5

1 ABOUT THIS DOCUMENT

1.1 Overview

The objective of the Blend Performance Monitor (BPM) application is to provide an integrated

information environment that supports the collection, storage and analysis of finished products blending information. This integrated information environment is used to improve the blend planning, stock

utilization, performance monitoring and finished product release functions.

Blend Performance Monitor is part of the Profit Blending and Movement (PBM) family of applications.

Working in conjunction with the Profit Blend Controller (PBC), Profit Blend Optimizer (PBO), Profit Movement Management (PMM) and other related products, Blend Performance Monitor forms part of a

total solution for blending and movement automation.

1.1.1 Product Name Changes

For users who are migrating from a version of LIMS Viewer that predates R431.1, the following product

suite and product names were changed starting with version R431.1:

Old Name New Name

Blending and Movement Automation (BMA) Profit Blending and Movement (PBM)

Experion Ratio Controller (ERC) Profit Blend Controller (PBC)

Open Blend Property Control (OpenBPC) Profit Blend Optimizer (PBO)

Inventory Monitor (IM) Profit Inventory Monitor (PIM)

Movement Automation (MA) Profit Movement Management (PMM)

The names of the remaining PBM applications (Blending Instructions, Experion Blend Controller, Blend

Performance Monitor, Experion Tank Monitor, LIMS Viewer and Production Browser) have not changed.

In general, the new product and suite names will appear in the operating displays and user documentation.

However, the old product and suite names (e.g. "BMA") will continue to appear in the internal software

structures, environment variables, system folder names, etc.

1.2 About This Guide

This manual describes how to install and configure the Blend Performance Monitor Release 5.0.1

software.

1.3 Before You Begin

Before you install Blend Performance Monitor, you should be familiar with Microsoft Windows® and Microsoft SQL Server® database administration, or has access to someone who is. This document is not

intended as a substitute for Windows or SQL Server database administration training, or as a description of Blend Performance Monitor functionality.


1.4 Related Documents

Further information about Blend Performance Monitor and related applications can be found in the

following documents.

Document Title

BPM-USR-500 Blend Performance Monitor User Guide

PBC-CFG-500 Profit Blend Controller Configuration Guide

PBO-CFG-500 Profit Blend Optimizer Configuration Guide

PMM-CFG-500 Profit Movement Management Configuration Guide

PBM-DSX-500 Profit Blending and Movement Network and Security Planning Guide

The BPM user documentation is installed on the BPM Server at \Program Files (x86)\Honeywell

\AMM\BPM\Help. The documents can also be accessed from the Windows Start menu at Programs > Honeywell BMA > Help.

See the Profit Blending and Movement Software Change Notice for a complete list of the PBM user

documentation.


2 INSTALLATION OVERVIEW

2.1 System Requirements

BPM Server

The BPM Server installation kit sets up the BPM Console Application (which includes the BPM Plan, Target and Actual Processors), Lab Service, Web Service and the Web Report user interface. It can also

be used to create the BPM database instance (BpmDb) in SQL Server. The BPM database must be

installed on the BPM Server.

No special hardware is required to support the BPM Server. Network access between BPM and the

desired data sources (i.e. blend planning system, blend control system and/or process historian) needs to

be considered.

Architecture

The BPM Server and its associated database are usually set up on a separate computer either on a Plant

Wide Control Network or Level 4 Plant Information Network. In order to allow data to be transferred to

and from the various data sources, be sure that the networks are configured to allow file transfer between them.

Figure 2-1 — Suggested Network Topology


See the PBM Network and Security Planning Guide for a description of the network topologies supported

by BPM, as well as the Windows security configuration used by all of the PBM applications, including BPM.

2.2 Prerequisites

Before you can install the BPM software on the BPM Server, the following software components must be

present:

Software Component Version Notes

Operating System Windows Server 2008 R2 (64-bit) SP1

or

Windows Server 2016

SQL Server SQL Server 2008 R2 SP2 (32-bit)

or

SQL Server 2012 SP3 (32-bit)

or

SQL Server 2014 (64-bit)

For SQL Server 2008 and SQL Server 2012, only the 32-bit platform is supported.

SQL Server's Reporting Services, and Business Intelligence Development Studio (SQL Server 2008) or SQL Server Data Tools1 (SQL Server 2012 and 2014), are mandatory BPM prerequisites. They must be present on the BPM Server prior to installing the BPM Server software. If SQL Server is already present, these features can be added after the initial SQL Server installation. See Section 2.2.1 for details.

1 Starting with SQL Server 2012, "Business Intelligence Development Studio" has been replaced by "SQL Server Data Tools".



ATTENTION:

The installation and configuration workflows for SQL Server 2008, 2012 and 2014 are broadly similar. As such, the reference workflows that are described in this document are those for SQL Server 2008. If differences between the installation and configuration workflows of the different versions of SQL Server apply, these are explicitly pointed out where applicable.



Web Browser Microsoft Internet Explorer (IE) 9 or later Compatibility view must be configured for IE 11 to support custom reports. To do this, proceed as follows:

Run IE

If the IE menu tool bar does not appear, press the Alt key

On the menu, select Tools >> Compatibility View settings

Enter the “BPM Server Name” in the “Add this website:” entry port and then select the Add button



Internet Information Services (IIS)

IIS 7.0 or later Must be installed and enabled. Be sure to enable ASP.NET extension. (See the Microsoft Support site for instructions on how to enable IIS and the ASP.NET extension.)

Is required by the BPM Web Service and Web Reports.

Refer to Section 3.1.2 of the PBM-INS document for background on the installation and configuration of the IIS software.

Microsoft .NET Framework

4.5.2 or later

ASP.NET Version 2.0 or later Is required for the BPM Web Reports.

Adobe Reader 6.0 or later

Process Historian (Optional)

Uniformance PHD R310.2 or later If BPM is going to be used to collect laboratory data then an interface to a process historian is required.

An interface between BPM and the PI historian is also supported. See the PBM Compatibility Matrix for the latest list of process historian releases supported by BPM.

ATTENTION:

Before you install the SQL Server 2008 or SQL Server 2012 software, you must specify the 32-bit platform. This is done by ensuring that the Processor Type is set to x86 prior to installing SQL Server.


2.2.1 Adding SQL Server Reporting Services, and Business Intelligence Development Studio or SQL Server Data Tools, to an Existing SQL Server Installation

Proceed as follows to add SQL Server Reporting Services, and Business Intelligence Development Studio

Business Intelligence Development Studio (SQL Server 2008) or SQL Server Data Tools (SQL Server

2012 or 2014), to an existing SQL Server database instance.

1. On the BPM Server access the SQL Server installation media and run SQL Server's setup.exe (right-click the setup.exe file name and select "Run as administrator" to launch the application).

2. In the SQL Server Installation Center, click Options.

3. For SQL Server 2008 and 2012, select x86 as the Process Type and then select Installation in the

navigation pane. For SQL Server 2014, select x64 as the Process Type and then select Installation in the navigation pane.


4. Click New installation or add features to an existing installation (SQL Server 2008) or New SQL Server

stand-alone installation or add features to an existing installation (SQL Server 2012 and 2014).

5. Follow the default steps until you reach the Installation Type screen shown below.

6. Select Add features to an existing instance of SQL Server 2008, SQL Server 2012 or SQL Server 2014

and then click Next.


7. i. For SQL Server 2008, in the Feature Selection screen select Reporting Services and Business

Intelligence Development Studio, and then click Next.


7. ii. For SQL Server 2012 and 2014, in the Feature Selection screen select Reporting Services - Native and

SQL Server Data Tools, and then click Next.


8. Follow the default steps until you reach the Server Configuration screen shown below.

9. For the SQL Server Reporting Services, enter the same account name and password as in the SQL Server service and then click Next. This is the identity that SQL Server runs under.


10. In the Reporting Services Configuration screen leave the report server Install option selected and click

Next.


11. Follow the default steps until you reach the Ready to Install screen shown below. Click Install.


12. Wait for the installation to complete and then click Close.


2.2.2 Configure SQL Reporting Services

Proceed as follows to configure SQL Server Reporting Services.

1. On the BPM Server launch the Reporting Services Configuration Manager from the Start menu at All

Programs > Microsoft SQL Server 20xx > Configuration Tools > Reporting Services Configuration

Manager.

2. In the Reporting Services Configuration Connection screen, enter the local BPM Server name, select

the report server instance and click Connect.


3. Navigate to the Web Service URL screen. Leave the default settings and click Apply.


4. Make sure that the apply operation is completed successfully before you proceed.


5. Navigate to the Database screen and click Change Database.

6. Select Create a new report server database and then click Next.


7. Select SQL Server Account as the Authentication Type. Enter sa as the Username and enter the

password. Finally click Next.

8. Leave the default Database settings and click Next to proceed.


9. Leave the default Credentials settings and click Next to proceed.

10. Review the Summary information and click Next.


11. Click Finish.

12. Back in the Reporting Services Configuration Manager navigate to the Report Manager URL screen. Leave the default settings and click Apply.


13. Make sure that the apply operation is completed successfully and then click Exit.

2.3 Installation and Configuration Steps

BPM Installation on the BPM Server

The Blend Performance Monitor software and database are installed together on the BPM Server as

described Section 3.

Upgrading BPM from BMA R400.1

If you are upgrading from the version of BPM released with BMA R400.1, the BPM software and the

BPM database (BpmDb) must be removed before you can install the new BPM software. Proceed as

follows to uninstall BPM:

Proceed as follows to upgrade BPM to PBM R500.1.

1. Remove the HW.BM.ConsoleApp from the Task Scheduler.

2. Drop the BpmDb database in SQL Server.

3. Using the Control Panel, Programs and Features applet uninstall the BPM Database and BPM Server software.

4. Reinstall the BPM software and recreate the BpmDb database from scratch as described in this

document.

Note: BPM database migration from an older database version is not supported in this case.

Upgrading BPM from BMA R410.1 and later

If you are upgrading from the version of BPM released with BMA R410.1, BMA R430.1 or PBM R431.1, several changes have been made that require the BPM software to be uninstalled before you can

install the new BPM software. In addition the BPM database needs to be updated.

Proceed as follows to upgrade BPM to PBM R500.1.

1. Remove the HW.BM.ConsoleApp from the Task Scheduler.

2. Using the Control Panel, Programs and Features applet uninstall the BPM Database and BPM Server

software.

3. Install the BPM software as described in Section 3.2, but do not create the BPM database.

4. Use the PBM Database Migration Tool to upgrade the BPM database. See Appendix F.2 for details.

Upgrading SQL Server Versions

If you want to upgrade from an older version of SQL Server to a new version of SQL Server, proceed as follows:

1. Prior to the SQL Server upgrade, detach the BpmDb database that is running on your existing system

and save the mdb and ldb files to backup media.

2. Upgrade SQL Server.

3. Attach the backed up BpmDb database to the newly installed SQL Server 2008, 2012 or 2014

instance.

Note: You can also uninstall the old version of the BPM Server software and install the new BPM Server software as part of this process if desired. Do not upgrade the BPM database in this case.


BPM Configuration

Blend Performance Monitor configuration consists of the following general steps:

Step Action Required See

1. Configure your site specific data. Required Section 4

2. Configure the interface to the blend control system.

If blend target and actual information is going to be collected from Profit Blend Controller, Profit Blend Optimizer or Profit Movement Management (for batch blends), see the Blend Performance Monitor Interface Configuration instructions in the corresponding product Configuration Guide for details.

Required Profit Blend Controller, Profit Blend Optimizer and/or Profit Movement Management Configuration Guides

3. Configure extended/custom data collection. Optional Section 5

4. Configure the SQL Server based custom reports. Optional Section 6

5. Configure the lab data interface. Optional Section 7

ATTENTION:

1. For PBM R500.1, an interface between Blend Performance Monitor and Profit Blend Controller is provided. A Blend Performance Monitor interface with Experion Blend Controller is not available at this time.

2. For systems running Windows Server 2008 and later, all executables must be run as administrator. In Windows Explorer, right-click the executable file name and select "Run as administrator" to launch the application.

Known Issue

Please note that BPM does not support blend data collection for flow-based recipes. Only volume percent based recipe data is supported.


3 BPM INSTALLATION

3.1 Advanced Preparation

Windows User and Group Settings

Prior to installing the Blend Performance Monitor software, the user and Windows group configuration described in the PBM Network and Security Planning Guide must be completed.

ATTENTION:

The BPM User group and the local BPM Administrator user are no longer used by BPM. The standard PBM Windows security (used by all of the PBM applications) must be used and is enforced by the BPM software installation.

Disable Windows Installer RDS Compatibility

If you are installing the BPM software on a computer running Windows Server 2008 R2 or later,

Windows Installer RDS Compatibility must be disabled before you can proceed with the installation. This

group policy is disabled as follows:

1. Log onto the system using an account with local administrator privileges.

2. In the Windows Control Panel, search for "Group Policy".

The search results should display a link labelled "Edit group policy".

3. Use the link to open the Local Group Policy Editor and then navigate to Computer Configuration >

Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop

Session Host > Application Compatibility.

4. In the list of settings, right click the Turn off Windows Installer RDS Compatibility setting and select

Edit from the shortcut menu.

5. In the Turn off Windows Installer RDS Compatibility dialog box, select the Enable option and click

OK to apply the change.

3.2 Install the BPM Software

Procedure

Proceed as follows to install the BPM software.

1. Log onto the target computer using an account with local administrator privileges.

2. In the setup files provided, navigate to the \BlendPerformanceMonitor folder, right-click the setup.exe file name and select "Run as administrator" to launch the application.

3. Review and accept the license agreement.

4. Enter your name, organization and BPM license key.


5. In the Custom Setup window verify that the Create Database subfeature is selected for new

installations. If you are upgrading an existing BPM Server installation, deselect this subfeature.

ATTENTION:

If a copy of the BPM database exists on the target computer you cannot proceed with the installation unless the existing database has been dropped (or renamed), or the Create Database feature has been deselected.

Starting with BMA R430.1, the BPM database can no longer be created manually using script files. The database must be created using the BPM Server InstallShield Wizard.


6. In the Identify Server Nodes screen, enter the computer name for the Historian Server (if applicable).

The SQL Server node is the local computer name and cannot be changed.

If BPM will not be collecting lab data from a process historian (e.g. PHD), the Historian Server name can be left blank.

7. If the Create Database feature was selected, use the Database Server window to set up the connection

to SQL Server.


Note:

If Windows authentication is selected, the current user must have sa role access in SQL Server.

If Server authentication is selected, enter the user ID and password for the local SQL Server's

System Administrator (sa).

8. If the Create Database feature was selected, use the Database Folder window to change the installation folder for the database if needed.

9. Proceed with software installation.

ATTENTION:

If the BPM software installation is not completed successfully, a message is displayed and the installation is automatically rolled back. When this happens, the BPM database installation may be partially completed. The database must be dropped before you attempt to create it again.

10. Once the BPM installation is completed, the PBM Security Configuration Tool runs automatically.

11. In Windows Administrative Tools open the IIS Manager.


12. Navigate to the default web site for this computer and confirm that the following services are present:

HW.BM.WebReports

HW.BM.WebService

13. In the \Program Files (x86)\Honeywell\AMM\BPM folder, open the HW.BM.Configuration.xml and review the configuration settings described in Appendix A.2.

14. If BPM's laboratory interface is going to be used, update the frequency of service execution setting as

described in Section 7.2.

15. Using the Windows Services applet, start the BPM Schedule Service.

16. If you have not already done so, assign the appropriate end users to the Product Administrators or Local Operators local groups.

3.3 Post Installation Instructions

3.3.1 Install the Microsoft Security Updates

Once the BPM software installations have been completed, install the Microsoft security and non-security updates that have been certified by Honeywell. Honeywell's Update Manager utility, that is packaged

with the Honeywell SUIT ISO Image, is used for this purpose.

ATTENTION:

Be sure to use the latest SUIT ISO that is available from the HPS Support Site. See the SUIT ISO User Guide to find out how to use the ISO and Update Manager to update the system.

Be sure that all of the PBM software has been installed on the target system before you run the Update Manager utility.

Do not install Microsoft security or non-security updates that have not been certified by Honeywell. (Installing uncertified updates could make your system inoperable.)


4 CONFIGURE SITE SPECIFIC DATA

4.1 Overview

The BPM database can be configured with site specific data in the following ways:

Using the supplied the Excel configuration template as described in Section 4.2.

Using the BPM Configuration utility as described in Section 4.4.

If BPM is going to be used to collect blend data from Profit Blend Controller, Profit Blend Optimizer

or Profit Movement Management, the existing product, property and tank settings can be imported from the PBM database (AmmDb) using the BPM Configuration utility as described in Section 4.3.

4.2 BPM Database Configuration Using the Excel Configuration Template

Excel Configuration Template

BPM's Excel configuration template is used to configure site specific data. This template is comprised of

two Excel workbooks: BM_ConfigTemplate.xls and BM_ConfigMacro.xls, that are installed to the

\Program Files (x86)\Honeywell\AMM\BPM\Configuration folder on the BPM Server.

BM_ConfigTemplate.xls is used for data entry. The configuration is defined in a series of worksheets

(described later in this section).

BM_ConfigMacro.xls imports the configuration data from BM_ConfigTemplate.xls and uses formulas to produce SQL statements.

Configuration Procedure

1. Enter the configuration data into BM_ConfigTemplate.xls, save the edits and close the workbook.

ATTENTION:

If implementing BPM in the context for use with PBC, PBO or PMM, please ensure that equipment, product and property information configured in the base configuration tables (IP_EQ, IP_PRDCT, BP_PROPERTY, etc.) is specified exactly as it is configured in the corresponding tables in the BpmDb database.

Also, please ensure that a "piece of equipment" called "_NO_DATA" is configured in the IP_EQ and IP_EQUIP_ATTR tables in the BpmDb database.

2. Open the BM_ConfigMacro.xls and navigate to the "SQL Scripts" worksheet.

3. Enter the path to BM_ConfigTemplate.xls in cell N2.

4. Click the Create SQL button. This macro copies the configuration data from BM_ConfigTemplate.xls

into BM_ConfigMacro.xls and produces SQL statements in column A of the "SQL Scripts" worksheet.

5. Save the insert statements from the "SQL Scripts" worksheet into a separate file.

6. On the computer where the BPM database instance is installed, transfer the insert statements to a database management tool (e.g. Query Analyzer for SQL Server).

7. Execute the insert statements to populate the BPM database.


ATTENTION:

These formulas do not produce statements which avoid duplicate record errors. Typically, some of the configuration may already be populated in the database, and duplicate record diagnostics will be produced. To prevent the insertion of duplicate entries, please check that the data being inserted does not already exist in the corresponding BPM table. The IP_ENG_UNIT table in particular should be checked for such occurrences. If one does not check for duplicate entries, early termination of the scripts may result depending on the tool used to execute the SQL.

BM_ConfigTemplate.xls Worksheets

Table 4-1 — BM_ConfigTemplate.xls Worksheet Instructions

Worksheet Template Macro Notes

products Enter each product name, report-as name, type and unit of measure.

Formulas produce SQL inserts to be used to add the products to the database and populate associated attributes required by BPM.

Unit of measure reporting requires the same unit of measure for all components and products. Only the first unit of measure will be used.

product_tanks Enter each tank name and report-as name.

Also enter each blender name and report-as name.

Formulas produce SQL inserts to be used to add the tanks and blenders to the database and populate associated attributes required by BPM.

Blenders must be configured in the product tanks list for processing to succeed. They are configured with an equipment type of TANK.

No configuration is required for component tanks, but if the debug level is set so that warning messages are logged, then unconfigured tanks will cause warnings to be logged.

properties Enter each property name, report-as name and unit of measure.

Formulas produce SQL inserts to be used to add the properties to the database and to associate it with BPM.

components Enter each component name, report-as name, type and unit of measure.

Formulas produce SQL inserts to be used to add the components to the database and populate associated attributes required by BPM.

Unit of measure reporting requires the same unit of measure for all components and products. Only the first unit of measure will be used.

If keyword files come from PBM, the “display name” from PBM configuration must be configured as the “prdct_name” in the products tab.

additives Enter each additive name, report-as name, type, and unit of measure.

Formulas produce SQL inserts to be used to add the additives to the database and populate associated attributes required by BPM.

Reporting requires the same unit of measure for all additives. Only the first unit of measure will be used.


Worksheet Template Macro Notes

specs Enter the product and property names, start and end dates, period IDs, and minimum or maximum values for blending and/or shipping.

Formulas produce SQL inserts to be used to add the specifications to the database.

Only need to configure the properties for which giveaway reporting is desired.

This sheet requires additional care because there are multiple insertions for the properties of each product, but only one insertion for each product. Product numbers and period ID values must be populated to match pre-existing data. The macro sheet manages this relationship. Do not edit the macro workbook without understanding the mechanism.

giveaway$ Enter the property names, cost, min or max basis, and TANK, HEADER, or LAB as certification source.

Formulas produce SQL inserts to be used to add the giveaway records to the database.

Only need to configure the properties for which giveaway reporting is desired.

tag_mapping Enter tank name, property name, and tag name.

Formulas produce SQL inserts to be used to add the tag mapping records to the database.

Only need to configure the process historian tag names for the product tank/property combinations for which lab data is being collected.

4.3 Import from the PBM Database

The BPM Configuration Utility can be used to import existing product, property and equipment settings from the PBM database (AmmDb) into the BPM database. Once this information has been imported, the

utility is used to complete the product, property and tank configuration for use with the BPM application

as described in Section 4.4.

ATTENTION:

The BPM Configuration Utility's Import facility will delete any existing product, property and equipment configuration in your BPM database. It will also delete all existing keyword data that has been collected and stored in the BPM database.

Do not use the AmmDb Import feature if you have existing configuration information or keyword data in the BPM database, that you are not prepared to loose.

If the BPM product, property and equipment configuration needs to be changed, this must be done manually in the BPM Configuration Utility as described in Section 4.4.

Be sure to disable the AllowAMMDBImport key in the Honeywell.BM.Configuration.exe.config file

after the AmmDb database information has been imported into BPM. This will remove the Import AMMDB button from the utility and ensure that the configuration is not accidentally overwritten in the future.


4.3.1 Advance Preparation

PBM Material and Product Naming Requirements

ATTENTION:

Without the BPM application, the PBM applications can use different descriptors for the names of a product (additives and components and instances of products and the terms product and material are used interchangeably throughout this document).

However, if BPM is implemented in an integrated PBM blending system that consists of both the blend ratio and blend property control applications, please make sure that the values of the IP_PROD_ATTR.ebcMaterialName and IP_PROD_ATTR.obpcMaterialName attributes configured in the PBM database (AmmDb) are identical for each distinct product in the system.

In the same vein, if BPM is implemented in an integrated PBM system, please make sure that the values of the IP_PROD_ATTR.ebcMaterialName, IP_PROD_ATTR.obpcMaterialName and IP_PROD_ATTR.Description attributes configured in the PBM database (AmmDb) are identical for each distinct product in the system.

Furthermore, please ensure that the value assigned to each set of attributes (ebcMaterialName, obpcMaterialName and Description) is distinct. In other words, one cannot have the values of the ebcMaterialName , obpcMaterialName and Description attributes for Product-1 set to, let’s say, “My Product“ and have the values of the ebcMaterialName, obpcMaterialName and Description attributes for Product-2 also set to “My Product “.

For systems where BPM is implemented with one or more blending applications, and PMM is subsequently added, please set the value of the IP_PROD_ATTR.Description attribute equal to the value of the corresponding IP_PROD_ATTR.ebcMaterialName / IP_PROD_ATTR.obpcMaterialName attribute so that whatever processes have been implemented to work with IP_PROD_ATTR.ebcMaterialName / IP_PROD_ATTR.obpcMaterialName values can continue to do so unperturbed.

In a similar vein, for systems where BPM is implemented with one or more PBM movement applications (i.e. PMM) and blending is subsequently added, please set the value of the IP_PROD_ATTR.ebcMaterialName / IP_PROD_ATTR.obpcMaterialName attribute equal to the value of the corresponding IP_PROD_ATTR.Description attribute.

On a related note, in an integrated PBM system, please ensure that the designation of “components” and “additives” is consistent for all of the products implemented in the system. Specifically, this entails the following:

For additives:

If a blend control application (e.g. PBC) is implemented, a record where the APPL_ENTITY_TYP field is set to a value of ebcAdditive must be defined for the additive in the IP_PROD_ENTITY_TYP table in the PBM database (AmmDb).

If PBO is implemented, a record where the APPL_ENTITY_TYP field is set to a value of obpcAdditive must be defined for the additive in the IP_PROD_ENTITY_TYP table in the PBM database (AmmDb).

If PMM is implemented, a record where the ATTR field is set to a value of SubType and the VALUE field is set to a value of 1103 must be defined for the additive in the IP_PROD_ATTR table in the PBM database (AmmDb).

For components:

If a blend control application (e.g. PBC) is implemented, a record where the APPL_ENTITY_TYP field is set to a value of ebcComponent must be defined for the component in the IP_PROD_ENTITY_TYP table in the PBM database (AmmDb).

If PBO is implemented, a record where the APPL_ENTITY_TYP field is set to a value of obpcComponent must be defined for the component in the IP_PROD_ENTITY_TYP table in the PBM database (AmmDb).

If PMM is implemented, a record where the ATTR field is set to a value of SubType and the VALUE field is set to a value that is not 1103 must be defined for the component in the IP_PROD_ATTR table in the PBM database (AmmDb).

Update the Configuration File for the BPM Configuration Utility

On the BPM Server navigate to the \Program Files (x86)\Honeywell\AMM\BPM

\HW.BM.Configuration folder and open the Honeywell.BM.Configuration.exe.config file in a Text Editor.

Figure 4-1 — Honeywell.BM.Configuration.exe.config File Contents

<?xml version="1.0" encoding="utf-8" ?>

<configuration>

<appSettings>

<add key="DateFormat" value="MM/dd/yyyy HH:mm:ss" />



<add key="DBType" value="SQLSERVER" />



<add key="DBProvider" value="SQLOLEDB.1"/>



<add key="DBHost" value="localhost" />



<add key="DBName" value="BPMDB" /> 

<add key="Username" value="" /> 

<add key="Password" value="" /> 



<add key="AllowAMMDBImport" value=""/>



<add key="AMMDBType" value="SQLSERVER" />



<add key="AMMDBProvider" value="SQLOLEDB.1"/>



<add key="AMMDBHost" value="localhost" />



<add key="AMMDBName" value="AMMDB" /> 

<add key="AMMUsername" value="" /> 

<add key="AMMPassword" value="" /> 

</appSettings>

</configuration>

1. Verify that the BPM database (BpmDb) connection settings are correct and adjust them if needed.

If you will be importing data from the PBM database (AmmDb) perform the following additional steps:

2. Verify that the PBM database (AmmDb) connection settings are correct and adjust them if needed. If

the AmmDb database is not present on the BPM Server node, be sure to change the AMMDBHost setting at minimum.

3. Ensure that the AllowAMMDBImport key has not been commented out.


4.3.2 Importing AmmDB Data into BPM

Proceed as follows to import the existing product, property and equipment settings from the PBM database into the BPM database.

1. On the BPM Server, start the BPM Configuration Utility by selecting Programs > Honeywell BMA >

Engineering Tools > BPM Configuration in the Windows Start menu.2

2. If the AmmDb Import feature has been enabled, the Import AMMDB button will appear at the top of the BPM Configuration Utility.

Note: If the Import AMMDB button does not appear, make sure that the AllowAMMDBImport key has been enabled in the Honeywell.BM.Configuration.exe.config file (as described in the previous

Section) and restart the BPM Configuration Utility.

2 The BPM Configuration Utility can also be accessed by double-clicking the Honeywell.BM.Configuration.exe file

that is stored in the \Program Files (x86)\Honeywell\AMM\BPM\HW.BM.Configuration folder.


3. Click the Import AMMDB button and answer Yes when prompted to proceed with the import.

4.a) If the import operation is completed successfully the following message is displayed. Click OK to

open the Import window.

The Import window's Status view shows the results of the import operation. This view is intended to be used for troubleshooting.


4.b) If errors occur during the import operation, the Status view shows where the error occurred.

Imported data errors are identified in the corresponding view, along with a tooltip that describes the

error.

Errors in the AmmDb database must be corrected and the AmmDb import operation must be started

again. You will not be able to save the imported data to the BPM database if there are errors.


5. In the Import window use the Tanks, Products and Properties views to review the settings that have

been collected from the AmmDb database.

The tanks and blenders are imported from the IP_EQ table, using the TYP filters for TANK and

BLENDER, respectively.

The products, components and additives are imported from the IP_PRDCT,

IP_PROD_ENTITY_TYP, IP_PROD_ATTR and BP_ADDITIVE tables.


The properties are imported from the CM_PROPERTY and BP_PROPERTY tables.

ATTENTION:

At this point nothing has been saved to the BPM database. If you close the Import window without saving, the imported data is lost.

6. In the Products view, the unit of measure in PRODUCT_UOM for products and components, is initially

set to the first unit of measure in the Vol.UOM list box that was loaded from the AmmDB database. You can select one of the other UOMs for all of the products and components (but not for additives)

if needed. For additives the UOM is collected from the VolumeUnits attribute in the BP_ADDITIVE table.

Note: BPM requires that the UOMs for all products and components be identical. (This is true, even across multiple blenders.) When you select a new UOM from the Vol.UOM list box, the same UOM is

applied to every product and component in the view. (This is needed for the BPM summary reports,

which sum the component and product quantities. BPM does not perform UOM conversions.)

For example, if you change the Vol.UOM to bbl, the PRODUCT_UOM for all of the products and components is changed to bbl as shown below.


ATTENTION:

1. Currently the units of measure must be volume or mass based units. This is true even for additives.

The unit type called "PORTION" (e.g. ppm) that is available in the BPM Configuration Utility - Products tab is not currently supported.

2. The text string used for the units of measure in the AmmDb can be mixed case. In BPM all UOM strings must be in all capitals. The import utility automatically converts the UOM case when it does the save to BPM.

3. The product type (TYP) imported from the AmmDb database will always be "MtlSpec". This setting should be changed in the BPM Configuration Utility's Products tab (described in Section 4.4.2) prior to use.

4. If new units of measure or product types are needed, they can only be added using the Import window. They cannot be added using the BPM Configuration Utility - Products tab.

7. Click the Save BPM button and answer Yes when prompted.

ATTENTION:

As indicated in the Confirmation message, the configuration of BPM is "incomplete " at this stage. Importing the AmmDb data into the BPM database is only part of the BPM configuration. The product specifications, reblend data, giveaway settings, etc. still need to be configured as described in Section 4.4.

8.a) If an error occurs the following message is displayed.

In this case the Status view displays an error message next to the Activity where the error occurred.

When an error occurs, all BPM Save operations (BPM database deletes and inserts) are rolled back.


8.b) If the BPM Save operations are successful the Status view shows the results of the Save BPM

operation.

9. Click OK in the Success message to close the Import window and return to the main configuration

screen.

ATTENTION:

1. After you import the equipment settings from the AmmDb database, verify that a "piece of equipment" called "_NO_DATA" is configured in the IP_EQ and IP_EQUIP_ATTR tables in the BpmDb database. If it does not exist, it must be added.

2. Be sure to disable the AllowAMMDBImport key in the Honeywell.BM.Configuration.exe.config file

after the AmmDb database information has been imported into BPM. This will remove the Import AMMDB button from the utility and ensure that the configuration is not accidentally overwritten in the future.


4.4 BPM Configuration Utility

The BPM Configuration Utility can be used to configure products, properties and equipment in the

context of the BPM application. Some reporting and processing controls can also be configured using this utility.

4.4.1 Common Utility Features

Figure 4-2 — BPM Configuration Utility

The buttons at the top of the display are common to all the Configuration utility tabs and perform the following functions:

Buttons Description

Save Saves the changes made in any of the BPM Configuration Utility tabs to the BPM database.

Note: If errors are encountered during the save operation, nothing is saved to the BPM database.

Reject Changes Rolls back all of the changes made in the BPM Configuration Utility since the last save operation.

Refresh Reloads the BPM Configuration Utility with the current contents of the BPM database.

Note: Any unsaved changes made within the BPM Configuration Utility are lost.

Copy Copies the contents of the currently selected rows to the Clipboard.

Print Prints the selected grid.

Note: The Copy and Print functions are not currently working.

Import AMMDB Imports the existing product, property and equipment settings from the PBM database (AmmDb) into the BPM database. See Section 4.3 for details.

This button will only appear if the AllowAMMDBImport key has been enabled in the Honeywell.BM.Configuration.exe.config file (as described in Section 4.3.1).


Use the add button ( ) to add a new record to the associated table.

Use the delete button ( ) to delete the currently selected record from the associated table.

Notes:

1. Whenever a line is edited, the box on the left side of the row is highlighted. The colors represent the

status of the row:

Yellow indicates that the data in the row is in an edited (unsaved) state.

Green identifies the row as new.

Red indicates an error in the row after a failed attempt to write to the BPM database.

2. Changes (including add and delete operations) are not automatically saved to the BPM database. This only happens when the Save button is clicked.

3. New entries can be manually added to any of the tables in the Configuration utility. Care must be

taken to enter values that are formatted correctly for BPM. If the new entries are not supported by BPM, the save operation will fail. (Note: The utility does not check formatting.)

4. The Enabled and Active options that appear in Products, Tanks and Properties tabs are not used by

BPM and can be ignored.

4.4.2 Products Tab

The Products tab is used to configure the components, additives and products in BPM. Properties can be

associated with selected products and seasons (time periods), so that seasonal limits can be specified.

Figure 4-3 — Products Tab


Table Description

Products Use the table at the top of the tab to configure the components, additives and products that exist in the applications that will supply blend data to BPM.

Period Use the Period table to select the property specification time period (seasons) for the component, additive or product that is currently selected in the Products table.

New time periods are identified by clicking the add button and using the Select Period dialog (Figure 4-4) to select the desired time period.

Note: The BM_PRODUCT_PERIOD table must be configured before you can select a period for a given product. This table is configured in the Spec Seasons tab described in Section 4.4.7.

Properties Use the Properties table to configure the property value limits for the currently selected product-season pair.

New properties are identified by clicking the add button and using the Add Properties dialog (Figure 4-5) to select the desired properties.

Notes:

1. Product properties can have a season assigned to them or a period. Specifications must have a period.

2. The Product Property Specification tables let you set a different of properties for each period.

Time Period Association

Time periods (seasons) of interest are selected for association with the currently selected product.

Figure 4-4 — Period Selection for Product Property Specification

Note: New time periods cannot be created in the Select Period dialog. The Spec Seasons tab (described in Section 4.4.7) must be used for this purposes.


Product Property Selection

The properties of interest for the currently selected product and season are selected from the Add

Properties dialog.

Figure 4-5 — Add Properties Dialog


4.4.3 Tanks Tab

The Tanks tab is used to configure the tanks and blenders in BPM. It is also used to associate properties with tanks and to associate tags with tank-specific properties.

Figure 4-6 — Tanks Tab

Table Description

Tanks Use the table at the top of the tab to configure the tanks and blenders that exist in the applications that will supply blend data to BPM.


Table Description

Tag - Property Mapping

Use the Tag - Property Mapping table to configure the properties associated with the currently selected tank, along with the historian tag for each property (if applicable).

New properties are identified by clicking the add button and using the Add Properties dialog to select the desired properties.

To select a property tag, click the associated Tagname cell and then click the button to open the Select Tag dialog.

Notes:

1. BPM does not provide a way to identify tanks as product or component (i.e. source) tanks only. BPM

assumes that tanks can be used for either type of operation.

2. Blenders must be configured as "tanks" in BPM.

3. The tagnames are populated from the current IP_TAG table in the BPM database. This database table

must be configured before you can assign tags to properties in the BPM Configuration Utility.

There is no tool available to populate IP_TAG table in BPM. The main reason for this is that the

number of tags of interest to BPM is usually quite small relative to the number of tags configured in a

historian. There is no way to automatically select them from the historian.

4. The tag Posted Date field is used by the Lab Service. See Section 7 for details.


ATTENTION:

Please ensure that a "piece of equipment" called "_NO_DATA" is configured in the IP_EQ and IP_EQUIP_ATTR tables in the BpmDb database.

4.4.4 Properties Tab

The Properties tab is used to configure the properties in BPM.

Figure 4-7 — Properties Tab

Note: The Is Blend Property and Display Seq settings are not used by BPM and can be ignored.


4.4.5 Giveaway Reporting Tab

The Giveaway Reporting tab is used to select properties for inclusion in giveaway reports and to specify the following:

Giveaway cost

Whether giveaway is associated with the upper or lower property limit

Whether the determining property value is taken from the tank, blend header or lab data

Figure 4-8 — Giveaway Reporting Tab

New properties are identified by clicking the add button and using the Add Properties dialog to select the

desired properties.

4.4.6 Reblend Rule Tab

The Reblend Rule tab is used to set the heuristics used to determine whether a blend event is a new blend

or a reblend.

Figure 4-9 — Reblend Rule Tab

If a blend has been running for longer than the number of days configured as the Last Blend Days, then the blend is automatically set to a new blend.


4.4.7 Spec Seasons Tab

The Spec Seasons tab is used to define the seasons used to specify property value limits for products.

Figure 4-10 — Spec Seasons Tab

4.4.8 Custom Reports Tab

The Custom Reports tab can be used to configure the reports that are accessed from the custom reports list

in the BPM Report Generator. Enter the report title and external URL link for each report. Use the up and

down arrows to control the order in which the reports appear in the selection list.

Figure 4-11 — Custom Reports Tab

ATTENTION:

If you plan to create SQL Server based custom reports (as described in Section 6) do not configure this table. The SQL Server based custom reports are accessed through the Custom Reports Explorer instead.

Do not create links to the SQL Server based custom reports in this table.


5 CONFIGURE CUSTOM/EXTENDED DATA COLLECTION

5.1 Background

Blend Performance Monitor is used as the repository and integration point for the following types of

blend data:

Blend plans

Blend targets

Blend actuals

Blend data is supplied to BPM in the form of keyword files that are created by other applications like

Profit Blend Controller, Profit Blend Optimizer and Profit Movement Management. The Plan, Target and

Actual files are text files with a defined structure. The Plan, or recipe, files must be supplied in the BPC

input format. The Target files and Actual files must be supplied in the LST output format.

Profit Blend Controller and Profit Blend Optimizer can generate target and actual keyword files for

blends. Profit Movement Management can generate target and actual keyword files for batch blends.

The blend plan files need to be generated by a blend planning tool (e.g. BLEND2). At this time blend plan keyword files cannot be generated by BI but this interface will be provided in the future. (The plan is to

have BPM read BI's recipe files (in XML format) instead of the currently supported .bpc keyword file

format.)

Identify Specific Blends

The blend plan and target data for a specific blend is stored in the BpmDb "PENDING" tables up until the

blend is closed. The recipe ID is used to associate the plan and target data with the blend in the PENDING tables. Once a blend is closed, the blend's plan and target data is moved from the PENDING

tables to the "BLND" tables, along with the actual blend data. A unique BLND_XREF_ID is created for

the blend and this ID is then assigned to all of the plan, target and actual data records for that blend when

they are stored in the BLND tables.

This means that prior to the close of a blend, BPM will not allow two planned or ongoing blends to use

the same recipe ID. If a second blend (say for a different blender) is created with the same recipe ID, and

a corresponding plan file is posted to BPM, BPM will overwrite the "pending" files for the first blend. - This is a known limitation in BPM and it will not be fixed in PBM R500.1.


5.2 Standard Data vs. Extended Data

5.2.1 Data Collected by BPM

Each blend plan file is broken down into strictly defined "sections" that correspond to specific sets of tables in the BPM database (BpmDb).

Table 5-1 — Blend Plan File - BpmDb Database Table Mapping

Blend Plan File Section Names

Corresponding BpmDb Tables Notes

GENERAL

INFORMATION

SECTION

BM_PENDING_PLANS

BM_BLND_INFO

General blend information including the Recipe ID

key (REC KEY) which is used to identify the blend prior to blend close.

COMPONENT

SECTION

BM_PENDING_PLAN_COMPS

BM_BLND_COMPONENTS

ADDITIVE

SECTION

BM_PENDING_PLAN_ADDITIVES

BM_BLND_ADDITIVES

PROPERTY

SECTION

BM_PENDING_PLAN_PRPRTY

BM_BLND_PROPERTIES

BLEND VALUES

SECTION

BM_PENDING_PLAN_COMP_PRPRTY

BM_BLND_COMPONENT_PROPERTIES

CUSTOM DATA BM_PLAN_ATTR If custom keywords are included in this section of the plan keyword file, the keywords and keyword values are stored in the BM_PLAN_ATTR table. This information is not used by BPM.

See Section 5.4 for details.

The blend target and actual files consist of a strictly defined set of records that correspond to specific sets

of tables in the BPM database (BpmDb).

Table 5-2 — Blend Target File - BpmDb Database Table Mapping

Blend Target File Records


<START BLEND

REC>

BM_PENDING_TARGETS

BM_BLND_INFO

General blend information including the Recipe ID

key (RECIPE) which is used to identify the blend prior to blend close.

Target files are identified by the BLEND_TYPE key

of TARGET.

<START BLEND

COMPONENT

REC>

BM_PENDING_TARGET_COMPS

BM_BLND_COMPONENTS

Components are identified by the RECORD_TYPE

key of COMP.

The <START BLEND COMPONENT REC> record

with a RECORD_TYPE key of HEEL is used to represent the blend destination at the start of the blend. The corresponding keyword values are stored in the component database tables. See Section 5.2.3 for details.

BM_PENDING_TARGET_ADDITIVES

BM_BLND_ADDITIVES

The <START BLEND COMPONENT REC> records

with a RECORD_TYPE key of ADDITIVE are used to represent additives.


Blend Target File Records


<START BLEND

PROPERTY

REC>

BM_PENDING_TARGET_PRPRTY

BM_BLND_PROPERTIES

<START BLEND

COMPONENT

PROPERTY

REC>

BM_PENDING_TARGET_COMP_PRPRTY

BM_BLND_COMPONENT_PROPERTIES

The <START BLEND COMPONENT PROPERTY

REC> records for the COMPONENT called HEEL are used to represent the heel property values in the blend destination at the start of the blend. The corresponding keyword values are stored in the component-property database tables. See Section 5.2.3 for details.

Table 5-3 — Blend Actual File - BpmDb Database Table Mapping

Blend Actual File Records


<START BLEND

REC>

BM_BLND_INFO General blend information including the Recipe ID

key (RECIPE) which is used to match the actual file with the blend plan and target data stored in the pending tables.

Actual files are identified by the BLEND_TYPE key

of ACTUAL.

<START BLEND

COMPONENT

REC>

BM_BLND_COMPONENTS Components are identified by the RECORD_TYPE

key of COMP.

BM_BLND_ADDITIVES The <START BLEND COMPONENT REC> records

with a RECORD_TYPE key of ADDITIVE are used to represent additives.

<START BLEND

PROPERTY

REC>

BM_BLND_PROPERTIES

Note: The blend actual files do not include <START BLEND COMPONENT PROPERTY REC> records. The blend values and heel property values are assumed to be the same as those in the blend target files.

Similarly, the pseudo component called "HEEL" is also not included in the actual files.

5.2.2 Standard vs. Extended Keywords

Each section or record in the keyword files contains a set of "keywords" and their current "values". BPM

recognizes a fixed list of these keywords that are referred to here as the "standard" keywords. When BPM reads a keyword file, it collects the data from the standard keywords and stores it in the appropriate

database tables.

See Appendix C.3 for the standard keyword mapping for blend target files. See Appendix D.3 for the standard keyword mapping for blend actual files.

Prior to BMA R410.1, any keywords that appeared in the keyword file sections, that were not part of the

standard keyword set, were ignored. The associated data was never collected and could not be displayed

in the BPM reports.

Starting in BMA R410.1, any keywords that appear in the keyword file sections that are not part of the

standard keyword set, are now collected and stored in a new set of "extended" BPM database tables. A

new version of each of the PENDING and BLND tables has been created with "_EXTENDED" added to


the table name. The new EXTENDED tables for the PLAN and TARGET PENDING tables, use the

RECIPE_ID to map the blend data to the blend. The new EXTENDED tables for the BLND tables, use the BLND_XREF_ID to map the blend data to the blend. Each EXTENDED table includes the

KEYWORD_NAME, KEYWORD_VALUE and TYPE (PLAN, TARGET or ACTUAL) for each

extended keyword that BPM finds.

5.2.3 BPM Changes for Heel Property Data Collection

Prior to BMA R410.1, heel property (or quality) data provided in the keyword files was ignored. This

happened for two reasons:

1. In the plan files, BPM used the list of components to map to the set of blend values in the BLEND

VALUES SECTION of the file. Since the heel property values appear after the blend values for each component in the blend values array, they were not being collected.

2. In the target and actual files, the <START BLEND COMPONENT REC> records that had a RECORD_TYPE of

HEEL were ignored. Similarly the <START BLEND COMPONENT PROPERTY REC> records for the

COMPONENT called HEEL were also being ignored.

Starting in BMA R410.1, a new component called "HEEL" is automatically added to the list blend components for blend plans. This pseudo component is associated with the heel property values at the end

of the blend values array in the plan file. Since these property values are part of the standard keywords,

the heel property values are now loaded into PENDING and BLND tables for the HEEL "component".

Similarly, the data that appears in the <START BLEND COMPONENT REC> and <START BLEND COMPONENT

PROPERTY REC> records for the HEEL "component" is now collected from the target and actual keyword

files. This data is also loaded into PENDING and BLND tables for the HEEL "component".

Note: The HEEL "component" is not included in the stored procedures for components. It is also filtered

out of the standard and custom reports supplied with BPM.

5.3 Adding the Extended Keyword Data to BPM Reports

5.3.1 BpmDb Stored Procedures

BPM is supplied with a set of stored procedures that can be used to collect the standard and extended

keyword values from the BLND and EXTENDED BLND tables. These stored procedures can be used to

populate custom BPM reports with either the standard or extended keyword values.

Table 5-4 — BpmDb Stored Procedures

BpmDb Stored Procedure Description

BF_NEXTVAL Gets the next available ID.

GetBmBlndAdditives Pivots the contents of the BM_BLND_ADDITIVES_EXTENDED table and adds it to the end of the BM_BLND_ADDITIVES table contents.

GetBmBlndAdditivesExtended Returns the pivoted contents of the BM_BLND_ADDITIVES_EXTENDED table only.

GetBmBlndComponentProperties Pivots the contents of the BM_PENDING_PLAN_COMP_PRPRTY_EXTENDED table and adds it to the end of the BM_PENDING_PLAN_COMP_PRPRTY table contents.

GetBmBlndComponentPropertiesExtended Returns the pivoted contents of the BM_PENDING_PLAN_COMP_PRPRTY_EXTENDED table only.


BpmDb Stored Procedure Description

GetBmBlndComponents Pivots the contents of the BM_BLND_COMPONENTS_EXTENDED table and adds it to the end of the BM_BLND_COMPONENTS table contents.

GetBmBlndComponentsExtended Returns the pivoted contents of the BM_BLND_COMPONENTS_EXTENDED table only.

GetBmBlndInfo Pivots the contents of the BM_BLND_INFO_EXTENDED table and adds it to the end of the BM_BLND_INFO table contents.

GetBmBlndInfoExtended Returns the pivoted contents of the BM_BLND_INFO_EXTENDED table only.

GetBmBlndProperties Pivots the contents of the BM_BLND_PROPERTIES_EXTENDED table and adds it to the end of the BM_BLND_PROPERTIES table contents.

GetBmBlndPropertiesExtended Returns the pivoted contents of the BM_BLND_PROPERTIES_EXTENDED table only.

GrantDbPermission Assigns table permissions.

spGetBlendAdditives Procedures used by the standard sample reports.

spGetBlendComponents Procedures used by the standard sample reports.

spGetBlendData Procedures used by the standard sample reports.

spGetBlendProperties Procedures used by the standard sample reports.

5.3.2 GetBmBlnd Stored Procedure Details

The "GetBmBlnd" stored procedures use the BLND_XREF_ID to link the standard and extended

keyword data from the same blend.

In the results from the "GetBmBlnd" stored procedures, the extended keywords are added after the

contents of the corresponding standard BLND table. Each extended keyword appears in a separate

column. To indicate where the extended keyword comes from, the keyword TYPE (PLAN, TARGET or ACTUAL) is added before the extended keyword name in the column header.

For example, the blend actual keyword files generated by PBO include an extended keyword called

ACTUAL_QTY in the <START BLEND COMPONENT REC> section of the file. When the "GetBmBlnd" stored

procedure for additives or components is run, the ACTUAL_QTY keyword value for each additive or component in the blend, appears in a column called "ACTUAL_ACTUAL_QTY". (See Figure 5-1 and

Figure 5-2 for an example.)

Each of the GetBmBlnd stored procedures can be filtered to show the extended keyword values for a

specific BPM blend data type or the results for an individual blend as follows:

exec GetBmBlndComponents '[data type]', '[BLND_XREF_ID]'

where:

[data type] Is the desired blend data type (plan, target, actual).

Note: This filter only applies to the extended keywords. For the stored procedures that show both the standard and extended keywords, the standard keyword values in the corresponding BLND table are always displayed.

[BLND_XREF_ID] Is the BLND_XREF_ID for the desired blend.


The following screen shots show the results from the GetBmBlndComponents stored procedure which has

been filtered to show the component blend data for the blend with the BLND_XREF_ID of 25 only. It has also been filtered to show the extended keyword values for the actual blend data only.

Figure 5-1 — Filtered GetBmBlndComponents Stored Procedure Results (Part 1)

Figure 5-2 — Filtered GetBmBlndComponents Stored Procedure Results (Part 2)


5.3.3 BPMBlendComponentsExtended Report

BPM is supplied with a sample custom report, called BPMBlendComponentsExtended, that displays a combination of standard and extended keyword values for the components of a given blend.

Figure 5-3 — BPMBlendComponentsExtended (Part 1)

Figure 5-4 — BPMBlendComponentsExtended (Part 2)


This report can be used as a guide for extracting extended keyword data from the "GetBmBlnd" stored

procedures for new custom reports.

ATTENTION:

This sample report will only work if the extended keywords included in the report exist in your plan, target and actual keyword files, and data from those keyword files has been collected in your BPM database.

5.4 Custom Data

5.4.1 Blend Plan File Custom Data

Each blend plan keyword file includes a section called CUSTOM DATA. If custom keywords are included in this section of the plan keyword file, they are transferred to the BM_PLAN_ATTR table. The keyword

name (ATTR), its VALUE and its attribute type (ATTR_TYP = REAL, BOOLEAN or CHARACTER) are stored along

with the corresponding Recipe ID for the blend.

Notes :

1. Keyword data collected from the CUSTOM DATA section is stored once in the BM_PLAN_ATTR table. It does not move from a PENDING table to a BLND table when the blend is closed. In addition, this

keyword data is not assigned a BLND_XREF_ID value when the blend is closed. As a result, it can only be tied the blend prior to blend close.

2. The Recipe ID and keyword name (ATTR) combination must be unique. If a new plan file is uploaded to BPM with the same recipe and keywords, the new keyword values will overwrite the existing ones.

3. The information stored in the BM_PLAN_ATTR table is not used by BPM.

4. Keywords that appear under CUSTOM RECORDS (NON-LCN) are ignored by BPM.

5.4.2 Blend Target and Actual File Custom Data

Profit Blend Controller, Profit Blend Optimizer and Profit Movement Management allow custom data can

be added to the end of the target and actual keyword files.

At this time custom records of this type are ignored by BPM.


6 CONFIGURE SQL SERVER BASED CUSTOM REPORTS

6.1 Using Report Manager

Report Manager is used to manage the SQL Server reporting services including:

Adding and removing reports

Setting report access security

Creating folder structures in the Report environment

Creating data sources

(Note: The BPM database is preconfigured as a data source by the BPM Server installation.)

Providing access to Report Builder

To access the Report Manager, open Internet Explorer on the BPM Server and type

http://localhost/Reports in the address bar.


ATTENTION:

1. If User Account Control (UAC) is enabled, run Internet Explorer as an administrator.

2. If enhanced security has been configured in Internet Explorer, the BPM Web Reports website must be added to the local trusted sites list. (In Internet Explorer open the Internet Options dialog by selecting the Tools > Internet Options menu item. In the Security tab, select the Trusted sites zone and click

the Sites button. Add the http://<ServerName>/HW.BM.WebReports URL to the websites list. If

the reports are being launched from the BPM Server, set the <ServerName> to localhost.)

A BPM Custom Reports folder is added to the home page of the Reporting Service automatically by the

BPM Server installation. This folder includes sample BPM reports and the shared BPM data source. The

shared BPM data source can be reused.

The shared BPM data source is set up with localhost and integrated Windows Security. These settings can

be changed if needed.

6.2 Create Custom Reports Using SQL Server Reporting Services

6.2.1 In Report Builder

Proceed as follows to create a custom report using Report Builder.

1. From the SQL Server Report Manager open Report Builder.

2. Create a new report.

3. Create a data source for the report, by browsing to the supplied shared data source and selecting it.

4. Create a data set. Use the dataset embedded in the report setting. Associate the data set to the data

source created in the previous step.

5. Drag and drop the data that you want to see into the report. Add titles, charts, labels, etc.

6. To customize your reports you can use stored procedures, database queries, etc. Use the supplied

sample reports as a guide.


7. If you want to include extended keyword data in the custom reports, see Section 5.3 for details.

8. Saving the report automatically publishes the report to the database server that you are currently connected to.

Be sure to review the Report Builder documentation available from Microsoft before you attempt to

create custom reports.


6.2.2 In Business Intelligence Development Studio or SQL Server Data Tools

ATTENTION:

1. If you are running SQL Server 2012, the supplied custom report project must be converted to SQL Server 2012 before you can use it to create custom reports. In SQL Server Data Tools open the

custom report project that is stored at \Program Files (x86)\Honeywell\AMM\BPM

\HW.BM.CustomReports\Samples\HW.BPM.CustomReports.rptproj and convert the project.

2. The screen shots shown below are from SQL Server 2008 Business Intelligence Development Studio. They will be different for SQL Server Data Tools in SQL Server 2012.

Proceed as follows to create custom reports using SQL Server's Business Intelligence Development

Studio (SQL Server 2008) or SQL Server Data Tools (SQL Server 2012).

1. In SQL Server's Business Intelligence Development Studio or SQL Server Data Tools, create a new

project or open the supplied custom report project (\Program Files (x86)\Honeywell

\AMM\BPM\HW.BM.CustomReports\Samples\HW.BPM.CustomReports.rptproj).

2. Create a new report or select one of the supplied sample reports as a starting point.

The sample reports are stored on the BPM Server at: \Program Files (x86)\Honeywell\AMM\BPM

\HW.BM.CustomReports\Samples.

3. Add the data source for the report.

4. If you are creating a new report from scratch, add the data set for the report.

Notes:

a) If you are using one of the sample reports, you do not need to add the data set because it is

already embedded in the report.

b) One data set is required for each report. A single shared data source can be used for all of the

reports in the project.

5. Specify the TargetReportFolder as BPM Custom Reports/<My Reports>, where <My Reports> is the name of your report folder.


6. Set up the report properties as needed. (See the screen shot below for an example.)


7. Customize the report as needed.

8. If you want to include extended keyword data in the custom reports, see Section 5.3 for details.

9. If desired you can add the supplied sample reports to your project.

6.2.3 Deploy the Reports

In Business Intelligence Development Studio or SQL Server Data Tools deploying the project deploys all

of the reports at once.

In Report Builder "publish" the reports to the report server. This will publish the current report to the

report server that you are currently connected to.

Be sure to publish or deploy the report to the \Program Files (x86)\Honeywell\AMM\BPM

\HW.BM.CustomReports\Samples folder on the BPM Server. When the end user launches the Custom Reports Explorer from the BPM Report Generator, the report will appear in the folder in which it was saved.

End User Access

By default members of the Product Administrators and Local Servers local groups have Content Manager access to the reports. Members of these local groups can create, manage and view reports.

Members of the Local Operators local group have Browser and My Reports access only. This means that

they can view reports.


7 PHD/LAB DATA INTERFACE

7.1 Overview

HW.BM.LabService

Characterization of finished products is measured in the laboratory and stored in a database, along with the time the material sample was taken. HW.BM.LabService is a Windows service that integrates this

data with the planning, target, and actual data from the blending operation.

The laboratory interface requires access to both the process historian database and to the BPM database. Be sure to review the network and firewall settings with the site's Network Administrator to ensure that

the HW.BM.LabService (which is installed on the BPM Server) has the necessary access privileges.

The Lab Service relies on OLEDB drivers that are provided with the historian software. If PI is selected

this driver is included with PI’s Data Access Package (DAP).

How it Works

The Lab Service exists to keep blended product property values (as recorded in

BM_BLEND_PROPERTIES) current with regard to available sample values from the lab. For this to work properly, the sampling time must be used as the timestamp associated with the sample value. Each

tank-property combination is associated with a unique historian tag name.

It is assumed that the plant personnel collects samples from the blend as it proceeds, and that these samples are then analyzed by the laboratory and that the property values are stored in PHD. BPM does

not respond directly to these operations in any way. BPM's Lab Service simply checks the identified PHD

tags for values when it runs.

Operations Performed on a Per-Tag Basis:

1. When the BPM Lab Service runs, BPM identifies all blending operations which began on or after the

BM_TAG_MAPPING.POSTED_DATE.

2. BPM catalogues the blending operations in BM_BLND_INFO. (The START time of each operation

is used in processing.)

3. BPM identifies all tag values (lab samples) which have timestamps on or after the

BM_TAG_MAPPING.POSTED_DATE.

4. BPM determines the time window for each blending operation as follows: The window begins with

that operation’s start time and ends with the start time of the next time-sequential blending operation

(whether new blend or reblend).

5. BPM identifies the most recent tag value within each blending operation time window as the tag of

interest.

Note: A Blend is considered by BPM to include the original blending operation and up to 4 reblend

operations associated with the original blend.

6. BPM populates the FINAL_LAB value for each Blend with the most recent tag value for the most

recent blending operation making up the Blend.

7. BPM records the timestamps for the tag values stored in BM_BLEND_PROPERTIES, in BM_BLEND_TAGTIMES.

8. BPM updates the POSTED_DATE with the earlier of

The most recent tag value timestamp associated with the BM_TAG_MAPPING record, or

The start time of the most recent blending operation (new blend or reblend)

The POSTED_DATE is used as the base date for queries to acquire historical lab data. It is a means of restricting the queries to data of possible interest.

The earlier of start time of the most recent blending operation or the most recent tag value timestamp is

used to ensure that all tag values for products in inventory are always considered, even if they come in out

of chronological order.

See Appendix E for additional details.

7.2 Lab Service Configuration

7.2.1 Update the Lab Service Configuration Settings

As part of the BPM Server installation, the HW.BM.LabService.exe.config file is installed to \Program

Files (x86)\Honeywell\AMM\BPM\HW.BM.LabService folder. This file is set up with the path to the HW.BM.Configuration.xml file, along with the frequency of service execution, as shown below.

Figure 7-1 — HW.BM.LabService.exe.config File Contents

<?xml version="1.0" encoding="utf-8" ?>

<configuration>

<appSettings>

<add key="BM_CONFIG_XML" value="BM_CONFIG_XML"/>

<add key="BM_LABSVC_FREQUENCY" value="5" />



<add key="ShowMessageBoxes" value="no"/>



<add key="TargetTag" value=""/>







<add key="MaxSamplesPerFetch" value=""/>



<add key="ConvertTagTimezone" value="true"/>



</appSettings>

<startup><supportedRuntime version="v2.0.50727"/></startup>

</configuration>

The settings in this file can be reconfigured as needed.

In particular, the lab service frequency (in minutes) is controlled by the BM_LABSVC_FREQUENCY setting.


7.2.2 Create Scheduled Tasks to Stop and Start the Honeywell BPM Lab Service

Create one scheduled task to stop and a second scheduled task to start the Honeywell BPM Lab Service on a weekly basis. This will ensure that the connections are re-established on a regular basis and to ensure

that they do not go ‘stale’. (Note: If you experience issues with the stability of the Lab Service, the

frequency of the stop and restart tasks can be increased.)

Create the Stop Honeywell BPM Lab Service

1. On the BPM Server, open the Task Scheduler applet that is available in the Control Panel under

Admin Tools.

2. In the Actions frame, select Create Task.

3. Enter a Name and Description in the General tab and update the configuration as shown below:

In the Security options, set the task to run as the local mngr user.


4. In the Triggers tab create a new Trigger and configure it so that the service will be stopped every

Sunday at 2:00 AM.


5. In the Actions tab create a New Action and configure it so that the HW.BM.LabService service will

be requested to stop using the service control command.


Create the Start Honeywell BPM Lab Service

1. On the BPM Server, open the Task Scheduler applet that is available in the Control Panel under

Admin Tools.

2. In the Actions frame, select Create Task.

3. Enter a Name and Description in the General tab and update the configuration as shown below:

In the Security options, set the task to run as the local mngr user.


4. In the Triggers tab create a new Trigger and configure it so that the service will be started every

Sunday at 2:05 AM.


5. In the Actions tab create a New Action and configure it so that the HW.BM.LabService service will

be requested to start using the service control command.

7.2.3 Start the Lab Service

The Lab Service is a Windows service. When it is installed, it is configured to start manually and is not

started by the installation. If the laboratory interface is going to be used, set up the Lab Service (BMLabSvc) to start automatically using the Windows Services applet.


APPENDIX A - BPM FILE PROCESSOR AND SERVICE SETTINGS

A.1 BPM Event Log

Purpose

All BPM messages are logged to a Windows Event Log called BPM_ErrorLog. This Event Log is created automatically by the BPM Server installation and must be present for the BPM components to run.

A.2 BPM Configuration File

Purpose

The BPM Configuration file (HW.BM.Configuration.xml) is used to update the BPM options, paths and credentials if needed. These settings are automatically filled in during the BPM Server installation.

File Location

The BPM configuration file is stored in the \Program Files (x86)\Honeywell\AMM\BPM folder on the BPM Server.

Format

Each entry in the file has this form:

<BMCONFIGURATOR>

<CODE>key</CODE>

<VALUE>value</VALUE>

</BMCONFIGURATOR>

A.2.1 BPM Configuration Codes

The following configuration codes are recognized.

Table A-1 — HW.BM.Configuration.xml Codes

CODE VALUE Purpose

Logging Controls

DEBUG_SWITCH ON or OFF Determines whether messages are entered into the BPM_ErrorLog node in the Windows Event Log system for access via Windows Event Viewer.

Note: This value should be set to OFF when the DEBUG_LEVEL is set to 3.

DEBUG_LEVEL Integer Determines which message types are output during processing:

1: Errors only

2: Errors and warnings

3: Errors, warnings, and trace messages

Note: In production systems be sure to set the DEBUG_LEVEL to 1 or 2. Level 3 is very verbose.


CODE VALUE Purpose

BM_LOG_ROOT Writable folder path Specifies the location of the application log file.

LOG_TO_FILE ON or OFF Controls whether messages are written to a file in BM_LOG_ROOT.

Plan, Target and Actual Processor

PLAN_FILE_LOCATION Writable folder path Input folder for Plan files

PLAN_PASS_LOCATION Writable folder path Plan files are relocated here following processing success

PLAN_FAIL_LOCATION Writable folder path Plan files are relocated here following processing failure

PLAN_FILE_FILTER Wildcard pattern Files matching this pattern are considered Plan input files when found in PLAN_FILE_LOCATION

The default value for this setting is "*.BPC".

TARGET_FILE_LOCATION Writable folder path Input folder for Target files

TARGET_PASS_LOCATION Writable folder path Target files are relocated here following processing success

TARGET_FAIL_LOCATION Writable folder path Target files are relocated here following processing failure

TARGET_FILE_FILTER Wildcard pattern Files matching this pattern are considered Target input files when found in TARGET_FILE_LOCATION

The default value for this setting is "*_TAR_*.LST".

ACTUAL_FILE_LOCATION Writable folder path Input folder for Actual files

ACTUAL_PASS_LOCATION Writable folder path Actual files are relocated here following processing success

ACTUAL_FAIL_LOCATION Writable folder path Actual files are relocated here following processing failure

ACTUAL_FILE_FILTER Wildcard pattern Files matching this pattern are considered Actual input files when found in ACTUAL_FILE_LOCATION

The default value for this setting is "*_ACT_*.LST".

Database Connections

BM_DB_TYPE SQLSERVER BPM database type code.

Note: Only SQL Server (SQLSERVER) is supported.

BM_DB_CONNECTSTRING Connection string BPM database connection string

For SQL Server, the user ID, password, Data Source, and initial catalog are set. For example:

<VALUE>Provider=SQLOLEDB.1;Integrated

Security=SSPI;Persist Security

Info=False;Initial Catalog=BpmDb;Data

Source=BPMDatabaseNodeName</VALUE>

Where BPMDatabaseNodeName is the name of the computer where the BPM database is stored.

BM_OPC_TYPE PHD, PI or IP21 Historian type.

Note: BPM has not been tested with the IP21 historian.


CODE VALUE Purpose

BM_OPC_CONNECTSTRING Connection string Historian connection string

For PHD set the value to:

<VALUE>Provider=UnfOPCProv.1;Persist

Security Info=False;Data

Source=OPC.PHDServerHDA.1;Location=myPhd

Node;Extended Properties=""</VALUE>

Where myPhdNode is the name of the PHD Server.

For PI set the value to:

<VALUE>Provider=PIOLEDB.1;Password="";Da

ta Source=myOpcNode;Persist Security

Info=True</VALUE>

Where myOpcNode is the name of the PI Server.

A.3 Plan, Target and Actual File Processor Settings

Plan, Target and Actual files are text files with a defined structure. The Plan, or recipe, files must be supplied in the BPC input format. The Target files and Actual files must be supplied in the LST output

format. (See Appendix B, C and D for details.)

Processing of the Plan, Target and Actual files is managed by two distinct subprocesses.

HW.BM.ConsoleApp prepares XML from the input files and passes it to HW.BM.WebService, which applies business rules and writes to the BPM database.

A.3.1 Plan, Target and Actual File Folder Structure

The BPM Server installation creates the folder structure under “BPM” as shown below. All files are to be placed in the “BPM” folder for processing. Once processed, the file is relocated into one of two

subfolders under the “Plan”, “Target” or “Actual” folders. Within each of these three folders, the “OK”

folder is used to place files which processed successfully, and the “Error” folder is used to place files which failed to process.

The location for these folders is automatically assigned in the BPM Configuration file

(HW.BM.Configuration.xml described in Table A-1) as part of the BPM Server installation.


Figure A-1 — Processing Folders

A.3.2 Console Application and Web Service Configuration Settings

The HW.BM.ConsoleApp\HW.BM.ConsoleApp.exe.config and HW.BM.WebService\Web.config files are automatically configured to reference the HW.BM.Configuration.xml file. This is accomplished in the

same way in both files:

<appSettings>

<add key=”BM_CONFIG_XML” value=

”C:\Program Files (x86)\Honeywell\AMM\BPM\HW.BM.Configuration.xml” />

<!—for HW.BM.ConsoleApp.exe.config only

<add key="HW.BM.ConsoleApp.localhost.BMWebService" value=

"http://localhost/HW.BM.WebService/BMWebService.asmx"/>

</appSettings>

The value for the key "HW.BM.ConsoleApp.localhost.BMWebService" is specific to

HW.BM.ConsoleApp.exe.config and contains the URL to HW.BM.WebService’s BMWebService.asmx file. Do not change this setting. (The BPM Console Application and Web Service are expected to be

installed on the same computer.)

There may be other <add> elements in the appSettings section, but only those shown above are of interest to BPM.


A.3.3 BPM Schedule Service

Automatic processing of Plan, Target and Actual files is controlled by the BPM Schedule Service. By default, this service launches the HW.BM.ConsoleApp every 5 minutes (300 seconds).3

If desired, the time interval (in seconds) can be reconfigured in the

HW.BM.ScheduleService.exe.config file, that is stored on the BPM Server at: \Program Files

(x86)\Honeywell\AMM\BPM\HW.BM.ScheduleService, as shown below.

<configuration>

<configSections>

<section name="Processes" type="CustomConfigSections.ProcessesSection" />

</configSections>

<Processes>

<Process Name="HW.BM.ConsoleApp" Params="Z"

path="%HWINSTALLPATH%\AMM\BPM\HW.BM.ConsoleApp" Interval="300" Enable="1"/>

</Processes>

<appSettings>

<add key="BM_CONFIG_XML" value="C:\Program Files

(x86)\Honeywell\\AMM\BPM\HW.BM.Configuration.xml"/>

</appSettings>

</configuration>

Restart the HW.BM.ConsoleApp service after you change this setting.

3 The Windows Task Scheduler is no longer used to schedule HW.BM.ConsoleApp operation.


APPENDIX B - BPM PLAN PROCESSOR

B.1 Overview

The BPM Plan Processor processes Plan files that show up in its configured Plan Input folder. After

passing validation checks the plan data is written to plan pending tables. The BPM Actual Processor (described in Appendix D) correlates the correct pending plan data and copies this data to the final tables

in the database.

File Format

Plan files are text files with a defined structure. The Plan, or recipe, files must be supplied in the BPC

input format.

A Plan file name matching pattern is configured in the HW.BM.Configuration.xml file. Typically, the

Plan function is configured with the pattern "*.BPC" to match all files in its Input folder having the .BPC extension. (See Table A-1 for this configuration.)

An example Plan file is shown in Figure B-1. The database tables affected by the service are described in

Appendix F.

Sample Plan File

A sample Plan file called RecipePlan.bpc is installed in the \Program Files (x86)\Honeywell\AMM\BPM

\Configuration folder on the BPM Server. This file can be used to manually emulate a blend plan from a planning tool (e.g. BLEND) and to verify that BPM file processing is working correctly. By default, the

sample file is configured to match the preconfigured PBM database (AmmDb).

This file should be copied to the applicable folders under \ProgramData\Honeywell\BMA\Database

\AMM\BPM\Plan for site-specific editing and subsequent file processing tests.

B.2 Processing Details

As Plan files appear in the Input folder they are processed as follows:

1. Each planned event is checked to determine if the data merits error or warning messages. If there are

errors the file is moved to the \Error folder and the database is not updated. If there are warnings the warning messages are posted and the database is updated. For example: A property that does not exist

in the properties table is an error, but a product tank that does not exist in the tanks table will merit a

warning.

a. Validate each component name against IP_PRDCT table. If the component name does not exist

then do not write the plan to the pending plan tables. Issue an error message and move the Plan

file to the \Error subfolder.

b. Validate each property name against IP_PRPRTY table. If the property name does not exist then do not write the plan to the pending plan tables. Issue an error message and move the Plan file to

the \Error subfolder.

c. Validate each product name against IP_PRDCT table. If the product name does not exist then

write the plan to the pending plan tables, issue a warning message and move the Plan file to the

\OK subfolder.


d. Validate each product tank name against IP_EQ table. If the product tank name does not exist

then write the plan to the pending plan tables, issue a warning message and move the Plan file to

the \OK folder.

2. If the plan is for a reblend then only the key header information is written to the pending plan tables.

If the plan is not a reblend then the details of the recipe, the properties and the blend values are

written to the pending plan tables.

3. If the pending tables already have a plan stored for a given recipe ID and a new plan is submitted for this recipe, the new plan will overwrite the old plan.

Figure B-1 — Plan File Example

*

*GENERAL INFORMATION SECTION

*

*Product/Period: 00G23

*

*START_DATE_TIME, 2006-03-02 13:56:12

*END_DATE_TIME, 2006-08-20 21:07:12

*RE-BLEND, NO

*PRODUCT_PRICE, 75.25

*

*RFG87 A5 (PL)

*

BLDR ID,GASOLINE

REC KEY, ADD

REC ID, 00G23

REC DES, RFG87 A5 (PL)

B CLASS, RFG_V

DEST TNK, T707

TPC, ON

SPARE01, OFF

SPARE02, OFF

VOL TARGET, 25000

FLW TARGET, 5000

VOL HEEL, 115700

*

*COMPONENT SECTION

*


*

* TANKID TGTPCT LO_PCT HI_PCT LO_VOL HI_VOL COST

BUTANE ,T516 , 10.00, 0.00, 20.00, 0, 99999, 0.000

MTBE ,T155 , 9.00, 0.00, 19.00, 0, 99999, 0.000

LT_ISO ,T501 , 3.50, 0.00, 13.50, 0, 99999, 0.000

LT_FCC ,T133 , 0.00, 0.00, 0.00, 0, 99999, 0.000

REFORMAT,T172 , 15.00, 5.00, 25.00, 0, 99999, 0.000

BASE_1 ,T159 , 35.23, 25.23, 45.23, 0, 99999, 0.000

ALKYLATE,T151 , 10.27, 0.27, 20.27, 0, 99999, 0.000

LO_OCT ,T156 , 15.00, 5.00, 25.00, 0, 99999, 0.000

LT_COMP ,T113 , 2.00, 0.00, 12.00, 0, 99999, 0.000

*

*ADDITIVE SECTION

*


*

* TANKID CONCENT

T-249 ,TK1 , 0.0000

DGS-104 ,TK2 , 6.0000

RED_DYE ,TK3 , 0.0000

ORNG_DYE,TK4 , 0.0000

T-511 ,TK5 , 6.0000


*

*PROPERTY SECTION

*


*

* SPEC LOLIMIT HILIMIT COST PROTO

RON , 91.729, 81.000, 100.000, 10.000, 91.729

MON , 82.272, 82.000, 95.000, 10.000, 82.272

(R+M)/2 , 87.000, 87.000, 95.000, 10.000, 87.000

RVP , 14.576, 6.400, 7.000, 10.000, 14.576

BENZENE , 0.516, 0.000, 1.300, 5.000, 0.516

AROMATIC, 28.681, 0.000, 100.000, 5.000, 28.681

OLEFINS , 8.962, 0.000, 100.000, 5.000, 8.962

OXYGEN , 1.945, 1.700, 2.500, 5.000, 1.945

SULFUR , 45.094, 0.000, 100.000, 5.000, 45.094

V/L , 108.753, 0.000, 250.000, 5.000, 108.753

IBP , 82.937, 80.000, 150.000, 5.000, 82.937

10%_PT , 96.002, 95.000, 122.000, 5.000, 96.002

50%_PT , 189.600, 170.000, 230.000, 5.000, 189.600

90%_PT , 320.764, 100.000, 365.000, 5.000, 320.764

FBP , 418.723, 100.000, 430.000, 5.000, 418.723

EVAP200 , 42.046, 0.000, 100.000, 5.000, 42.046

EVAP_300, 79.903, 0.000, 100.000, 5.000, 79.903

DI , 1033.565, 0.000, 2000.000, 5.000, 1033.565

VOC , -1.018, -100.000, 100.000, 5.000, -1.018

NOX , 12.327, 6.800, 100.000, 5.000, 12.327

TOXIC , 23.151, 21.500, 100.000, 5.000, 23.151

G_API , 60.945, 50.000, 80.000, 5.000, 60.945

SG , 0.737, 0.000, 1.000, 5.000, 0.737

MTBE% , 1.945, 0.000, 20.000, 5.000, 1.945

ETBE% , 0.000, 0.000, 10.000, 5.000, 0.000

*

*BLEND VALUES SECTION

*


*

* BUTANE LT_ISO REFORMAT ALKYLATE LT_COMPHeel Quality

* MTBE LT_FCC BASE_1 LO_OCT

RON , 93.387,118.000, 82.800, 90.900,105.100, 83.596, 92.986, 75.000, 80.000, 92.000

MON , 86.264,100.000, 79.800, 79.300, 95.000, 77.243, 86.038, 75.000, 78.000, 82.000

(R+M)/2 , 89.825,109.000, 81.300, 85.100,100.050, 80.420, 89.512, 75.000, 79.000, 87.000

RVP , 50.000, 8.500, 12.000, 8.800, 0.700, 9.127, 7.750, 4.700, 22.000, 15.000

BENZENE , 0.000, 0.000, 0.000, 0.400, 0.400, 0.728, 0.165, 1.300, 3.000, 0.500

AROMATIC, 0.400, 0.000, 0.900, 5.000, 84.400, 17.509, 2.323, 22.900, 0.000, 30.000

OLEFINS , 0.000, 0.000, 0.000, 20.000, 0.000, 8.584, 8.264, 1.900, 0.000, 10.000

OXYGEN , 0.000, 18.200, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 2.000

SULFUR , 0.000, 0.000, 0.000, 30.000, 0.310,119.301, 12.804, 10.000, 0.000, 45.000

V/L ,-176.753,120.920,103.161,131.748,198.855,144.891,143.559,156.505, 45.859,107.009

IBP ,-181.000,139.000, 89.000, 91.000,229.000, 94.338, 89.388,142.000, 47.000, 80.000

10%_PT ,-128.000,128.000,108.000,124.000,259.000,128.547,137.289,144.000, 72.000, 90.000

50%_PT , 84.000,128.000,122.000,167.000,219.000,231.955,192.190,181.000,105.000,190.000

90%_PT ,316.000,264.000,157.000,256.000,357.000,267.227,259.488,266.000,146.000,330.000

FBP ,365.000,365.000,204.000,347.000,435.000,364.372,365.669,365.000,206.000,430.000

EVAP200 ,100.000, 80.000, 99.000, 68.600, 0.000, 46.266, 36.520, 60.000, 90.000, 40.000

EVAP_300,100.000,100.000,100.000, 98.100, 63.800, 69.668, 64.184, 95.000,100.000, 80.000

DI ,376.000,840.000,685.000,943.000,1402.500,1155.914,1041.992,1025.000,569.000,1035.000

VOC , -1.018, -1.018, -1.018, -1.018, -1.018, -1.018, -1.018, -1.018, -1.018, -1.018

NOX , 12.327, 12.327, 12.327, 12.327, 12.327, 12.327, 12.327, 12.327, 12.327, 12.327

TOXIC , 23.151, 23.151, 23.151, 23.151, 23.151, 23.151, 23.151, 23.151, 23.151, 23.151

G_API ,110.600, 57.700, 82.800, 67.800, 33.800, 60.268, 70.273, 73.000, 85.000, 60.000

SG , 0.585, 0.748, 0.660, 0.710, 0.856, 0.740, 0.701, 0.692, 0.654, 0.739

MTBE% , 0.000, 18.200, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 2.000

ETBE% , 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000


*

*CUSTOM DATA - REALS Entries: 0

*

*

*CUSTOM DATA - BOOLEAN

*

*

*CUSTOM DATA - CHARACTER

*

REGION: REGION1/REGION2 ,REGION1

SEASON: WINTER/SUMMER ,

*

*CUSTOM RECORDS (NON-LCN)

*END OF CUSTOM RECORDS

*

*END OF RECIPE


APPENDIX C - BPM TARGET PROCESSOR

C.1 Overview

The BPM Target Processor processes the Target files that appear in its configured Target Input folder.

These files represent the starting conditions in the blend control system for the blend event. After passing validation checks the target data is written to target pending tables to await processing of the actual blend

event data. The BPM Actual Processor (described in Appendix D) correlates pending target data and

copies it to the final tables in the database.

File Format

Target files are text files with a defined structure. These files must be supplied in the LST output format.

A Target file name matching pattern is configured in the HW.BM.Configuration.xml file. Typically, the

Target function is configured with the pattern "*_TAR_*.LST" to match all target files in its Input folder. (See Table A-1 for this configuration.)

C.2 Processing Details

The BPM Target Processor processing details are identical to those documented for the BPM Plan

Processor (in Appendix B) with the following exception:

Target files, like Plan files, include blend values. Some installations may not collect plan data thus blend

values would not be posted. To ensure that the blend values are captured, the pending blend values table

is updated with the blend values contained in the Target file.

Blend Performance Monitor 87

C.3 BPM Keyword Mapping for the Target File

The following table lists the final destination database table storage location, after the corresponding Actual file is processed, for the keyword

entries in the Target file. The temporary database tables (i.e. BM_PENDING_xxxx) are not included here. The column labeled “Shown in” indicates the location in the Blend Analysis Report or the Blend Values Report where the data is displayed. Other reports may show the same

data, but these are not listed here.

For Entries within <START BLEND REC> and <END BLEND REC>:

From Target File Value of Keyword BPM Database Table/Column Shown in Blend Analysis Report

Notes

BLEND_NO Numeric BM_BLND_INFO/BLND_NO Header, Blend No. If coming from PBO, this is the “blend number” used by PBO for the blend.

BLEND_TYPE TARGET The value is not directly stored in the database.

BLEND_TANK String Value is NOT shown. A string value Indicating the destination of the blend (tank id or pipeline id).

REBLEND_IND 1 or 0 Value is NOT shown. A value of 1 indicates this is for a reblend, 0 indicates this is a new blend. Reblend handling is not currently supported.

TARGET_RUN_DATE_TIME Date/time string. BM_BLND_INFO/TGT_DT_TIM

Blend Data, Date and Time, Target column and Header, Start

If coming from PBO, this is the actual start time of the blend detected by PBO.

BLENDER_NAME String Blender name must match value in the Actual file

PRODUCT String BM_BLND_INFO/TGT_PRDCT_NAME Value is NOT shown.

RECIPE String Recipe ID//blend order name must match value in the Actual file

HEADER_TARGET_QTY Numeric BM_BLND_INFO/TGT_HDR_QTY Blend Data, Header Vol, Target column

The value is the target volume for the blend (excludes heel).

HEEL_QTY Numeric BM_BLND_INFO/TGT_HEEL_QTY Blend Data, Heel Vol, Target column

The value is the heel volume of the destination.


For Entries within <START BLEND COMPONENT REC> and <END BLEND COMPONENT REC>:


Notes

COMPONENT String Component name must match value in the Actual file

COMPONENT_TANK String Value is NOT shown.

TARGET_QTY Numeric BM_BLND_COMPONENTS/TGT_AIM for components

Formulation, Target column The starting recipe.

RECORD_TYPE COMP or ADDITIVE The value is not directly stored in the database. Indicates if entries are for components or additives.

MIN_QTY Numeric BM_BLND_COMPONENTS/TGT_MIN Formulation, Lo Limit Component limit changes during a blend are not recorded.

MAX_QTY Numeric BM_BLND_COMPONENTS/TGT_MAX Formulation, Hi Limit Component limit changes during a blend are not recorded.

COMPONENT_UNITS String Entries are ignored. Keyword is not required in Target file.

For Entries within <START BLEND PROPERTY REC> and <END BLEND PROPERTY REC>:


Notes

PROPERTY String Property name must match value in the Actual file.

PROPERTY_UNITS Entries are ignored. Keyword is not required in Target file.

PROPERTY_MIN Numeric BM_BLEND_PROPERTIES/TGT_MIN Property Section, Lo Limit column

If keyword is NOT in Actual file, the values from Target file are stored and displayed.

PROPERTY_MAX Numeric BM_BLEND_PROPERTIES/TGT_MAX Property Section, Hi Limit column

If keyword is NOT in Actual file, the values from Target file are stored and displayed.



Notes

PROPERTY_RESULT Numeric BM_BLEND_PROPERTIES/TGT_AIM Property Section, Target

RECORD_TYPE Entries are ignored. Keyword is not required in Target file.

For Entries within <START BLEND COMPONENT PROPERTY REC> and <END BLEND COMPONENT PROPERTY REC>:

From Target File Value of Keyword BPM Database Table/Column Shown in Blend Values Report

Notes

COMPONENT String BM_BLEND_COMPONENT_PROPERTIES/COMP_NAME

In the header for the blend values shown in the right hand side of report.

PROPERTY String BM_BLEND_COMPONENT_PROPERTIES/PRPRTY_NAME

In the header for the blend values shown in the right hand side of report.

PROPERTY_UNITS String Entries are ignored. Keyword is not required in Target file.

BLEND_VALUE Numeric BM_BLEND_COMPONENT_PROPERTIES/EOB_VALUE

In the right hand side of report Blend Value changes during a blend are not recorded by BPM.

RECORD_TYPE Entries are ignored. Keyword is not required in Target file.


APPENDIX D - BPM ACTUAL PROCESSOR

D.1 Overview

Once an Actual file for a blend event is posted to the database, the BPM Actual Processor correlates the

associated pending Plan and Target file data with the actual data. This function also applies the reblend rules and posts the reblend data accordingly.

The Actual file contains the results of the blend event and is similar in format to the Target file, except

that it does not include component blend values.

File Format

Actual files are text files with a defined structure. These files must be supplied in the LST output format.

An Actual file name matching pattern is configured in the HW.BM.Configuration.xml file. Typically, the

Actual function is configured with the pattern "_ACT_*.LST" to match all Actual files in its Input folder. (See Table A-1 for this configuration.)

D.2 Processing Details

As Actual files appear in the Input folder they are processed as follows:

1. If the file fails validation, error messages are written to the log file and the file is moved to the Errors folder.

2. The following sequence of checks are used to determine if the Actual file is associated with a reblend

event:

a. Locate the Pending Plan file matching the recipe ID and determine if the reblend flag is set to yes. If this is reblend go to Step 3.

b. Locate the last Actual blend event in BM_BLND_INFO table for the product tank represented by

the Actual file and apply the reblend rule as follows:

i. Read the reblend rule table for the "last_blend_days" and "heel_volume" parameters.

ii. Calculate the Reblend Window Date (RWD) as the end of blend date for the last Actual blend

event plus "last_blend_days".

iii. Calculate the Last Blended Volume (LBV) as the sum of heel plus header volume for the last

Actual blend event.

iv. If new event start of blend date is before the RWD and the new blend event heel volume is

greater than LBV "heel_volume" then the new event is a reblend.

v. If new event is a reblend go to Step 3, otherwise go to Step 4.

3. If the Actual file is a reblend:

a. Post the reblend details to the appropriate existing blend header table.

b. Remove the pending target records for this recipe ID.


4. If the Actual file is not a reblend:

a. Search the BM_BLND_INFO table to see if the recipe ID already exists. If the recipe ID already exists then this is an error, otherwise go to Step 4.b.

b. Post the new blend event details to the header table and associated recipe, properties and additive

tables.

c. Post the associated pending plan and target records for the recipe ID.

d. Remove the pending target records for this recipe ID.


D.3 BPM Keyword Mapping

The following table lists the final destination database table storage location, after an Actual file is processed, for the keyword entries in the Actual

file. The column labeled “Shown in Blend Analysis Report” indicates the location in the Blend Analysis Report where the data is displayed. Other reports may show the same data, but these are not listed here.

Note that Blend Value records are not processed from the Actual file. Any blend value entries in the Actual file will be ignored.

For Entries within <START BLEND REC> and <END BLEND REC>:

From Actual File Value of Keyword BPM Database Table/Column Shown in Blend Analysis Report

Notes

BLEND_NO Numeric BM_BLND_INFO/BLND_NO Header, Blend No. If coming from PBO, this is the “blend number” used by PBO for the blend.

BLEND_TYPE ACTUAL The value is not directly stored in the database.

BLEND_TANK String BM_BLND_INFO/ACTUAL_TANK Header, Tank A string value Indicating the destination of the blend (tank id or pipeline id).

REBLEND_IND 1 or 0 Value is NOT shown. A value of 1 indicates this is for a reblend, 0 indicates this is a new blend. Reblend handling is not currently supported.

START_DATE_TIME Date/time string. BM_BLND_INFO/EOB_START_DT_TM Header, Start Actual blend start time

END_DATE_TIME Date/time string. BM_BLND_INFO/EOB_END_DT_TM Header, End and Blend Data, Date and Time, Actual column

Actual blend end time

BLENDER_NAME String BM_BLND_INFO/BLNDR_NAME Header, Blender Blender name

PRODUCT String BM_BLND_INFO/EOB_PRDCT_NAME Header, Product

RECIPE String BM_BLND_INFO/RECIPE_ID Header, Recipe ID Recipe/blend order name

HEADER_TARGET_QTY Numeric BM_BLND_INFO/EOB_HDR_QTY Blend Data, Header Vol, Actual column

HEEL_QTY Numeric BM_BLND_INFO/EOB_HEEL_QTY Blend Data, Heel Vol, Actual column


For Entries within <START BLEND COMPONENT REC> and <END BLEND COMPONENT REC>:


Notes

COMPONENT String BM_BLND_COMPONENTS/COMP_NAME

Formulation, Component column

Component name.

COMPONENT_TANK String BM_BLND_COMPONENTS/COMP_EQ_NAME for components

BM_BLND_ADDITIVES/COMP_EQ_NAME for additives

Formulation, Tank

Additive, Tank

Tank swings during a blend are not recorded. Only the final tank is shown.

COMPONENT_QTY Numeric BM_BLND_COMPONENTS/EOB_QTY for components

BM_BLND_ADDITIVIESS/EOB_QTY for additives

Formulation, Header Volume for components

Additives, Quantity for additives

Component and additive volumes in blend.

RECORD_TYPE COMP or ADDITIVE The value is not directly stored in the database. Indicates if entries are for components or additives.

MIN_QTY Numeric Entries are ignored. Keyword is not required in Actual file.

MAX_QTY Numeric Entries are ignored. Keyword is not required in Actual file.

COMPONENT_UNITS String BM_BLND_COMPONENTS/QTY_UNITS for components

BM_BLND_ADDITIVES/QTY_UNITS volume units for additives

Not shown for components.

Volume units for additives.

For Entries within <START BLEND PROPERTY REC> and <END BLEND PROPERTY REC>:


Notes

PROPERTY String BM_BLEND_PROPERTIES/PRPRTY_NAME

Property name must match value in the Actual file.



Notes

PROPERTY_UNITS String BM_BLEND_PROPERTIES/UNITS Property section, Units If no entries exist in the Actual file, corresponding values are retrieved from IP_PRPRTY table.

PROPERTY_MIN Numeric BM_BLEND_PROPERTIES/TGT_MIN Property Section, Lo Limit column

If keyword is in Actual file, values from target file are not retained.

PROPERTY_MAX Numeric BM_BLEND_PROPERTIES/TGT_MAX Property Section, Hi Limit column

If keyword is in Actual file, values from target file are not retained.

PREDICTED_TANK_RESULT Numeric BM_BLEND_PROPERTIES/EOB_TANK_PRDCTD

Property Section, Analyzer column

If coming from PBO, this is the calculated average for the blend destination.

RECORD_TYPE Entries are ignored. Keyword is not required in Actual file.

HEEL_RESULT Numeric BM_BLEND_PROPERTIES/EOB_HEEL Property Section, Heel column

PREDICTED_HEADER_RESULT

Numeric BM_BLEND_PROPERTIES/EOB_HDR_PRDCTD

Value is NOT shown.


APPENDIX E - BPM LAB DATA SERVICE

E.1 Overview

The BPM Lab Data Service relies on the lab data for blend tanks and blend properties being posted to

either of two process historians (PHD or PI). BPM maintains a mapping table of the historian tags with the key being the tank ID and the property ID. Each time the service is run it fetches the most current

values for each tag and posts them to the correct end of blend events. Once the lab data for a tag is posted

successfully the appropriate date is written to the mapping table as the "Posted Date".

E.2 Processing Details

The layout of the Tag Mapping table is as follows:

tank_name prprty_name tag_name Posted_date conv_factor lab_tank_name lab_prprty_name

Only the first four fields are used for the service. The others are reserved for future use.

In the following discussion, assume the tag mapping table has the following entries:

tank_name property_name tag_name posted_date

E701 RON E701_RON 11/11/06 3:00

E701 MON E701_MON 11/13/06 15:00

E701 RVP E701_RVP 11/13/06 9:00

E701 T10 E701_T1O 11/14/06 15:35

When the service runs it processes this table one tag record at a time. For each record, it fetches the current tag value for the historian tag and all previous values for the tag, back to and including all tag

values dated at or after the "Posted Date". For example if the service next runs on 11/19/06 at 17:00

hours, it might fetch the following values for tag E701_RON above:

phd_date RON

11/18/06 16:00 96.2

11/15/06 13:00 96.8

11/15/06 4:00 95.3

11/11/06 3:00 95.9

The historian values above indicate that there were three more lab readings recorded since the service last

run and these need to be posted to the correct blend event tables in BPM. The reading on 11/11/06 at

3AM is re-posted as well (just in case this reading was based on a second test of the sample and a new value entered in the historian for this date).


Now the service posts these values by processing the BPM table of actual blend events for tank E701 in

descending order by end date of the blend event. For example assume the last series of blend events for tank E701 looked like this:

blend_end_date tank_name type_blend

11/18/06 9:00 E701 Initial

11/15/06 8:00 E701 Reblend

11/14/06 22:00 E701 Initial

11/10/06 19:00 E701 Initial

Working through the table above from the last recorded blend event back, the historian lab values for

RON would get posted as follows:

blend_end_date tank_name type_blend phd_date RON

11/18/06 9:00 E701 Initial 11/18/06 16:00 96.2

11/15/06 8:00 E701 Reblend 11/15/06 13:00 96.8

11/14/06 22:00 E701 Initial 11/15/06 4:00 95.3

11/10/06 19:00 E701 Initial 11/11/06 3:00 95.9

Effectively the service when run always starts by fetching the last historian recorded lab value and this

value is posted to the blend event just before the historian recorded date for this value. After posting all

the historian values for RON, the Posting Date in the mapping table is updated. The "Posted Date" is the earliest date between the date of the first historian record fetched for RON (in this example 11/18/2006

16:00) or the last actual blend date (in this example 11/18/06 9:00).

A Special Case

There is a remote possibility that the service to post Actual blend event data might be suspended either

intentionally or accidentally for some time while the Lab posting service continues. The service would

post the most recent lab result to the last blend event in the database (likely not the correct lab result). Once the Actual blend event service is started up and the blend event database is brought up to date, the

Lab service will automatically correct the problem posting the correct lab values.


APPENDIX F - BPM DATABASE

F.1 BPM Database Tables

The following table lists the database tables in the BPM database instance (BpmDb) in SQL Server.

Table Name Description

Data Tables

BM_BLND_INFO Contains the blend header information for each blend event

BM_BLND_COMPONENTS Contains component recipe data for each blend event

BM_BLND_PROPERTIES Contains property data (analyzer and lab) for each blend event

BM_BLND_ADDITIVES Contains additive information if additives are used in blend control

BM_BLND_COMPONENT_PROPERTIES Contains component blend values for a blend event

BM_PENDING_PLANS Contains pending blend plan header data

BM_PENDING_PLAN_COMPS Contains pending plan component recipe data

BM_PENDING_PLAN_PRPRTY Contains pending plan property data

BM_PENDING_PLAN_ADDITIVES Contains pending plan additive data

BM_PENDING_PLAN_COMP_PRPRTY Contains pending plan blend values

BM_PENDING_TARGETS Contains target blend header data

BM_PENDING_TARGET_COMPS Contains target component recipe data

BM_PENDING_TARGET_PRPRTY Contains target property data

BM_PENDING_TARGET_ADDITIVES Contains target additive data

BM_PENDING_TARGET_COMP_PRPRTY Contains target blend values

BM_*_EXTENDED Contains the extended keywords and keyword values for the corresponding database table. (See Section 5.2 for details.)

Configuration Tables

IP_PRDCT Contains product configuration data

IP_PRDCT_ATTR Identifies units of measure and other attributes

IP_PRDCT_PRICE Contains product and component price data

IP_EQ Contains tank configuration data

IP_EQ_ATTR Contains tank attributes

IP_PRPRTY Contains property configuration data

IP_TAG Contains historian tags for tank property values

BM_GIVEAWAY Identifies properties set for Giveaway reporting

BM_PRODUCT_PERIOD Defines period during the year when specs are active

BM_PRODUCT_SPEC Links products to a spec period for one or more property spec details

BM_PRODUCT_SPEC_DETAIL Defines min/max property specs for a product-period entry

BM_REBLEND_RULE Contains parameters for identifying a reblend event


Table Name Description

BM_TAG_MAPPING Contains list of tags as source of Lab data

BM_STD_REPORT Contains list of standard reports available via the Web

BM_USR_REPORT Contains list of custom reports available through BPM Report Generator.

Note: This table must not contain links to the SQL Server based custom reports.

ATTENTION:

This is not a complete list of tables used by BPM but rather provides a broad overview of the purpose of key tables.

Database Notes

1. The Header record for a blend is created when Actual results are successfully processed.

2. Plan and Target results are held in pending tables until Actual results are posted and the header record

is created.

3. Lab data gets posted to correct blend events through the Lab Data Service processing logic.

4. Plan and Target data in pending tables that do not have associated Actual data posted to the database can be purged from the database periodically from these data tables, but BPM does not perform this

purge automatically. The source text files for plans and targets are kept until manually purged.

5. Reblend data captured includes some header data and actual recipe and the off-line Lab results. (Plan and Target data for reblends is not stored in the database but source files can be maintained.)

F.2 PBM Database Migration Tool

Purpose

The PBM Database Migration Tool is used to manage the migration of PBM databases from older

versions to the present, including the PBM database (AmmDb), LIMS Viewer database (LDR) and BPM

database (BpmDb).

ATTENTION:

For the PBM R500.1 release, the PBM Database Migration Tool can be used to upgrade the AmmDb and LDR databases, but only for standalone LIMS Viewer installations. (This is in addition to upgrading the BPM database.) If any other Production Browser-based applications are present (e.g. PBC, PBO, PIM, PMM, etc.), the AmmDb Upgrade utility, delivered with the Production Browser Server software, must be used to upgrade the AmmDb database. (See the Production Browser Installation Guide for details.)

See the PBM Client and Server Installation Guide for the instructions for using the PBM Database Migration Tool to migrate the AmmDb and LDR databases.

Supported Database Versions

The PBM Database Migration Tool supports BpmDb database upgrades from BMA R410.1 and later. It

cannot be used to upgrade older versions of this database.


F.2.1 Prerequisites

For BPM, the PBM Database Migration Tool must be run locally on the BPM Server where the BpmDb is stored.

The database migration can only be performed when the BpmDb database is down and the BPM

application is not running (i.e. all BPM processes must be stopped).

F.2.2 Update Procedure

Proceed as follows to update a BPM database to the current version:

1. On the BPM Server where the database is installed, run the PBM Database Migration Tool by

selecting All Programs > Honeywell BMA > Engineering Tools > PBM Database Migration in the Windows Start menu.4

2. In the Database view, leave the (Local) server identification unchanged. Select the database

authentication method. If Server authentication is selected, enter the user ID and password for the SQL Server's System Administrator (sa). Finally select the database name.

4 You can also run the PBMDbMigration.exe file which is located in the \Program Files (x86)\Honeywell

\AMM\Tools\PBMDbMigration folder.


Settings Description

Connection timeout Set the time in seconds for database connection timeout.

Execution timeout Set the time in seconds for the migration tool's execution timeout.

Note: The size of this period will depend on the size of your BpmDb database. Be sure to set this value to a big number to avoid premature database upgrade termination.

3. When the database name is selected, the tool determines the current database version by checking the

BpmDb database table called BM_DATABASE_VERSION.5

If the current database version matches the target database version, a message is displayed indicating that the database is up-to-date and no migration is required.

If the database needs to be updated, the Migration Matrix is populated with the required updates.

Note: The same migration is performed for both BMA R410.1 and BMA R430.1 upgrades. The BpmDb database version number shown as the starting point for the migration is "4.3.0" in both

cases.

5 For upgrades from BMA R410.1 or BMA R430.1, the existing BPM database does not include the BM_DATABASE_VERSION table. This table is added in BMA R430.1. In this case, the Migration Tool determines the required migration based on the existence (or lack thereof) of the BM_DATABASE_VERSION table.


4. Before you proceed with the migration, use the Options view to update the log file path and database

backup settings if needed.

Option Description

Log file path By default the log file is stored in the local %HwProgramData%\BMA\Database folder. Click the browse button to change the target folder for the log file.

Backup database Select the Backup database option to have a backup copy of the database be created before the database migration is performed.

The target for the backup database is always the %HwProgramData%\BMA

\Database\SQLServer\Backup folder on the local server. (This path cannot be changed.)

5. Click Migrate to update the database.

6. Use the Output view to monitor the migration operation and to verify the results.


APPENDIX G - TROUBLESHOOTING TIPS

G.1 Picture Printing Not Available

Issue:

If the following error message appears, this means that the Windows feature required to print from the default image viewer on Windows is disabled. (This feature is disabled by default on Windows 2008.)

To resolve this problem, install the Windows Server 2008 Desktop Experience feature as follows:

1. Click Start, click Administrative Tools, and then double-click Server Manager.

2. In Server Manager, click Add Features under Features Summary.

3. In the Add Features Wizard dialog box, make sure that the Desktop Experience option is selected.

4. Click Next, and then click Install.

5. After the installation process is complete, click Close, and then close Server Manager.

ATTENTION:

After you install Desktop Experience, you have to restart your computer.


G.2 SQL Server Reporting Services Encryption Key Loss

Issue:

Errors can occur if the encryption key used by SQL Server Reporting Services is lost. This can happen if the log on account in SQL Server Reporting Services is changed and the system is restarted.

Resolution:

If the encryption key had been backed up, it can be restored in the Reporting Services Configuration Manager as shown below.

Otherwise, the encryption key must be deleted and recreated as described below:

How to Delete Encryption Keys (Reporting Services Configuration Manager)

1. Start the Reporting Services Configuration tool, and then connect to the report server instance you

want to configure.

2. On the Encryption Keys page click Delete. Click OK.

3. Restart the Report Server Windows service.


How to Recreate Encryption Keys (Reporting Services Configuration Manager)

1. Disable the Report Server Web service and HTTP access by modifying the IsWebServiceEnabled

property in the rsreportserver.config file. This step temporarily stops authentication requests from being sent to the report server without completely shutting down the server. You must have minimal

service so that you can recreate the keys.

If you are recreating encryption keys for a report server scale-out deployment, disable this property on all instances in the deployment.

i. Open Windows Explorer and navigate to: \Program Files (x86)\Microsoft SQL

Server\report_server_instance\Reporting Services.

ii. Replace "drive" with your drive letter and "report_server_instance" with the folder name that

corresponds to the report server instance for which you want to disable the Web service and

HTTP access.

For example for SQL Server 2008 R2: C:\Program Files (x86)\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting

Services\ReportServer

iii. Open the rsreportserver.config file.

iv. For the IsWebServiceEnabled property, specify False, and then save your changes.

2. Start the Reporting Services Configuration Manager and connect to the report server instance you

want to configure.

3. On the Encryption Keys page click Change. Click OK.

4. Restart the Report Server Windows service.

5. Re-enable the Web service and HTTP access by modifying the IsWebServiceEnabled property in the

rsreportserver.config file.

Notices

Documentation feedback

You can find the most up-to-date documents on the Honeywell Process Solutions support website at:

http://www.honeywellprocess.com/support

If you have comments about Honeywell Process Solutions documentation, send your feedback to:

[email protected]

Use this email address to provide feedback, or to report errors and omissions in the documentation. For

immediate help with a technical problem, contact your local Honeywell Process Solutions Customer

Contact Center (CCC) or Honeywell Technical Assistance Center (TAC) listed in the “Support and other contacts” section of this document.

How to report a security vulnerability

For the purpose of submission, a security vulnerability is defined as a software defect or weakness that

can be exploited to reduce the operational or security capabilities of the software.

Honeywell investigates all reports of security vulnerabilities affecting Honeywell products and services.

To report a potential security vulnerability against any Honeywell product, please follow the instructions

at:

https://honeywell.com/pages/vulnerabilityreporting.aspx

Submit the requested information to Honeywell using one of the following methods:

Send an email to [email protected].

or

Contact your local Honeywell Process Solutions Customer Contact Center (CCC) or Honeywell

Technical Assistance Center (TAC) listed in the “Support and other contacts” section of this

document.


mailto:[email protected]

https://honeywell.com/pages/vulnerabilityreporting.aspx

mailto:[email protected]

Support and other contacts

For support and other contact details, go to https://www.honeywellprocess.com/en-US/contact-

us/customer-support-contacts/Pages/default.aspx.

World Wide Web

Honeywell Process Solutions website:


Elsewhere

Contact your nearest Honeywell office.

https://www.honeywellprocess.com/en-US/contact-us/customer-support-contacts/Pages/default.aspx

https://www.honeywellprocess.com/en-US/contact-us/customer-support-contacts/Pages/default.aspx


For more information

To learn more about Honeywell’s products or

solutions visit www.honeywellprocess.com or

contact your Honeywell account manager.

Honeywell Process Solutions

1250 West Sam Houston Parkway South

Houston, TX 77042

Honeywell House, Skimped Hill Lane

Bracknell, RG12 1EB

Shanghai City Centre, 100 Junyi Road

Shanghai, China 20051

www.honeywellprocess.com © 2016 Honeywell International Sàrl

http://www.honeywellprocess.com/