AssetWise Performance Management. APM Installation Prerequisites

(1)

AssetWise Performance

Management

APM Installation

Prerequisites

(2)

tered trademarks or service marks of Bentley Systems, Incorporated or one of its direct or indirect wholly owned subsidiaries. All other brands and product names are trademarks of their respective owners.

Copyright Notice

Including software, file formats, and audiovisual displays; may only be used pursuant to applicable software license agreement; contains confi-dential and proprietary information of Bentley Systems, Incorporated and/or third parties which is protected by copyright and trade secret law and may not be provided or otherwise made available without proper authorization.

For reference, a copy of the End User License Agreement named “EULA.pdf” is installed in the same folder as the product.

APM Installation Prerequisites Published April 2014 APM Release 7.2.0 Corporate Headquarters Bentley Systems, Incorporated 685 Stockton Drive Exton, PA 19341-0678 USA Phone: (1) 610 458-5000 Fax: (1) 610 458-1060 http://www.bentley.com International Headquarters Bentley Systems International Limited Second Floor, Block 2, Park Place

Upper Hatch Street Dublin 2 Ireland Phone: +353 1 436 4600 Fax: +353 1 416 1261 http://www.bentley.com Asia Headquarters Bentley Engineering Software Systems Unit 1402-06, Tower 1 China Central Place, Beijing 100022 China

Phone: (86) 10 5929 7000 Fax: (86) 10 5929 7001

(3)

Installation Prerequisites

This document defines the recommended minimum hardware and soft-ware for APM server and client environments. Use this document as a reference before installing APM to ensure proper configuration.

Note: While every effort is made to ensure the accuracy of this

information, the specifications are a broad guide. If your system’s configuration does not meet the requirements specified in this document, contact APM Technical Services for an evaluation or for guidance in deployment strategies that accommodate non-com-pliant technologies.

Definitions

Supported Configurations

Supported configurations are combinations of hardware, operating sys-tems, drivers, and other third-party software required for an APM instal-lation to function properly. They represent what we know to work with the confidence gained from normal quality assurance measures in multi-ple situations. These recommendations do not mean that other configura-tions will not support a functioning APM installation.

Unsupported Configurations

Unsupported configurations are combinations of hardware, operating systems, drivers, and other third-party software that might degrade per-formance of an APM installation or cause it to function improperly. While Bentley will endeavour to assist customers with unsupported configura-tions, errors or support solutions might require fixes that involve the cus-tomer moving to a supported configuration or upgrading to the latest versions of third-party software.

(6)

APM Deployment Options

There are a number of possible software configurations.

Smart-client Deployment

This deployment is most common and is generally recommended. It involves running a minimum software component set on the client con-nected to a physical or virtual application server. Different clients might connect to the same application server or to distinct application servers for scalability, if needed. To facilitate load balancing across multiple application servers, the APM Server Manager is generally deployed, run-ning under IIS. It serves as a single point of entry that routes new clients to the least active application server. The Server Manager can also be used to route handheld and remote synchronization requests across mul-tiple synchronization servers. This deployment uses a separate database server with which the application servers communicate.

Thick-client Deployment

This deployment avoids the need for a separate application server. The client computer runs the client software components, plus the application server software components, and connects to the separate database server. The application server can run either in the same process space as the client (using the -l option on the IvaraClient executable) or as a separate software server instance. This deployment uses a separate data-base server, to which the physical client communicates (via the applica-tion server running locally on the client). Thick-client deployment with an in-process application server is required for definability (modification/ extension of the core product’s object model and user interface).

(7)

Installation Prerequisites

Citrix

®

or Terminal Services Deployment

As with prior versions of APM, the client can be deployed using Citrix or Terminal Services if necessary. In this configuration, the Citrix Servers can deploy smart or thick clients.

Remote Computing Deployment

The remote computing client is a stand-alone deployment in that all soft-ware components that are required to run the application are local. The remote client software is comprised of a relatively small database, object model, and user interface.

The remote computing synchronization server is a Service Provider (pos-sibly running on its own application server) that allows remote comput-ers to synchronize with the main system.

(8)

Client Minimum Requirements

The table in this section outlines the minimum recommended hardware and software requirements for various APM client deployments.

Smart Client Thick Client Remote Client

CPU Single or multi-core

1.5+ GHz Multi-core 2+ GHz Multi-core 1 GHz or better Memory 1 GB 2 GB 1 GB Display Resolution 1280 x 1024 1280 x 1024 1024 x 728 Operating System Microsoft® Windows Vista® + SP1,

Win-dows 7, or WinWin-dows 8.1 Windows 7

Database Software N/A See “Supported

Database Software” on page 11 Microsoft SQL Server 2008 R2 Express or Microsoft SQL Server 2012 Express1

Other Software • Microsoft .NET 4.5 (plus the latest

patches) is required for client comput-ers

• Microsoft Office Outlook®_{2007 or 2010} is required for sending emails from cli-ent computers

• Microsoft Excel®_{2007 or 2010 is} required for exporting checksheets, tables, RFQ supplier bids, and so on

• Microsoft Project 2007 or 2010 is

required for exporting schedules (EAM module)

• Microsoft .NET

Framework 4.5 (plus the latest patches) is required for cli-ent computers2

• Microsoft Excel

2007 or 2010

1. If supported database software is not present on the computer, the APM Remote install utility prompts the user. With the user’s confirmation, the utility downloads and installs Microsoft SQL Server 2012 Express.

2. If Microsoft .NET is not present on the computer, the APM Remote install utility prompts the user. With the user’s confirmation, the utility downloads and installs Microsoft .NET.

(9)

Application Server Requirements

The table in this section outlines the minimum recommended require-ments for APM application server computers. It is based on the assump-tion that the applicaassump-tion server will access the APM database using a network ODBC connection.

Note: Connection to the internet is required on APM application

server computers.

Minimum Recommended

CPU 3 GHz Xeon multi core processor or faster.

Additional CPU cores should have significant benefit due to the multi-threaded nature of the application server software.

A minimum of one physical server core per 10 active concurrent users is recommended.

Memory A minimum of 2 GB with an additional 150 MB

per active concurrent user is recommended for each IvaraServer instance running on the appli-cation server.

Multiple instances of the application server exe-cutable or service per hardware server may improve scalability.

Operating System Microsoft Windows Server 2008R2 or Microsoft

Windows Server 2012R21

1. Foundation Edition is not supported.

Microsoft .NET Framework

(10)

Database Server Requirements

In order for the APM application to provide acceptable performance when accessing information stored in the database, the database server needs to be configured appropriately. Items to be considered include:

• Amount of memory • Number of CPUs

• Disk capacity and throughput • Network bandwidth

• Backup and recovery • Fault tolerance

• Configuration of the operating system and database options • ANSI or Unicode format

Note: The database and master APM installation can reside on

the same computer. However, if the database server uses a non-Windows operating system (for example, if you are running Oracle on a Solaris™_{machine), the master APM installation must be on a} separate computer. This is because the APM software only runs under a Windows operating system.

For help in server sizing and configuration, contact Bentley Technical Services. As a basic guideline, the APM database consumes approxi-mately 1 GB of disk per 10,000 assets. Memory required is typically 10% of the database size. An example of a server processor on which an APM database has been successfully deployed is an HP Proliant DL380 G6 EE4450 with 2 CPUs.

(11)

Supported Database Software

This table shows which database management systems are supported for APM Enterprise.

* The required Oracle 11.2.0.2 Client components are:

• SQL *Plus • Oracle Net

• Oracle Data Provider for .NET • Oracle Providers for ASP .NET

Note: If the 64-bit version of APM is to be installed, be sure to

install the 64-bit version of the Oracle Client components.

DBMS Client

Microsoft SQL Server 2008 R2 Microsoft SQL Server 2012

SQL Server Native Client 2008 R2 SQL Server Native Client 11.0

(12)

Citrix and Terminal Services Server Requirements

The table in this section outlines the minimum recommended require-ments for setting up APM on a Citrix®_{server or Windows Server} Termi-nal Services.

Note: We recommend that you set up your Citrix or Terminal

Ser-vices server on a separate computer from your SQL Server or Ora-cle database.

The computer hosting your Citrix or Terminal Services server is subject to the same general requirements as any APM client computer. For example, the SQL Server or Oracle Client component must be installed. The table below provides a sample of Citrix/Terminal Services configura-tions used successfully with APM.

Memory • Average memory requirements vary from

75-256 MB per user depending on the level of customizations and the application fea-tures used

• Memory requirements can be reduced by

deploying application servers and hosting only smart clients on Citrix/Terminal Ser-vices Number of Concurrent Users Manufacturer (example)

Make/Type CPU Model #CPUs per RAM Quantity 10 HP Proliant DL380 G6 EE5540 1 4 GB 1 20 HP Proliant DL380 G6 EE5540 1 8 GB 1 50 HP Proliant DL380 G6 EE5540 2 14 GB 1 100 HP Proliant DL380 G6 EE5540 2 14 GB 2

(13)

Synchronization Service Provider for Mobile Computing

A computer acting as a synchronization server for APM Mobile.NET, APM Remote, or both has the following requirements:

Minimum Recommended

CPU 2 GHz processor, minimum. Multiple CPUs

or multiple cores are recommended. If you expect to require numerous concurrent uploads and downloads, more cores will help significantly.

Memory Minimum 4 GB. Memory requirements

depend on the total of handheld computers, tablets, or both that will be synchronized at simultaneously. 100MB RAM is required per concurrent upload or download.

Operating System Windows Server 2008 R21 or Windows

Server 2012R2

1. Microsoft SQL Server Native Client on Windows Server 2008 R2 is supported with SQL Server 2005 SP3 and SQL Server 2008 SP1. Install the 64-bit Native Client to see the 32-bit ODBC drivers.

The handheld synchronization server’s capacity is highly dependent on the memory (and processing power) of the server it is running on as well as the nature of the data being synchronized. Bentley has successfully tested the following using representative customer data:

40 concurrent synchronizations on a 4 core, 3 GB server. 120 concurrent synchronizations on an 8 core, 8 GB server.

Microsoft .NET Framework Microsoft .NET Framework version 4.5

(14)

Handheld Device Requirements

Handheld computers can be used to collect maintenance or inventory data to be uploaded into APM. The APM Mobile.NET application is installed on each handheld device. The application is used to record indi-cator readings, which can also include attached images, or inventory counts.

Hardware and software requirements for handheld computers:

• Windows Mobile 5 • Windows Mobile 6 or 6.5

• Minimum memory requirement for the handheld device is 64 MB

with minimum free program memory of 24 MB

Note: A handheld device with 64 MB of memory will handle a

lim-ited number of checksheets and indicators or count sheets and items. If you assign activities with many lines to a device, it will need more memory.

• Microsoft .NET Compact Framework 3.5. This software is provided in

the APM Mobile.NET installation package.

• Microsoft ActiveSync® _{or Windows Mobile Device Center is required} for installing APM Mobile.NET on the handheld computer. After installation, the handheld computer can use ActiveSync or Mobile Device Center to exchange data with the APM database while docked to a work station. Alternatively, the handheld computer can connect to your Windows network either wirelessly or using an Ethernet® port.

• When a handheld computer is connected to the network wirelessly,

additional configuration might be needed to access the web service. This is true when a wireless security protocol such as PEAP (Pro-tected Extensible Authentication Protocol) or LEAP (Lightweight Extensible Authentication Protocol) is in use. Be sure to verify that the handheld supports your desired wireless security protocol. For example, PEAP can be supported by installing additional software on the handheld computer, such as the Juniper Networks®_Odyssey Access Client for Windows Mobile handhelds.

APM Mobile.NET works with the APM application server that performs the upload and download processes for APM Mobile.NET, APM Remote, or both. For more information, see “Synchronization Service Provider for Mobile Computing” on page 13.

(15)

Note: If you are upgrading from a previous APM version, you

must also upgrade the APM Mobile.NET program on each hand-held computer. Review the instructions in “Upgrading Handhand-held Device Software” in the APM Upgrade Guide.

(16)

APM Supervisor Dashboard

The APM Supervisor Dashboard is a set of Android, Windows 8.1, and iOS applications optimized for personal mobile devices like smart phones and tablets. The dashboard allows maintenance managers and execu-tives to monitor KPIs and asset health indexes within APM and to make simple updates like acknowledgments and approvals.

APM Supervisor Dashboard works in a connected environment over WiFi or Broadband networks. The APM Supervisor Dashboard for Android has been available on Google Play since the 7.1 release of APM. The Windows 8.1 application will be available from the Windows App Store shortly. The iOS application for iPhones and iPads will be released in the future.

(17)

APM Integration to SAP®

Using the Computerized Maintenance Management System (CMMS) Integration functionality in APM, you can exchange information about assets, work requests, work order tasks, standard tasks, and standard jobs with SAP Plant Maintenance.

Note: The CMMS integration functionality does not work with

sites where the EAM module is enabled.

Before installing or upgrading APM, make sure that SAP®_{ECC and SAP} NetWeaver are installed and configured correctly. The integration solu-tion is designed to work with the Plant Maintenance applicasolu-tion.

The integration plugin has been verified to work with:

• SAP ECC 6.0, Enhancement Pack 4 and SAP NetWeaver PI 7.1.1

Bentley will make reasonable efforts to support later ECC and NetWeaver service packs.

For information about setting up and using the integration functionality, see APM Integration Guide for SAP Plant Maintenance with Dynamic Mapping.

(18)

APM Integration to IBM® Maximo®

Using the CMMS integration functionality in APM, you can exchange information about assets, work orders, standard tasks, and standard jobs with IBM Maximo Asset Management software.

Before installing or upgrading APM, make sure that IBM®_Maximo® Enterprise Suite 6.x or 7.1.x is installed and configured correctly.

Note: For information about setting up Maximo 6.x, see the

Max-imo Enterprise Adapter System Adminstrator’s Guide. For infor-mation about setting up Maximo 7.1.x, see the Integration Guide for IBM Maximo Asset Management 7.1.

The plugin has been verified to work with Maximo Enterprise Suite 6.0 and 7.1 (with Maximo Basic Services Release 7.1.1.4 Hot Fix Build:017). Bentley will make reasonable efforts to support later Enterprise Suite service packs.

Note: The APM integration plugin for Maximo is certified “Ready

for Tivoli” for IBM Maximo Enterprise Suite 6.0 and 7.1.

For information about setting up and using the integration functionality, see APM Integration Guide for IBM Maximo.

(19)

APM Integration to Oracle® eAM

Using the Computerized Maintenance Management System (CMMS) Integration functionality in APM, you can exchange information about assets, work requests, work orders, standard tasks, and standard jobs with Oracle eAM software.

Before installing or upgrading APM, make sure that Oracle®_E-Business Suite is installed and configured correctly. The integration solution is designed to work with the Enterprise Asset Management (eAM) applica-tion.

The APM application server computer requires:

• Oracle 11.2.0.2 Client components: • SQL *Plus

• Oracle Net

• Oracle Data Provider for .NET • Oracle Providers for ASP .NET

Note: If the 64-bit version of APM is installed, be sure to install

the 64-bit version of the Oracle client components.

The Oracle 11.2.0.2 client components must reside on the computer where the Oracle integration adapter is installed, typically, where the APM integration server is installed.

These components can be downloaded from the Oracle web site.

The plugin has been verified to work with Oracle E-Business Suite 12.0.6 and 11.5.10. Bentley will make reasonable efforts to support later Oracle E-Business Suite service packs.

(20)

APM Integration to Isograph Availability Workbench®

Using the integration functionality in APM, you can export failure modes from MTA2 and RCM2 analyses to the Isograph Availability Workbench (AWB), where you can analyze and optimize the data. You can then import optimization results into the APM analysis, review the recom-mendations in the Optimization view, and make appropriate changes to the action plans.

Before installing or upgrading APM, make sure that the following requirements are met:

• Isograph Availability Workbench v2.1 or later must be installed and

configured correctly.

For information about installing Availability Workbench, see Avail-ability Workbench Installation and Licensing Guide from Isograph. • Valid Isograph Availability Workbench license.

The plugin has been verified to work with Availability Workbench 2.1.19.0. Bentley will make reasonable efforts to support later Availabil-ity Workbench service packs.

For information about setting up and using the integration functionality, see APM Integration Guide for Isograph Availability Workbench.

(21)

ODC Services Requirements

Description Requirements OPC DA1

1. For OPC DA and OPC HDA, both x86 and x64 OPC SDK must be installed on the computer running APM smart client.

OPC Real Time

Data Access • OPC Core Components 3.00 (105.1) (x64) Redistributable

• Microsoft Visual C++ 2008

(x64) Redistributable

• OPC Core Components 3.00

(105.1) (x86) Redistributable

• OPC DA 2.XX and OPC DA

3.0 Servers

OPC HDA OPC Historical

Data Access • OPC Core Components 3.00 (105.1) (x64) Redistributable

• Microsoft Visual C++ 2008

(x64) Redistributable

• OPC Core Components 3.00

(105.1) (x86) Redistributable

• OPC HDA 1.2 Servers OSI Pi2

2. APM is validated with OSISoft SDK version 1.3.8.388 with Patch 1.3.8.391 for both 32-bit and 64-bit versions of the SDK. When running APM in a 32-bit environment, install the 32-bit SDK on both server and client computers.

When running APM in a 64-bit environment, install the 32-bit SDK first and then the 64-bit SDK on the server. The 32-bit SDK must be installed on the client because the APM client is only

sup-OSI Pi connectivity Pi SDK from OSISoft installed and configured

AssetWise Performance Management. APM Installation Prerequisites