APC Validated Process - Reference Architecture V10
APC Validated Process - Reference Architecture V10
V10
Version Number: 10
June 2017
Copyright (c) 2017 by Aspen Technology, Inc. All rights reserved.
Aspen APC Manager, Aspen Apollo, Aspen Cim-IO, Aspen DMC3, Aspen DMCplus (with SmartStep technology),
Aspen DMCplus Builder, Aspen DMCplus Composite, Aspen Inferential Qualities, Aspen Inferential Quality Builder,
Aspen InfoPlus.21, Aspen IQ, Aspen IQmodel Powertools, Aspen Nonlinear Controller, Aspen Online Deployment,
Aspen PID Watch, Aspen PID Watch Performance Monitor, Aspen Process Controller, Aspen Process Recipe, Aspen
Process Recipe Manager, Aspen Process Sequencer, Aspen Process Statistical Analyzer, Aspen Production Control
Web Server, Aspen Recipe Explorer, Aspen RTO Watch, Aspen RTO Watch Performance Monitor, Aspen SmartAudit,
Aspen State-Space Controller, Aspen Transition Manager, Aspen Watch, Aspen Watch Performance Monitor, Aspen
Manufacturing Suite Advanced Process Control, AspenTech, aspenONE, 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.
2 Installation Workflow...........................................................................................7
Install Workflow ............................................................................................... 7
Determine servers and class of software ................................................... 8
Software requirements and Install Media ................................................... 9
Additional Relevant Information ............................................................... 9
Third-party Software ............................................................................ 10
iii
iv Contents
1 Introduction
Related Documents
Installation and Configuration guide (describes how to install, and configure
software on the reference architecture)
Validated Process Test document.
Advanced Process Control V10 Installation Guide:
https://esupport.aspentech.com/S_Article?id=000044966
APC Configuration guide: available after install APC Online software.
C:\Program Files (x86)\Common Files\AspenTech
Shared\APCConfigurationGuide\default.htm
Reference Architecture
Diagram
Advanced Process Control (APC) V10 is implemented using the reference
architecture and specific versions of AspenTech software. The reference
architecture is made up of hardware and third-party software that are typical
in providing a secure IT infrastructure.
The diagram below shows the reference architecture that was configured and
used to execute the accompanying APC V10 Validated Processes. Detailed
system-level information is provided in the chart and tables that follow.
1 Introduction 1
Note: APC Online, APC Performance Monitor, and APC Web Server
communicate over Local Area Networks (LANs), with remote client
connections via the WAN.
Later sections of this document present additional details regarding the order
of the installation and APC V10-specific instructions.
The hardware specifications listed in the next section are the AspenTech
reference architecture specifications used to qualify APC V10. Customers may
use this information as a reference guide and can make adjustments
according to their particular IT policies and requirements. The configuration
documented in this guide reflects the actual configuration used in the APC
qualification and is intended for reference purposes only.
Servers Configuration
Below is the list of machines used during this validated process workflow. The
software and hardware used in this configuration can be considered best
practice. However, the section Basic Deployment Recommendations provides
good insights about minimum hardware specs for APC servers. The software
requirements are presented in Chapter 2.
2 1 Introduction
Comp. 3rd Party/ Release Hardware & OS Client/
Solution Comment
# AspenTech Version Specification Server
1 Introduction 3
3. APC Web Server
4. APC Performance Monitor
The products in each class are listed below.
APC Desktop
Aspen DMC3 Builder for building Aspen DMC3 or APC applications
Aspen Nonlinear Controller Builder
Aspen DMCplus Desktop for building Aspen DMCplus or Aspen DMC3
applications
Aspen Inferential Quality Builder
Aspen PID Watch Performance Monitor
Aspen SmartAudit
APC Online
Aspen DMC3 (when running as an online server product)
Aspen DMCplus Controller (with Aspen SmartStep technology)
Aspen DMCplus Composite
Aspen Inferential Qualities
APC Web Server
Aspen Production Control Web Server
APC Performance Monitor
Aspen Real Time Optimizer (RTO) Watch Performance Monitor Server
Aspen Watch Performance Monitor Server
Basic Deployment
Recommendations
Due to performance considerations, APC Performance Monitor (Aspen
Watch) should always be installed on a dedicated server machine.
For APC Web Server and APC Online classes of software, if the machine
has sufficient memory and number of cores (6 to 16 GB of memory and 6 to 8
cores or more) allocated to run the APC Software, then it may be viable to
install APC Online and APC Web Server on the same computer. Obviously,
several criteria—such as the number and size of the applications, and the
number of web users—dictate how many processing cores and memory are
required.
Running all classes of Aspen Process Control software on virtual machines is
acceptable. However, a virtual machine must be given sufficient processing
cores (2 to 4, minimum) and memory allocation (4GB, minimum) in order to
perform well in a production environment.
Installing APC Desktop products on an APC Online server is perfectly
acceptable for uses such as modifying controller configurations. However,
extensive use of the desktop tools on an online server may interfere with the
performance of the online controller applications.
4 1 Introduction
Minimum server configurations for example
applications
The following notes exemplify server configurations that are minimal, but
acceptable, in installations where recommended hardware recommendations
cannot be met.
APC Online
All APC Online server products require a minimum of two virtual
processors (four is recommended), and a minimum of 4 GB of RAM to
function.
The DMCplus / DMC3 control engine is not computationally intensive, and
four virtual processors and 4 GB of RAM are sufficient if the following
conditions exist:
o A hosted Composite application is of moderate size (<200 variables).
o Number of future MV moves is limited to 14, and the controller is of
moderate size (<50 MVs).
o Move Plan Option (DYNOPT) is set to zero (0). Setting the DYNOPT=3
increases the computational requirements.
o Maximum controller size is moderate (i.e., <50 MVs per controller),
and the total number of controllers is less than ten.
1 Introduction 5
For calculating actual hard disk space required, see the
WatchDiskSizeCalcs.xls file, available from AspenTech Support1 or,
after installation, from the Tools folder.
APC Performance Monitor requires a high performance processor (as
recommended in "Error! Reference source not found.") if the sum of MVs and C
Vs for all controllers it monitors exceeds 200 in total.
The following chapters outline the installation and configuration steps taken to
implement APC V10. Each chapter outlines the steps involves for one of the
machines used in the APC implementation.
Note: The components were installed in the order listed in these chapters.
Any exceptions to the rule are explicitly noted.
Chapter 2: Installation Workflow
Chapter 3: APC Software Installation
Chapter 4: Post-Install
1
Aspen Watch Disc Size Calculation Spreadsheet:
http://support.aspentech.com/webteamasp/KB.asp?ID=135042
6 1 Introduction
2 Installation Workflow
Install Workflow
In order to ensure a complete and smooth installation, a basic workflow with
the main important steps is proposed.
2 Installation Workflow 7
In this workflow user would start the software installation by defining the
number of servers and their requirements. After that, the class of software for
each server is defined. The install media could be available in a shared drive
in the network. Before proceeding with the installation in each server, make
sure that the pre-requisites (windows features and roles) for each server are
installed. For each class of software, confirm if any third-party software is
needed. Once that step is completed, proceed with the software installation
and then check the post install configuration.
The sections below provide more details on the steps in the flowchart above.
APC Desktop
APC Online
8 2 Installation Workflow
Software requirements and Install Media
Determine whether software and hardware requirements have been met.
Determine the licensing method that is in use at your site, and select the
appropriate installation DVD.
Notes:
Aspen Production Control Web Server does not run on a Windows Terminal
Server.
You must be logged into an account with Administrator privilege when first
downloading AspenTech plotting components on the Web client.
Note: All installation procedures in this guide assume you are using an
account with FULL administrator privileges, including privileges to write to the
Windows Registry. If installation fails, consult your Information Services (IS)
personnel to determine if there are group policies or some other restrictions
in force that limit the capability of local administrators.
2 Installation Workflow 9
Third-party Software
In this section, the list of third-party software used in APC Software is
presented.
Java™ 8 or later – 32-bit (i.e., Windows x86 or i586)
Accept the license and then download the Window x86 Offline, copy the
downloaded file to the APC Web Server and install using Admin rights.
10 2 Installation Workflow
Microsoft IE 9 or later. (IE10 and IE11 are recommended.)
Internet Explorer (IE) is required for computers accessing the APC Web
Interface. Besides, APC Web Server and Performance Monitor also
require IE 9 or later.
2 Installation Workflow 11
3 APC Software Install
Notes:
During installation, always clear check boxes that include "Optional 3rd
Party Installations."
To complete the JRE installation in an environment where there is no
Internet connection, you can obtain the "Windows Offline (32-bit)"
installation file for Java on a separate computer that has an Internet-
connection. Look for the offline installation file.
When the JRE installation is complete, verify that it is installed by
inspecting the Windows Control Panel. The Windows Control Panel should
include a Java (32-bit) applet.
Note: FTP Server and SMTP Service are not required and can be omitted
from the IIS install.
13 In the Confirmation page, click Install.
14 After the features are installed, the Results page is displayed. Click
Close.
15 Close the Server Manager Dashboard when all tasks are completed.
5 In the Server Roles page, select the Web Server (IIS) row from the
Roles list. The Add Roles and Features Wizard dialog box is displayed.
Note: FTP Server and SMTP Service are not required and can be omitted
from the IIS install.
10 In the Confirmation page, click Install.
Note: FTP Server and SMTP Service are not required and can be omitted
from the IIS install.
4 Close the Server Manager dialog box and Programs and Features
window when complete.
4 Accept the terms of the software agreement (select the check box) and
click Next. The software prerequisites are verified.
Important:
After any AspenTech software product has been installed in the root
folder, the root folder destination cannot be changed, and the File
Location tab will be disabled. All further AspenTech product installations
on this computer will be made to that root folder by default.
Common components are always installed under Program Files
(x86)\Common Files\AspenTech Shared, regardless of the root folder
destination (File Location) specified.
There are environment variables that point to the Program Files and
Program File (x86) directories on the system drive and the installation
program is using. These type of environment variables do not exist for
other drives.
ProgramFiles=C:\Program Files
ProgramFiles(x86)=C:\Program Files (x86)
ProgramW6432=C:\Program Files
If your computer is 64-bit capable, and you choose to install to an
alternate drive or folder location, for example: E:\, the 32-bit software
application files are installed to an "E:\AspenTech (x86)" folder, and 64-
bit software application files are installed to an "E:\AspenTech" folder.
9 Specify the SLM License Server and, if applicable, the Aspen Framework
Security Server or Aspen Local Security Server. Then click Next.
Note: Aspen Framework Server is a security server for large-group,
enterprise installations. If applicable, verify that your system
administrator has installed the Aspen Framework Server.
The screen for identifying the Windows services account is displayed.
The next chapter provides some additional configuration needed for each
class of software: APC Builder Products, APC Online Products, APC Web
Server and APC Performance Monitor.
In this chapter we provide the main configuration tasks needed after installing
Aspen APC software.
In this chapter we review the post-configuration install needed for each class
of software:
APC Desktop
APC Online
APC Desktop
>>> APC Online, Web Server and Performance Monitor
If the Windows Firewall feature in the Windows operating system is enabled,
you will need to click Unblock in the Windows Security Alert dialog box the
first time you run certain desktop products and attempt to connect to an
online server. If you see the follow screen, just click the “Allow access”
button.
3. Watch the status bar at the bottom of the window for a message
stating that InfoPlus.21 has been started successfully:
Note: If you receive an error, look in one of the following files for
more information:
o PROGRAMDATA\etc\cfg\awlog.txt
o PROGRAMDATA\etc\cfg\upgrade.out
...where PROGRAMDATA, for typical installations, is...
C:\ProgramData\AspenTech\APC\Performance Monitor.
TSK_RTO4
The CIMIODMCP line specifies the default configuration for the Aspen DMCplus
Context Cim-IO server. The cimiosetcim_200 line specifies an optional
configuration for another Cim-IO device from which you might want to read or
write Aspen InfoPlus.21 data.
If you want Aspen Watch to communicate with the OPC server you could add
an extra line in the cimio_logical_devices.def file. For example:
IODEV5 OPC_Server_Name CIOASPENTECH_01
will establish communication between the Aspen Watch server and the OPC
server. In this case the CIOASPENTECH_01 must be a tcp service as in the
example below.
Additionally, the cimiosetcim_200 TCP port configuration specified in the
Windows\System32\drivers\etc\services file must be configured consistently
in the APC Online server and APC Performance Monitor server:
DCOM considerations when OPC Server is remote to Aspen Cim-IO for OPC interface.
Solution ID: 108885
Product(s): Aspen Cim-IO for OPC
CIMIO_T_API synchronous works with a remote CIM-IO/OPC connection, but why doesn’t
asynchronous?
Solution ID: 133142
Product(s): Aspen Cim-IO for OPC, Aspen Inferential Qualities
Aspen Cim-IO for OPC gets "Access denied" when connecting to a remote Fisher Delta V
OPC server.
Solution ID: 115547
Then click the Add CIM-IO Interface… link under Actions on the top right
corner. This will open the following dialog:
In this dialog you can set the interface name and description and also
configure a specific user account to connect. Click next:
Return to the CIM-IO Interface Manager and you should see this:
Open the test-api utility and confirm tags can be read from the OPC server:
Check the Enable Server checkbox to enable the APC Online server, which
will start the AspenTech Production Control RTE Server after the configuration
changes are saved.
Click the Add Source button, then configure an IOIP21 Cim-IO Data Source
as shown below, then click Add Source to save the configuration. Note that
the Hostname for the DLGP Service is the APC Performance Monitor server.
Click the Users and Roles tab, and configure an appropriate user account for
the online application permissions.
Tip: From the Start screen of Windows Server 2012, press the
Windows key + Q, and search for "ADSA Client".