AspenAtOMSV12 Inst

g
Aspen Tank and Operations Manager
Installation Guide
Version Number: V12
October 2020
Copyright (c) 2020 by Aspen Technology, Inc. All rights reserved.
Aspen Tank and Operations ManagerTM, Aspen Tank and Operations Manager BrowserTM , and Aspen Operations
Reconciliation and AccountingTM, and the aspen leaf logo are trademarks or registered trademarks of Aspen
Technology, Inc., Bedford, MA.
All other brand and product names are trademarks or registered trademarks of their respective companies.
This document is intended as a guide to using AspenTech's software. This documentation contains AspenTech
proprietary and confidential information and may not be disclosed, used, or copied without the prior consent of
AspenTech or as set forth in the applicable license agreement. Users are solely responsible for the proper use of
the software and the application of the results obtained.
Although AspenTech has tested the software and reviewed the documentation, the sole warranty for the software
may be found in the applicable license agreement between AspenTech and the user. ASPENTECH MAKES NO
WARRANTY OR REPRESENTATION, EITHER EXPRESSED OR IMPLIED, WITH RESPECT TO THIS DOCUMENTATION,
ITS QUALITY, PERFORMANCE, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
Aspen Technology, Inc.

20 Crosby Drive
Bedford, MA 01730
USA
Phone: +(781)221-6400
Toll Free: (1) (888) 996-7100
http://www.aspentech.com
Contents
1 Introduction .........................................................................................................1
Overview......................................................................................................... 1
Related Documentation ..................................................................................... 1
Technical Support ............................................................................................ 2
2 Overview ..............................................................................................................3
aspenONE Overview ......................................................................................... 3
aspenONE Media .............................................................................................. 4
Licensing ......................................................................................................... 4
SLM License Server ................................................................................ 5
Localization ..................................................................................................... 6
Accessing aspenONE Documentation .................................................................. 6
Aspen Manufacturing Suite Overview .................................................................. 7
Tank and Operations Manager Features and Subfeatures Overview ........................ 7
Installation Overview ........................................................................................ 9
System Requirements ....................................................................................... 9
Pre-Installation Checklist ................................................................................... 9
Checking Installation Account Privileges .................................................. 10
3 Installing Aspen Tank and Operations Manager .................................................11

Purpose ........................................................................................................ 11
Overview....................................................................................................... 11
Server Install ....................................................................................... 11
Standard Install ................................................................................... 11
Before You Install ........................................................................................... 12
Granular Downloads ....................................................................................... 13
Installing Aspen Tank and Operations Manager for the first time .......................... 14
Getting Started .................................................................................... 15
Installing other AspenTech products ....................................................... 25
Verify the Installation ........................................................................... 25
4 Post Install Configuration ..................................................................................27

Post Install Configuration Check List ................................................................. 27
5 Creating or Upgrading an Aspen Tank and Operations Manager Database .........29

Creating a New Tank and Operations Manager Database ..................................... 29
Oracle Connection ................................................................................ 33
MS SQL Server Connection .................................................................... 35
Creating the Tank and Operations Manager database separate from the AORA
database ............................................................................................. 36
Creating the Tank and Operations Manager database in the existing AORA
Accounting database instance ................................................................ 40
Contents iii
Upgrading the Tank and Operations Manager Database ....................................... 42
Upgrading a database from a previous version ......................................... 42
6 Aspen Tank and Operations Manager Aspen Framework Security ......................45

Implementing Tank and Operations Manager AFW Security System ...................... 45
Aspen Oil Movement and Shipping Admin ................................................ 47
Aspen Oil Movement and Shipping.......................................................... 47
Aspen Oil Movement and Shipping Tank Areas ......................................... 47
aspenONE ATOMS AFW Security Application ............................................ 48
Create Tank and Operations Manager Roles ....................................................... 48
Assign Users to Tank and Operations Manager Roles .......................................... 49
Grant Rights to Tank and Operations Manager Roles ........................................... 50
7 Aspen Tank and Operations Manager Server Post Install Configuration .............51
Configure Aspen Operations Reconciliation and Accounting ODBC Source .............. 51
MSSQL Specific ODBC configuration ........................................................ 53
Oracle specific ODBC configuration ......................................................... 56
Configure Tank and Operations Manager Workstation ......................................... 58
Configure AtOMS and AORA ADSA Sources for AtOMS Browser ............................ 65
To create an ADSA source to AtOMS and AORA: ....................................... 65
Configure Real-Time ADSA Source.................................................................... 74
Configure Tank and Operations Manager Monitors .............................................. 80
Tank and Operations Manager Movement Monitor Service ......................... 80
Tank and Operations Manager Tank Monitor Service ................................. 84
Restarting Tank and Operations Manager Monitors ................................... 88
8 Aspen Tank and Operations Manager Viewer Post Install Configuration ............91
Configure Tank and Operations Manager Viewer ................................................. 91
Tank and Operations Manager Viewer Web ........................................................ 94
Grant User Trust and Permission to Run the XBAP .................................... 94
Configure mMDM for Aspen Tank and Operations Manager XBAP Database
Support .............................................................................................. 96
Access Aspen Tank and Operations Manager XBAP from IE ........................ 98
Permission Errors Troubleshooting .......................................................... 99
9 Aspen Tank and Operations Manager Importer Post Install Configuration .......101
Configure Aspen Tank and Operations Manager Importer .................................. 101
10 Aspen Tank and Operations Manager Tank Calculator Post Install Configuration105
Configure Aspen Tank and Operations Manager Tank Calculator ......................... 105
11 Operations Accounting Interface Post Install Configuration...........................111

Operations Accounting ODBC Source .............................................................. 112
Duplicate Tank and Operations Manager OLEDB Data Link File ........................... 112
Start the Operations Accounting Interface Application ....................................... 113
Preferences Form ......................................................................................... 113
Configuring Grid Colors ................................................................................. 115
Configuring Rounding options ........................................................................ 116
Preventing Double Compensation in Operations Accounting Interface ................. 116
Configuring Data Propagation in Tank and Movement Events ............................. 117
iv Contents
12 Aspen Tank and Operations Manager Client Post Install Configuration ..........119
Configure Aspen Operations Reconciliation and Accounting ODBC Source ............ 119
MSSQL Specific ODBC configuration ...................................................... 121
Oracle specific ODBC configuration ....................................................... 124
Configure Tank and Operations Manager Config for Client ................................. 126
Update Firewall Settings in the Server Machine ................................................ 132
13 Populate Aspen Tank and Operations Manager Database ...............................135

Overview..................................................................................................... 135
14 Upgrading Aspen Tank and Operations Manager ............................................137

Overview..................................................................................................... 137
Before You Upgrade ...................................................................................... 137
Upgrading the Security Server ............................................................. 138
Completing a System Backup............................................................... 139
Backup the Tank and Operations Manager database and others ............... 139
Shutting down InfoPlus.21 .................................................................. 139
Shutting down Microsoft SQL Server ..................................................... 139
Shutting down services ....................................................................... 139
Duplicate the Tank and Operations Manager directory tree ...................... 140
Upgrading Tank and Operations Manager ........................................................ 140
Upgrading Tank and Operations Manager from V7.2, V7.3, V8.0, V8.5, V8.7,
V8.8, V8.9, V9, V10, V11 .................................................................... 140
Upgrading Tank and Operations Manager from V7.1 and earlier versions ... 141
After You Upgrade ........................................................................................ 141
15 Repairing Aspen Tank and Operations Manager .............................................143

Overview..................................................................................................... 143
Repairing Tank and Operations Manager ......................................................... 143
After You Repair ........................................................................................... 143
16 Removing Aspen Tank and Operations Manager .............................................145

Before You Remove Aspen Tank and Operations Manager.................................. 145
Uninstall AspenTech Software ........................................................................ 145
17 Troubleshooting .............................................................................................147
AspenTech Support ...................................................................................... 147
Operations Accounting Interface Troubleshooting ............................................. 147
“Warning: No Aspen Operations Reconciliation and Accounting Connect server
specified.” ......................................................................................... 147
“Could not connect to Aspen Operations Reconciliation and Accounting Model
xxxxxx.” ........................................................................................... 148
18 Prerequisites ..................................................................................................151
Creating an Oracle Database ......................................................................... 151
Oracle Client Installation ..................................................................... 152
Server Installation .............................................................................. 155
Database Configuration ....................................................................... 160
Installation Check .............................................................................. 161
Contents v
Appendix A – Configuration Files ........................................................................163
AspenTech.MSC.Settings.xml File ................................................................... 163
Example of AspenTech.MSC.Settings.xml File ........................................ 163
vi Contents
Contents vii
1 Introduction
This installation manual describes:

 How to install and configure Aspen Tank and Operations Manager,
formerly known as AtOMS
 How to install and configure Aspen Tank and Operations Manager Browser
 How to upgrade, reinstall, or remove the Aspen Tank and Operations
Manager software
 How to create or upgrade an Aspen Tank and Operations Manager
database
 How to install and configure a database of type MSSQL to work with the
Aspen Tank and Operations Manager software
Overview
Aspen Tank and Operations Manager, formerly known as AtOMS, is included
in the Aspen Manufacturing suite of products. The instructions in this guide
focus solely on installing Aspen Tank and Operations Manager as a single part
of an integrated solution. The instructions do not address the installation
instructions for the entire suite or industry solution.
Note: For information about Aspen Industry Solutions, see the aspenONE
Deployment Guide document.
Related Documentation
A number of documents have been produced to assist users to learn and use
Aspen Tank and Operations Manager applications. The documentation set
consists of the following:
 Manuals
o Aspen Tank and Operations Manager Release Notes
o Aspen Tank and Operations Manager Integration User Guide
o Aspen Operations Reconciliation and Accounting Installation Guide
o Aspen Operations Reconciliation and Accounting Integration User
Guide
1 Introduction 1
o Aspen Data Source Architecture Installation Guide
o Aspen Framework Server Installation Guide
o Aspen InfoPlus.21 Product Family Installation Guide
o Aspen InfoPlus.21 Product Family Configuration Guide
o Aspen Local Security Installation Guide
 Help Files
o Aspen Tank and Operations Manager Help
o Aspen Tank and Operations Manager Browser Help
o Aspen Tank and Operations Manager – Admin Tool Help
o Aspen Operations Accounting Connect Help
Technical Support
AspenTech customers with a valid license and software maintenance
agreement can register to access the online AspenTech Support Center at:
https://support.aspentech.com
This Web support site allows you to:
 Access current product documentation
 Search for tech tips, solutions, and frequently asked questions (FAQs)
 Search for and download application examples
 Search for and download service packs and product updates
 Submit and track technical issues
 Send suggestions
 Report product defects
 Review lists of known deficiencies and defects
Registered users can also subscribe to our Technical Support
e-Bulletins. These e-Bulletins are used to alert users to important technical
support information such as:
 Technical advisories
 Product updates and releases
Customer support is also available by phone, fax, and email. The most up-to-
date contact information is available at the AspenTech Support Center at
https://support.aspentech.com.
2 1 Introduction
2 Overview
This chapter provides an overview of the Aspen Tank and Operations Manager
software including the installation requirements and process. It includes the
following:
 aspenONE Overview
 Aspen Manufacturing Suite Overview
 Aspen Tank and Operations Manager Features and Subfeatures Overview
 System Requirements
 Pre-Installation Checklist
aspenONE Overview
aspenONE® is the comprehensive set of software solutions and professional
services provided by AspenTech; these are designed to help process
companies achieve their operational excellence objectives. AspenTech
customers are better able to increase capacity, improve margins, reduce
costs, and become more energy efficient.
aspenONE solutions include the industry’s leading:
 Simulation and design products in the aspenONE Engineering suite.
 Plant operations products in the aspenONE Manufacturing suite.
 Supply chain management products in the aspenONE Supply Chain suite.
 Predictive and prescriptive analytic products in the aspenONE Asset
Performance Management suite.
The token-based aspenONE Licensing Model gives customers the flexibility to
access and use any aspenONE product at precisely the time it is needed. This
is especially critical in the dynamic market conditions of the process industries
‒ whether during down economies or in high-growth periods. This enables
customers to lower their risk while maximizing the return on their software
investment.
2 Overview 3
aspenONE Media
Unless you have specifically requested a USB drive, you will receive
instructions on how to download the aspenONE media.
Download the media that you are entitled to and extract the zip file(s) using a
zip extractor such as WinZip/7-Zip. You may choose from the following:
 Aspen Engineering – includes all Aspen Engineering products, Aspen
PIMS and Aspen Administration and Licensing components.
 Aspen Manufacturing and Supply Chain – includes all Aspen
Manufacturing products, Aspen Petroleum Supply Chain products,
aspenONE Supply Chain Management products, GDOT, and aspenONE
Infrastructure products as well as Aspen Administration and Licensing
components.
 aspenONE Asset Performance Management – includes all APM
products.
 aspenONE Software License Manager includes all Aspen
Administration components (Aspen SLM, Aspen SLM tools, and ALC Auto
Upload Tool).
Note: The product Release Notes and Installation Guides are included in the
Documentation sub-folders under each family of products. There is a link to
the Getting Started Guide on the Install Browser.
Licensing
To manage your product entitlement, you will receive one of the following
separately:
 A license file if you are using the SLM Server to manage the products to
which you are entitled.
 Aspen License Deployment Assistant (ALDA): ALDA is a utility that will
update a license server with the necessary licenses needed for a new
release without having to send a new license key for applicable suites and
qualified customers. For qualified customers, ALDA is available on the
electronic software download site.
 A pre-configured dongle containing your customer license file if you are
operating using a dongle to manage the products to which you are
entitled.
Note: An invoice noting the products for which you are licensed is sent
separately from the software shipment.
You will have access to one or more of the following:
o aspenONE Token Media – Contains the media that supports the
aspenONE Licensing Model token-based system. This all-inclusive
token-based licensing model was introduced in July 2009. Under this
licensing model, customers are entitled to install and run all of
AspenTech’s products as long as they have purchased sufficient
tokens. To install software purchased under this commercial
4 2 Overview
agreement, use this media. Software installed from the aspenONE
Token media requires run-time token-based license keys.
o aspenONE Standard Media – Contains the media that supports
perpetual and pre-aspenONE Licensing Model token-based systems. If
you have perpetual license agreements or token-based license
agreements by product (pre-July 2009), you should use the media
labeled Standard. Software installed from the aspenONE Standard
media requires older license keys that have been in use since the
aspenONE 2004 release.
Upgrading to the aspenONE Licensing Model for

Manufacturing and Supply Chain V8.x and above
If you have recently signed a new aspenONE Licensing Model agreement or if
you have superseded an old license agreement with an aspenONE Licensing
Model token-based license agreement for aspenONE Manufacturing and
Supply Chain, you will receive a new token-based license file. During
installation of any product in Aspen Manufacturing and Supply Chain, you will
get a message indicating that the newly installed software will use the token-
based license key. Accepting the warning message enables you to install the
software.
Notes:
 If you do not have the updated token-based license file, please contact
AspenTech Customer Support.
 We have seen issues extracting large zip files on earlier versions of
Windows. If you do not have access to an extractor, you may use the zip
extractor utility on the Download Center.
 If you have an MSC perpetual license purchased prior to 2011 and are
entitled to Informatica upgrades, you can download the Informatica
software from the Download Center.
 Some products previously available on CD-ROM or DVD are not included.
If you do not find a product, please contact AspenTech Support at
https://support.aspentech.com.
SLM License Server

Before you install products, it is recommended that you install and configure
the SLM License Server.
When you deploy aspenONE V12 software on client machines, the SLM server
should be from the V12 release. When migrating to a new version of
aspenONE, the SLM Server should always be upgraded first, followed by the
SLM clients. This is done to avoid any potential incompatibility issues. During
this transition period, it is possible to have clients at a lower version than the
SLM Server.
For more information about licensing, please see Software License Manager
(SLM) Installation and Reference Guide on the aspenONE media.
2 Overview 5
Localization
The V12 release media includes all localized products that are available when
V12 is released. The Knowledge Base article #000093657 contains a
spreadsheet that identifies which products are localized and how to access the
localization.
Accessing aspenONE
Documentation
There are several ways to access Product Help files and context-sensitive Help
(these are available depending on the type of application):
 Clicking the Help button.
 Pressing F1 while in the application.
 Accessing the application’s Help menu.
 Clicking a Help icon. For example:
Documentation in PDF format can be found in the following ways:

 Installation Guides and Release Notes can be found by clicking the
corresponding link on the Welcome page of the aspenONE Installer.
 Logging onto the AspenTech Customer Support site, clicking Support in
the upper right-hand side and then clicking Product Documentation.
 Downloading all the available documentation (other than Help files) from
the AspenTech Customer Support website via the zip file of the aspenONE
Documentation.
For Aspen Plus, Aspen HYSYS, Aspen Exchanger Design and Rating, Aspen
Economic Evaluation, Aspen DMC3 Builder, and Aspen Fidelis Reliability only,
you can access additional documents by:
 Clicking the Aspen Knowledge icon on the Resources ribbon. (All products
except Economic Evaluation.)
 Entering a search string within the Search Aspen Knowledge search box –
available in the upper-right corner of the application. (All products except
Economic Evaluation.)
 Clicking Aspen Knowledge from the Help menu (Economic Evaluation
only).
6 2 Overview
Aspen Manufacturing Suite
Overview
AMS applications deliver production dispatching, production execution,
historical data management, advanced control, inferential modeling, process
analysis and monitoring, production tracking, and quality management
services for manufacturing environments.
Tank and Operations Manager

Features and Subfeatures
Overview
Aspen Tank and Operations Manager provides information about events
derived from automatic monitoring and control of oil movements and shipping
transactions. Being a client-server application, it communicates with real-time
and relational databases to fulfill its functions.
The Server feature provides tank and movement monitoring, configuration
and management of the databases accessed, and tank related level to volume
calculation functions.
The Client feature is a graphical user interface that allows you to create,
view, and print Tank and Operations Manager movements, orders, and
shipment transactions.
Aspen Tank & Operations Manager Browser is a web-based application
that provides operations managers and operators a system for recording and
monitoring activities that utilizes both real-time data and the plant model
from Aspen Operations Reconciliation & Accounting (AORA).
Aspen Operations Reconciliation & Accounting (AORA) Connect
combines the configuration of the Aspen Operations Reconciliation &
Accounting and Aspen Tank & Operations Manager applications into a
common interface that organizes them into a set of views.
The Interfaces feature provides the Operations Accounting Interface, which
is a graphical user interface that allows you to import Tank and Operations
Manager transactional data, interactively or automatically in batch mode, into
the Aspen Operations Reconciliation and Accounting (cut-off based) database.
The Tank Calculator Web Pages feature provides a thin, web-based client
application that enables you to calculate tank related data using the tank
information in the Tank and Operations Manager and Aspen Operations
Reconciliation and Accounting databases.
Feature Subfeature Description Notes
ADSA Directory Server None Data sources to Aspen AspenTech

products recommends that you
install to the server
computer.
2 Overview 7
Important: The ADSA

Directory Server
connection does not
cross most firewalls.
Ensure that each LAN is
given its own ADSA
Directory Server.
Aspen Local Security None Aspen Local Security Server Aspen recommends
Server or Aspen is a security server that you install to the
Framework designed for Aspen point server computer.
solutions; Aspen Framework
is a security server for
enterprise-wide solutions.
Aspen Operations Core Plant data model, material Aspen recommends
Reconciliation and balance, and reconciliation that you install to the
Accounting software server computer.
Aspen Operations Retrieves data from text Aspen recommends
Reconciliation and files or a data historian that you install to the
Accounting Connect (currently InfoPlus.21 and server computer.
PI) for use by Aspen
Operations Reconciliation
and Accounting. Provides
the post-install
configuration options for
Aspen Tank and Operations
Manager.
InfoPlus.21 Core server Real-time database, Aspen recommends
feature historian, and process data that you install to the
server. server computer.
Aspen SQLPLus AspenTech proprietary SQL Requires InfoPlus.21
application.
SQLPLus Client Builds and executes queries Aspen recommends
and views results that you install to the
server or client
computer.
SQLPlus ODBC The ODBC interface for Aspen recommends
SQLPlus that you install to the
server or client
computer.
Aspen Process Data Core Provides access to process Aspen recommends
data in InfoPlus.21 and PI that you install to the
server computer.
RDBMS Required by InfoPlus.21
Aspen recommends
that you install to the
server computer.
Aspen Process Explorer Core Provides graphics and Aspen recommends
trending for real-time data that you install to the
server or client
computer.
Process Data Rest Gets data from IP.21. Aspen recommends
Service (PDRest) that you install to the
8 2 Overview
server computer.
Aspen Web Server An aspenONE application. It Aspen recommends
is available from within the that you install to the
aspenONE MES web server. server computer.
Installation Overview
Aspen Tank and Operations Manager can be implemented as a stand-alone
application or as part of the refinery automation suite of products that may
include planning (Aspen PIMS), scheduling (Aspen Petroleum Scheduler),
real-time acquisition (Aspen InfoPlus.21), material balance and reconciliation
(Aspen Operations Reconciliation and Accounting), and LIMS systems.
System Requirements
For the most up-to-date hardware and software requirements that must be
met in order to install AspenTech products, refer to the following website:
https://www.aspentech.com/platform-support/
Important: You must have administrator privileges to carry out a Tank and
Operations Manager installation.
Pre-Installation Checklist
Before installing Aspen Tank and Operations Manager, refer to the following
checklist to ensure a smooth installation.
Verify that all system requirements are met (see the

“System RequirementsSystem RequirementsSystem
Requirements” section).
If connecting to a remote Oracle database from the Tank
and Operations Manager Server node, a compatible
version of Oracle client software must be installed on the
Tank and Operations Manager Server node.
Verify that there is enough available disk space for any
other AMS software you are planning to install.
Verify that all additional third-party product software has
been installed. (See the “System Requirements”
section).
Check that you have local Administrator privileges. For
instructions, see the following section on Checking
Installation Account Privileges.
2 Overview 9
Obtain name/IP address of the Aspen Software License
Manager (SLM) server.
Confirm that the Aspen Software License Manager
service is installed and running. For more information
about the Aspen Software License Manager, refer to the
Aspen Software License Manager (SLM) Installation and
Reference Guide.
If you have an aspenONE license, verify that Aspen
Framework (AFW) or Aspen Local Security is installed
and running. For more information, refer to the Aspen
Framework Server Installation Guide.
Checking Installation Account Privileges

When installing AMS, you must use an account with local Administrator
privileges.
10 2 Overview
3 Installing Aspen Tank and
Operations Manager
Purpose
This chapter explains how to install the current version of the AMS products.
This installation assumes that you do not currently have Aspen Tank and
Operations Manager installed on your computer.
Overview
The AspenTech Installer can guide you through the installation of a single
product as well the installation of a group of products that are integrated to
provide industry solutions. This manual describes the installation of Tank and
Operations Manager within the AspenTech AMS family of products.
Important: This chapter describes how to install Tank and Operations

Manager. It does not describe how to install other AspenTech products. If you
choose to install Tank and Operations Manager simultaneously with other
AspenTech products or currently have AspenTech products residing on your
computer, some installation dialog boxes you encounter might not be
described in this guide. Refer to the various product installation guides for
descriptions of these dialog boxes.
There are two installation options available, Server and Standard.
Server Install
 Using the Server Install, it is possible to install either the Tank and
Operations Manager Server components and/or the Tank and Operations
Manager Client components.
Standard Install
 Using the Standard Install, it is possible to install only the Tank and
Operations Manager Client components.
3 Installing Aspen Tank and Operations Manager 11

 The flow chart shown below illustrates the recommended sequence of
steps you should follow when installing Tank and Operations Manager for
the first time.
Install and configure

your Operations
Accounting Server
(including database
creation and
configuration)
Install and configure

your Tank and
Operations Manager
Server (including
database creation and
configuration)
Verify that the Tank If changes are needed

Install one Tank and and Operations for successful client
Operations Manager Manager module can configuration, update
be successfully Tank and Operations
client
opened Manager Config file
(See Appendix)
Install remaining
Tank and
Operations Manager
clients
Legend denotes substep
Note: Some intermediate steps have been omitted for simplicity, such as the
installation and configuration of other related products such as the database
repository, the Aspen Framework, and InfoPlus.21. These will be explained in
detail later.
Before You Install

Please follow all the procedures carefully to ensure your installation is
successful.
If you experience any difficulty, please contact AspenTech Online Technical
Support Center for assistance.
 Read the Aspen Tank and Operations Manager Installation Guide. See the
aspenONE Documentation folder.
 Read the Aspen Tank and Operations Manager Release Notes.
 Read this manual in its entirety before starting your new installation.
12 3 Installing Aspen Tank and Operations Manager

 Confirm that pre-installation actions detailed in the “Pre-Installation
Checklist” section are complete.
 If the ADSA Directory Server is to be installed locally, check its system
requirements so you can install it at the same time as Tank and
Operations Manager.
Note: For more information see the Aspen Data Source Architecture
Installation Guide.
 Confirm that the Software License Manager is installed and running.
Obtain IP Address/name of the SLM server.
 Confirm the Aspen Framework server or Aspen Local Security server is
installed and running. If you are planning to use Aspen Local Security
server and it has not been installed, check its system requirements so that
you can install it at the same time as Tank and Operations Manager.
Note: For more information, see the Aspen Framework Server Installation
Guide or the Aspen Local Security Installation Guide.
 Confirm the Aspen InfoPlus.21 is installed and running. If you are planning
to use Aspen InfoPlus.21 and it has not been installed, check its system
requirements so that you can install it at the same time as Tank and
Operations Manager.
 Log on to the machine as a user with administrator privileges.
Granular Downloads
aspenONE V12 includes the ability to download some individual
products/product families that can be used independently of a full
suite. These sub-components are referred to as granular downloads. The
granular downloads are used to provide smaller downloads in situations where
customers only need a specific product/product family. If more than one
granular download is needed, it is recommended that the entire suite is
downloaded because it may take less time overall as opposed to downloading
two or more sub-components.
V12 Engineering (ENG): In the case of the ENG media, users can download
the entire suite or one of the items listed under the ENG group:
 Aspen Economic Evaluation
 Aspen Exchanger Design and Rating with Aspen Properties, Aspen
Simulation Workbook and Aspen Version Comparison Assistant
 Aspen Simulation Workbook
 Aspen Multi-Case Analysis
 Aspen Cim-IO & Process Data*
*The Cim-IO & Process Data software is from the Manufacturing & Supply
Chain suite and is useful for customers deploying a 3rd party historian and is
included for convenience. Note: The Aspen Cim-IO & Process Data software is
not a part of the overall Engineering suite download, and only available as a
separate download.

V12 Manufacturing & Supply Chain (MSC): In the case of the MSC media,
users can download the entire suite or one of the items listed under the MSC
group:
 V12 Batch APC
 Aspen Supply Chain Management
 Aspen Planning, Scheduling and Blending, Supply & Distribution
 Aspen Manufacturing Execution Systems & Advanced Process Control
 Aspen Unified
 V12 Aspen GDOT Online
 V12 Aspen GDOT Offline & Unified GDOT Builder
 Aspen Informatica PowerCenter 10.4
 Aspen Cim-IO & Process Data
V12 Asset Performance Management (APM): In the case of the APM
media, there is no downloadable suite. Users can download the products
listed below the APM group:
 Aspen Asset Analytics
 Aspen Fidelis
 Aspen ProMV
 Aspen Mtell
 Aspen Mtell for Oil Well Optimization
 Aspen Asset Performance Management Insights
 Aspen Enterprise Insights On-Premise Stack
V12 Aspen Internet of Things (AIoT): In the case of the AIoT media,
there is no downloadable suite. Users can download the products listed below
the AIoT group:
 Aspen Cloud Connect
 Aspen Edge Connect
Software License Manager (SLM): In the case of the SLM media, the only
granular download is ALDA:
 aspenONE License Deployment Assistant (ALDA)
Installing Aspen Tank and

Operations Manager for the
first time
Log on using the account name and password of an account in the
Administrators group of the target computer.
Note: Before you begin installation, you will want to review the Release
Notes and print copies of the Installation Guides for products that will be
installed. Those documents are included under each suite’s folder on the
media in your package.

Getting Started
1. You can begin your software installation by clicking on the media
download or inserting the aspenONE media into the USB drive. The
AutoPlay dialog box is displayed.
2. Select Run aspenONE Install Browser.
3. User Account Control confirmation
Before you see the Welcome page, you may see the following:
You must click Yes to continue.

If you do not see this dialog box or something similar, you may have
accessed the installation incorrectly and in doing so, appropriate settings may
not occur. The consequence is that the applications may not run correctly or
errors may appear even though the installation seems to complete
successfully. If this dialog box does not appear, cancel the installation and
re-launch setup.exe to start the installation again.
Carefully read the instructions, make your selections and proceed with the
installation.
Note: If patches are available for the product that you are installing, a screen
may appear that lets you view the patches before you install. You will also
have an opportunity to view the updates after you finish the installation
process.
The AspenTech Suite selection screen appears. The screen you see varies
depending on how you are accessing the Aspen Tank and Operations Manager
installation.

The following links are available:
o Patents – Allows you to download a document with a list of recent
patents.
o Need Help? – Connects to the AspenTech Support Web site, where
you can find knowledge base articles, tips, and solutions to known
problems.
o Getting Started – Links to brochure containing information about
prerequisites, installing and upgrading the software, documentation
and translated versions.
o What’s New? – Links to a description of new features.
4. Click INSTALL NOW.

aspenONE Manufacturing & Supply Chain Installer
The AspenTech Installation Welcome Page provides options to install or

upgrade aspenONE products, configure licensing, and create install scripts for
unattended installations.
The following links are available on the left side of the aspenONE Installer
Welcome Page:
 Get Started Guide – Opens the AspenTech Deployment Solutions Web
site.
 Installation Guides – Opens a folder that contains all the Installation
Guides for the products.
 Release Notes – Opens a folder that contains all the Release Notes for
the products.
 aspenONE Product Documentation – Opens the AspenTech Support
Web site.
 aspenONE Update Center – Connects to the Aspen Support Update
Center so that you can check to see if there are patches available for the
product(s) that you are installing. You must be a registered user on the
Support Web site to access the Update Center.
 Unattended Install Notes – Provides instruction on creating an
unattended installation.
 Support Services – Connects to the AspenTech Support Web site, where
you can find knowledge base articles, tips, and solutions to known
problems.
 AspenTech Home – Connects to the AspenTech Web site.

 Contact Us – Connects to the AspenTech Support Web site, where you
can obtain the latest e-mail and telephone contact information and find
the AspenTech Support location closest to you. You can see hours of
operation for global support and submit your support issues.
The following options are available on the aspenONE Installer Welcome Page:
 Install aspenONE products – Launches the installation process during
which you will select new products to be installed on this computer.
 Repair – Repair existing installation errors.
 Prepare Deployments (For IT Personnel/Deployment Groups) –
Create install scripts and copy media to automate software deployment.
Notes:
 Be sure that the SLM license server or standalone license is available prior
to installation. SLM tools are automatically installed when installing
aspenONE products.
Click Install aspenONE Products.
License Terms and Conditions
Select I accept the terms of the agreement and click Next to continue.

Product Selection (Server)
Note: You can add Aspen Plant Operations Family features later by starting
the installation process again, choosing Install aspenONE Products and
selecting the features available on this product selection screen.

Product Selection (Desktop)
File Location
Notes:

 Once the installation of any AspenTech product to the default folder has
been completed, this folder cannot be changed and the Change Current
Destination Folder dialog box will no longer display. Any further
AspenTech installations on the computer are made to that folder by
default.
 Common features are always installed in the Program files\Common
Files\AspenTech Shared folder regardless of the destination location
selected.
Prerequisite Validation
This screen will only appear if prerequisites are missing.

In V12 the capability to install and/or configure some of the product pre-
requisites during the Aspen software installation process – mostly Microsoft
Internet Information Services (IIS) was added. If the prerequisites window
appears, you will see the “Install Prerequisites” option at the bottom of the
screen. Here is a description of the icons related to installing pre-requisites.
(These must be installed before the AspenTech installation can proceed). You
may also encounter other icons that are informational only.
 This item can be installed automatically by selecting “Install

Prerequisites”
 or This item cannot be installed automatically by selecting

“Install Prerequisites”. Select the link in the item’s description to open
an AspenTech support site link that describes how to install this item.
 This item is informational

To install the prerequisites:
1 Click Install Prerequisites if you want to install or configure the relevant
prerequisites.
1 When the Install Prerequisites option is selected, the Install
Prerequisites screen appears. This will identify which prerequisites can be
installed and/or configured.
2 All options will be checked by default - unselect any that you do not want
installed automatically and then click Install.
When Install is selected, PowerShell windows will appear that perform
the install and/or configuration for the specified prerequisites. When the
install and/or configuration steps are done, you will see the Install
Prerequisites window again.
3 Click “x” to close the window and return to the installation process.

Specify Licensing and Security
An option is available to specify buckets. If you use buckets, you can specify
them during the install or later using the SLM Configuration Wizard. Also,
when Resolve server name is checked, the fully qualified server name is
used in the registry. If you use aliases, you can uncheck this setting.
Note: Specify your Aspen Framework Security server name, or you can
specify the server name in the Security Server URL row in AFW Tools later.

Windows Services Account Information
Verify Your Installation

Installation Progress
Installing other AspenTech products

At this point, you can choose to install other AspenTech products.
Important: The Product Selection dialog box displays the space required
to install the products you have selected. If there is not enough space on the
destination disk to install all the products you have selected, a warning
message appears. You can choose to install anyway, and the installation
program installs as many of the products that you selected as possible.
Verify the Installation

To verify that the Aspen Tank and Operations Manager installation was
successful, complete the following steps for each program:
1 Use the Start menu to open Operations Accounting.
2 Click Help and verify the About… option displays the version you
installed.

4 Post Install Configuration
After you have installed the Aspen Tank and Operations Manager (Tank and
Operations Manager) software, it is recommended that you perform the
following configuration steps.
Post Install Configuration

Check List
Create or upgrade your Aspen Operations Reconciliation and
Accounting database. For its normal operation, Tank and
Operations Manager requires that an Aspen Operations
Reconciliation and Accounting database and model exists and
be up and running. At a minimum, Tank and Operations
Manager requires tank related data in Aspen Operations
Reconciliation and Accounting for volume calculations.
Run the Aspen Database Wizard to create or upgrade your
database. For details, see the “Creating or Upgrading an
Aspen Tank and Operations Manager Database” chapter.
Set security from the Aspen Framework Server or Aspen Local
Security and restart the AFW Security Client Service. See
the “Aspen Tank and Operations Manager Aspen
Framework Security” chapter in this guide or the Aspen
Framework Server Installation Guide.
Configure the Tank and Operations Manager Server. See the
Chapter “Aspen Tank and Operations Manager Server Post
Install Configuration”
Configure Operations Accounting Interface. See the Chapter
“Operations Accounting Interface Post Install
Configuration”
Configure Tank Calculator. See the Chapter “Aspen Tank and
Operations Manager Tank Calculator Post Install
Configuration”
Configure Tank and Operations Manager Clients. See the
Chapter “Aspen Tank and Operations Manager Client”
4 Post Install Configuration 27

28 4 Post Install Configuration
5 Creating or Upgrading an
Aspen Tank and Operations
Manager Database
This chapter describes the tasks you can perform from the Aspen Database
Wizard utility such as the creation or upgrade of an Aspen Tank and
Operations Manager database.
Creating a New Tank and

Operations Manager Database
The Aspen Database Wizard assists you in creating the Tank and Operations
Manager database. You can specify the location, initial size, estimated growth,
and maximum size of the database.
You start the Aspen Database Wizard following an initial Tank and Operations
Manager installation. You may also choose to delay the configuration of the
Tank and Operations Manager database to a later time.
Important: Either an MSSQL Server or Oracle database management system

must be installed and running prior to creating a Tank and Operations
Manager database. If connecting to a remote Oracle database from the Tank
and Operations Manager Server node, the Tank and Operations Manager
server node must include installation of Oracle client software compatible with
your Oracle database.
To create a new Tank and Operations Manager database:

1 Start the Aspen Database Wizard following an initial Aspen Tank and
Operations Manager installation. You may also choose to delay the
configuration of the Tank and Operations Manager database to a later
time. On the Start menu, click Aspen Database Wizard to launch the
Aspen Database Wizard. Click Next after the Aspen Database Wizard
opens.
5 Creating or Upgrading an Aspen Tank and Operations Manager Database 29

Important: Either an MS SQL Server or Oracle database management
system must be installed and running prior to creating a Tank and
Note: MS SQL Server collation must not be set to case-sensitive for the
instance of MS SQL Server where the Batch.21 database resides. You can
use MS SQL Server Enterprise Manager to confirm this setting.
2 On the Choose an AspenTech product dialog box, choose the Aspen

Tank and Operations Manager option as the Aspen product for which to
30 5 Creating or Upgrading an Aspen Tank and Operations Manager Database

create the database.
3 Click Next. The Create a new database or upgrade an existing

database dialog box displays.
4 To configure the Tank and Operations Manager database, choose the
Create the database/tablespace, users and database objects
(Recommended) or the Create the database objects in an existing
database options and click Next.
o The Create the database/tablespace, users and database
objects (Recommended) option allows you to automatically create a
complete Oracle or MS SQL Server database.
o The Create the database objects in an existing database option
allows you to create the tables and objects for the Tank and
Operations Manager database in the same instance that the Aspen
Operations Reconciliation and Accounting database was created. The
option allows you to create the tables and objects both manually and
automatically. Before you select this option, you must have created
the Aspen Operations Reconciliation and Accounting database and
privileged users.
o The Update the existing database and database objects option
allows you to automatically update the existing Oracle or MS SQL
Server database or database objects.
Note: AspenTech recommends this option for Oracle databases.

5 Read the Connect to the database message box to determine the type
of database provider and database server you want to use to create your
Tank and Operations Manager database. Click Next.
6 Select the Provider tab on the Data Link Properties dialog box. Then
select the Microsoft OLE DB Provider for SQL Server database or
select Oracle Provider for OLE DB for Oracle database.
Data Link Properties dialog box for SQL Server

Data Link Properties dialog box for Oracle
7 Click Next. The Connection tab is displayed.

The Data Link Properties - Connection tab is slightly different for an
Oracle or MS SQL Server connection. For your database type, see the
following sections on “Oracle Connection” or “MS SQL Server
Connection.”
Oracle Connection
o In the Data Source: box, enter an existing server name with which to
connect to the Oracle database.
o Select the Use Windows NT Integrated Security option if you want
to use NT operating system authentication to access the Tank and
Note: To access an Oracle database using Windows NT integrated
security, you must install additional Oracle software for NTS
authentication on the Oracle client and database. For more information,
see http://www.oracle.com.
Or
o Select the Use a specific user name and password option to use
database authentication to access the Tank and Operations Manager
database. If you choose this option, enter the User name and
Password of the relational database user (i.e., system administrator or
database administrator) and check the Allow saving password
option.
Notes:

 AspenTech does not recommend selecting the Blank password check
box.
 You do not need to use the Advanced or All tabs on the Data Link
Properties dialog box.
Connection Tab for Oracle on Data Links Properties dialog box
o Click Test Connection. The Microsoft Data Link message box

appears to inform you if the test connection succeeded.

MS SQL Server Connection
o In the Select or enter a server name: list, select or type an existing
server name with which to connect to the MS SQL Server database.
Note: Click Refresh to update the list of server names.
o Select Use Windows NT Integrated Security if you want to use NT
operating system authentication to access the Tank and Operations
Manager database.
Or
Select Use a specific user name and password to use database
authentication to access the Tank and Operations Manager database.
If you choose this option, enter the User name and Password of the
relational database user (i.e., system administrator or database
administrator) and check the Allow saving password option.
Note: AspenTech does not recommend selecting the Blank password
check box.
o Select the Select the database on the server: but leave the list
blank.
Note: You do not need to use the Advanced or All tabs on the Data Link
Properties dialog box.
Connection Tab for SQL Server on Data Links Properties dialog box

8 Click Test Connection. The Microsoft Data Link message box appears
to inform you if the test connection succeeded. If the test connection was
successful, click OK to close the Microsoft Data Link message box.
Note: If the test connection was unsuccessful, return to Step 6 to redefine

your choices on the Connection tab.
9 Click OK on the Data Link Properties dialog box to display the Aspen
Database message box informing you that the database connection was
opened. Click Continue. This will bring the Specify database location
dialog box that will be different depending on whether you chose to create
the Tank and Operations Manager database separate from the Aspen
Operations Reconciliation and Accounting database or in the same
instance where the Aspen Operations Reconciliation and Accounting
database is located.
Creating the Tank and Operations Manager

database separate from the AORA database
1 In the Specify database location dialog box, enter the full path (DOS or
UNIX) or browse to the location where you want to put the Aspen Tank
and Operations Manager database in the Enter the path of the
directory to store the Tank and Operations Manager database: box.

2 Type the estimated size of the Tank and Operations Manager database
and the amount the database must be expanded each time the size
exceeds the maximum allocated in the Size: and Growth increment:
boxes respectively. The values default to 100 megabytes and 500
megabytes respectively. Click Next.
Note: The Maximum size: box is the largest size to which the Tank and
Operations Manager database can grow if the Unlimited check box is not
selected. The default value is 500 megabytes in the Size: box.
o Select the Unlimited check box if you want the database to expand
until it reaches the storage capacity of the disk on which it resides. If
this option is selected, the Maximum Size value is overridden.
o Click Next. The Aspen Database Wizard – Database Temporary
Segment/Log File Location dialog box is displayed.
3 Enter the full path (DOS or UNIX) or browse to the location where you
want to save the temporary segments (for Oracle) or a log files (for SQL
Server) for the Tank and Operations Manager database.

4 Enter and verify the password of the Tank and Operations Manager
internal database owner account in the Specify the internal database
account dialog box.
5 Click Next. The Choose authentication method dialog box displays.

o If you chose the Windows authentication method, select the Create
user for operating system authentication option and enter the
domain and user for the account under which the Tank and Operations
Manager Server is running.
o If you chose to only use database authentication for Tank and
Operations Manager ADO connection string, select the Do not create
user for operating system authentication.

6 Click Next and Finish to create the database on the Verify database
information dialog box.
7 Click Finish to create the database on the Verify database information
dialog box.
8 Click Close at the Creating the database dialog box indicating that the
Tank and Operations Manager database was successfully completed.

Creating the Tank and Operations Manager
database in the existing AORA Accounting
database instance
1 In the Specify database location dialog box, enter the name of the
existing database instance where the Tank and Operations Manager
database tables and objects will be created in the textbox The name of
the Tank and Operations Manager database: and then click the Next
button. This Verify database information dialog box will appear.

2 Click the Finish button after verifying all the choices made to start the
database creation process. At the end, the Creating the database dialog
will contain the summary of the steps achieved during the creation.
3 Confirm that the Tank and Operations Manager tables and objects have
been created in the same instance where Aspen Operations Reconciliation
and Accounting resides. Use the respective MSSQL or Oracle Enterprise
manager tool to verify this. For example, the SQL Server Enterprise
Manager will show the Tank and Operations Manager tables in the Aspen
Operations Reconciliation and Accounting.

Upgrading the Tank and
Operations Manager Database
Upgrading a database from a previous
version
Upgrading of versions prior to 2006 is not supported as part of the product.
These older versions of Aspen Tank and Operations Manager were distributed
as an Aspen Services Project, separately from aspenONE, and cannot
automatically upgrade to Tank and Operations Manager 2006 or later.
Database Wizard
1 After the post-install restart of the Tank and Operations Manager server,
open the Aspen Database Wizard (Start | Programs | AspenTech |
Common Utilities | Aspen Database Wizard). Click Next on the Aspen
Database Wizard dialog box.
2 On the Choose an AspenTech product dialog box, choose the Aspen

Tank and Operations Manager option as the Aspen product for which to
upgrade the database.

3 Click Next. To update the existing Tank and Operations Manager database
and database objects, choose the Update the existing database and
database objects option and click Next.
4 Read the Connect to the database message box to determine the type
of database provider and database server you want to use to upgrade
your Tank and Operations Manager database. Click Next.
Note: To create a new Tank and Operations Manager database, see the
“Creating a New Tank and Operations Manager Database” subsection in
this chapter for details on choosing the Create the
database/tablespace, users and database and Create database
objects in an existing database options.
5 Go to the “Creating a New Tank and Operations Manager Database”
subsection in “Creating or Upgrading an Aspen Tank and Operations
Manager Database.” The upgrade dialog boxes from this point are the
same as the first-time installation dialog boxes.

6 Aspen Tank and Operations
Manager Aspen Framework
Security
The Aspen Framework (AFW) or Aspen Local Security (ALS) provides the
framework for Aspen Tank and Operations Manager security. Both AFW and
ALS use the AFW Security Manager to configure Aspen Tank and Operations
Manager security. For ALS, the AFW Framework Security Manager is located
on the computer where ALS is installed. For Aspen Framework Security, the
AFW Framework Security Manager is located on the Framework server.
Important: Security permissions configured for earlier versions of Aspen

Tank and Operations Manager previous to V7.1 need to be backed up using
the AFW Tools utility before you uninstall the old version of AFW. The backed-
up security data files can then be restored for Aspen Tank and Operations
Manager V12 using the same utility. In this manner, the security is preserved
when you install Aspen Tank and Operations Manager V12. Security is
enabled when Tank and Operations Manager is first installed; you will not
have access to Tank and Operations Manager until configured.
To configure Aspen Tank and Operations Manager security, complete the
necessary steps described in this chapter. For general information about
Aspen Framework Security, see the Aspen Framework Server Installation
Guide.
Implementing Tank and

Operations Manager AFW
Security System
To implement the Tank Operations Manager AFW Security System for the first
time:
1 To start the Aspen Framework Security Manager, click
Start | Programs | AspenTech | AFW Security Manager.
6 Aspen Tank and Operations Manager Aspen Framework Security 45

2 In the first dialog box that appears, select the Use Operating System
Logon User check box and click OK.
If the message AFW Security Manager is not secured is displayed,

click OK.
For information about how to secure the AFW Security Manager, refer to
the AFW Security Manager documentation.
The AFW Security application window opens.
3 In the left pane, right-click the Applications node and select All Tasks|
Import Application…. to bring up the Windows Explorer Open File
dialog window.
4 Browse to locate the directory where Tank and Operations Manager was
installed. Then select the following XML files under the Scripts folder, for
import:
o Aspen Oil Movement Shipping Admin.xml
o Aspen Oil Movement Shipping.xml
46 6 Aspen Tank and Operations Manager Aspen Framework Security

o Aspen Oil Movement Shipping Tank Areas.xml
o aspenONE ATOMS AFW Security Application.xml
5 Import the .XML files individually.
Aspen Oil Movement and Shipping Admin

The securable objects under this Tank and Operations Manager AFW
application are meant to secure activities performed by diverse types of Tank
and Operations Manager Administrator roles. The objects are grouped in two
major categories: User Interface and Ship Interface securable objects.
The objects can be granted three permissions or properties each: Read,
Write, and Delete.
For both the User and Ship Interface categories, only the Read property
should be assigned to the Execute object.
Aspen Oil Movement and Shipping

and Operations Manager Operator roles when using the Tank and Operations
Manager Client mainly. As with the Admin case, the objects are grouped in
two main categories: User Interface and Ship Interface securable objects.
The objects can be granted only the permission Execute (or not).
For the Ship Interface category, only the Read property should be assigned
to the Execute object.
Aspen Oil Movement and Shipping Tank

Areas
and Operations Manager operator roles when to see and work with tanks not
assigned to a certain source/destination node. The objects can be granted
three permissions or properties each: Read, Write, and Execute.
For the User Interface category, only the Read property should be assigned
to the Execute object.
To configure the Tank and Operations Manager Oil Movement and Shipping
Tank Areas.xml:
1. After importing the Aspen Oil Movement Shipping Tank Areas.xml into
AFW Security Manager, add the areas set in the Aspen Operations
Reconciliation and Accounting into the AFW Security Manager as Securable
Objects.
2. Name each security object as its ID in the Aspen Operations Reconciliation
and Accounting.
3. Assign an appropriate role and appropriate privileges to each securable
object.

4. Select the appropriate area for all the tanks in the Aspen Tank and
Operations Manager Configuration Tool.
5. In the table AtOMS_Config, set the OBJ_Type field of Tank Security
Active to 50005 and the DESCRIPT field to 1.
aspenONE ATOMS AFW Security Application

The securable objects under AspenOne ATOMS are meant to secure
activities performed by various types of Tank and Operations Manager
operator roles when using Aspen Tank and Operations Manager Browser.
aspenONE ATOMS AFW Security Application.xml is placed under:
<Driver>:\Program Files \AspenTech\ProcessData
To configure the aspenONE ATOMS AFW Security Application.xml:
1. Import the aspenONE ATOMS AFW Security Application.xml into AFW
Security Manager.
2. Assign an appropriate role and appropriate privileges to each securable
object and securable group.
Create Tank and Operations

Manager Roles
After the Tank and Operations Manager AFW Security Applications are created
as appropriate, you can create the Administrator and Operator roles
envisioned for the refinery. For example, two types of roles are envisioned to
group most users at first: Tank and Operations Manager Administrator and
Tank and Operations Manager Operator. To create the two roles:
1 To start the Aspen Framework Security Manager, click
Start | Programs | AspenTech | AFW Security Manager.
2 In the first dialog box which appears, select the Use Operating System
Logon User check box and click OK.

If the message AFW Security Manager is not secured is displayed,
click OK.
For information about how to secure the AFW Security Manager, refer to
the AFW Security Manager documentation.
The AFW Security application window opens.
3 In the left pane, right-click the Roles and then select New | Role and
define one or more roles. For example: Tank and Operations Manager
Administrator and Tank and Operations Manager Operator.
Assign Users to Tank and

Operations Manager Roles
After Tank and Operations Manager roles are defined in AFW, you can proceed
to assign users and/or groups of users to each of the roles. To assign users or
groups:
1 In the right pane, click one role and then right-click to select the
Properties option from the context menu. For example: click Tank and
Operations Manager Administrator or Tank and Operations
Manager Operator and then right-click and select Properties.
2 Click the Members tab of the Properties dialog box.
3 Click Add to add members to the role using the Trusted Domain and
User Groups dialog box and click OK.
4 Click OK again to return to the AFW Security Manager application
window.

Grant Rights to Tank and
Operations Manager Roles
After Tank and Operations Manager roles are assigned to users and groups,
you can grant rights or permissions to each role for all the securable objects
in every Tank and Operations Manager AFW application. To assign
permissions to a securable object:
1 In the right pane, click one Securable Object and then right-click to
select the Properties option from the context menu. For example: click
Alarm Type on Admin User Interface and then right-click and select
Properties.
2 From the Role drop-down list, select one of the Tank and Operations
Manager roles.
3 Click one or more of the object permissions Read, Write, or Delete to
add these permissions to the role and click OK or Apply to return to the
AFW Security Manager application window.

Manager Server Post Install
Configuration
The steps to properly configure an Aspen Tank and Operations Manager

Server after the aspenONE installation and creation of the Tank and
Operations Manager database are:
1. Configure Aspen Operations Reconciliation and Accounting ODBC source
2. Configure Tank and Operations Manager workstation
3. Configure AtOMS and AORA ADSA source
4. Configure InfoPlus.21 ADSA source
5. Configure Tank and Operations Manager monitor services
Configure Aspen Operations

Reconciliation and Accounting
ODBC Source
Aspen Tank and Operations Manager requires an ODBC Data Source to Aspen
Operations Reconciliation and Accounting. It also requires an OLE/DB
connection, but this is handled later.
1 Log on with the user account used to install Tank and Operations
Manager.
2 Invoke the Data Sources (ODBC) tool. Click Start | Settings | Control
Panel | Administrative Tools and click the ODBC Data Sources (32-
bit). The following screen will appear:
7 Aspen Tank and Operations Manager Server Post Install Configuration 51

3 Click Add. The Create New Data Source window displays all the ODBC
drivers available in your computer. Select the native driver for your
database. A native driver is a driver provided by the database
manufacturer. E.g.: Oracle for an Oracle database instead of the
Microsoft ODBC for Oracle. Click Finish to bring up the database
specific dialog box.
Create New Data Source for SQL
52 7 Aspen Tank and Operations Manager Server Post Install Configuration

Create New Data Source for Oracle
MSSQL Specific ODBC configuration

1 For SQL Server, a dialog like the following will be shown. Enter the
corresponding DSN Source Name, Description, and Server. Note that the
Name should be unique. Click Next to continue.
2 Select the authentication method to access the Tank and Operations

Manager database and then click Next to continue

3 Select the Aspen Operations Reconciliation and Accounting database from
the Change the default database to drop-down menu.
4 Click Next to bring the Microsoft SQL Server DSN Configuration

window (intentionally omitted) and click Finish to bring the summary
page ODBC Microsoft SQL Server Setup.
5 Verify that the information on the summary is correct and then click Test
Data Source to reconfirm that the information entered connects to the
desired database. If successful, then click OK to exit out of the
configuration.

Note: Aspen Tank and Operations Manager Browser requires an ODBC Data
Source (64-bit) to work properly. Please repeat the previous steps to
configure the data source.
Oracle specific ODBC configuration

1 For Oracle, a dialog box similar to the following will be shown. Enter the
corresponding data in the fields Data Source Name, Description, TNS
Service Name (database server name: port number/database sid or
database server IP address:port number/database sid), and User ID.
Note that the Source Name must be unique. For example:

2 Click Test Connection to verify that the database connection with the
configuration entered is successful. You will be prompted to enter the
password of the User ID specified.

Configure Tank and Operations
Manager Workstation
This step primarily provides the Tank and Operations Manager applications
with the necessary information to access both the Aspen Operations
Reconciliation and Accounting data and the Tank and Operations Manager
database. Also, here you will define other miscellaneous parameters that
regulate as well the operation of these programs.
1. Start the Tank and Operations Manager Configuration Tool, which will
display the Configuration Tool dialog box. Enter the following fields on
the General tab:
Parameter Meaning
Server Name of the computer on which the Tank

and Operations Manager monitor
processes execute
Connection String Data Source Name, username, password,
Language Localized language supported. Default
(English) or Spanish
2. Click the tab User and set the following choices:
Parameter Meaning
Operating UOM Defines whether Tank and Operations
Manager uses Volume or Mass for
movements
Fractional Gauge Indicate whether Tank and Operations
Manager should display fractions for
gauges in fractions of inches or decimal
fractions (_none)
Scale The fractions scale to choose from
Normalize Fractions

Use Line Segments
Disable Stop gauge
Timeline
For our example we leave all answers at default values.
3 Click the Server tab to specify and define the contents of OLE DB UDL file
that will be used to obtain connect information to your Tank and
Operations Manager database. If the text box File is empty, click the
browser button to select the path and file name of the UDL file. The Data
Link Properties dialog box appears. We recommend selecting the path to
the folder where Tank and Operations Manager was installed and
AtOMS.udl as the filename, but any path or name will work. After the
filename has been selected and shows in the textbox, click Properties to
bring up the Data Link Properties dialog box, which is used to configure
the Tank and Operations Manager Data Source.
4 Click the Provider tab and select the native OLE DB provider specific to
your database and then click Next. The following dialog box depends on
the Provider selected.

5 For Microsoft OLE DB Provider for SQL Server: in the Select or enter
a server name field, enter the name of the server where your Tank and
Operations Manager database is located, and choose the authentication
method to access your database in the section Enter information to log

on to the server. If you use a specific user name and password, please
do NOT specify a blank password. Also make sure that the Allow saving
password is selected. Select your Tank and Operations Manager
database from the list in Select the database on the server. Click Test
Connection to make sure that the information provided allows a
successful connection to the specified database.
6 For Oracle Provider for OLE DB, the following dialog box is brought up.
Enter in Data Source the name of the local TNS service that connects to

your Tank and Operations Manager (and Aspen Operations Reconciliation
and Accounting) database. Specify the User name and Password used
to log on to the Tank and Operations Manager database. Click Test
Connection to confirm that the provided information allows a successful
connection to the specified database.
7 Click OK to leave the Data Link Properties box and return to the Aspen
Tank and Operations Manager dialog box. At this point you could click
Accept to save the configuration made until this point, as seen in the
following figure.

8 Click the Tools tab; in here, specify the path and file name of the Tank
and Operations Manager Administrator and Configuration tools so these
can be invoked from within other applications. Click the respective browse
buttons to point to where the utilities are located. You can click Accept
again afterwards.
9 Click the Debugging tab; in here you will define whether diagnostic
messages should be output from the Client application and their level of
detail.
10 Select the Debug Level from the list proposed and then click Accept to
save your choice.
11 Click Exit to terminate the Tank and Operations Manager Configuration
application.

For AtOMS Browser, you can use Aspen Operations Accounting Connect to do
this configuration:
1. Launch the Aspen Operations Accounting Connect by clicking Connect
(AORA) from the Start menu.
2. Click AtOMS | Configuration.
AtOMS Configuration allows you to provide the Aspen Tank and Operations
Manager applications with the necessary information to access both the
Aspen Operations Reconciliation and Accounting data and the Aspen Tank
and Operations Manager database.
3. Enter the required fields.
Reconciliation Basis field:
o Temperature: Standard conditions for temperature to define the
standard reference conditions to express the volumes of gases and
liquids. Used to calculate the tank gauge. You can use 15°C, 20°C, or
60F.
o Operating unit of measure: Defines whether Aspen Tank and
Operations Manager uses Volume or Mass for movements.
Fraction Gauge – Use Fractional Gauge to measure the tank inventory.
Inventory fractional gauge readings are entered for Inventory Fractional
Gauge instruments. The reading is entered as a gauge height in feet,
inches, and fractional inches. The reading is used to calculate the gross
volume of material in a tank from a strapping table.
o Normalize Fractions: Use normalize fractions in the system.
o Scale precision: When using Fractional Gauges, enter the scale in
fractions of an inch used. If using Decimal gauges, select None.
Timeline: A timeline of the restore operations performed on the
database.
Advanced Options:
o Disable Stop Gauge: If you check Disable Stop Gauge, the Stop
Gauge Source field is disabled in the Movement Detail View. If you
uncheck Disable Stop Gauge, the Stop Gauge Source is enabled in
the Movement Detail View.

o Propagate Event User Values: Check on to automatically propagate
event user values from movement to tank.
o Use Line Segment: Line Segment is used to hold volume and
manage line displacements when a product is put into a line and
pushes another product packed in the line. Check on to enable this
option.
Configure AtOMS and AORA

ADSA Sources for AtOMS
Browser
An ADSA sources to AtOMS and AORA needs to be configured in the server
where the Tank and Operations Manager monitoring services run.
To create an ADSA source to AtOMS and

AORA:
1 Start the ADSA Client Config Tool from the Start menu. The ADSA
Properties dialog box appears.
2 Click the Configuration tab and click Public Data Source. The Aspen
Public Data Source dialog box appears.

3 Click Add… to add a new data source, or select the existing data source
and then click Edit….
The DataSourceName dialog box appears. The DataSourceName refers
to the data source name you add or select.
Note: AtOMS only allows to configure one public data source in ADSA. If
there are multiple entries in ADSA, AtOMS Browser will not provide
specific data source while making request, so AtOMS Browser may not
work properly.
4 Click Add…, the Add Service dialog box appears.

5 Select Aspen ATOMS Web Client, and click OK. The Aspen ATOMS
Web Client Properties dialog box appears.
6 Click Setup…. the Data Link Properties dialog box appears.

7 On the Provider tab, select the data to which you want to connect and
click Next. The focus comes to the Connection tab.
8 On the Connection tab, enter the required information to connect to the
database. Clicking Test Connection can test if the connection is setup
successfully.
Microsoft OLE DB Provider for SQL Server Connection

Oracle Provider for OLE DB Connection
9 Click OK. An ADSA source to AtOMS has been configured.

Repeat the same procedure to add the Aspen AORA Reporting (OData)
service to the same public data source.
11 Click the Configuration tab and click Public Data Source. The Aspen
Public Data Source dialog box appears.

12 Click Add… to add a new data source, or select the existing data source
and then click Edit….
The DataSourceName dialog box appears. The DataSourceName refers
to the data source name you add or select.

14 Select Aspen AORA Reporting (OData), and click OK. The Aspen
ATOMS Web Client Properties dialog box appears.
15 Click Setup…. the Data Link Properties dialog box appears.

16 On the Provider tab, select the data to which you want to connect and
click Next. The focus comes to the Connection tab.
17 On the Connection tab, enter the required information to connect to the
database. Clicking Test Connection can test if the connection is setup
successfully.
Microsoft OLE DB Provider for SQL Server Connection

Oracle Provider for OLE DB Connection
18 Click OK in the Data Link Properties window to return to the Aspen

AORA Reporting (OData) Properties window. In the Aspen AORA
Reporting (OData) Properties window, Server Connection String
displays based on your previous settings. Enter the correct schema name
in the Schema field, and click OK to save the new data source. You can
find the schema name in SQL Server Management Studio.
19 Click OK. An ADSA source to AORA has been configured.

20 When finishing, open the HTML5 compliant browser as Administrator,
and type the URL: http://<webservername>/AtOMS.

21 Click Tank & Operations Manager, and confirm AtOMS Browser displays
tank and movement records at the specified database properly.
Configure Real-Time ADSA

Source
An ADSA source to the real-time database, InfoPlus.21 or Oil Systems PI,
needs to be configured in the server where the Tank and Operations Manager
monitoring services run because the services need to access real-time tank
gauging and flows data and to store calculated tank data. Please refer to the
Aspen InfoPlus.21 Product Family Installation Guide and Aspen InforPlus.21
Product Family Configuration Guide to follow the steps recommended to
configure an ADSA source. Assuming in our example that the name of the
server where our real-time database InfoPlus.21 is running and where the
ADSA Directory server is maintained in w2012-Seven, the minimum set of

ADSA services necessary to communicate with the InfoPlus.21 system from
Tank and Operations Manager can be depicted in the following figure:
If we were using PI as the real-time data, then the ADSA services configured
in our ADSA source entry would look like this:

If you use the AtOMS Browser, execute the following steps:
2 Click the Configuration tab and then click Public Data Source. The
Aspen Public Data Source dialog box appears.
3 Select the data source which is named as machine name, and then click
Edit….
Note: To use AtOMS Browser, an AtOMS Web Client service must be

configured in Aspen ADSA. Currently, AtOMS Browser architecture only
supports one data source of AtOMS Web Client and AORA at a time. If you
have multiple data sources configured for AtOMS Web Client or AORA in
Aspen ADSA, AtOMS Browser may not work properly.

5 Select the required services and click OK, the Service Properties dialog
box appears, where the Service refers to the service you select to add.
Configure each service in the Service Properties dialog box and then
click OK.
The following services should be added and configured, each service
should be added and configured one by one:
Note: If you have the IP.21 server installed on the same machine, these
services will be added automatically.
o Aspen DA for IP.21

o Aspen Process Data (IP.21), this service has no parameter to configure.
o Aspen Process Data Service

o Aspen SQLplus service component
6 Click OK to close the ADSA Properties dialog box. And then launch the
Aspen Operations Accounting Connect by clicking Connect (AORA) from
the Start menu.
7 Click AtOMS | Service Monitor, and in the RTDB Server: field, enter
the public data source name added in ADSA.

8 Restart the following services:
o Aspen OMS Movement Monitor
o Aspen OMS Tank Monitor
When finishing, open AtOMS Browser and confirm AtOMS Browser gets tank
values from IP.21 successfully.

Manager Monitors
The Aspen Tank and Operations Manager Movement Monitor and Tank Monitor
Services are standard Windows Services that should be activated only on the
Tank and Operations Manager Server. Apart from the configuration screen,
there is no user interface for these applications.
The Aspen Tank and Operations Manager Monitor services maintain links to
the Tank and Operations Manager Database, Aspen Operations Reconciliation
and Accounting and real-time database whenever possible. The server install
procedure of Tank and Operations Manager installs these two services.
Tank and Operations Manager Movement

Monitor Service
The Tank and Operations Manager movement monitor service is responsible
for periodic update of movements in the Tank and Operations Manager
Database. It runs at a predefined interval to gather movement information,
read current values from the real time database, perform the required
calculations, and update the Tank and Operations Manager database with the
results.
The key objectives of the movement monitor are:
 Start issued movements at the operator’s command
 Complete movements at the operator’s command
 Update active movements with information from the real time database
 Perform all calculations defined for each movement based on the most
current values from the real time database
 Store cutoff conditions at the predefined cutoff time
Configuration Steps
1 Use the shortcut created in Start | All Programs | AspenTech | Aspen
Manufacturing Suite | Aspen Tank and Operations Manager |
Monitors | Configure Movement Monitor. The dialog box titled Aspen
Tank and Operations Manager Movement Monitor will be shown:

The following parameters should be configured in the Tank and Operations
Manager Movement Monitor service:
o Activation Interval (seconds)
The time interval (in seconds) to activate the Movement Monitor scan
service. The default value of 300 (5 minutes) is recommended.
o App Server
The server where Aspen Tank and Operations Manager Server resides.
It is expected to be the same machine where the Tank and Operations
Manager Movement Monitor Service is running.
o RTDB Server
The Server where the real-time database resides. Normally the name
of your ADSA data source.
o Density Conversion Factor in Std Units
Must match the configuration for this parameter in Aspen Operations
Reconciliation and Accounting. This value can be found in the
OLOCONFG table.
o Propagate Initial Quality
When checked, the initial values of Density and %H2O of the tank
selected as control element, for each movement, will be propagated as
manual values to all other Density and %H2O instruments for that
movement.
o Write back field
Alternative field name when the definition record of calculated
variables in InfoPlus.21 is not IP_AnalogDef. By default Tank and
Operations Manager assumes that all calculated variables will be
defined by the definition record IP_AnalogDef, in which case the field
name where the new calculated value will be stored is
IP_INPUT_VALUE.

o Cutoff Time (hh:mm:ss)
The time of the day defined as the Cutoff time. Normally, you just
need to set the Hour and Minute here, because only Hour and Minute
are displayed in the Movement Detail dialog box.
IMPORTANT! For Aspen Tank and Operations Manager Movement
Monitor to activate a movement successfully. the Cutoff Time needs to
be the same as the accounting time displayed in the Movement Detail
dialog box.
o ConnectionString
Aspen Operations Reconciliation and Accounting connection
information in the form of “DSNname, username, password,”.
Advanced Options:
o Debug Level
This parameter controls the amount of information that will be logged
to the Windows Event message log. The default value of 0 should be
used. Any number greater that 0 will make the Movement Monitor
Service to issue messages to the Windows Event application log.
o Log Database Events
to the Windows Event message log. If checked, messages will be sent
to the Application Log with information about access to the Tank and
Operations Manager Database.
o Time Database Access
This parameter instructs the service to generate log files timing the
database access. Two files will be generated to reflect the amount of
time the service waits for database operations to complete. The files
will be created in the installation directory:
MMTimennnn.txt: Time to access the ATOMS_MOVEMENT_TABLE.
MMTimeEvnnnn.txt: Time to access the ATOMS_MOVEMENT_EVENT
table.
nnnn stands for the thread id accessing the database.
o Log Calculations
If checked, a log file will be created with all Level to Volume
calculations.
If you use AtOMS Browser, you need to configure the Aspen Operations
Accounting Connect.
1. Start the Aspen Operations Accounting Connect by clicking Connect
2. Click AtOMS | Service Monitor.
3. Configure the required information on the Service Monitor window.
The Service Monitor window of Aspen Operations Accounting Connect is
responsible for periodic update of tanks and movements in the Aspen
Tank and Operations Manager Database. The following fields are required
for Movement Monitor service:
o Application Server: The server where Aspen Tank and Operations
Manager Server resides. It is expected to be the same machine where
the Movement and Tank Monitor Service are running.

o Cutoff time: The time of the day when it is the end of previous
production day and the beginning of next production day. At the Cutoff
time, the system automatically takes Inventory snapshot for a
movement or tank. For Movement Monitor to activate a movement
successfully, the Cutoff Time needs to be the same as the Beginning
of accounting day displayed in the Movement Detail window.
o Movement monitor (sec): The time interval (in seconds) to activate
the Movement Monitor scan service. The default value of 300 (5
minutes) is recommended.
o RTDB Server: Real Time Database server. The server where the real
time database resides.
o Writeback Field: Defines the field number to be used for storing
calculated monitored data back into IP.21 records. By default, Aspen
Tank and Operations Manager assumes that all IP.21 records used to
read and write data into are defined with the definition record
IP_AnalogDef (the field name where the new calculated value will be
stored is IP_INPUT_VALUE), which determines the field into this
definition where new values should be read and stored. If a different
definition record is used and the field containing the calculated values
is named differently, this field is the place where that field name is
specified.
o Connect String: Shows ODBC data source information of the model.
Model: The ODBC model name to which Aspen AtOMS is connected.
Password: Model password.
User Name: Model user name.
Zone: Use Standard Name of the Time Zone. For example, Pacific
Standard Time.
o Advanced Options:
Debug Level: This parameter controls the amount of information that
is logged to the Windows Event message log. The larger the selected
number, the larger the amount of information that is sent.
Density Conversion Factor: Enter the water density value in this
field, same as the DensityWater value in the Aspen AORA OLOCONFG
data table.
Log Calculations: If checked, a log file is created with all Level to
Volume calculations.
Log DB Event: This parameter controls the amount of information
that is logged to the Windows Event message log. If checked,
messages are sent to the Application Log with information about
access to the Aspen Tank and Operations Manager Database.
Propagate Initial Quality: Defines whether the initial values of
density and %H2O of the tank selected as the control element are
propagated as manual values to other Density and %H2O instruments
in that movement.
Time DB Access: This parameter instructs the service to generate log
files timing the database access. The files are generated to reflect the
amount of time the service waits for database operations to complete.
The files will be created in the installation directory.

The AtOMS | Movment Monitor window of the Aspen Operations Accounting
Connect allows you to view the Movement Monitor Statics.
Click Get Stat to obtain the latest movement monitoring status information.
OK status indicates that the connections to the application server and real
time database server are successful.
Refer to the Aspen Operations Accounting Connect Help for more details
about the Movement Monitor window.
Tank and Operations Manager Tank Monitor

Service
The Tank and Operations Manager tank monitor service is responsible for
periodic update of tank information in the Tank and Operations Manager
database. It runs at a predefined interval to gather tank information, read
current values from the real time database, perform the required calculations
and update the Tank and Operations Manager database with the results.
The key objectives of tank monitor are:
 Update current tank conditions at a predefined time interval.
 Perform calculations defined for each tank and update the Tank and
Operations Manager database
 Store cutoff conditions at the predefined cutoff time
Configuration Steps
1 Use the shortcut created in Start | All Programs | AspenTech | Aspen
Monitors | Configure Tank Monitor. The dialog box titled Aspen Tank
and Operations Manager Tank Monitor will be shown:

The following parameters should be configured in the Tank and Operations
Manager tank monitor service:
o Activation Interval (seconds)
The time interval (in seconds) to activate the tank monitor scan
service. The default value of 300 (5 minutes) is recommended.
o App Server
The server where Aspen Tank and Operations Manager Server resides.
It is expected to be the same machine where the Tank and Operations
Manager tank monitor service is running.
o RTDB Server
The server where the real time database resides. Normally the name
of your ADSA data source.
o Level Deadband
The amount by which the tank level should change to determine if it is
being filled or drained. If the tank level does not change at least by
this amount, it is considered to be in a STEADY state. This number
should be in the same units of measure as the tank levels in the real-
time database.
o Density Conversion Factor in Std Units
Must match the configuration for this parameter in Aspen Operations
Reconciliation and Accounting. This value can be found in the
OLOCONFG table.
o Write back field
Alternative field name when the definition record of calculated
variables in InfoPlus.21 is not IP_AnalogDef. By default, Tank and
Operations Manager assumes that all calculated variables will be
defined by the definition record IP_AnalogDef, in which case the field
name where the new calculated value will be stored is
IP_INPUT_VALUE.

o Cutoff Time (hh:mm:ss)
The time of the day defined as the Cutoff time. Normally, you just
need to set the Hour and Minute here, because only Hour and Minute
are displayed in the Movement Detail dialog box.
IMPORTANT! For Aspen Tank and Operations Manager Movement
Monitor to activate a movement successfully. the Cutoff Time needs to
be the same as the accounting time displayed in the Movement Detail
dialog box.
o ConnectionString
Aspen Operations Reconciliation and Accounting connection
information in the form of “DSNname, username, password, zone”.
Advanced Options:
o Debug Level
to the Windows Event message log. The default value of 0 should be
used. Any number greater that 0 will make the movement monitor
service to issue messages to the Windows Event application log.
o Log Database Events
to the Windows Event message log. If checked, messages will be sent
to the Application Log with information about access to the Tank and
Operations Manager Database.
o Time Database Access
This parameter instructs the service to generate log files timing the
database access. Two files will be generated to reflect the amount of
time the service waits for database operations to complete. The files
will be created in the installation directory:
MMTimennnn.txt: Time to access the ATOMS_MOVEMENT_TABLE.
MMTimeEvnnnn.txt: Time to access the ATOMS_MOVEMENT_EVENT
table.
nnnn stands for the thread id accessing the database.
o Log Calculations
If checked, a log file will be created with all level to volume
calculations.
If you use the AtOMS Browser, you need to configure the Aspen Operations
Accounting Connect.
1. Start the Aspen Operations Accounting Connect by clicking Connect
2. Click AtOMS | Service Monitor.
3. Configure the required information on the Service Monitor window.
The Service Monitor window of Aspen Operations Accounting Connect is
responsible for periodic update of tanks and movements in the Aspen
Tank and Operations Manager Database. The following fields are required
for Tank Monitor service:
o Application Server: The server where Aspen Tank and Operations
Manager Server resides. It is expected to be the same machine where
the Movement and Tank Monitor Service are running.

o Cutoff time: The time of the day when it is the end of previous
production day and the beginning of next production day. At the Cutoff
time, the system automatically takes Inventory snapshot for a
movement or tank. For Movement Monitor to activate a movement
successfully, the Cutoff Time needs to be the same as the Beginning
of accounting day displayed in the Movement Detail window.
o Tank monitor (sec): The time interval (in seconds) to activate the
tank monitor scan service. The default value of 300 (5 minutes) is
recommended.
o RTDB Server: Real Time Database server. The server where the real
time database resides.
o Writeback Field: Defines the field number to be used for storing
calculated monitored data back into IP.21 records. By default, Aspen
Tank and Operations Manager assumes that all IP.21 records used to
read and write data into are defined with the definition record
IP_AnalogDef (the field name where the new calculated value will be
stored is IP_INPUT_VALUE), which determines the field into this
definition where new values should be read and stored. If a different
definition record is used and the field containing the calculated values
is named differently, this field is the place where that field name is
specified.
o Connect String: Shows ODBC data source information of the model.
Model: The ODBC model name to which Aspen AtOMS is connected.
Password: Model password.
User Name: Model user name.
Zone: Use Standard Name of the Time Zone. For example, Pacific
Standard Time.
o Advanced Options:
Debug Level: This parameter controls the amount of information that
is logged to the Windows Event message log. The larger the selected
number, the larger the amount of information that is sent.
Density Conversion Factor: Enter the water density value in this
field, same as the DensityWater value in the Aspen AORA OLOCONFG
data table.
Log Calculations: If checked, a log file is created with all Level to
Volume calculations.
Log DB Event: This parameter controls the amount of information
that is logged to the Windows Event message log. If checked,
messages are sent to the Application Log with information about
access to the Aspen Tank and Operations Manager Database.
Propagate Initial Quality: Defines whether the initial values of
density and %H2O of the tank selected as the control element are
propagated as manual values to other Density and %H2O instruments
in that movement.
Time DB Access: This parameter instructs the service to generate log
files timing the database access. The files are generated to reflect the
amount of time the service waits for database operations to complete.
The files will be created in the installation directory.

The AtOMS | Tank Monitor window of the Aspen Operations Accounting
Connect allows you to view the Tank Monitor Statics.
Click Get Stat to obtain the latest tank monitoring status information. OK
status indicates that the connections to the application server and real time
database server are successful.
Refer to the Aspen Operations Accounting Connect Help for more details
about the Tank Monitor window.
Restarting Tank and Operations Manager

Monitors
The Tank and Operations Manager monitor services must be re-started after
changing any of the configuration parameters discussed in this section.
1 Open the Services applet in Start Menu | Settings | Control Panel |
Administration Tools | Services and locate both Tank and Operations
Manager monitor services.

2 Double-click each service to bring up their Properties dialog box. On the
General tab, use Stop and Start accordingly to restart the service.

Manager Viewer Post Install
Configuration
Perform the following configuration steps to finish configuration for Aspen

Tank and Operations Manager Viewer after the aspenONE installation and
creation of the Tank and Operations Manager database.

Manager Viewer
1 On the desktop, click Start | All Programs | AspenTech | Aspen
Viewer
The first time you run it, the following warning will display to reminder
you to configure database information for Viewer.
If you have configured it before, then this warning dialog will not appear
any more in future. You can skip step 2 and go to step 3 directly.
2 Press OK. The following configuration dialog appears to allow you to
configure relative information:
8 Aspen Tank and Operations Manager Viewer Post Install Configuration 91

On this configuration dialog, you can choose your preference culture,
operating unit of measure, as well as database.
For the database, use the database you created in section “Configure
Aspen Operations Reconciliation and Accounting ODBC Source” as
Advisor Database; Use the one you created in section “Creating a New
Tank and Operations Manager Database” as OMS Database.
3 Press OK. The following form appears:
4 If you want to re-configure some options, you can select File |

Configuration to configure them again:
92 8 Aspen Tank and Operations Manager Viewer Post Install Configuration

The following configuration dialog appears:
5 Press Summaries; the summaries form appears:

Tank and Operations Manager
Viewer Web
Tank and Operations Manager Viewer Web (XBAP) displays a read-only view
of movements, orders and inventory from Internet Explorer. The prerequisite
to use XBAP is to have Aspen Tank and Operations Manager and Aspen
Manufacturing Master Data Manager (mMDM) installed on one computer.
Note: Aspen Tank and Operations Manager Viewer Web (XBAP) only supports
Microsoft SQL server in V12.
You have to configure XBAP before using XBAP. The whole configuration
procedure includes the following two steps:
 Grant User Trust and Permission to Run the XBAP
 Configure mMDM for Aspen Tank and Operations Manager XBAP
Database Support
Grant User Trust and Permission to Run the

XBAP
Tank and Operations Manager Viewer Web (XBAP) works on client machines
after you are granted permission to access the XBAP. To grant the permission,
you can run a batch script, Grant_Atoms_XBAP_Permission.bat, or install the
Aspen certificate manually into the Internet Explorer certificate store.
To Run the Batch Script:

A batch file, Grant_AtOMS_XBAP_Permission.bat, installs automatically during
the XBAP installation procedure. The default directory is C:\Program

Files\AspenTech\AtOMS. The system administrator needs to run this script on
each machine, after installing XBAP, to install the AspenTech certificate into
IE.
To run the script:
1. Click Start | Run, and type cmd in the Run dialog box to open a
command window.
2. Type “<directory of Grant_AtOMS_XBAP_Permission.bat> localhost.” By
default, it should be “C:\Program
Files\AspenTech\AtOMS\Grant_Atoms_XBPA_Permission.bat localhost.”
Press Enter.
3. Type Yes to the confirmation question and press Enter. The script begins
running.
A message appears, indicating the operation is successful when the script
finishes.
4. Type “<directory of Grant_Atoms_XBAP_Permission.bat>
AtOMSXbapServerName.” By default, it should be “C:\Program
Files\AspenTech\AtOMS\Grant_Atoms_XBAP_Permission.bat
AtOMSXbapServerName.”
Here, the AtOMSXbapServerName refers to the server name where the
XBAP will be deployed.
After both commands are successfully executed, IE will recognize AspenTech
certificate as a trusted source via its digital certificate.
To Install mycrdentials.pfx Manually:

1. Open IE and click Internet Options from the Tools menu. The Internet
Options dialog box appears.
2. Click the Content tab. In the Certificates area, click Certificates. The
Certificates dialog box appears.
3. Click the Trusted Root Certification Authorities tab in the Certificates
dialog box and click Import…. The Certificate Import Wizard dialog
box appears.
4. Click Next to the File to Import page. Click Browse… and click on the
mycredentials.pfx file. Click Next.
Note: The mycredentials.pfx is not installed with the Aspen Tank and
Operations Manager. Please contact with our Customer Support to get the
mycredentials.pfx if you need the certificate.
5. On the Password page, leave the Password field blank and click Next to
the Certificate Store page.
6. Click the Place all certificates in the following store option and click
Next.
7. Make sure the You have specified the following settings: field
displays the correct certificate information. Click Finish to exit the
certificate import wizard.
8. A Security Warning dialog box will appear, asking you to confirm the
installation of the certificate. Click Yes to install or click No to cancel the
installation.

You will be back to the Certificates dialog box after the certificate
installation.
9. Click the Trusted Publishers tab in the Certificates dialog box. Click
Import…, the Certificate Import Wizard dialog box appears.
10. Repeat step 4 to step 7 to add the mycredentials.pfx into the Trusted
Publishers.
After completing all steps, the certificate is installed into IE. The next step is
to configure mMDM for Aspen Tank and Operations Manager XBAP database
support.
Configure mMDM for Aspen Tank and

Operations Manager XBAP Database
Support
Tank and Operations Manager Viewer Web (XBAP) must get database
connection information from mMDM. So the mMDM database must be
installed and configured to provide XBAP the database information.
Note: The mMDM database can be installed by using Aspen mMDM

Administrator.
To Configure mMDM for Aspen Tank and Operations

Manager XBAP Database Support:
1. Open Aspen mMDM Editor from Start | All Programs | AspenTech |
AspenONE Infrastructure | Aspen mMDM Editor V12. The Aspen
mMDM Editor V12 – aspenONE dialog box appears.
Check to see if Aspen Tank and Operations Manager and Aspen Operations
Reconciliation and Accounting share the same database. If Aspen Tank and
Operations Manager and Aspen Operations Reconciliation and Accounting use
two separate databases, execute step 2 to step 11 to create a new alias
domain for Aspen Tank and Operations Manager first. If Aspen Tank and
Operations Manager and Aspen Operations Reconciliation and Accounting use
the same database, then go straight to step 12.
2. Click Alias | Alias Domain Types from the tree view in the Aspen
mMDM Editor.
3. Right-click the mouse in the Alias Domain Type table displayed on the
right and click New… from the shortcut menu. The New (Alias Domain
Type) – mMDM Definition Editor dialog box appears.
4. On the General tab, enter the Alias Type Name (i.e. Uncategorized) and
Description.
5. On the Details tab, select Database Connector as the type of the
Application Connector.
6. Click OK. You can see the newly added alias type in the Alias Domain
Types table.
7. Click Alias | Alias Domains from the tree view in the mMDM Definition
Editor.

8. Right-click the mouse in the Alias Domains table displayed on the right
and click New… from the shortcut menu. The New (Alias Domain) –
mMDM Definition Editor dialog box appears.
9. On the General tab, enter the Alias Domain Name and Description.
10. On the Details tab, select the newly created alias domain type (i.e.
Uncategorized) as the domain type.
11. Click … on the right side of the Data Source area. The mMDM Database
Connection Wizard dialog box appears.
12. If Aspen Tank and Operations Manager and Aspen Operations
Reconciliation and Accounting use the same database, click Alias | Alias
Domains from the tree view in the Aspen mMDM Editor once it is open.
13. Double click Aspen Advisor in the Alias Domains table displayed on the
right. The Aspen Advisor (Alias Domain) – mMDM Definition Editor
dialog box appears.
14. On the Details tab, click … on the right side of the Data Source area.
The mMDM Database Connection Wizard dialog box appears.
15. Select the Database Type and Server Name, and click Next.
16. On the Specify Connection Information page, enter the User Name
and Password, select the Database Name, and select the Store this
information using encryption check box if you want to encryption your
connection string. Click Next.
17. Ensure the information displayed in the Summary of Wizard Tasks is
correct. Click Finish to exit the wizard.
18. You can see the connection string in the Data Source area on the Details
tab. Click OK and you will return to the Aspen mMDM Editor main dialog
box.
19. Click Class | Classes from the tree view in the Aspen mMDM Editor.
20. Right-click the mouse in the Classes table displayed on the right and click
New… from the shortcut menu, the New (Classes) – mMDM Definition
Editor dialog box appears.
21. On the General tab, enter the Name (i.e. OMSLocation) and
Description.
22. On the Details tab, find Boolean under the Intrinsic folder and drag it
to the Design field on the right, under the class (i.e. OMSLocation) you
just created.
23. Rename the Boolean property to IsMass in the Design field.
24. In the Properties area on the bottom left, set the DefaultValue as
False.
25. Click the Categories tab located at the bottom of the tree view. Drag
Domain Namespace from the tree view to the Design field, under the
class (i.e. OMSLocation) you just created.
26. Rename the domain namespace as Advisor, and set the DefaultValue as
Aspen Advisor. Keep other properties as default.
27. Repeat step 25 and step 26 to add a domain namespace named OMS to
your new created class (i.e. OMSLocation).
o If your Aspen Tank and Operations Manager and Aspen Operations
Reconciliation and Accounting share the same database, select Aspen
Advisor as the DefaultValue of the OMS domain namespace.

o If your Aspen Tank and Operations Manager and Aspen Operations
Reconciliation and Accounting use different database, set the
DefaultValue of the OMS domain namespace as the alias domain you
created at the beginning (i.e. Uncategorized).
28. Click OK to finish the setting and to return to the Aspen mMDM Editor
main dialog box.
29. Click Generic | Generic Item Types from the tree view in the Aspen
mMDM Editor.
30. Right-click the mouse in the Generic Item Types table displayed on the
right and select New… from the shortcut menu, the New (Generic Item
Types) – mMDM Definiton Editor dialog box appears.
31. On the General tab, enter the Name (i.e. OMSLocation) and
Descritpion, then click OK to finish.
32. Click Generic | Generic Items from the tree view in the Aspen mMDM
Editor.
33. Right-click the mouse in the Generic Items table displayed on the right
and select New… from the menu, the New (Generic) – mMDM
Definition Editor dialog box appears.
34. On the General tab, enter the Name (i.e. LakeCharles) and Descritpion.
35. On the Details tab, select the new created generic item type (i.e.
OMSLocation) from the Type list.
36. In the Classes tab, drag the class you create earlier (i.e. OMSLocation)
from the tree view to the field on the right.
Note: You can modify the DefaultValue of the class here.
37. Click OK to save the setting and return to the Aspen mMDM Editor main
dialog box.
The mMDM configuration for Aspen Tank and Operations Manager database
support is complete. You can now exit the Aspen mMDM Editor V12 –
aspenONE.
Access Aspen Tank and Operations

Manager XBAP from IE
After completing these settings, you are now able to access XBAP from
Internet Explorer.
1. Open IE and enter the following address:
http://AtOMSXbapServername:port/AspenTech/OMS/SmartClient/Aspente
ch.MSC.OMS.Xbap.xbap?<GenericItemType>=<GenericItemName>
Here, the AtOMSXbapServerName refers to the machine name where you
install Aspen Tank and Operations Manager. The default port is port 80.
You do not need to specify the port number when you use the default
port.
2. Press Enter, the movements, orders and inventory information will
display in IE.

Permission Errors Troubleshooting
Permission errors may appear when trying to run XBAP. The “Trust Not
Granted” error is the most typical error you will encounter.
Execute the following to check if all the configurations are properly executed
when the “Trust Not Granted” error appears:
1. Open IE, click Internet Options from the Tools menu. The Internet
Options dialog box appears.
2. On the Security tab, click the Trusted Sites and click Sites. The
Trusted sites dialog box appears.
3. Ensure http://localhost and http://AtOMSXBAPServername/ are
trusted sites.
Here the AtOMSXBAPServername refers to the machine name where you
installed Aspen Tank and Operations Manager. Close the dialog box.
4. On the Security tab, click Custom Level. The Security Settings –
Trusted Sites Zone dialog box appears.
5. Ensure all the settings under the Downloads section are enabled.
6. Ensure you select Automatic Logon with current user name and
password for the User Logon.
If all the settings are correct, but you still encounter the same error, then you
will need to use the Code Access Security Policy Tool (Caspol.exe). The
Caspol.exe is available from:
http://msdn.microsoft.com/en-us/library/cb6t8dtz(v=VS.80).aspx.
Basically, the Code Access Security Policy Tool is used to grant the machine
level permissions to XBAP.
Caspol.exe doesn’t allow duplicated groups. You must check if the desired
groups are added and make sure there is no duplication.
1. Click Start | Run, and type cmd in the Run dialog box to open a
command window.
2. Type “<directory of Caspol.exe> Caspol.exe/lg.” The Caspol.exe usually
comes with Microsoft.NET Framework. By default, the command line
should be “C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
Caspol.exe/lg.”
Press Enter.
3. This command lists all the groups that have been added to the policy.
Check the URLs added by running Grant_Atoms_XBAP_Permission.bat,
and make sure there is no duplication.
4. If you find any duplicated URLs, run the command “<directory of
Caspol.exe> Caspol.exe/rg [groupname]” to remove the duplicated URLs.
5. Locate the tool Mage.exe, the usual directory is C:\Program
Files\Microsoft.NET\SDK\v2.0\Bin.
Note: You need to sign the manifest of the Click-Once deployments
before using Mage.exe.
6. Type “<directory of Mage.exe> Mage.exe-cc” in the command window to
clear the application cache. This removes any remaining downloaded files
from previous launch of XBAP.

By doing all the above, there should be no permission issues when you use
XBAP.
Manager Importer Post
Install Configuration
Perform the following configuration steps to finish configuration for Tank and
Operations Manager Importer after the aspenONE, EIF and ODM installation
and creation of the Tank and Operations Manager database.
Note: Aspen Tank and Operations Manager Importer is only supported on

SQL Server 2005. Only server machine needs the configuration for Aspen
Tank and Operations Manager Import. Because EIF is only required on the
Tank and Operations Manager server.
Configure Aspen Tank and

Operations Manager Importer
Aspen Tank and Operations Manager Importer provides a visual configuration
editor for Tank and Operations Manager Adapter.
1. On the desktop, click Start | All Programs | AspenTech | Aspen
Importer Configuration
2. Fill the necessary information in the Importer Configuration dialog box.
9 Aspen Tank and Operations Manager Importer Post Install Configuration 101
Operations Accounting
o Server – the server with which to connect to the Aspen Operations
Accounting database.
o Database – the database on the selected server.
o Integrated Security – check box to enable Windows authentication.
o User – the user name with the permission to access the database.
o Password – the password specific with the user name.
Tank Ops. Manager
o Server – the server with which to connect to the Aspen Tank and
Operations Manager.
o Database – the database on the selected server.
o Integrated Security – check box to enable Windows authentication.
o User – the user name with the permission to access the database.
o Password – the password specific with the user name.
ODM Domain – The domain name used to retrieve mappings between
alias names and canonical IDs in the ODM database.
Interface Name – The application name for the user in audit table.
Message Topic – The topic in the Windows Service Access.
Interface Id – A numeric value representing this application. It is used in
different tables as an identity of this application.
Volume Attribute Id – If measurement type is mass and this setting is
enabled, it will create a movement attribute based on the setting value. If
the value is invalid, no movement attribute is created.
Mass Attribute Id – If measurement type is volume and this setting is
enabled, it will create a movement attribute based on the setting value. If
the value is invalid, no movement attribute is created.
Vessel Attribute Id – This is a default movement attribute to be created
regardless measurement type if this setting is enabled. If the setting value
is invalid, no movement attribute is created.
102 9 Aspen Tank and Operations Manager Importer Post Install Configuration
Epsilon Precision – A threshold value to determine if a coming value
should be ignored or not. Only a value greater than the setting value will
be accepted.
Tank Area Overriding – The area of the source tank is assigned as the
area of the movement if this flag is true. Otherwise, the area of the
destination tank is used as the area of the movement.
Note: Tank Area Overriding applies to tank-to-tank movements only.
Ignore Gas Movements – Movements of gases are ignored when this
check box is selected.
Persist Batch Id – The batch ID is saved when this check box is
selected.
Ignore Non-Tank Movements – The movement is ignored if no tanks
are involved if this check box is selected.
Delete Pending Movements – The pending movements are deleted if
this check box is selected. Otherwise they are updated.
Notes: The fields with asterisk (*) must be configured. Others are
optional.
9 Aspen Tank and Operations Manager Importer Post Install Configuration 103
104 9 Aspen Tank and Operations Manager Importer Post Install Configuration
10 Aspen Tank and
Operations Manager Tank
Calculator Post Install
Configuration
Perform the following configuration steps to finish configuration for Tank and
Operations Manager Tank Calculator after the installation and configuration of
Aspen Tank and Operations Manager and Aspen Operations Reconciliation and
Accounting.
Configure Aspen Tank and

Operations Manager Tank
Calculator
1. Open global.asa file with text editor. This file is usually under the folder
c:\inetpub\wwwroot\Aspentech\TankCalculator. In the global.asa file,
enter the proper connection information and save the changes.
o ModelServer is the name of the computer that runs Aspen Operations

Reconciliation and Accounting Model.
o ModelName is ODBC data source name.
10 Aspen Tank and Operations Manager Tank Calculator Post Install Configuration 105
o ConnectionString is the Aspen Operations Reconciliation and
Accounting connection information in the form of “DSNname,
username, password,”.
o LOG_LEVEL is the diagnostic message debug level. 255 is the
common value for most messages, zero means no messages.
o LOG_FILE is the path and name of the log file containing diagnostic
messages.
2. Open MS Internet Explorer, Click Tools on the Menu bar. From the
Tools drop-down list, select Compatibility View settings. Add Model
Server website to Compatibility View.
106 10 Aspen Tank and Operations Manager Tank Calculator Post Install Configuration
3. MS Internet Explorer, click Tools on the Menu bar. From the Tools
drop-down list, select Internet options. Under Security tab, select
Local Intranet. Click Sites to open Local intranet window, and add
http://<servername> to the zone.
4. From MS Internet Explorer, click Tools on the Menu bar. From the
Tools drop-down list, select Internet options. Under Security tab,
select Trusted sites. Click Sites to open Trusted sites window, and add
http://<servername> to the zone.
5. Open the Aspen Tank and Operations Manager Tank Calculator Web client
page http://<AtOMSWebServer>/TankCalculator. Aspen Tank
Calculator opens.
11 Operations Accounting
Interface Post Install
Configuration
Note: If your site does not use Aspen Operations Reconciliation and
Accounting for daily data reconciliation, you can skip this section.
The Operations Accounting Interface is an optional Tank and Operations
Manager feature that reads tank and movement transactions from the Tank
and Operations Manager database to be used by the Aspen Operations
Reconciliation and Accounting (Operations Accounting) application. Those
readings are written on Operations Accounting’s import tables to be imported
to Operations Accounting’s data tables using the standard Operations
Accounting’s Connect utility which usually must be executed manually by the
Operations Accounting engineer. However, Operations Accounting Interface
can, if properly configured, execute automatically and remotely to Aspen
Operations Reconciliation and Accounting Connect.
The Operations Accounting Interface software is installed from the aspenONE
media whenever the Tank and Operations Manager sub-feature Interfaces is
selected during a standard or server installation of Tank and Operations
Manager.
The Operations Accounting Interface connects to both databases Aspen
Operations Reconciliation and Accounting and Tank and Operations Manager
and therefore it is ODBC and OLEDB compliant respectively.
This section will help you to decide how to adjust parameters inside the
Operations Accounting Interface to properly run this application.
Important:
 The Operations Accounting model should be installed and a reference to
the Operations Accounting Connect application has to be made. If not
done before, go the Operations Accounting directory (normally
C:\Program Files\AspenTech\Advisor) and open (double-click)
IIAutoHist.exe. You may close this application immediately.
 For the Operations Accounting Interface to function properly, you need to
launch Operations Accounting Interface Preferences page once and update
the settings.
11 Operations Accounting Interface Post Install Configuration 111

Operations Accounting ODBC
Source
The Operations Accounting Interface requires an ODBC source to
communicate with the Operations Accounting database. This is the same data
source already configured in the Chapter titled “Post Install ConfigurationPost
Install ConfigurationPost Install ConfigurationPost Install ConfigurationPost
Install ConfigurationPost Install ConfigurationPost Install ConfigurationPost
Install ConfigurationPost Install ConfigurationPost Install ConfigurationTank
and Operations Manager Server Post Install Configuration”, section
“Configure Aspen Operations Reconciliation and Accounting ODBC
Source”. You will need to specify this ODBC source in Operations Accounting
Interface to open the Operations Accounting model. Please refer to that
section for details if it the ODBC data source has not been configured yet. If
the data source is already configured, there is nothing else to be done for this
step.
Duplicate Tank and Operations

Manager OLEDB Data Link File
The Operations Accounting Interface requires an OLE DB Data Link file to
communicate with your Tank and Operations Manager database. The interface
expects to find the .UDL file AtOMS.udl in the same directory where the
utility resides, usually in folder
<INSTALL_ROOT>\Aspentech\AtOMS\Interfaces\AtOMSAdvConnect.
So the objective of this step is to define an AtOMS.udl file with the
connectivity information to your Tank and Operations Manager database.
However, if everything has been properly configured, this file should be a
duplicate of the udl file configured in the Chapter above titled “Tank and
Operations Manager Server Post Install Configuration”, section “Configure
Tank and Operations Manager Workstation” under the paragraph
dedicated to enter configuration in the Server tab.
You can copy the udl file created in the previous step to the directory where
Operations Accounting Interface expects to find it and rename it AtOMS.udl
if the source file has a different name.
112 11 Operations Accounting Interface Post Install Configuration

Start the Operations
Accounting Interface
Application
The sections that follow use the Operations Accounting Interface application
to provide forms that configure operating functions.
To start the interface’s main program, run the shortcut Start Menu |
Programs | AspenTech | AMS Manufacturing Suite | Aspen Tank and
Operations Manager | Operations Accounting Interface. A window
similar to the following appears the first time it is run:
Preferences Form
The Preferences dialog form allows you configure several Operations
Accounting Interface options.
Note: We strongly recommend adjusting the parameters in this section by

using the form provided and not by editing the settings file. However, some
parameters do not have a form to adjust them yet. For those specific
parameters, you will be directed to adjust them directly on the settings file.
1 Click File | Preferences. The Preferences dialog box appears.

2 Adjust on this form as necessary the following parameters
Section/Parameter Meaning
Tank Reading Options

Send Tank Gauges: Check to send tank gauges to Aspen Operations
Reconciliation and Accounting.
Level gauge and Volume Send Level or Volume measurements to
Operations Accounting option.
Allow Bad Properties Option used to pass properties with BAD status to
Operations Accounting. It is not recommended to
use this option
Fraction Scale When using Fractional Gauges, enter the scale in
fractions of an inch used. If using Decimal
gauges, select 0.
Movement Transfer Options
Send Movements Check to send movement transactions to
Operations Accounting.
Integrator Mass and Volume Check integrator value to be sent option:
Volume/Mass
User Defaults
Model ODBC DSN Connection to Operations Accounting
Database
UserName Operations Accounting user with privileges to
open, close and import.
AdvConn Server Server where Operations Accounting Connect was
installed, if it was not installed locally.
Auto Run Connect Run automatically Operations Accounting Connect
option
Log SQL Check to send detailed database access to the
Log file.
Line Displacement
Line Displacement Detection Check to activate this option.

Tolerance Quantity Amount in selected Movement Engineering Units
(Volume or Mass) of tolerance for Line
Displacement Detection. A displacement
movement will be detected if the target quantity
of the movement is equal to the capacity of the
line used plus or minus the tolerance.
Configuring Grid Colors

The Select Colors dialog form allows you to customize the grid colors.
Note: It is strongly recommended that the parameters in this section be

adjusted using the form provided and not by editing the settings file.
However, some parameters do not have a form to adjust them yet. For those
specific parameters only, the reader will be directed when necessary to adjust
them directly on the settings file.
1 Click the Options | Colors menu option to bring up the Select Colors
form.
2 Click on any of the blocks next to Grid, Font, or Error to bring up their
respective color palette from which you can either select a new color, from
the colors already available, or define your own custom colors.

Configuring Rounding options
You can configure Operations Accounting Interface to round some instruments
to a specified number of decimal places. Locate the RoundInfo section of the
configuration file (AspenTech.MSC.Settings.xml) and select a suitable number
of decimal places for each type of instrument. See Appendix A for detailed
information about the settings file and the parameters defined within.
Preventing Double
Compensation in Operations
Accounting Interface
When Operations Accounting Interface is configured to transfer integrator
volumes to Operations Accounting as explained in the Preferences form
earlier in this chapter, it needs to prevent double compensation on net
volumes transferred. In order to do so, Operations Accounting Interface
would need for you to supply:
 The base temperature used in Operations Accounting volume
compensation
 The units of measurement for %BSW in Operations Accounting
 The units of measurement for density of liquids in Operations Accounting
Please locate the Property Config section in the
AspenTech.MSC.Settings.xml configuration file and enter all the parameters
indicated. See Appendix A for detailed information about the settings file
and the parameters defined within.

Configuring Data Propagation
in Tank and Movement Events
You can configure data propagation in tank and movement events to improve
the working efficiency by minimizing the need to enter new readings in
multiple places.
These settings are not initially available in the AspenTech.MSC.Settings.xml
configuration file. You can choose from the lines below and copy them under
the [Common] section of the AspenTech.MSC.Settings.xml file:
<setting name="Propagation">
<setting name="ActivateMovementFromTankCurrentToStart"
type="string" value="True"/>
<setting name="FromTankCutoffToTankCurrent" type="string"
value="True"/>
<setting name="FromMovementCutoffToTankCurrent" type="string"
value="True"/>
<setting name="FromMovementStartToTankCurrent" type="string"
value="True"/>
<setting name="FromMovementEndToTankCurrent" type="string"
value="True"/>
<setting name="FromTankCurrentToMovementCurrent" type="string"
value="False"/>
<setting name="CompleteMovementFromTankCurrentToEnd"
type="string" value="True"/>
<setting name="FromTankCutoffToMovementCutoff" type="string"
value="True"/>
</setting>
Note:
 If a more current value exists, the data are not propagated. For
Movements and Cutoffs, Tank and Operations Manager uses the Event
Time for the comparison. For example, if an operator closes a movement
with an end time of 11:00, and then manually updates values, while the
tank current conditions are updated at 11:15, the data are not propagated
from the movement to the tank. Because the update time 11:15 of the
tank current conditions is more current than the Movement event time
11:00.
 The instrument values are not propagated backwards in time. For example,
after the activation of a movement, the changes you make to the tank
current conditions are not propagated to the movement. And after the
tank cutoff, the changes you make to the tank current conditions are not
propagated to the tank cutoff.
 Tank Current to Cut-Off Propagation ALWAYS occurs and does not require
a setting in AspenTech.MSC.Settings.xml file.
See Appendix A for detailed information about the settings file and the
parameters defined within.

12 Aspen Tank and
Operations Manager Client
Post Install Configuration
The steps to properly configure an Aspen Tank and Operations Client after the
installation are:
1. Configure Aspen Operations Reconciliation and Accounting ODBC source
2. Configure Aspen Tank and Operations Manager Config
3. Update firewall settings in the Server Machine
Configure Aspen Operations

ODBC Source
Aspen Tank and Operations Manager requires an ODBC Data Source to Aspen
Operations Reconciliation and Accounting.
1 Log on with the user account used to install Tank and Operations Manager
Client.
2 Invoke the Data Sources (ODBC) tool. Click Start | Settings | Control
Panel | Administrative Tools and click the ODBC Data Sources (32-
bit). The following screen will appear:
12 Aspen Tank and Operations Manager Client Post Install Configuration 119
3 Click Add. The Create New Data Source window displays all the ODBC
drivers available in your computer. Select the native driver for your
database. A native driver is a driver provided by the database
manufacturer. E.g.: Oracle for an Oracle database instead of the
Microsoft ODBC for Oracle. Click Finish to bring up the database
specific dialog box.
Create New Data Source for SQL
120 12 Aspen Tank and Operations Manager Client Post Install Configuration
Create New Data Source for Oracle
MSSQL Specific ODBC configuration

1 For SQL Server, a dialog like the following will be shown. Enter the
corresponding DSN Source Name, Description, and Server. Note that the
Name should be unique. Click Next to continue.
2 Select the authentication method to access the Tank and Operations

Manager database and then click Next to continue
3 Select the Aspen Operations Reconciliation and Accounting database from
the Change the default database to drop-down menu.
4 Click Next to bring the Microsoft SQL Server DSN Configuration

window (intentionally omitted) and click Finish to bring the summary
page ODBC Microsoft SQL Server Setup.
5 Verify that the information on the summary is correct and then click Test
Data Source to reconfirm that the information entered connects to the
desired database. If successful, then click OK to exit out of the
configuration.
Oracle specific ODBC configuration
1 For Oracle, a dialog box similar to the following will be shown. Enter the
corresponding data in the fields Data Source Name, Description, TNS
Service Name (database server name: port number/database sid or
database server IP address:port number/database sid), and User ID.
Note that the Source Name must be unique. For example:
2 Click Test Connection to verify that the database connection with the
configuration entered is successful. You will be prompted to enter the
password of the User ID specified.
Manager Config for Client
This step primarily provides the Tank and Operations Manager applications
with the necessary information to access both the Aspen Operations
Reconciliation and Accounting data and the Tank and Operations Manager
database.
Start the Tank and Operations Manager Configuration Tool, see Chapter 7
Configure Aspen Tank and Operations Manager Config for specific
descriptions for each parameter:
Here, we directly use default values.
1 Click the Server tab to specify and define the contents of OLE DB UDL file
that will be used to obtain connect information to your Tank and
Operations Manager database. If the text box File is empty, click the
browser button to select the path and file name of the UDL file. The Data
Link Properties dialog box appears. We recommend selecting the path to
the folder where Tank and Operations Manager was installed and
AtOMS.udl as the filename, but any path or name will work. After the
filename has been selected and shows in the textbox, click Properties to
bring up the Data Link Properties dialog box, which is used to configure
the Tank and Operations Manager Data Source.
3 Click the Provider tab and select the native OLE DB provider specific to
your database and then click Next. The following dialog box depends on
the Provider selected.
4 For Microsoft OLE DB Provider for SQL Server: in the Select or enter
a server name field, enter the name of the server where your Tank and
Operations Manager database is located, and choose the authentication
method to access your database in the section Enter information to log
on to the server. If you use a specific user name and password, please
do NOT specify a blank password. Also make sure that the Allow saving
password is selected. Select your Tank and Operations Manager
database from the list in Select the database on the server. Click Test
Connection to make sure that the information provided allows a
successful connection to the specified database.
5 For Oracle Provider for OLE DB, the following dialog box is brought up.
Enter in Data Source the name of the local TNS service that connects to
your Tank and Operations Manager (and Aspen Operations Reconciliation
and Accounting) database. Specify the User name and Password used
to log on to the Tank and Operations Manager database. Click Test
Connection to confirm that the provided information allows a successful
connection to the specified database.
6 Click OK to leave the Data Link Properties box and return to the Aspen
Tank and Operations Manager dialog box. At this point you could click
Accept to save the configuration made until this point, as seen in the
following figure.
7 Click the Tools tab; in here, specify the path and file name of the Tank
and Operations Manager Administrator and Configuration tools so these
can be invoked from within other applications. Click the respective browse
buttons to point to where the utilities are located. You can click Accept
again afterwards.
8 Click the Debugging tab; in here you will define whether diagnostic
messages should be output from the Client application and their level of
detail.
9 Select the Debug Level from the list proposed and then click Accept to
save your choice.
10 Click Exit to terminate the Tank and Operations Manager Configuration
application.
Update Firewall Settings in the
Server Machine
This step finalizes the Aspen Tank and Operations Manager Client Post Install
Configuration. When the client and server are located at different machines,
the client machine is not able to access the server machine database. This
step enables the connection.
1 Log on with the user account to the server machine.

2 To update the firewall settings, click Start and search for Windows
Firewall with Advanced Security, right-click and Run as
administrator.
3 In the left pane, click Inbound Rules and left-click New Rule in the
upper-right navigation pane Actions.
4 Select Program from the Rule Type List. Then, click Next.
5 Specify the path and file name. Click the Browse… button to point to the
AtOMSMonitor.exe file location, and then click Next.
6 Choose Allow the connection for the Action, and click Next.
7 Check all the Boxes (Domain, Private, Public) to ensure the server
machine enables the connection.
8 Finally, enter the name for the rule and click Finish.
9 The same steps above to create the create the new inbound rule for
AtOMSTankMonitor.exe.
13 Populate Aspen Tank and
Operations Manager
Database
This section provides general information for populating an Aspen Tank and
Operations Manager database version 2006 or later. Emphasis is made in the
interdependency between Tank and Operations Manager and Aspen
Operations Reconciliation and Accounting, essential for the normal and correct
operation of Tank and Operations Manager.
Overview
Some basic information about your site must be inserted in the Tank and
Operations Manager database, such as tanks, lineups, field instruments, etc.,
some of which must be obtained from the Aspen Operations Reconciliation
and Accounting (Operations Accounting) database and some must be
obtained from the real-time database (RTDB).
After the Tank and Operations Manager database is initialized, Tank and
Operations Manager will use the Operations Accounting calculation engine to
perform volume and tank related calculations.
Important: Even if Operations Accounting is not used at the plant for data
reconciliation, Tank and Operations Manager still needs these functions from
Operations Accounting.
Tank and Operations Manager accesses current values from the RTDB
instruments defined in the Node Instrument table to perform tank and
movement monitoring functions.
Populating Methods
Therefore, populating the Tank and Operations Manager database will consist
in propagating some of the Operations Accounting and RTDB entities into
Tank and Operations Manager Tables, among others:
 Tanks
 Node Instruments
13 Populate Aspen Tank and Operations Manager Database 135

 Lineups (optional)
 There are a number of ways to extract data from Operations Accounting
and the RTDB for the purpose of completing the information to be inserted
into the Tank and Operations Manager database tables. Most of the ways
involve using Excel spreadsheets or add-ins, VBA programming,
intermediate MS Access databases tables, or a combination of all the
above.
 Alternatively, you can use the utility provided by Tank and Operations
Manager called Admin to manually create tanks, node instruments, and
lineups, etc. in your plant. For specific details about how to create these
entities with the Admin, please consult the Aspen Tank and Operations
Manager Admin Tool Help.
136 13 Populate Aspen Tank and Operations Manager Database

14 Upgrading Aspen Tank
and Operations Manager
This chapter provides general information and procedures for upgrading Tank
and Operations Manager.
Overview
Aspen Tank and Operations Manager can be upgraded in the following ways:
 Upgrade to V12 from V11, V10, V9, V8.8, V8.7, V8.5, V8.0, V7.2 or V7.3
by clicking on the V12 media download or inserting a V12 USB drive and
selecting Upgrade or Repair Existing Products.
 Upgrade from versions V7.1 and earlier by removing your old version of
Aspen Tank and Operations Manager and reinstalling V12, as described in
Chapter 3.
Caution:
If you have previously installed more than one Aspen Manufacturing Suite
product on the same computer, you must upgrade all previously installed
products at the same time. If you are also installing an additional Aspen
Manufacturing Suite product, you may install it at the same time as you
perform the upgrades.
Aspen Infoplus.21 32bits is not compatible with Aspen AtOMS V12 in the
same machine. If you want to install Aspen Infoplus.21 and Aspen AtOMS in
the same machine, it is recommended to back up your data, uninstall Aspen
Infoplus.21 32bits, and install Aspen Infoplus.21 64bits. For details about
Aspen Infoplus.21 upgrade, please refer to Aspen Infoplus.21 documents.
Before You Upgrade

 Read the aspenONE Deployment Guide. See aspenONE Documentation.
 Read the Aspen Tank and Operations Manager Release Notes.
 Read this manual in its entirety before starting your upgrade.
14 Upgrading Aspen Tank and Operations Manager 137

 Confirm the system requirements for Tank and Operations Manager. For
details, see the “System Requirements” section in the “Overview”
chapter.
 Check the system requirements for the ADSA Directory Server so that you
can install it at the same time as you install Tank and Operations Manager
or InfoPlus.21.
Note: For more information, see the Aspen Data Source Architecture
Installation Guide.
 Confirm that the Software License Manager (SLM) is installed and running.
Obtain IP address/name of the SLM server. For more details, see the
Software License Manager (SLM) Installation and Reference Guide.
 Confirm the Aspen Framework server or Aspen Local Security server is
installed and running. If you are planning to use the Aspen Local Security
server and it has not been installed, check its system requirements so that
you can install it at the same time as you install Tank and Operations
Manager or InfoPlus.21.
Note: The Operating System or platforms upon which Aspen Framework
or Aspen Local Security may be installed are listed in the Aspen
Framework Server Installation Guide or the Aspen Local Security Server
Installation Guide.
 Ensure you have the required permissions. See “Checking Installation
Account Privileges” in the “Overview” chapter.
 Upgrade the security server. See the “Upgrading the Security Server”
section in this chapter.
 Complete a system backup. See the “Completing a System
BackupCompleting a System Backup” section in this chapter.
 Save a backup of your database. See the “Backup the Tank and
Operations Manager database and others” section in this chapter.
 Shut down InfoPlus.21. See the “Shutting down InfoPlus.21” section in
this chapter.
 Shut down the Microsoft SQL Server if it is running on the same computer
to which you will install. See the “Shutting down Microsoft SQL
Server” section in this chapter.
 Shut down services. See the “Shutting down services” section in this
chapter.
 Duplicate your Tank and Operations Manager directory tree. See the
“Duplicate the Tank and Operations Manager directory tree” section
in this chapter.
Upgrading the Security Server

When upgrading from Tank and Operations Manager versions 2006 and
above, you may also be upgrading the Aspen Framework server or Aspen
Local Security server. Upgrade the security server if desired. For more
information, see the Aspen Framework Server Installation Guide or the Aspen
Local Security Server Installation Guide.
138 14 Upgrading Aspen Tank and Operations Manager

Completing a System Backup
AspenTech recommends that you back up your system before you begin the
upgrade.
Backup the Tank and Operations Manager

database and others
Use the respective SQL Server or Oracle Enterprise Manager to perform a
backup of your Tank and Operations Manager database. If the Aspen
Operations Reconciliation and Accounting database is installed separate from
the Tank and Operations Manager tables, then you should backup this
database as well.
Shutting down InfoPlus.21

To shut down InfoPlus.21:
1. Click Start | All Programs | AspenTech | Aspen Manufacturing Suit
| Aspen InfoPlus.21 | InfoPlus.21 Manager. The Aspen InfoPlus.21
Manager tool is displayed.
2. Clear the START@BOOT checkbox.
3. If there are one or more tasks in the Running Tasks list, click STOP
InfoPlus.21. This will shut down InfoPlus.21. The Running Tasks list
will be emptied and the status line at the bottom will display the text
InfoPlus.21 has been stopped successfully.
4. Close the Aspen InfoPlus.21 Manager dialog.
Shutting down Microsoft SQL Server

If Microsoft SQL Server is running on the machine on which you are installing
InfoPlus.21, you must stop Microsoft SQL Server.
Shutting down services

Important: You must stop all AspenTech services except the Software
License Manager Service before upgrading/uninstalling.
To shut down associated services:
1 Make sure that you are logged on using the administrator account, or an
account that is in the administrator group.
2 Click Start | Settings | Administrative Tools | Control Panel.
3 Double-click the Services icon.
4 In the Services dialog box, stop:
 All Aspen services (These services will depend on the Aspen software that
you have on that computer.)
o Aspen Data Source Directory
o Aspen Local AFW Trustee Server

o Aspen Registry Security Server
o Aspen OMS Movement Monitor
o Aspen OMS Tank Monitor
o Aspen SQLplus Authorization Server
o Aspen Timezone Information
 Each InfoPlus.21 Task Service for groupXXX service (or in the case of
version 4, Aspen InfoPlus.21 Task Service)
 InfoPlus.21 Browser service
 CIM-IO Manager service
 NobleNet Portmapper for TCP service
 IIS Admin Service
Duplicate the Tank and Operations Manager

directory tree
Copy and rename the AspenTech\AtOMS\Interfaces\AtomsAdvConnect
directory tree so key configuration files are preserved for restoration after the
upgrade:
 The OLE DB UDL link files
Upgrading Tank and Operations

Manager
Complete all steps in the “Before You Upgrade” section before upgrading to
Tank and Operations Manager V12.
Upgrading Tank and Operations Manager

from V7.2, V7.3, V8.0, V8.5, V8.7, V8.8,
V8.9, V9, V10, V11
To upgrade to Tank and Operations Manager from V7.2, V7.3, V8.0, V8.5,
V8.7, V8.8, V9, V10, or V11, follow the “Upgrade or Repair Existing Products”
path instructions:
1 Click on the V12 aspenONE product media download or insert a V12
aspenONE product USB drive. The AspenTech Installation Browser
dialog box is displayed.
Note: If this dialog box does not appear a few seconds after inserting the
USB drive, browse to the USB drive and start setup.exe.
2 Choose Upgrade or Repair Existing Products, and follow the
instructions on the subsequent dialog boxes.

Upgrading Tank and Operations Manager
from V7.1 and earlier versions
To upgrade to V12 Tank and Operations Manager from V7.1 and earlier, you
need to uninstall the old version then reinstall V12.
Note: aspenONE Shared Components can hold all the installed features
shared by more than one product group.
To uninstall old version then install V12

1 Log on using the account name and password of an account in the
2 Click Start | Programs | AspenTech | Uninstall AspenTech
Software.
3 The AspenTech Uninstaller – Select Products dialog box is displayed.
4 Select Aspen Tank and Operations Manager, and then click Uninstall.
Notes:
 If Aspen Operations Reconciliation and Accounting is installed on the same
machine, before reinstalling you need to also uninstall Aspen Operations
Reconciliation and Accounting using the same method.
 If there are any other Aspen products installed, upgrade those products
before reinstalling Aspen Tank and Operations Manager. Please refer to
the individual Aspen product Installation Guides for specific upgrade
instructions.
5 Click on the V12 aspenONE product media download or insert a V12
aspenONE product USB drive and follow the instructions in Chapter 3 for
Installing Tank and Operations Manager.
Note: AspenTech recommends you choose Custom Install, since there
are predefined dependencies between bundles or products such that any
bundle or product selected may cause other bundles or products to be
automatically selected as well.
After You Upgrade

1 Restore the OLE DB UDL Link files saved during the preparation steps.
2 Review the “Post Install Configuration Check List” section in the
“Post-Install Configuration” chapter to make sure that any new provisions
added to the most recent version of Tank and Operations Manager are
incorporated or adjusted accordingly so it meet your site requirements.
These activities include the upgrade of your database, configuration of
security, and others that are essential for the correct operation of Tank
and Operations Manager.

15 Repairing Aspen Tank and
Operations Manager
Overview
Use the instructions in this section to repair corrupt data or missing elements
in your AspenTech applications.
Repairing Tank and Operations

Manager
To repair Tank and Operations Manager:
1 Click on the aspenONE product media download or insert an aspenONE
product USB drive. The AspenTech Installation Browser dialog box is
displayed.
Note: If this dialog box does not appear a few seconds after inserting the
USB drive, browse to the USB drive and start setup.exe.
2 Choose Upgrade or Repair Existing Products, and follow the
instructions on the subsequent dialog boxes.
After You Repair

For more information about the post-installation processes of Tank and
Operations Manager, see the ““Post Install Configuration Check List”
section of the “Post Install Configuration” chapter.
15 Repairing Aspen Tank and Operations Manager 143

144 15 Repairing Aspen Tank and Operations Manager
16 Removing Aspen Tank and
Operations Manager
This chapter explains the steps for removing Aspen Tank and Operations
Manager and lists some recommendations concerning the removal of Aspen
Tank and Operations Manager software.
Before You Remove Aspen Tank

and Operations Manager
Before you remove the Aspen Tank and Operations Manager product, run
through the following check list:
To prevent the loss of data, ensure there is nothing other than
application data stored under the Aspen Tank and Operations
Manager root folder.
If you find out that project data has been saved under the Aspen
Tank and Operations Manager root directory, you should save this
data into another area before continuing with the uninstall process.
Ensure the machine has been restarted since the last install/un-
install of AspenTech applications otherwise the un-install will not
occur.
If system contains any data or configuration files that may be
needed later, make backup copies of the database
Uninstall AspenTech Software

1 Log on using the account name and password of an account in the
2 Click Start | Programs | AspenTech | Uninstall AspenTech
Software.
3 The AspenTech Uninstaller – Select Products dialog box is displayed.
4 Select Aspen Tank and Operations Manager, and then click Uninstall.
16 Removing Aspen Tank and Operations Manager 145

146 16 Removing Aspen Tank and Operations Manager
17 Troubleshooting
This chapter provides information about problems that might arise during the
installation process or after you try to run the Aspen Tank and Operations
Manager software. It also lists typical error messages and explains how to
correct them.
AspenTech Support
AspenTech customers with a valid license and software maintenance
agreement can register to access the Online Technical Support Center at
http://support.aspentech.com.
Registered users can also subscribe to AspenTech Technical Support e-
bulletins. These e-bulletins proactively advise customers of important
technical issues, product updates and service pack announcements. For
support by phone and e-mail, refer to Chapter 1, “Introduction.”
Operations Accounting
Interface Troubleshooting
“Warning: No Aspen Operations
Reconciliation and Accounting Connect
server specified.”
An attempt to execute the Aspen Operations Reconciliation and Accounting
Connect utility failed and causes an error dialog box to display explaining the
severity and consequences.
The Operations Accounting Interface utility attempted to create an object to
execute the Aspen Operations Reconciliation and Accounting Connect utility
(IIAutoHist.exe) via DCOM and failed. There are two possible reasons and
solutions for this problem:
 The remote server name where Aspen Operations Reconciliation
and Accounting is installed has not been specified.
17 Troubleshooting 147
If Aspen Operations Reconciliation and Accounting was installed in a
separate computer then you must specify the name of that server in the
preferences menu as indicated by the error dialog box and attempt the
opening of the model again.
Note: You must manually startup and close the Aspen Operations
Reconciliation and Accounting Connect utility (IIAutoHist.exe) on the
remote computer at least once so its DCOM automation interface is
initialized and enabled for other external programs like Operations
Accounting Interface.
 Aspen Operations Reconciliation and Accounting Connect has not
run at least a first time.
Regardless of whether Aspen Operations Reconciliation and Accounting is
installed in the local computer or a remote one, you must manually start
up and close at least once the Aspen Operations Reconciliation and
Accounting Connect utility (IIAutoHist.exe). This is necessary because the
recycle operation initializes and enables the DCOM automation interface
that is required for other external programs like Operations Accounting
Interface to operate the Aspen Operations Reconciliation and Accounting
Connect.
“Could not connect to Aspen Operations

Reconciliation and Accounting Model
xxxxxx.”
Warning shows when an attempt to open the Aspen Operations Reconciliation
and Accounting model xxxxx failed.
Usually this error occurs the first time the utility Operations Accounting
Interface is executed after installing Tank and Operations Manager. Among
the many reasons for the failure are:
 Aspen Operations Reconciliation and Accounting is not installed.
Verify that the Aspen Operations Reconciliation and Accounting software
has been installed in the specified server. The server where Aspen
Operations Reconciliation and Accounting is expected is defined in the
Preferences form, accessed via the File | Preferences menu option.
 Aspen Operations Reconciliation and Accounting ODBC Source is
not an available source.
1. Verify that an ODBC Source to access your Aspen Operations
Reconciliation and Accounting database has been properly defined and
tested in the list of System DSN sources. Use the Data Sources
(ODBC) tool as indicated in the configuration steps for Operations
Accounting Interface in an earlier section.
2. Make sure that the correct Aspen Operations Reconciliation and
Accounting ODBC Source appears in the list of ODBC sources in the
Model combo list in the Open Model logon form.
3. Make sure that the proper credentials (User Name and Password) for
the Aspen Operations Reconciliation and Accounting account are
entered in the Open Model logon form.
148 17 Troubleshooting
Note: The first time, it is recommended that you enter both the user
name and the password of the Aspen Operations Reconciliation and
Accounting account. By default, the program uses superuser as the User
Name and an arbitrary Password to make the connection fail the first
time.
 Aspen Operations Reconciliation and Accounting account
credentials are incorrect.
The first time, you must type in both the user name and the password of
the superuser account. The program uses by default superuser as the
User Name and an arbitrary Password to make the connection fail the
first time.
17 Troubleshooting 149
150 17 Troubleshooting
18 Prerequisites
This chapter expands on any prerequisites so that you can work with the
Aspen Tank and Operations Manager software successfully. It describes the
following:
 How to create an Oracle database
 What are the compulsory steps if you are running Tank and Operations
Manager on Windows Server
Creating an Oracle Database

The Oracle DB is a big infrastructure with a Service, a SID, lots of files, which
is known as Oracle’s schema.
Generally the Oracle installation involves a process to create a DB, which
frequently is the fixed and static DB. Often this original DB is used by our
Aspen products (Batch.21, IP 21, Tank and Operations Manager), and it is
frequently characterized by a SID name ORCL. You can check your
configuration parameters for the current database in the file:
C:\Oracle\Ora92\network\ADMIN\tnsnames.ora.
Opening this file (tnsnames.ora), you can see something as shown in the
example below which features a standard and default creation where the term
w2012-afo03.qae.aspentech.com matches the standard <USER.DOMAIN>
definition:
# tnsnames.ora Network Configuration File:
C:\app\Administrator\product\12.1.0\dbhome_1\network\admin\tnsnam
es.ora
# Generated by Oracle configuration tools.
ATOMSDB =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = w2012-
afo03.qae.aspentech.com)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = atomsdb)
)
)
18 Prerequisites 151
In this example, the host word corresponds exactly to the name of the host
PC (w2012-afo03 in this example), and the default service definition
corresponds to the DB name (SERVICE_NAME = atomsdb).
This process creates a large structure where you can locate your schemas and
within them, your tables and dataset.
There are two options available:
 Client installation which installs all required basic client software
 Server installation which installs the database plus all basic client software
Oracle Client Installation

1. Start the Oracle Universal Installer program.
You then follow the instructions given on the screens that appear.
2. In the first screen which appears (Welcome screen), click Next.
3. In the second screen (Specify Source Location), specify the

products.xml file path under the Oracle Client installation package. Click
Next.
152 18 Prerequisites
4. In the third screen (Select Installation Type), regarding the Oracle
client, choose the Runtime option and click Next to continue.
5. In the fourth screen (Specify Home Details), specify a base location for
storing all Oracle software and configuration-related files, and either
choose the default Software Location name (OraHome1) and path or
change the location: for example, E drive, in which case you must specify
another name, such as OraHome9. Click Next.
6. In the fifth screen is a progress screen. Click Next to continue.
7. In the sixth screen, a Summary of all the settings for the client
installation is displayed. Click Install to complete the installation, or
Previous if you want to change any of the previous settings.
8. If you have clicked Install an Install progress screen is displayed and
you can cancel the installation process at any time; click Next otherwise.
9. After the installation process is complete, click Exit on the End of

Installation screen.
Note: There are the minimum steps required to allow the client machine to
run the Tank and Operations Manager software accessing the Oracle server
database.
Server Installation
1 Start the Oracle Universal Installer program.
Follow the instructions given on the screens that appear.
2 In the first screen which appears (Welcome screen), click Next.
3 In the second screen (File Locations), either choose the default
destination name and path (OraHome92 and C:\oracle\ora92) or change
the location: for example E drive, in which case you must specify another
name, such as OraHome9 (see example below). Click Next.
4 The third screen is a progress screen. Click Next to continue.

5 In the fourth screen (Available Products), choose the Oracle9i
Database 9.2.0.1.0 option, as you need to install database and client.
Click Next.
6 In the fifth screen (Installation Types), choose the Personal Edition
option that will enable you to install both Server and Client on the same
machine so that the latter can act as server and client. Click Next to
continue.
7 In the sixth screen (Database Configuration), choose the General

Purpose option and click Next to continue.
8 In the seventh screen (Oracle Server for Microsoft Transaction
Server), use the default port number (2030), then click Next.
9 In the eighth screen (Database Identification), specify the Global
Database name and the SID. Click Next to continue.
10 In the ninth screen (Database File Location), the location of the

database files is displayed. Click Next to continue.
11 In the tenth screen (Database Character Set), specify a character set.
As Tank and Operations Manager supports several languages, choose the
Use Unicode option. Click Next.
12 In the eleventh screen, a Summary of all the database settings is

displayed. Click Install to complete the installation, or Previous if you
want to change any of the previous settings.
13 If you have clicked Install, an Install progress screen is displayed and

you can cancel the installation process at any time.
Database Configuration
1 After all the main elements are installed, the Database Configuration
Assistant will automatically run, completing the database creation. Or
you can run Database Configuration Assistant to create the database
at any time.
2 Click Password Management, and specify a password for the SYS and
SYSTEM accounts available in the new database, then click OK.
If the installation process has been successful, the End of Installation
screen will be displayed. At that point you can click Close as the process
is complete.
Installation Check
To make sure that the installation has been successful, you can check that
both SYS and SYSTEM accounts are properly connected to the Host client
defined as “atoms_ora” (not case sensitive).
Follow these steps:
1 Start the SQL application by running SQL Plus.
The following screen is displayed:
2 Check the connection from SYSTEM, by entering the user name and
password required together with the Host string atoms_ora.
3 Repeat the operation to check the connection from SYSTEM.
4 After you have clicked OK, the following window appears showing that the
connection has been successful.
If installing Tank and Operations Manager Web Server on Windows Server

2003, verification of aspx pages must be enabled as follows:
1 Open the Internet Information Services (IIS) Manager by selecting
Administration Tools | Internet Information Services (IIS)
Manager from the Start program.
2 In the IIS Navigation Pane, expand Internet Information Services
(IIS) | Machine Name (Local Computer) and select Web Services
Extensions.
In the main pane, verify that the Active Server Pages status is Allowed.
Appendix A – Configuration
Files
AspenTech.MSC.Settings.xml
File
This file is located in the Documents and Settings\All Users\Application
Data\AspenTech directory. It contains configuration settings that tailor the
behavior of Aspen Tank and Operations Manager.
Note: This file should not need to be changed manually as the Operations
Accounting Interface tool provides the Preference menu option to generate
it. In the event that the desired settings are not appearing in this file when
using the GUI tool, this file can then be modified to correct the problem(s) for
future executions of this utility.
Example of AspenTech.MSC.Settings.xml
File
Section or Property Name Description
[Tank Options]
SendTK=1 Send Tank Gauges option:
0 = Do not send
1 = Send
Levels=True Send Level or Volume
measurements to Aspen Operations
option:
True = Send Levels only to Aspen
Operations Reconciliation and
Accounting
False = Send Volumes only to
Aspen Operations Reconciliation
and Accounting.
AllowBadProp=0 Send property data with bad
Appendix A – Configuration Files 163

quality to Aspen Operations
switch. Possible values are:
0 = Do not send
1 = Send
FracScale=16 Fraction scale for tank gauges:
16 = 1/16
32 = 1/32
[Transactions] Movements transfer options
SendTrans=1 Send movement transfers option:

0 = Do not send movement
transfers
1 = Send
Mass=False Send integrator volume/mass
option:
False = Send Volume values
True = Send Mass values
[Advisor] Properties specific to the operation
of Aspen Operations Reconciliation
and Accounting.
AdvModel=AtOMSDb ODBC Data Source to Aspen
Accounting.
AdvUser=superuser Aspen Operations Reconciliation
and Accounting user name with
privileges to open, close, and
import
AdvPass=ˆÉ…»Å„Ä …<;ni*ug% Password for the user above. This
is encrypted, do NOT modify.
autoImport=true Import mode switch. The selected
Tank and Operations Manager data
is always copied to the
corresponding import tables in the
and Accounting database. In
addition Operations Accounting
Interface can execute
(locally/remotely via DCOM) the
and Accounting Connect utility that
will transfer data from import
tables into their respective
destination table in Aspen
Accounting. If for some reason, this
utility is unable to execute the
and Accounting Connect utility the
switch will be forced to false. The
two possible values are:
True = The interface will Import
164 Appendix A – Configuration Files

and will execute the Aspen
Accounting Connect utility
automatically.
False = Interface will import Tank
and Operations Manager data into
and Accounting tables but will not
(may NOT be able to) execute
and Accounting Connect. This latter
utility will have to be executed
manually by the user. The interface
will leave the data in the Aspen
Accounting import tables.
IIAutoHist_exe_Server=** Undefined Name of the server where the
** Aspen Operations Reconciliation
and Accounting Connect utility
(IIAUTOHIST.EXE) is located.
Generally the utility is located
where Aspen Operations
server software was installed.
[Log] SQL Diagnostic options
LogSQL=1 Log SQL commands option:

0 = Do not send SQL commands
executed to log file
1= Send all commands executed to
log file.
[Property Config] The parameters in this section
MUST be supplied when the option
to transfer integrator volumes to
and Accounting has been specified
in the [Transactions] section above,
parameter mass. Failure to supply
these parameters will result in
double compensation of net
volumes transferred to Aspen
Accounting and in failure to
transfer property data to Aspen
Accounting.
TempName=Temperature Name in Aspen Operations
Reconciliation and Accounting for
the property Temperature
TempBaseValue=15 Base temperature for
compensation. The possible values
are: 60 for 60°F or 15 for 15°C
TempUOM=C UOM for temperature above.
Possible values are F for

Fahrenheit, C for Celsius
WaterCont=%H2O UOM of %BSW
WaterCont Name=Contained H2O Name in Aspen Operations

Reconciliation and Accounting of
the property %BSW
Density Name=Density Liquid Name in Aspen Operations
Reconciliation and Accounting of
the property Liquid Density
Density UOM=SG UOM of the property above.
[RoundInfo] Contains information about the

number of decimals to used when
transferring measurements each
type of instrument to Aspen
Accounting
Level=1
Volume=0
Mass=3
Density=4
Temp=1
BSW=2
Default=2
[Line Displacement]
Detection=1 Detect line displacement option:
0 = Do not detect
1 = Detect
Tolerance=2000 Amount in selected Movement
Engineering Units (Volume or Mass)
of tolerance for Line Displacement
Detection. A displacement
movement will be detected if the
target quantity of the movement is
equal to the capacity of the line
used plus or minus the tolerance.
[Options] Program execution options
AutoOpen=false On startup should open last model

automatically:
False = Do not open a model
True = Open last model
automatically
UseLineup=TRUE
LogAppend=true Append/Overwrite log file option:
False = Overwrite log file on
startup
True = Append

[Debug] Diagnostic option
DBLevel=0 Debug level option. A value

between 0 and 255.0 means no
debug information is generated
[COLOR] Default colors used in grid. Decimal
equivalent of RGB combination
generally expressed as a
hexadecimal number RRGGBB. This
is maintained automatically by the
interface, the last color selection in
the frmColors form will be used.
GridColor=16777215
FontColor=0
ErrColor=255
MinutesToAlertTimeToLevel=40 By default, this option is turned off.
You can manually add
MinutesToAlertTimeToLevel and a
minute value under the [Common]
section .
For example,
“MinutesToAlertTimeToLevel=40”an
d Time to Level is 2/9/2015 13:45,
when the current time reaches
2/9/2015 13:05, the Time to Level
section is highlighted in the Red
color in the Tank Summary view.
[Propagation]
ActivateMovementFromTankCurrentToSta True=If you activate an Issued
rt movement, the data in the Tank
Current Form are propagated to
Movement Start Conditions.
False=Data are not propagated.
FromTankCutoffToTankCurrent True=If you update the Tank Cutoff
Form, and then click OK, the data
in the Tank Cutoff Form are
propagated to the corresponding
fields in the Tank Current Form.
FromMovementCutoffToTankCurrent True=If you update the Movement
Cutoff Form, and then click OK, the
data in the Movement Cutoff Form
are propagated to the
corresponding fields in the Tank
Current Form.
FromMovementStartToTankCurrent True=For an Active movement, you
can update Movement Start
Conditions. The data in the
Movement Start Conditions are

FromMovementEndToTankCurrent True=For a Completed movement,
you can update Movement End
Conditions. The data in the
Movement End Conditions are
FromTankCurrentToMovementCurrent This setting only propagates data
from tank current to corresponding
active movement.
True=If you update the Tank
Current Form, the data in the Tank
Current Form are propagated to the
Movement conditions.
CompleteMovementFromTankCurrentToEnd True=If you complete an Active
movement, the data in the Tank
Current Form are propagated to
Movement End Conditions.
FromTankCutoffToMovementCutoff True=If you update the Tank Cutoff
Form of a specified day, and then
click OK, the data in the Tank
Cutoff Form are propagated to the
corresponding fields in the
Movement Cutoff form of that
specified day.

AspenAtOMSV12 Inst

Uploaded by

Copyright:

Available Formats

You might also like

AspenAtOMSV12 Inst

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AspenAtOMSV12 Inst

Uploaded by

Copyright:

Available Formats

g

Aspen Tank and Operations Manager

Aspen Technology, Inc.

3 Installing Aspen Tank and Operations Manager .................................................11

4 Post Install Configuration ..................................................................................27

5 Creating or Upgrading an Aspen Tank and Operations Manager Database .........29

6 Aspen Tank and Operations Manager Aspen Framework Security ......................45

11 Operations Accounting Interface Post Install Configuration...........................111

13 Populate Aspen Tank and Operations Manager Database ...............................135

14 Upgrading Aspen Tank and Operations Manager ............................................137

15 Repairing Aspen Tank and Operations Manager .............................................143

16 Removing Aspen Tank and Operations Manager .............................................145

This installation manual describes:

Upgrading to the aspenONE Licensing Model for

SLM License Server

Documentation in PDF format can be found in the following ways:

Tank and Operations Manager

ADSA Directory Server None Data sources to Aspen AspenTech

Important: The ADSA

Verify that all system requirements are met (see the

Checking Installation Account Privileges

Important: This chapter describes how to install Tank and Operations

3 Installing Aspen Tank and Operations Manager 11

Install and configure

Install and configure

Verify that the Tank If changes are needed

Legend denotes substep

Before You Install

12 3 Installing Aspen Tank and Operations Manager

3 Installing Aspen Tank and Operations Manager 13

Installing Aspen Tank and

14 3 Installing Aspen Tank and Operations Manager

You must click Yes to continue.

3 Installing Aspen Tank and Operations Manager 15

16 3 Installing Aspen Tank and Operations Manager

The AspenTech Installation Welcome Page provides options to install or

3 Installing Aspen Tank and Operations Manager 17

License Terms and Conditions

18 3 Installing Aspen Tank and Operations Manager

3 Installing Aspen Tank and Operations Manager 19

20 3 Installing Aspen Tank and Operations Manager

This screen will only appear if prerequisites are missing.

 This item can be installed automatically by selecting “Install

 or This item cannot be installed automatically by selecting

 This item is informational

3 Installing Aspen Tank and Operations Manager 21

22 3 Installing Aspen Tank and Operations Manager

3 Installing Aspen Tank and Operations Manager 23

Verify Your Installation

24 3 Installing Aspen Tank and Operations Manager

Installing other AspenTech products

Verify the Installation

3 Installing Aspen Tank and Operations Manager 25

Post Install Configuration

4 Post Install Configuration 27

Creating a New Tank and

Important: Either an MSSQL Server or Oracle database management system

To create a new Tank and Operations Manager database: