AMS Suite: Intelligent Device Manager
Version 12.0 Installation Guide
Installation Guide
NOVEMBER 2012
AMS Suite: Intelligent Device Manager Installation Guide
NOVEMBER 2012
Disclaimer
The contents of this publication are presented for informational purposes only, and
while every effort has been made to ensure their accuracy, they are not to be
construed as warranties or guarantees, express or implied, regarding the products or
services described herein or their use or applicability. We reserve the right to modify
or improve the designs or specifications of such products at any time without notice.
Copyright and Trademark Information
© Emerson Process Management. 2012. All rights reserved.
The Emerson logo is a trademark and service mark of Emerson Electric Co.
AMS, PlantWeb™, SNAP-ON™, Asset Portal™, DeltaV™, RS3™, PROVOX™, Ovation™,
FIELDVUE™, and ValveLink™ are marks of one of the Emerson group of companies.
HART® and WirelessHART® are registered trademarks of the HART Communications
Foundation of Austin, Texas, USA.
FOUNDATION™ is a mark of the Fieldbus Foundation of Austin, Texas, USA.
All other marks are property of their respective owners.
Document History
Part Number Date Description
10P5824A001 Dec 2008 Update, software version 10.0
10P5824A001 Dec 2008 Update, software version 10.0
Apr 2009 Update, software version 10.1
10P5824A501 Nov 2009 Update, software version 10.5
Apr 2010 Update, software version 11.0
10P5824B101 Aug 2010 Update, software version 11.1
Jan 2011 Update, software version 11.1.1
10P5824C001 Nov 2012 Update, software version 12.0
2
Installation Guide AMS Suite: Intelligent Device Manager
NOVEMBER 2012
License Agreement
Definitions: The term "You" includes, but is not limited to, users of the Fisher-Rosemount Systems, Inc. (FRSI)
product embodied in the computer program herein, the user’s employer, the employer’s wholly owned
subsidiaries, parent company, agents, employees, contractors, and subcontractors. The term "License
Agreement" refers to one of FRSI’s License Agreements, including but not limited to, all Software License
Agreements, accompanying FRSI products, all Beta Test Agreements, and all Master License Agreements.
Any and all use of this product is subject to the terms and conditions of the applicable License Agreement. The
terms and conditions of the applicable License Agreement by and between You and FRSI shall remain effective
to govern the use of this product.
The existence of a License Agreement by and between You and FRSI must be confirmed prior to using this
product. If the site at which this Program is used is a Licensed Facility under a Master License Agreement with
FRSI, the applicable License Certificate that was sent to You applies. If the site at which this Program is used is
NOT a Licensed Facility under a Master License Agreement with FRSI and the use of the program is NOT
governed by a Beta Test Agreement, the use of this Program shall be governed by the Software License
Agreement that is printed in the sales literature, on the package in which the program was delivered, and in
this manual.
License Certificate for AMS Suite: Intelligent Device Manager
If the site at which this Program is used is a Licensed Facility under a Master License Agreement between You
and Fisher-Rosemount Systems, Inc., this Licensed Copy is provided for Licensee’s use pursuant to its Master
License Agreement with FRSI ("Agreement") as modified herein. If this is an original Licensed Copy, it may be
used only on the equipment with which it has been provided except as otherwise provided in the Agreement.
If this is a Licensed Copy of a Revision or Upgrade, it may only be used in lieu of and under the same terms as
the Licensed Copy previously provided to Licensee.
Notwithstanding provisions of the Agreement, the term of the Limited Warranty for this Licensed Copy is 90
days from the date of shipment from FRSI. Licensee’s other rights and obligations with respect to its use of this
Licensed Copy are set forth in the Agreement. Questions concerning Licensee’s rights and obligations should
be directed to Project Operations, Emerson Process Management, 12301 Research Boulevard, Austin, Texas
78759.
Software License Agreement for AMS Suite: Intelligent Device Manager
BY OPENING THIS PACKAGE YOU AGREE TO ACCEPT THESE TERMS AND CONDITIONS. IF YOU DO NOT AGREE
WITH THESE TERMS, YOU SHOULD PROMPTLY RETURN THE PACKAGE UNOPENED AND YOUR MONEY WILL BE
REFUNDED. FRSI provides this computer program and related materials for your use. You assume
responsibility for the acquisition of a machine and associated equipment compatible with the program, and
for installation, use, and results obtained from the program.
LICENSE: FRSI grants to you a non-transferable, non-exclusive license to: (a) use all fully paid up licensed
programs provided to you to run a single machine; (b) copy the program for backup or modification purposes
in support of the program on the single machine. You must reproduce and include the copyright notice on any
copy or modification. YOU MAY NOT REVERSE ENGINEER, USE, COPY, OR MODIFY ANY PROGRAM OR
RELATED MATERIALS OR ANY COPY, MODIFICATION, IN WHOLE OR IN PART, EXCEPT AS EXPRESSLY
PROVIDED FOR IN THIS LICENSE. IF YOU TRANSFER POSSESSION OF ANY COPY OR MODIFICATION OF THE
PROGRAM OR RELATED MATERIALS TO ANOTHER PARTY, YOUR LICENSE IS AUTOMATICALLY TERMINATED.
No license, express or implied, is granted under any intellectual property directly or indirectly owned by FRSI
which does not specifically read on the program as provided hereunder, nor shall any license, except the
license specifically granted herein, be implied in law, implied in equity, or exist under the doctrine of patent
exhaustion.
TITLE: Title to and ownership of the program and related materials shall at all times remain with FRSI or its
licensors. Your right to use the same is at all times subject to the terms and condition of this Agreement. FRSI
may, from time to time, revise or update the program and/or related materials and, in so doing, incurs no
obligation to furnish such revisions or updates to you.
3
AMS Suite: Intelligent Device Manager Installation Guide
NOVEMBER 2012
TERM: This license is effective upon opening this package. You may terminate it at any time by destroying the
program and the related materials together with all copies and modifications in any form. It will also terminate
upon conditions set forth elsewhere in this Agreement or if you fail to comply with any term or condition of
this Agreement. You agree upon such termination to destroy the program and the related materials together
with all copies and modification in any form.
LIMITED WARRANTY: FRSI warrants the media on which the program is furnished to be free from defects in
materials and workmanship under normal use for a period of ninety (90) days from the date of delivery to you
as evidenced by a copy of your invoice. However, FRSI does not warrant that the functions contained in the
program will meet your requirements or that the operation of the program will be uninterrupted or error free.
THE PROGRAM AND RELATED MATERIALS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
PROGRAM IS WITH YOU; SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE ENTIRE COST OF ALL
NECESSARY SERVICING, REPAIR, OR CORRECTION.
LIMITATIONS OF REMEDIES: FRSI’s entire liability and your exclusive remedy shall be: (1) the replacement of
any media not meeting FRSI’s "Limited Warranty" and which is returned with a copy of your invoice to FisherRosemount Systems, Inc., 12301 Research Boulevard, Austin, Texas 78759, USA, or (2) if FRSI is unable to
deliver replacement media which is free of defects in materials or workmanship, you may terminate this
Agreement by returning the program and your money will be refunded. IN NO EVENT WILL FRSI BE LIABLE TO
YOU FOR ANY DAMAGES ARISING OUT OF ANY CAUSES WHATSOEVER (WHETHER SUCH CAUSES BE BASED IN
CONTRACT, NEGLIGENCE, STRICT LIABILITY, OTHER TORT, PATENT INFRINGEMENT, OR OTHERWISE),
INCLUDING ANY LOST PROFITS, LOST SAVINGS, OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES
ARISING OUT OF THE USE OR INABILITY TO USE SUCH PROGRAM EVEN IF FRSI HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES, OR OF ANY CLAIM BY ANY OTHER PARTY.
GOVERNING LAW: This Agreement, and all matters concerning its construction, interpretation, performance,
or validity, shall be governed by the laws of the State of Texas.
EXPORT RESTRICTIONS: Licensee shall comply fully with all laws, regulations, decrees, and orders of the United
States of America that restrict or prohibit the exportation (or reexportation) of technical data and/or the direct
product of it to other countries, including, without limitation, the U.S. Export Administration Regulations.
U.S. GOVERNMENT RIGHTS: The programs and related materials are provided with "RESTRICTED RIGHTS." Use,
duplication, or disclosure by the U.S. Government is subject to restrictions set forth in the Federal Acquisition
Regulations and its Supplements.
THE PROGRAM IS NOT FOR USE IN ANY NUCLEAR AND RELATED APPLICATIONS. You accept the program with
the foregoing understanding and agree to indemnify and hold harmless FRSI from any claims, losses, suits,
judgements and damages, including incidental and consequential damages, arising from such use, whether
the cause of action be based in tort, contract or otherwise, including allegations that FRSI’s liability is based on
negligence or strict liability.
To the extent that a third party owns and has licensed to FRSI any portion of the program, such third party
owner shall be a beneficiary of this Agreement, and shall have the right to enforce its rights under this
Agreement independently of FRSI.
GENERAL: You may not sublicense, assign, or transfer the license or the program and related materials without
the prior written consent of FRSI. Any attempt otherwise to sublicense, assign, or transfer any of the rights,
duties, or obligations hereunder without such consent is void.
Should you have any question concerning this Agreement, please contact your FRSI representative or sales
office.
YOU ACKNOWLEDGE THAT YOU HAVE READ THIS AGREEMENT, UNDERSTAND IT, AND AGREE TO BE BOUND
BY ITS TERMS AND CONDITIONS. YOU FURTHER AGREE THAT IT IS THE COMPLETE AND EXCLUSIVE
STATEMENT OF THE AGREEMENT BETWEEN US WHICH SUPERSEDES ANY PROPOSAL OR PRIOR AGREEMENT,
EXCEPT THE MASTER LICENSE AGREEMENT, ORAL OR WRITTEN, AND ANY OTHER COMMUNICATIONS
BETWEEN US RELATING TO THE SUBJECT MATTER OF THIS AGREEMENT. YOU AGREE THAT FRSI MAY AUDIT
YOUR FACILITY TO CONFIRM COMPLIANCE OF THE FOREGOING PROVISIONS.
4
Installation Guide AMS Suite: Intelligent Device Manager
NOVEMBER 2012
Contents
Chapter 1 Introduction............................................................................................... 9
To install a standalone AMS Device Manager system.......................................................9
To install a Distributed AMS Device Manager system.......................................................9
To install AMS Device Manager on a DeltaV system......................................................... 9
To install AMS Device Manager on an Ovation system...................................................10
To install AMS Device Manager Web Services ................................................................10
About this guide...........................................................................................................10
Before you begin ..........................................................................................................11
Upgrading an AMS Device Manager system ..................................................................11
Upgrading from AMS Device Manager 10.0 or later...........................................12
Upgrading from AMS Wireless Configurator .....................................................15
Upgrading from AMS Device Configurator........................................................16
Uninstalling AMS Device Manager ................................................................................18
Chapter 2 System requirements ............................................................................... 19
Hardware requirements................................................................................................19
PC processing speed, memory, and disk space .................................................19
Serial interfaces ................................................................................................20
USB interfaces ..................................................................................................20
Network requirements .................................................................................................20
Software requirements.................................................................................................21
Operating systems ...........................................................................................21
Support for Remote Desktop Services...............................................................22
Other software requirements ...........................................................................23
Windows security requirements ...................................................................................26
AMS Device Manager installation......................................................................26
AMS Device Manager use..................................................................................26
AmsServiceUser................................................................................................27
Requirements for system interface networks ...............................................................28
Wireless............................................................................................................28
DeltaV ..............................................................................................................29
Ovation ............................................................................................................33
PROVOX ...........................................................................................................35
FF HSE ..............................................................................................................36
RS3...................................................................................................................37
STAHL ..............................................................................................................37
HART Multiplexer Network ...............................................................................38
8000 BIM..........................................................................................................38
5
AMS Suite: Intelligent Device Manager Installation Guide
NOVEMBER 2012
HART Over PROFIBUS .......................................................................................39
Kongsberg........................................................................................................39
Siemens............................................................................................................40
ABB ..................................................................................................................41
Det-Tronics.......................................................................................................41
PROFIBUS ......................................................................................................... 42
Chapter 3 Installing AMS Device Manager................................................................. 43
Requirements and constraints ...................................................................................... 44
Upgrading from a previous version of AMS Device Manager..........................................45
CONSOLIDATING DATABASES .................................................................................. 46
Consolidating Service Notes .............................................................................47
Determining computer names..........................................................................48
Installing Server Plus Station software .......................................................................... 49
Installing Client SC Station software ............................................................................. 52
Adding a user to the AMSDeviceManager group ...........................................................54
Licensing a Distributed System ..................................................................................... 55
Configuring a Distributed System................................................................................. 56
Installing SNAP-ON applications ...................................................................................56
Modifying a Distributed System....................................................................................57
Changing station types.....................................................................................58
Changing a Client SC Station to access a different Server Plus Station................58
Adding Client SC Stations .................................................................................59
Replacing an AMS Device Manager Station PC................................................... 59
Renaming an AMS Device Manager PC.............................................................. 61
Adding a new communication interface ...........................................................62
Adding more tags than currently licensed.........................................................63
Installing AMS Device Manager on domain controllers......................................63
Domain controller security requirements .........................................................64
Mobile workstation ......................................................................................................64
Licensing AMS Device Manager 12.0 on DeltaV stations................................................65
Installing AMS Device Manager 12.0 on DeltaV stations................................................66
DeltaV actions ..................................................................................................66
DeltaV Upgrade Wizard ....................................................................................67
Uninstalling DeltaV software ............................................................................ 67
Licensing AMS Device Manager 12.0 on Ovation stations..............................................68
Installing AMS Device Manager 12.0 on Ovation stations.............................................. 68
Uninstalling Ovation software .......................................................................... 69
Chapter 4 Configuring communication interfaces..................................................... 71
HART modems ...................................................................................................71
6
Installation Guide AMS Suite: Intelligent Device Manager
NOVEMBER 2012
Configuring AMS Device Manager for a HART modem ...................................... 72
Connecting a HART modem .............................................................................72
After a modem is installed ................................................................................74
Field Communicators ................................................................................................... 75
Configuring AMS Device Manager for a Field Communicator ............................76
Connecting a Field Communicator ...................................................................76
Documenting calibrators..............................................................................................77
Configuring AMS Device Manager for a documenting calibrator .......................77
Connecting a documenting calibrator ..............................................................78
Connecting devices to a documenting calibrator..............................................78
HART Multiplexer Network Interface............................................................................. 78
Preparing a HART Multiplexer Network Interface .............................................79
Configuring AMS Device Manager for a HART Multiplexer Network .................. 79
System interfaces .........................................................................................................81
Wireless............................................................................................................82
DeltaV ..............................................................................................................84
Ovation ............................................................................................................87
FF HSE ..............................................................................................................90
PROVOX ...........................................................................................................91
RS3...................................................................................................................93
STAHL HART .....................................................................................................96
8000 BIM..........................................................................................................98
HART Over PROFIBUS........................................................................................99
Kongsberg Maritime .......................................................................................101
Siemens .........................................................................................................102
ABB ................................................................................................................102
Det-Tronics.....................................................................................................104
PROFIBUS .......................................................................................................105
Determining the system interface structure and device data ..........................106
AMS Device Manager Web Services ............................................................................ 107
AMS Device Manager Web Services and AMS Asset Portal 3.2 .........................108
AMS Suite: Asset Performance Management ..................................................108
Chapter 5 Starting to Use AMS Device Manager ...................................................... 109
After installation.........................................................................................................109
Changing Windows Firewall settings...............................................................109
Usernames and passwords..............................................................................109
Logging in to User Manager ............................................................................110
Assigning an “admin” password......................................................................110
Adding a username.........................................................................................111
Changing passwords.......................................................................................112
Changing rights and permissions....................................................................112
Using AMS Device Manager ........................................................................................113
7
AMS Suite: Intelligent Device Manager Installation Guide
NOVEMBER 2012
Adding devices to an AMS Device Manager installation...................................115
DTM Launcher ................................................................................................115
AMS Suite Calibration Connector....................................................................115
Device Description Update Manager...............................................................116
Attaching a Roving Station to a Server Plus Station .........................................117
Chapter 6 Troubleshooting installation................................................................... 119
Error messages...........................................................................................................119
8
Installation Guide AMS Suite: Intelligent Device Manager
NOVEMBER 2012
1Introduction
To install a standalone AMS Device Manager
system
• Read “Before you begin” on page 11.
• Confirm that your system meets AMS Device Manager requirements starting on
page 19.
• For a new installation of a standalone AMS Device Manager system, follow the
Server Plus installation steps in section
beginning on page 43.
• For upgrading from AMS Device Manager 10.0 or later, review Tab l e 1 on
page 13 and follow the appropriate steps.
3, “Installing AMS Device Manager”
To install a Distributed AMS Device Manager
system
• Read “Before you begin” on page 11.
• Confirm that your system meets AMS Device Manager requirements starting on
page 19.
• For a new installation of a distributed AMS Device Manager system, follow the
Server Plus and Client SC installation steps in section
Manager” beginning on page 43.
• For upgrading from AMS Device Manager 10.0 or later, review Tab l e 1 on
page 13 and follow the appropriate steps.
3, “Installing AMS Device
To install AMS Device Manager on a DeltaV
system
• Read “Before you begin” on page 11.
• Confirm that your system meets minimum requirements for a co-deployment
(refer to the documentation provided with your DeltaV system).
• For a new installation of AMS Device Manager on a DeltaV system, follow the
installation steps starting on
page 66.
9
AMS Suite: Intelligent Device Manager Installation Guide
NOVEMBER 2012
To install AMS Device Manager on an Ovation system
• Read “Before you begin” on page 11.
• Confirm that your system meets minimum requirements for a co-deployment
(refer to the documentation provided with your Ovation system).
• For a new installation of AMS Device Manager on an Ovation system, follow the
installation steps starting on
page 68.
To install AMS Device Manager Web Services
• Read “Before you begin” on page 11.
• Confirm that your system meets AMS Device Manager requirements starting on
page 19.
• Follow the installation steps on page 107.
About this guide
This AMS Suite: Intelligent Device Manager Installation Guide contains the following
information:
• Section 1, “Introduction” – Provides an overview of AMS Device Manager
installation and directs you to the appropriate procedures for installing AMS
Device Manager for your setup and circumstances.
• Section 2, “System requirements” – Lists the system requirements for AMS
Device Manager, including hardware, software, and security requirements. This
section also defines additional requirements for system interface networks.
• Section 3, “Installing AMS Device Manager” – Describes the procedures for
installing AMS Device Manager software. Installing AMS Device Manager on a
DeltaV or Ovation network is also detailed.
• Section 4, “Configuring communication interfaces” – Describes how to
configure the AMS Device Manager network and install network
communication devices (HART modems, HART multiplexers, Field
Communicators, documenting calibrators, and system interface networks).
• Section 5, “Starting to Use AMS Device Manager” – Describes how to start
using AMS Device Manager and how to access additional information.
10
• Section 6, “Troubleshooting installation” – Provides troubleshooting steps you
can take if you have problems installing AMS Device Manager.
Installation Guide AMS Suite: Intelligent Device Manager
NOVEMBER 2012
For more information, refer to AMS Device Manager Books Online or contact your
local Emerson Process Management Sales/Service Office.
Before you begin
To install and use AMS Device Manager software effectively, you should be familiar
with the basic functions and operation of:
• Microsoft
• Your local area network (LAN) configuration and security
• Your communication devices and field devices
• Network components installed in your system
• AMS Device Manager security requirements (see “Starting to Use AMS Device
Manager” on page 109)
• Database backup/restore procedures (see “Backing up a database” on page 16
and “Restoring a database” on page 17)
®
Windows
®
Upgrading an AMS Device Manager system
When you upgrade to a new version of AMS Device Manager, the installation process
overwrites all existing files located in the AMS folder (except the database files and
license files). Before you upgrade, you should back up your database as a precaution
against loss of data (see
installation. In the unlikely event that database files are damaged or altered in some
way, you can use the backup files to restore the database.
Prior to upgrading your AMS Device Manager application, you should uninstall any
SNAP-ON applications on the AMS Device Manager station. You should also stop any
programs or processes that access AMS Device Manager Servers (see
page 13). You do not need to remove most of the system interfaces, such as RS3,
PROVOX, Ovation, and others.
The DeltaV System Interface requires that you re-apply the interface after upgrading
AMS Device Manager. To do this, in the Network Configuration utility, display the
properties of the DeltaV System Interface, click OK, and then click Close.
After you have completed the upgrade, start the application and right-click each of
the network icons. Select Rebuild Hierarchy followed by Scan > New Devices.
page 16). The backup files are not changed during
Ta b le 1 on
11
AMS Suite: Intelligent Device Manager Installation Guide
NOVEMBER 2012
If you are using the Alert Monitor feature, click the Alert Monitor button on the
AMS Device Manager toolbar to open the Alert List. Click the Station Monitoring
button in the toolbar and ensure that all the stations you need to monitor are
selected.
Install the latest version of the SNAP-ON applications that were removed prior to
upgrading; see
“Installing SNAP-ON applications” on page 56.
NOTICE
AMS Device Manager does not support automatic upgrading from version 9.x or
earlier. Contact customer support for instructions for your situation.
Upgrading from AMS Device Manager 10.0 or later
Ta b le 1 on page 13 provides steps for most AMS Device Manager users upgrading
from AMS Device Manager 10.0 and later.
12
Installation Guide AMS Suite: Intelligent Device Manager
NOVEMBER 2012
Table 1: Upgrading from AMS Device Manager 10.x or later
Desired 12.0 Setup
Current
Setup
Server Plus Station Client SC Station
Server Plus
Station
• Check in all calibration routes
• Back up existing database (page 16)
• Uninstall SNAP-ON applications, if
installed
2
• Uninstall AMS Suite Calibration
Connector application, if installed
• Uninstall T+H TACC components, if
installed (refer to TACC guides
downloaded from T+H)
• Remove any configured HART Over
PROFIBUS but not HART Over
PROFIBUS / Router DTM System
Interfaces
• Stop any programs or processes that
access AMS Device Manager Server
• Stop AMS Asset Portal Data
Collection or AMS Suite APM, if
running
• Stop AMS Device Manager Server in
system tray if running
• Install Server Plus Station software
(page 49)
• Get new license codes, if required
(page 55)
• Reapply the DeltaV System
Interface, if applicable (page 11)
• Install required SNAP-ON
applications (
page 56)
2
• Install AMS Suite Calibration
Connector application, if applicable
• Install new T+H TACC components,
if applicable (page 99)
• Configure HART Over PROFIBUS/
Router DTM System Interfaces, if
applicable (page 99)
• Install latest version of Web
Services, if required (page 107)
• Add all Windows Users (local or
domain) to the AMSDeviceManager
Windows group
• If you plan to continue using AMS
Asset Portal, restar t Data Collection,
but if you have purchased AMS Suite
APM, contact PlantWeb Services for
assistance.
• Check in all calibration routes
• Back up existing database (page 16)
• Consolidate existing databases, if
necessary (page 46)
• Uninstall SNAP-ON applications
• Uninstall AMS Suite Calibration
Connector application, if installed
• Uninstall T+H TACC components, if
installed (refer to TACC guides
downloaded from T+H)
• Remove any configured HART Over
PROFIBUS but not HART Over
PROFIBUS / Router DTM System
Interfaces
1
• Stop any programs or processes that
access AMS Device Manager Server
• Stop AMS Device Manager Server in
system tray if running
• Uninstall previous AMS Device
Manager software (page 18)
• Install Client SC Station software
(page 52)
• Install required SNAP-ON
applications (
page 56)
2
• Configure required communication
interfaces (page 71)
• Install new T+H TACC components,
if applicable (
page 99)
• Configure HART Over PROFIBUS/
Router DTM System Interfaces, if
applicable (
page 99)
• Add all Windows Users (local or
domain) to the AMSDeviceManager
Windows group
2
1
13
AMS Suite: Intelligent Device Manager Installation Guide
NOVEMBER 2012
Table 1: Upgrading from AMS Device Manager 10.x or later (Continued)
Desired 12.0 Setup
Current
Setup
Server Plus Station Client SC Station
Client SC
Station
• Check in all calibration routes
• Back up existing database (page 16)
• Uninstall SNAP-ON applications, if
installed
2
• Uninstall T+H TACC components, if
installed (refer to TACC guides
downloaded from T+H)
• Remove any configured HART Over
PROFIBUS but not HART Over
PROFIBUS / Router DTM System
Interfaces
• Stop any programs or processes that
access AMS Device Manager Server
• Stop AMS Device Manager Server in
system tray if running
• Uninstall previous AMS Device
Manager software (page 18)
• Install Server Plus Station software
(page 49)
• Get new license codes (page 55)
• Configure required communication
interfaces (page 71)
• Install required SNAP-ON
applications (
page 56)
2
• Install AMS Suite Calibration
Connector application, if applicable
• Install new T+H TACC components,
if applicable (page 99)
• Configure HART Over PROFIBUS/
Router DTM System Interfaces, if
applicable (page 99)
• Install latest version of Web
Services, if required (
page 107)
• Add all Windows Users (local or
domain) to the AMSDeviceManager
Windows group
• If you plan to use AMS Asset Portal,
star t Data Collection, but if you have
purchased AMS Suite APM, contact
PlantWeb Services for assistance.
• Uninstall SNAP-ON applications
• Uninstall T+H TACC components, if
installed (refer to TACC guides
downloaded from T+H)
• Remove any configured HART Over
PROFIBUS but not HART Over
PROFIBUS / Router DTM System
Interfaces
• Stop any programs or processes that
access AMS Device Manager Server
• Stop AMS Device Manager Server in
system tray if running
1
• Install Client SC Station software
(page 52)
• Reapply the DeltaV System
Interface, if applicable (page 11)
• Install required SNAP-ON
applications (
page 56)
2
• Install new T+H TACC components,
if applicable (page 99)
• Configure HART Over PROFIBUS/
Router DTM System Interfaces, if
applicable (page 99)
• Add all Windows Users (local or
domain) to the AMSDeviceManager
Windows group
2
1
14
Ta bl e 1 Notes:
1
Processes that must be stopped before upgrading include:
• AMSPlantServer
• AMSFileServer
Installation Guide AMS Suite: Intelligent Device Manager
NOVEMBER 2012
• AMSConnectionServer
• AMSOPC
• AMSGenericExports
• AmsFFServer
• AmsFFAtDeviceBroker
• AMSLicenseServer
• AmsDeviceAlertServer
• AmsHseServer
• AMSDevTypeRemote
• AMSPBServer
2
SNAP-ON applications must be uninstalled before installing the latest version.
Upgrading from AMS Wireless Configurator
To install an AMS Device Manager Server Plus or Client SC Station on a PC that has
AMS Wireless Configurator installed:
1. Open the Windows Control Panel and use Add or Remove Programs (XP) or
Programs and Features (Windows 7) to remove AMS Wireless Configurator.
2. Obtain new license codes for AMS Device Manager (see “Licensing a Distributed
System” on page 55).
3. Install AMS Device Manager (see “Installing Server Plus Station software” on
page 49 or “Installing Client SC Station software” on page 52).
4. If you installed a Server Plus Station in step 3, restore your backed up database
(see “Restoring a database” on page 17).
If you installed a Client SC Station in step 3, you may need to consolidate your backedup AMS Wireless Configurator database with an existing database (if so, refer to
“Consolidating databases” on page 46).
15
AMS Suite: Intelligent Device Manager Installation Guide
NOVEMBER 2012
Upgrading from AMS Device Configurator
AMS Device Configurator is an unlicensed, limited-feature version of AMS Device
Manager provided to DeltaV users. To upgrade to a fully licensed version of AMS
Device Manager:
1. Obtain new license codes for AMS Device Manager (see “Licensing a Distributed
System” on page 55).
2. Stop AMS Device Manager Servers (Start > All Programs > AMS Device Manager
> Terminate Servers).
3. Select Start > All Programs > AMS Device Manager > Licensing > Licensing
Wizard.
4. Follow the instructions in the Licensing Wizard.
5. Start AMS Device Manager to see the changes.
Backing up a database
To back up a database:
1. Run Database Verify/Repair to check the database for duplicate, missing, and
corrupt records (select Start > All Programs > AMS Device Manager > Database
Utilities > Database Verify Repair).
Note
For a very large database, the Verify/Repair operation can take a considerable length of
time.
2. Back up your database (select Start > All Programs > AMS Device Manager >
Database Utilities > Database Backup). Save your backup file in a location on
your local drive not in the AMS folder.
Note
If performing a database backup on a Windows 7/Windows 2008 Server PC with User
Account Control enabled, log in with a username included in the AmsDeviceManager
Windows group to avoid multiple error messages.
16
Installation Guide AMS Suite: Intelligent Device Manager
NOVEMBER 2012
Restoring a database
To restore a dat abase:
1. Close AMS Device Manager and any related applications (for example, Alert
Monitor, Server Plus Connect), if open.
2. Stop all database connections.
3. Stop AMS Device Manager Servers (Start > All Programs > AMS Device Manager
> Terminate Servers).
4. If the database backup file is located on a network drive, copy it to a local drive.
5. Select Start > All Programs > AMS Device Manager > Database Utilities >
Database Restore.
6. Select the database backup file you want to restore and click Open.
Note
If you are restoring a database that was created on a different PC and you want to retain the
Device Monitor List and Alert Monitor alerts, before you restore the database on the new
station, ensure that the names of the PC and system interfaces configured on the new
station are the same as the original station.
If performing a database restore on a Windows 7/Windows 2008 Server PC with User
Account Control enabled, log in with a username included in the AmsDeviceManager
Windows group to avoid multiple error messages.
17
AMS Suite: Intelligent Device Manager Installation Guide
NOVEMBER 2012
Uninstalling AMS Device Manager
You must uninstall AMS Device Manager software if you are upgrading from any
versions earlier than 10.0. If you are upgrading from any of these versions, contact
customer support for instructions for your situation. You do not need to uninstall
AMS Device Manager software if you are upgrading from version 10.0 or later. The
installation program modifies the earlier version and migrates the existing database
to the new version.
Manager 12.0.
Note
If you have SNAP-ON applications or the Calibration Connector application installed,
uninstall them before uninstalling AMS Device Manager. If your applications use an external
database, you must back up that database before you uninstall the application (if you want
to keep the data).
To uninstall AMS Device Manager:
1. Back up your existing database. Save your backup file in a location outside the
AMS folder.
Ta b le 1 on page 13 provides the steps to upgrade to AMS Device
2. Save your license.dat file in a location outside the AMS folder.
3. Stop the AMS Device Manager Server by right-clicking the icon in the system
tray and selecting Stop AMS Device Manager Server.
4. Open the Windows Control Panel and use Add or Remove Programs (XP) or
Programs and Features (Windows 7) to remove AMS Device Manager.
See “Consolidating databases” on page 46 for information about consolidating
multiple AMS Device Manager databases.
18
Installation Guide AMS Suite: Intelligent Device Manager
NOVEMBER 2012
2System requirements
Each PC in your system must meet minimum software and hardware requirements to
ensure successful installation and operation of AMS Device Manager. System
interface networks and SNAP-ON applications may have additional requirements.
Hardware requirements
PC processing speed, memory, and disk space
The recommended free hard disk space specified below is the amount needed for AMS
Device Manager installation, not the amount needed for daily operation (there are no
recommended minimum amounts for daily operation). If you receive a message
during installation that you do not have enough hard disk space, free up as much
space as possible and then retry the installation.
Recommended Requirements w/
Station Type
Server Plus
Station
Client SC
Station
Notes:
Additional hard disk space is required for migrating the database if you are upgrading from
an earlier version of AMS Device Manager. The amount of space required depends on the
size of the existing database.
Additional space may be required on the Server Plus Station for the database, depending
on the size of your database.
Additional hard disk space is required for SNAP-ON applications.
Set virtual memory to 2—3 times the size of the physical memory.
Minimum Requirements w/AMS
Device Manager only
Intel® Core™2 Quad, 2 GHz or
greater
3 GB or more of memory
2 GB or more of free hard disk
space
Intel® Core™2 Duo, 2.4GHz or
greater
2 GB or more of memory
2 GB or more of free hard disk
space
Intel® Core™2 Quad, 3 GHz or
greater
3 GB or more of memory
4 GB or more of free hard disk
space
N/A
AMS Suite APM or
AMS Asset Portal
If you use AMS Asset Portal version 3.2, for optimal performance, it should be
installed on a non-AMS Device Manager PC. If you choose to co-deploy with AMS
Device Manager, the PC must meet the requirements above.
19
AMS Suite: Intelligent Device Manager Installation Guide
NOVEMBER 2012
AMS Suite: Asset Performance Management is a product offering that replaces AMS
Asset Portal. The AMS Suite APM Client Framework can be installed on an AMS Device
Manager 12.0 station that meets the requirements above. Other components of AMS
Suite APM must be installed on additional non-AMS Device Manager PCs. For more
information about AMS Suite APM, contact your Emerson Process Management
Sales/Service Office.
Serial interfaces
• An RS-232 serial interface is required for a serial HART multiplexer network or
documenting calibrator.
• A serial HART modem requires a serial port with a dedicated interrupt.
USB interfaces
• A USB port and USB HART modem drivers are required to use a USB HART
modem. See the Release Notes for a list of supported modems.
• A USB port is required to connect a 375 or 475 Field Communicator using a USB
Infrared Data Association (IrDA) adapter. In some cases, IrDA drivers may be
necessary. See the Release Notes for a list of supported adapters.
• A USB port is required to connect a 475 Field Communicator or Bluetooth
modem using a USB Bluetooth adapter. Only Microsoft Bluetooth components
are supported (see the Release Notes for more information).
Network requirements
• AMS Device Manager is designed to operate on an Ethernet network running
TCP/IP.
• Mobile AMS Device Manager stations are allowed to connect wirelessly using
wireless plant network technology. Some communications slowdown can be
expected with wireless networking.
• AMS Device Manager supports deployment within a single domain or
workgroup or across multiple domains or workgroups. For more information,
refer to KBA NA-0800-0113. The Microsoft Windows Management
Instrumentation and Workstation services must be running on the PC during
installation.
20
• AMS Device Manager does not support deployment between a network
workgroup and a network domain.
Installation Guide AMS Suite: Intelligent Device Manager
NOVEMBER 2012
For information about working with network firewalls, refer to “Changing Windows
Firewall settings” on page 109.
Software requirements
Operating systems
AMS Device Manager supports the following Windows operating systems.
Operating System Ver sion
Windows XP
Windows Server 2003
Windows Server 2003 R2
Windows 7
Windows 7
Windows Server 2008
Windows Server 2008
Windows Server 2008 R2
Windows Server 2008 R2
1
Only 32-bit versions of the operating systems are supported.
2
32-bit and 64-bit versions of the operating systems are supported.
3
Only 64-bit versions of the operating systems are supported.
Professional Service Pack 3
Standard Edition Service Pack 2
Standard Edition Service Pack 2
Professional Service Pack 1
Enterprise Service Pack 1
Standard Edition Service Pack 2
Enterprise Service Pack 2
Standard Edition
Enterprise
3
3
1
1
1
2
2
2
2
See the Release Notes for additional operating systems support with DeltaV and Ovation
co-deployments.
Notes
• Intermixing of operating system families is not supported. You can use
combinations of Windows XP and Server 2003 PCs or Windows 7 and Server
2008 PCs. No other combinations are supported.
• A Server operating system (Windows Server 2003/2008) and server-class PC
(for example, Dell PowerEdge) are recommended if the database is expected to
be greater than 4 GB due to the SQL Server version required (see
page 24); or if
AMS Device Manager is installed on a DeltaV ProfessionalPLUS Station,
Application Station, or Maintenance Station and Batch Historian or VCAT will be
used. Contact your hardware vendor for recommendations on server-class PCs
and server operating systems.
21
AMS Suite: Intelligent Device Manager Installation Guide
NOVEMBER 2012
• The correct operating system service pack (SP) must be installed on your PC
before installing AMS Device Manager. If your PC does not have the correct SP
installed, or you are unsure, contact your network administrator.
• See “Changing Windows Firewall settings” on page 109 for additional operating
system configuration considerations.
• AMS Device Manager is supported on a Hyper-V virtual PC only when co-
deployed with DeltaV on the same operating systems supported in nonvirtualized environments.
Support for Remote Desktop Services
Remote Desktop Services (also known as Terminal Services) is a component of
Microsoft Windows (both server and client versions) that allows you to access
applications and data on a remote computer over a network, even from a client
computer that is running an earlier version of Windows. AMS Device Manager can be
used in Remote Desktop Services environment if the following conditions are met:
• Remote Desktop Services must be set up prior to AMS Device Manager
installation.
• Use of Remote Desktop Services is limited to 5 concurrent sessions when AMS
Device Manager is installed on Windows server-class computers.
Note
Do not attempt to install AMS Device Manager using Remote Desktop Services; this is not a
supported installation method and may produce undesirable results.
• AMS Device Manager is not supported on a Windows Server PC where Remote
Desktop Services
• If multiple users are running AMS Device Manager in a Remote Desktop session,
is set to Relaxed Security.
and one of the users runs Terminate Servers, the AMS Device Manager
application and AMS Device Manager Servers shut down for all users.
Note
In a Remote Desktop Services environment, only 1 AMS ValveLink SNAP-ON application
session is permitted at any given time. The AMS Wireless SNAP-ON application is not
supported in a Remote Desktop Services environment.
Contact Microsoft for Remote Desktop Services licensing information. Questions
about AMS Device Manager licensing requirements should be directed to your
Emerson Process Management Sales/Service Office.
22
Installation Guide AMS Suite: Intelligent Device Manager
NOVEMBER 2012
Other software requirements
Web browser
AMS Device Manager requires Microsoft Internet Explorer (IE) Version 6.0, SP 1 or
later. If you do not have a supported version of Internet Explorer, contact your IT
department for assistance.
AMS Device Manager Web Services
Microsoft Internet Information Services (IIS) and AMS Device Manager 12.0 Server
Plus software must be installed on your system before you can install AMS Device
Manager Web Services. AMS Device Manager Web Services is not supported on Client
SC stations. If you do not have IIS installed, contact your IT department for assistance.
Note
Some control systems do not allow IIS to be installed on the same PC. Check your control
system documentation to determine IIS compatibility.
Note
If you want to install AMS Device Manager Web Services on a DeltaV station, it must be a
DeltaV Application or ProfessionalPLUS station.
.NET Framework
AMS Device Manager 12.0 requires and installs Microsoft .NET Framework 4.0 and
3.5 Service Pack 1. Microsoft .NET Framework 3.5 SP1 is a cumulative update that
includes the following versions:
• 2.0
• 2.0 SP2
• 3.0
• 3.0 SP2
• 3.5
23
AMS Suite: Intelligent Device Manager Installation Guide
NOVEMBER 2012
Database–Microsoft SQL Server 2008
AMS Device Manager 12.0 uses a named instance, Emerson2008, of SQL Server 2008
for its database. The default password for this named instance is 42Emerson42Eme.
The size of your database determines which edition of SQL Server 2008 you must use:
• If your database is less than 4 GB, you can use SQL Server 2008 Express. The AMS
Device Manager setup installs this version.
• If your database is greater than 4 GB or will be at some future time, you must
install a full version of SQL Server 2008
(You must purchase one of these separately if you do not already have it.) These
versions of SQL Server recommend server operating systems.
Note
The AMS Device Manager database must be located on the AMS Device Manager Server
Plus Station. Any other location is not supported.
NOTICE
before you install AMS Device Manager.
Do not use the Windows compress feature on the PC drive where AMS Device
Manager is installed. AMS Device Manager will be unable to open your database
information. Reinstallation of AMS Device Manager will be required.
The AMS Device Manager installation program installs or updates SQL Server on your
PC as follows:
• If no SQL Server is installed, the AMS Device Manager installation program will
install SQL Server 2008 and create an Emerson2008 named instance with a
password of 42Emerson42Eme.
• If an instance of SQL 2008 Express is installed, but not the Emerson2008 named
instance, the AMS Device Manager installation program will create the
Emerson2008 named instance with a password of 42Emerson42Eme.
• If the SQL Server 2008 Emerson2008 named instance is already installed, the
AMS Device Manager installation program will continue with the next part of
the installation program. Access to the SQL Server system administrator (‘sa’)
account is required. If you do not have access, contact your network
administrator for more information.
• If you have previously installed a full version of SQL Server 2008, you should
create an SQL named instance of Emerson2008 prior to installing AMS Device
Manager (refer to your SQL Server documentation). Otherwise, the AMS Device
Manager installation will install SQL 2008 Express.
24
A Microsoft SQL Server 'sa' account password is required for AMS Device Manager
operation. Therefore, the AMS Device Manager setup creates a password
(42Emerson42Eme) for the Emerson2008 named instance. For security reasons, it is
recommended that you change the SQL password.
Installation Guide AMS Suite: Intelligent Device Manager
NOVEMBER 2012
To change an SQL Server ‘sa’ account password on your AMS Device Manager station:
1. Insert the AMS Device Manager program DVD in the DVD drive of the target PC.
2. Select Start > Run from the Windows taskbar.
3. In the text box, type CMD and click OK to open the command prompt.
4. At the command prompt, type:
D:\TECH_SUPPORT_UTILITIES\CHANGE_SA_PASSWORD\SQLPASWD_SQLSER
VER <oldpassword> <newpassword>
Where:
D is the DVD drive letter
<oldpassword> is the default (42Emerson42Eme) or other current SQL password
<newpassword> is the password you want to use
5. Press ENTER. You should see the message "The SA password in SQL has been
changed from oldpassword to newpassword."
6. Close the command prompt.
Note
Your local Windows security policies may prevent you from changing the ‘sa’ password
again until a predetermined length of time has elapsed.
Software supported for Drawings and Notes
• Microsoft Word 2003, 2007, and 2010
• Microsoft Excel 2003, 2007, and 2010
• WordPad
25
AMS Suite: Intelligent Device Manager Installation Guide
NOVEMBER 2012
Windows security requirements
AMS Device Manager installation
Installation of AMS Device Manager has these security requirements:
• Local or domain administrator rights for the PC(s) on which AMS Device
Manager is to be installed.
• If you are installing AMS Device Manager on a PC that has the correct version of
SQL Server and the Emerson2008 named instance (see
SQL Server 2008” on page 24), you need to know the SQL Server ‘sa’ account
password, if a password other than the default (42Emerson42Eme) has been
set.
• During the AMS Device Manager installation, the Use simple file sharing
(Windows XP) option is automatically disabled. To avoid any AMS Device
Manager operational issues, leave this option disabled.
“Database–Microsoft
Other network security requirements may also apply to the installation. Contact your
network administrator for more information.
AMS Device Manager use
The AMS Device Manager installation creates the AMSDeviceManager Windows user
group on the PC. Members of this group have all the permissions necessary to
operate AMS Device Manager. The Windows user must be a member of this group on
all AMS Device Manager stations. Windows users must be members of the
AMSDeviceManager group before their properties can be changed in User Manager.
To add a new user, see the
page 109.
“Usernames and passwords” procedures beginning on
26
Installation Guide AMS Suite: Intelligent Device Manager
NOVEMBER 2012
AmsServiceUser
A Windows user account called AmsServiceUser is automatically created on each
AMS Device Manager station and added to the Users Windows user group unless the
station is installed on a Windows domain controller. If AMS Device Manager is
installed on a domain controller, all other stations that are part of that domain use the
domain account, not a local account.
The AmsServiceUser account is made a member of the AMSDeviceManager Windows
group on all AMS Device Manager stations as well as a member of the Users Windows
user group on non-domain controller stations. This user account runs the AMS Device
Manager Servers. If your AMS Device Manager system is located on a network that
requires periodic changing of passwords, the AmsServiceUser account password can
be changed using the AMSPasswordUtility.exe utility from the AMS\Bin folder on
each AMS Device Manager station. Do not use the Windows User Manager to change
this password as AMS Device Manager will no longer launch.
Note
If the AMS Suite Calibration Connector application (page 115) is installed when you change
the password for the AmsServiceUser, you must also change the password for
AmsCalibrationConnectorWS properties. This requires a change in the Windows Services
console of your workstation. If you are unsure how to do this, contact your IT department.
27
AMS Suite: Intelligent Device Manager Installation Guide
NOVEMBER 2012
Requirements for system interface networks
Requirements for system interface networks are in addition to the hardware and
software requirements for AMS Device Manager.
Wireless
The Wireless System Interface requires:
• An Ethernet adapter to connect to the gateway.
• One or more (up to 16) wireless gateways that allow communication between
the AMS Device Manager station and a collection of wireless devices.
• WirelessHART devices. Refer to the AMS Device Manager Supported Device List
for a list of supported WirelessHART devices. The Supported Device List can be
accessed after AMS Device Manager installation is complete (select Start > All
Programs > AMS Device Manager > Help > Supported Device List).
• A valid SSL certificate (if using the optional Security Setup utility) allowing the
AMS Device Manager station to securely communicate with the gateway.
Contact your local Emerson Process Management Sales/Service Office for more
information about the Security Setup utility and certificate.
28
Installation Guide AMS Suite: Intelligent Device Manager
NOVEMBER 2012
DeltaV
DeltaV System Interface station software requirements:
• AMS Device Manager 12.0 can be installed on the following DeltaV 9.3.1,
10.3.1, 11.3, 11.3.1, 12.3 stations:
DeltaV Workstations AMS Device Manager Software
ProfessionalPLUS Station Server Plus or Client SC
ProfessionalPLUS as Remote Client Server Server Plus or Client SC
Local Application Station Server Plus or Client SC
Remote Application Station Server Plus or Client SC
Local "Operate" Station
• Professional
• Operator
• Base
• Maintenance
Operator Station as Remote Client Server Client SC only
Remote "Operate" Station
• Professional
• Operator
• Base
• The DeltaV System Interface must be configured on a licensed AMS Device
Server Plus or Client SC
Client SC only
Manager station that is on the DeltaV network.
To install AMS Device Manager on a DeltaV network, see the procedures in “Installing
AMS Device Manager 12.0 on DeltaV stations” on page 66.
• For HART support only, AMS Device Manager 12.0 can be installed on a
separate PC connected to a DeltaV 9.3.1 or 10.3.1 ProfessionalPLUS Station
through a separate Ethernet connection. Contact your local Emerson Process
Management Sales/Service Office for more information.
• AMS Device Manager 12.0 supports DeltaV version 11.3 and later in co-
deployed installations only.
• If the Server Plus software is not on a DeltaV station, the SI and Simulate
dongles cannot be used to license AMS Device Manager — a license.dat file is
required.
29
AMS Suite: Intelligent Device Manager Installation Guide
NOVEMBER 2012
• Supported HART I/O hardware and software revision:
— Analog Input HART Module, 8-channel, Series 1, Revision 2.21 or higher
— Analog Input HART Module, 8-channel, Series 2, Revision 1.26 or higher
— Analog Input HART Module, 16-channel, Revision 1.17 or higher
— Analog Output HART Module, Series 1, Revision 2.25 or higher
— Analog Output HART Module, Series 2, Revision 1.26 or higher
— HART AI 8 Channel Card, S-Series, Revision 1.26 or higher
— HART AI 16 Channel Card, S-Series, Revision 1.17 or higher
— HART AO Card, S-Series, Revision 1.26 or higher
• Supported Intrinsically Safe HART I/O hardware and software revision:
— Analog Input HART Module, 8-channel, Revision 2.39 or higher
— Analog Output HART Module, 8-channel, Revision 2.00 or higher
• Supported Zone I/O hardware and software revision:
— Analog Input or Analog Output, Revision 1.14 or higher
• Supported FOUNDATION fieldbus I/O hardware and software revision:
— Fieldbus H1, Series 1, Revision 1.8 or higher (does not support fieldbus
alerts)
— Fieldbus H1, Series 2, Revision 2.2 or higher
— Fieldbus H1 S-Series Integrated Power, Revision 4.87 or higher
— Fieldbus H1 S-Series, Revision 2.2 or higher
• Supported CHARM I/O hardware and software revision:
— CHARM I/O Carrier (CIOC), Revision 11.3.1 or higher
— AI 4-20 mA HART CHARM, Revision 1.18 or higher
— AO 4-20 mA HART CHARM, Revision 1.18 or higher
— AI 4-20 mA HART (Intrinsically Safe) IS, Revision TBD (Contact your local
Emerson Process Management Sales/Service Office for more
information.)
30
— AO 4-20 mA HART (Intrinsically Safe) IS, Revision TBD (Contact your local
Emerson Process Management Sales/Service Office for more
information.)
Loading...