AMS AMS Device Manager v14.5 Planning and Installation Guide Manuals & Guides

Download

AMS Device Manager

Version 14.5 Planning and Installation Guide

Planning and Installation Guide

January 2022

Document history

Date Description

May 2017 Update, software version 13.5

May 2018 Update, software version 14.0

October 2019 Update, software version 14.1.1

September 2020 Update, software version 14.5 (managed)

January 2022 Update, software version 14.5 (general)

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 Device Manager

If the site at which this Program is used is a Licensed Facility under a Master License Agreement between You and FisherRosemount 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 Contract Management, FisherRosemount Systems, Inc., 1100 W Louis Henna Blvd, Round Rock, Texas 78681.

Software License Agreement for AMS Device Manager

BY OPENING THE SOFTWARE PACKAGE, INDICATING ASSENT ELECTRONICALLY, OR DOWNLOADING, INSTALLING, COPYING, OR USING THE SOFTWARE, YOU AGREE TO ACCEPT THE TERMS AND CONDITIONS OF THIS SOFTWARE LICENSE AGREEMENT (THE “AGREEMENT”). IF YOU DO NOT AGREE WITH THESE TERMS AND CONDITIONS, DO NOT CONTINUE DOWNLOADING, INSTALLING, COPYING OR USING THE SOFTWARE AND RETURN THE SOFTWARE FOR A REFUND.

Fisher Rosemount Systems, Inc., an Emerson Automation Solutions company (“Emerson”) provides the Software for your use. As used in this Agreement, the term “Software” refers to software, firmware and all related access keys, license management devices, documentation (e.g., manuals and specifications) and libraries as well as revisions or updates to the foregoing provided by Emerson or its distributor.

LICENSE AND RESTRICTIONS: Subject to your compliance with this Agreement and payment of applicable fees, Emerson grants you a non-transferable, non-exclusive license to: (a) use the Software provided to you to run on a single machine solely for your internal business purpose; and (b) copy the Software for backup purposes. A single machine may consist of a single physical machine with a single operating system or a single virtual machine running in a hosted environment. You may transfer the Software to another physical or virtual machine (e.g., a replacement machine), but only if you uninstall or otherwise delete the Software from the physical or virtual machine on which the Software was previously installed. Your license to use the software may be perpetual or subject to a subscription period as specified in the documentation governing your purchase of the license. You agree not to exceed any limits applicable to your use of the Software (e.g., as may be identified in the documentation for the Software) nor use any features of the Software for which you have not purchased a license. Emerson may use technological and/or other measures to prevent unlicensed access to and/or use of the Software and/or its features, and you acknowledge and agree to the use of such measures, and that you shall not circumvent nor attempt to circumvent such measures. You must reproduce and include the copyright notice on any copy. YOU MAY NOT REVERSE ENGINEER, DECOMPILE, USE, COPY OR MODIFY THE SOFTWARE OR ANY BACKUP COPY (PERMITTED ABOVE), IN WHOLE OR IN PART, EXCEPT AS EXPRESSLY PROVIDED IN THIS LICENSE. IF YOU TRANSFER POSSESSION OF THE SOFTWARE OR ANY COPY TO ANOTHER PARTY, YOUR LICENSE IS AUTOMATICALLY TERMINATED AND NO RIGHTS ARE TRANSFERRED TO SUCH OTHER PARTY. Unless otherwise expressly permitted in writing, you may not use the Software to provide hosted services, subscription services, training services, consulting services, service bureau, time sharing, or rental use to third parties. No license, express or implied, is granted under any intellectual property directly or indirectly owned by Emerson which does not specifically read on the Software 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.

SECURITY ASSESSMENTS: In the event you wish to assess the vulnerability of the Software (including conducting a penetration test or any other form of vulnerability assessment or test), you agree to obtain Emerson’s prior written consent. Emerson will not unreasonably withhold or unduly delay such consent, but you agree that Emerson may require that: (i) Emerson participate in any such tests/assessments, (ii) receive the results of such tests/assessments, and (iii) you not publish, distribute, or otherwise make available the results (in whole or part) to any third party without the express written consent of Emerson. Emerson may further require that any such tests/assessments be conducted in accordance with and subject to a separate written agreement between you and Emerson.

DIGITAL SIGNATURES: Emerson may attach or otherwise associate digital signatures to files of the Software to aid detection of subsequent modifications to such files. However, in attaching or associating such digital signatures, Emerson does not (i) guarantee that the Software or the files can be trusted, nor (ii) assume any liability or claim authorship with regard to third party files.

DATA PRIVACY AND USE: When you download, install or use the Software, Emerson may use automatic means to collect information about your device and about your use of the Software. You also may be required to provide certain information about yourself as a condition to downloading, installing or using the Software or certain of its features or functionality, and the Software may provide you with opportunities to share information about yourself with others. We may collect information, including but not limited to information relating to the manner or frequency of your use of the Software. This includes data that we collect as part of our services. Some of the data we collect is relatively static, such as data about the product (for example, serial numbers and device IDs and the Emerson model and serial number), but other data is more dynamic, such as information about current and past product usage levels, information about abnormal product functioning, information about the status and location of products used with the Software and/or your device. We collect this data from you and the product and transmit it through your network and/or Internet services. Monitoring may continue until the Software is deleted or the services are cancelled or terminated. Note that if you do not allow us to collect this information, we may not be able to provide the full capabilities of products and services. All information we collect through or in connection with this Software and the use of the Software in connection with Emerson products is subject to the Emerson privacy notice found at https://www.emerson.com/enus/privacy-notice (“the Privacy Notice”). We will collect, use and disclose your personal information and the personal information of your additional users as set out in that Privacy Notice, and you and the additional users or third parties you have granted access or control consent to us doing so. The Privacy Notice applies subject to requirements of local law. In the event of a conflict between the Privacy Notice and applicable data protection laws, the stricter obligation applies. Furthermore, the data that is generated and collected by the Software may be stored in a hosted environment at a location identified to you in the documentation for the Software. You are solely responsible for compliance with all applicable local, state and federal data sovereignty laws, regulations and restrictions as it relates to the movement of data generated and collected by the Software.

TITLE: Title to and ownership of the Software, including all copies of the Software, shall at all times remain with Emerson or its licensors. Your right to use the same is at all times subject to the terms and condition of this Agreement. Emerson may, from

time to time, revise or update the Software and, in so doing, incurs no obligation to furnish such revisions or updates to you, except as otherwise provided in a separate written agreement.

TERM: You may terminate this license at any time by destroying the Software together with all copies in any form. This license 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 promptly (i) destroy the Software together with all copies in any form and confirm such destruction in writing to Emerson or (ii) return the Software and all copies to Emerson.

LIMITED WARRANTY: Emerson warrants the media on which the Software 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, Emerson does not warrant that the functions contained in the Software will meet your requirements or that the operation of the Software will be uninterrupted or error free. In addition, Emerson does not warrant that the Software or any equipment, system, or network on which the Software is used will be free of vulnerability to intrusion or attack. THE SOFTWARE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. EMERSON MAKES NO REPRESENTATIONS OR WARRANTIES ON BEHALF OF ITS LICENSORS.

LIMITATIONS OF REMEDIES: Emerson's entire liability and your exclusive remedy shall be: (i) the replacement of any media that does not conform with Emerson's "Limited Warranty" and which is returned with a copy of your invoice to Emerson, or (ii) if Emerson is unable to deliver a replacement media which is free of defects in materials or workmanship, you may terminate this Agreement by returning the Software and your money will be refunded. IN NO EVENT WILL EMERSON 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 EMERSON HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, OR OF ANY CLAIM BY ANY OTHER PARTY. TO THE EXTENT THE FOREGOING LIMITATION IS UNENFORCEABLE, EMERSON’S TOTAL LIABILITY WILL BE LIMITED TO DIRECT DAMAGES UP TO THE AMOUNT YOU ACTUALLY PAID FOR THE SOFTWARE GIVING RISE TO THE LIABILITY.

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, excluding its conflict laws. The 1980 United Nations Convention on Contracts for the International Sale of Goods does not apply to this Agreement.

EXPORT RESTRICTIONS: You 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: With respect to acquisition of the Software by or for the United States government, the Software is provided with "RESTRICTED RIGHTS" and is classified as “Commercial Computer Software,” as the term is defined in the applicable provisions of the Federal Acquisition Regulations and its supplements including the Department of Defense FAR Supplements. The terms and conditions of this Agreement govern the United States government’s use of the Software, except to the extent any term or condition is inconsistent with the federal laws of the United States.

GENERAL: You may not sublicense, assign, or transfer the license or the Software without the prior written consent of Emerson. Any attempt otherwise to sublicense, assign or transfer any of the rights, duties, or obligations hereunder without such consent is void.

NUCLEAR APPLICATIONS: THE SOFTWARE IS NOT FOR USE IN ANY NUCLEAR AND RELATED APPLICATIONS. You accept the Software with the foregoing understanding and agree to indemnify and hold harmless Emerson from any claims, losses, suits, judgments 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 Emerson’s liability is based on negligence or strict liability.

THIRD PARTY SOFTWARE: To the extent that a third-party owns any portion of the Software licensed under this Agreement, 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 Emerson. Any third-party Software, not licensed under this Agreement, shall be subject to third-party owner’s applicable license agreement and registration requirement, and you authorize Emerson to provide your contact information, including company name, mailing address, telephone number, ship-to recipient address, and primary contact’s name, mailing address, telephone number, and email address, to such third-party owner for the purposes of product registration, support, and compliance with applicable import and export control laws, regulations, orders, and requirements.

Should you have any question concerning this Agreement, please contact your Emerson 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, ORAL OR WRITTEN, AND ANY OTHER COMMUNICATIONS BETWEEN US RELATING TO THE SUBJECT MATTER OF THIS AGREEMENT. YOU AGREE THAT EMERSON MAY AUDIT YOUR FACILITY AND RECORDS TO CONFIRM COMPLIANCE WITH THE TERMS OF THIS AGREEMENT. EMERSON AGREES TO PROVIDE A REASONABLE WRITTEN NOTICE PRIOR TO CONDUCTING SUCH AN AUDIT AND AGREES TO CONDUCT THE AUDIT DURING REGULAR BUSINESS HOURS WITHOUT UNREASONABLY INTERFERING WITH YOUR NORMAL BUSINESS OPERATION.

Third Party and Open-source Software Notice

The Software contains certain 3rd party (including “open source”) content, and Emerson makes the Software available to you under the terms and conditions of the 3rd party license agreements governing such content. The following copyright statements and licenses apply to various 3rd party content, which is distributed with the Software.

[AMSDeviceManager_Development_Main : 14.5] Components: Entity Framework 6.1.0 : (Apache License 2.0 AND Microsoft .NET Library License) NUnit Framework 2.5.9.10348 : Nunit License Prism Library v7.2.0.1233-pre-pre : MIT License quicklinkapi4net r56 : MIT License WoWHead-data-parser master-20120622 : Copyright Text: NUnit Framework 2.5.9.10348 sourceforge:nunit/2.5.9.10348 Copyright © 2010 Charlie Poole. All Rights Reserved Copyright ? 2002-2008 Charlie Poole Copyright © 2002-2009 Charlie Poole Copyright Copyright © 2002-2004 James W. Newkirk, Michael C. Two, Alexei A. Vorontsov Copyright (C) 2002-2003 James W. Newkirk, Michael C. Two, Alexei A. Vorontsov. \nCopyright (C) 2000-2003 Philip Craig.\nAll

http:'nunit.org/?p=license&r=2.4' *********************************** Copyright (c) 2007")[assembly:AssemblyTrademarkAttribute("")];[assembly:AssemblyCultureAttribute("")]; Copyright ? 2002-2008 Charlie Poole or Copyright Copyright 2007, Charlie Poole// This is free software licensed under the NUnit license. You may// obtain a copy of the license at

http://nunit.org/?p=license&r=2.4// ******************************* copyright information at the start of the program.The /help or /? option displays a brief help

message Copyright ? 2002-2004 James W. Newkirk, Michael C. Two, Alexei A. Vorontsov Copyright © 2002-2009 Charlie Poole or Copyright ? 2000-2002 Philip A. Craig © 2000-2002 Philip A. Craig2. Altered source versions must be plainly marked as such, and must not be

misrepresented as being the original software.3. This notice may not be rem © 2002-2004 James W. Newkirk, Michael C. Two, Alexei A. Prism Library v7.2.0.1233-pre-pre github:PrismLibrary/Prism:v7.2.0.1233-pre-pre Copyright © 2014")[assembly: AssemblyTrademark("")][assembly: AssemblyCulture("")] Copyright (c) .NET Foundation Copyright © 2016")[assembly: AssemblyTrademark("")][assembly: AssemblyCulture("")] Copyright © 2017")[assembly: AssemblyTrademark("")][assembly: AssemblyCulture("")] Copyright © 2014")[assembly: AssemblyTrademark("")][assembly: AssemblyCulture("")][assembly: ComVisible(false)] Copyright © 2015")[assembly: AssemblyTrademark("")][assembly: AssemblyCulture("")][assembly: CLSCompliant(true)] WoWHead-data-parser master-20120622 unknown:undefined Copyright; descriptionLabel.Text companyLabel.Text += AssemblyCompany; base.OnLoad(e); } Copyright; } } Copyright © Heisenberg 2011")[assembly: AssemblyTrademark("")][assembly: AssemblyCulture("")] Copyright { get { object[] attributes =

Assembly.GetExecutingAssembly().GetCustomAttributes(typeof(AssemblyCopyrightAttribute), ©", @"©") .Replace(@" .Replace(@"¬", @"¬") .Replace(@"<name>", @"$N") .Replace(@"<class>", @"$C") quicklinkapi4net r56 unknown:undefined

Copyright (C) EyeTech Digital Systems * // Original Author: Caleb Hinton * // All rights reserved Copyright © 2010")[assembly: AssemblyTrademark("")][assembly: AssemblyCulture("")]// Setting ComVisible to false makes the

types in this assembly not visible // to COM components. If you n Copyright (c) 2010-2011 Justin Weaver Copyright (c) 2010-2011 Justin WeaverHomepage: http://quicklinkapi4net.googlecode.com Copyright (c) 2010-2011 Justin Weaver * * Permission is hereby granted, free of charge, to any person obtaining a copy * of this

software and associated documentation files (the "Software"), to Licenses: Apache License 2.0 (Entity Framework 6.1.0) Apache License Version 2.0, January 2004 ========================= http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by

the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.

3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: a. You must give any other recipients of the Work or Derivative Works a copy of this License; and b. You must cause any modified files to carry prominent notices stating that You changed the files; and c. You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and d. If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do

not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.

5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.

6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.

8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS

APPENDIX: How to apply the Apache License to your work To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

--Microsoft .NET Library License (Entity Framework 6.1.0) MICROSOFT SOFTWARE LICENSE TERMS MICROSOFT .NET LIBRARY ================================ These license terms are an agreement between Microsoft Corporation (or based on where you live, one of its affiliates) and you. Please read them. They apply to the software named above, which includes the media on which you received it, if any. The terms also apply to any Microsoft * updates, * supplements, * Internet-based services, and * support services for this software, unless other terms accompany those items. If so, those terms apply. BY USING THE SOFTWARE, YOU ACCEPT THESE TERMS. IF YOU DO NOT ACCEPT THEM, DO NOT USE THE SOFTWARE.

-------------------------------------------------------------------------------IF YOU COMPLY WITH THESE LICENSE TERMS, YOU HAVE THE PERPETUAL RIGHTS BELOW.

1. INSTALLATION AND USE RIGHTS. a. Installation and Use. You may install and use any number of copies of the software to design, develop and test your programs. You may modify, copy, distribute or deploy any .js files contained in the software as part of your programs. b. Third Party Programs. The software may include third party programs that Microsoft, not the third party, licenses to you under this agreement. Notices, if any, for the third party program are included for your information only.

2. ADDITIONAL LICENSING REQUIREMENTS AND/OR USE RIGHTS. a. DISTRIBUTABLE CODE. In addition to the .js files described above, the software is comprised of Distributable Code. "Distributable Code" is code that you are permitted to distribute in programs you develop if you comply with the terms below. i. Right to Use and Distribute.

* You may copy and distribute the object code form of the software. * Third Party Distribution. You may permit distributors of your programs to copy and distribute the Distributable Code as part of those programs. b. Distribution Requirements. For any Distributable Code you distribute, you must * use the Distributable Code in your programs and not as a standalone distribution; * require distributors and external end users to agree to terms that protect it at least as much as this agreement; * display your valid copyright notice on your programs; and * indemnify, defend, and hold harmless Microsoft from any claims, including attorneys' fees, related to the distribution or use of your programs. c. Distribution Restrictions. You may not * alter any copyright, trademark or patent notice in the Distributable Code; * use Microsoft's trademarks in your programs' names or in a way that suggests your programs come from or are endorsed by Microsoft; * include Distributable Code in malicious, deceptive or unlawful programs; or * modify or distribute the source code of any Distributable Code so that any part of it becomes subject to an Excluded License. An Excluded License is one that requires, as a condition of use, modification or distribution, that * the code be disclosed or distributed in source code form; or * others have the right to modify it. * SCOPE OF LICENSE. The software is licensed, not sold. This agreement only gives you some rights to use the software. Microsoft reserves all other rights. Unless applicable law gives you more rights despite this limitation, you may use the software only as expressly permitted in this agreement. In doing so, you must comply with any technical limitations in the software that only allow you to use it in certain ways. You may not * work around any technical limitations in the software; * reverse engineer, decompile or disassemble the software, except and only to the extent that applicable law expressly permits, despite this limitation; * publish the software for others to copy; * rent, lease or lend the software; or * transfer the software or this agreement to any third party. * BACKUP COPY. You may make one backup copy of the software. You may use it only to reinstall the software. * DOCUMENTATION. Any person that has valid access to your computer or internal network may copy and use the documentation for your internal, reference purposes. * EXPORT RESTRICTIONS. The software is subject to United States export laws and regulations. You must comply with all domestic and international export laws and regulations that apply to the software. These laws include restrictions on destinations, end users and end use. For additional information, see www.microsoft.com/exporting

* SUPPORT SERVICES. Because this software is "as is," we may not provide support services for it. * ENTIRE AGREEMENT. This agreement, and the terms for supplements, updates, Internet-based services and support services that you use, are the entire agreement for the software and support services. * APPLICABLE LAW. a. United States. If you acquired the software in the United States, Washington state law governs the interpretation of this agreement and applies to claims for breach of it, regardless of conflict of laws principles. The laws of the state where you live govern all other claims, including claims under state consumer protection laws, unfair competition laws, and in tort. b. Outside the United States. If you acquired the software in any other country, the laws of that country apply. * LEGAL EFFECT. This agreement describes certain legal rights. You may have other rights under the laws of your country. You may also have rights with respect to the party from whom you acquired the software. This agreement does not change your rights under the laws of your country if the laws of your country do not permit it to do so. * DISCLAIMER OF WARRANTY. THE SOFTWARE IS LICENSED "AS-IS." YOU BEAR THE RISK OF USING IT. MICROSOFT GIVES NO EXPRESS WARRANTIES, GUARANTEES OR CONDITIONS. YOU MAY HAVE ADDITIONAL CONSUMER RIGHTS OR STATUTORY GUARANTEES UNDER YOUR LOCAL LAWS WHICH THIS AGREEMENT CANNOT CHANGE. TO THE EXTENT PERMITTED UNDER YOUR LOCAL LAWS, MICROSOFT EXCLUDES THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. FOR AUSTRALIA – YOU HAVE STATUTORY GUARANTEES UNDER THE AUSTRALIAN CONSUMER LAW AND NOTHING IN THESE TERMS IS INTENDED TO AFFECT THOSE RIGHTS. * LIMITATION ON AND EXCLUSION OF REMEDIES AND DAMAGES. YOU CAN RECOVER FROM MICROSOFT AND ITS SUPPLIERS ONLY DIRECT DAMAGES UP TO U.S. $5.00. YOU CANNOT RECOVER ANY OTHER DAMAGES, INCLUDING CONSEQUENTIAL, LOST PROFITS, SPECIAL, INDIRECT OR INCIDENTAL DAMAGES. This limitation applies to * anything related to the software, services, content (including code) on third party Internet sites, or third party programs; and * claims for breach of contract, breach of warranty, guarantee or condition, strict liability, negligence, or other tort to the extent permitted by applicable law. It also applies even if Microsoft knew or should have known about the possibility of the damages. The above limitation or exclusion may not apply to you because your country may not allow the exclusion or limitation of incidental, consequential or other damages. Please note: As this software is distributed in Quebec, Canada, some of the clauses in this agreement are provided below in French. Remarque : Ce logiciel étant distribué au Québec, Canada, certaines des clauses dans ce contrat sont fournies ci-dessous en français. EXONÉRATION DE GARANTIE. Le logiciel visé par une licence est offert « tel quel ». Toute utilisation de ce logiciel est à votre seule risque et péril. Microsoft n'accorde aucune autre garantie expresse. Vous pouvez bénéficier de droits additionnels en vertu du droit local sur la protection des consommateurs, que ce contrat ne peut modifier. La ou elles sont permises par le droit locale, les garanties implicites de qualité marchande, d'adéquation

à un usage particulier et d'absence de contrefaçon sont exclues. LIMITATION DES DOMMAGES-INTÉRÊTS ET EXCLUSION DE RESPONSABILITÉ POUR LES DOMMAGES. Vous pouvez obtenir de Microsoft et de ses fournisseurs une indemnisation en cas de dommages directs uniquement à hauteur de 5,00 $ US. Vous ne pouvez prétendre àaucune indemnisation pour les autres dommages, y compris les dommages spéciaux, indirects ou accessoires et pertes de bénéfices. Cette limitation concerne : * tout ce qui est relié au logiciel, aux services ou au contenu (y compris le code) figurant sur des sites Internet tiers ou dans des programmes tiers ; et * les réclamations au titre de violation de contrat ou de garantie, ou au titre de responsabilité stricte, de négligence ou d'une autre faute dans la limite autorisée par la loi en vigueur. Elle s'applique également, même si Microsoft connaissait ou devrait connaître l'éventualité d'un tel dommage. Si votre pays n'autorise pas l'exclusion ou la limitation de responsabilité pour les dommages indirects, accessoires ou de quelque nature que ce soit, il se peut que la limitation ou l'exclusion ci-dessus ne s'appliquera pas à votre égard. EFFET JURIDIQUE. Le présent contrat décrit certains droits juridiques. Vous pourriez avoir d'autres droits prévus par les lois de votre pays. Le présent contrat ne modifie pas les droits que vous confèrent les lois de votre pays si celles-ci ne le permettent pas.

--MIT License (quicklinkapi4net r56) /* QuickLinkDotNET : A .NET wrapper (in C#) for EyeTech's QuickLink API. * * Copyright (c) 2010-2011 Justin Weaver * * Permission is hereby granted, free of charge, to any person obtaining a copy * of this software and associated documentation files (the "Software"), to * deal in the Software without restriction, including without limitation the * rights to use, copy, modify, merge, publish, distribute, sublicense, and/or * sell copies of the Software, and to permit persons to whom the Software is * furnished to do so, subject to the following conditions: * * The above copyright notice and this permission notice shall be included in * all copies or substantial portions of the Software. * * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE * AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS * IN THE SOFTWARE

--MIT License (Prism Library v7.2.0.1233-pre-pre)

The MIT License (MIT) Copyright (c) .NET Foundation All rights reserved. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files

(the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED

TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE

--Nunit License (NUnit Framework 2.5.9.10348) Nunit License ============= Copyright © 2002-2012 Charlie Poole Copyright © 2002-2004 James W. Newkirk, Michael C. Two, Alexei A. Vorontsov Copyright © 2000-2002 Philip A. Craig This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:

1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment (see the following) in the product documentation is required. Portions Copyright Copyright © 2002-2012 Charlie Poole or Copyright

2002-2004 James W. Newkirk, Michael C. Two, Alexei A. Vorontsov or Copyright

2000-2002 Philip A. Craig

2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software.

3. This notice may not be removed or altered from any source distribution. [AMS_ThinClient_Main : 14.5] Components: twitter-bootstrap-bundle 1.2 : MIT License Copyright Text: twitter-bootstrap-bundle 1.2 packagist:evheniy/twitter-bootstrap-bundle:1.2 Copyright (c) 2011-2015 Evheniy Bystrov copyright-mark:before Copyright 2011-2015 Twitter, Inc. Licenses: MIT License (twitter-bootstrap-bundle 1.2) Copyright (c) 2011-2015 Evheniy Bystrov Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights

to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED

[CCServices_main : 1.0] Components: @santeri_test/test-package 0.0.1 : ISC License Copyright Text: Licenses: ISC License (@santeri_test/test-package 0.0.1) ISC License (ISCL) ================== Copyright (c) 4-digit year, Company or Person's Name Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies. THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE

INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

Planning and Installation Guide Contents

January 2022

Chapter 1 Introduction.................................................................................................................19

Chapter 2 System requirements................................................................................................... 27

Chapter 3 Install AMS Device Manager......................................................................................... 51

Chapter 4 Prepare to use AMS Device Manager............................................................................ 77

Chapter 5 Troubleshoot installation errors...................................................................................83

Appendix A DeltaV system interface deployment concepts............................................................. 85

Appendix B Other deployment concepts......................................................................................... 93

Appendix C Version compatibility................................................................................................... 99

Index .................................................................................................................................. 101

xvii

Contents Planning and Installation Guide

January 2022

xviii

Planning and Installation Guide Introduction

January 2022

1 Introduction

This AMS Device Manager Planning and Installation Guide contains the following information:

• Chapter 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.

• Chapter 2, System requirements – Lists the system requirements for AMS Device

Manager, including hardware, software, and security requirements. This chapter also defines additional requirements for system interface networks and sizing considerations when planning your system.

• Chapter 3, Install AMS Device Manager – Describes the procedures for installing AMS

Device Manager. This chapter also details AMS Device Manager installation on a DeltaV network.

• Chapter 4, Before using AMS Device Manager – Describes configuration steps needed

before using AMS Device Manager.

• Chapter 5, Troubleshoot installation errors – Provides troubleshooting steps you can

take if you have problems installing AMS Device Manager.

• Appendix A, DeltaV system interface deployment concepts – Provides architecture

diagrams for implementing AMS Device Manager with DeltaV.

• Appendix B, Other deployments – Provides architecture diagrams for implementing

AMS Device Manager with supported system interfaces.

• Appendix C, Version compatibility – Provides matrices on AMS Device Manager

compatibility with SNAP-ON applications and DeltaV.

Note

The information in this manual was current and reviewed as of the printed date. Changes to supported systems and applications may have changed after that date. Consult your local Emerson sales office to verify.

1.1 Before you begin

To install and use AMS Device Manager software effectively, you should be familiar with the basic functions and operation of:

• Microsoft Windows

• Your local area network (LAN) configuration and security

• Your communication devices and field devices

• Network components installed on your system

You should also be aware of:

• AMS Device Manager system requirements (see page 27)

• Database backup procedures (see page 21)

Introduction Planning and Installation Guide

January 2022

• Database restore procedures (see page 22)

NOTICE

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.

1.2 Configuration Assessment Tool

In preparation for deploying AMS Device View on your network, you should review your PC's Internet Information Services (IIS) configuration to ensure that your system is set up the way you want it. The Center for Internet Security (CIS) provides a tool to automatically check your IIS settings to assess and alert you to possible threat vectors depending on your security configuration needs. You can download this tool from https:// www.cisecurity.org/cybersecurity-tools/cis-cat-pro/

In addition to the automated checking performed by the CIS-CAT Pro version, Emerson has created several additional XML-based scripts that can be run with this tool. These XML scripts can be found in Tech Support Utilities in the AMS Device View folder on the AMS Device Manager media.

1.3 Installation overviews

The following overviews direct you to specific information and procedures required for your type of installation.

1.3.1

1.3.2

Install a standalone AMS Device Manager system

A standalone AMS Device Manager system is a Server Plus Station that maintains the AMS Device Manager database, with no associated Client SC Stations.

Procedure

1. Read Before you begin.

2. Confirm that your system meets AMS Device Manager requirements on page 27.

3. Do one of the following:

• For a new installation, follow the Server Plus Station installation steps on page

57.

• For upgrading from AMS Device Manager 13 or later, see page 52.

Install a distributed AMS Device Manager system

A distributed AMS Device Manager system is a client/server deployment of AMS Device Manager Stations. It allows multiple AMS Device Manager Stations access to a common database and all connected devices in the distributed system.

Planning and Installation Guide Introduction

January 2022

Procedure

1. Read Before you begin.

2. Confirm that your system meets AMS Device Manager requirements on page 27.

3. Do one of the following:

• For a new installation, follow the Server Plus Station and Client SC Station

installation steps on page 51.

• For upgrading from AMS Device Manager 13 or later, see page 52.

1.3.3 Install AMS Device Manager on a DeltaV system

Procedure

1. Read Before you begin.

2. Confirm that your system meets minimum requirements for a co-deployment (refer to the documentation provided with your DeltaV system).

3. Follow the installation steps on page 74.

1.4 Database operations

The following database procedures are essential to successfully install or upgrade to AMS Device Manager 14.5:

• Back up a database – Do this procedure before upgrading to AMS Device Manager

14.5.

• Restore a database – Do this procedure after upgrading AMS Device Manager to 14.5

from version 10.0 to 12.5.

1.4.1

Back up a database

Note

If performing a database backup on a PC with User Account Control enabled, log in with a Windows administrator user to avoid multiple error messages.

Procedure

1. Enter Database Backup on the Start screen and click Database Backup.

2. In the Backup Database dialog, enter or select the name of the backup file. Select a

secure location on your local drive outside the AMS folder.

3. Click Save.

4. Enter Database Verify Repair on the Start screen and click Database Verify

Repair to check the database for duplicate, missing, and corrupt records.

Note

For a very large database, the Verify/Repair operation can take a long time.

5. Do one of the following:

• If Database Verify Repair does not return any errors, repeat steps 1 to 3.

Introduction Planning and Installation Guide

January 2022

• If Database Verify Repair returns any errors, run Database Verify Repair until

there are no more errors and repeat steps 1 to 3.

1.4.2 Restore a database

Notes

• 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 PC with User Account Control enabled, log in with

a Windows administrator user to avoid multiple error messages.

• Ensure your Windows user has System → Database Utilities → Restore Database

permission in AMS Device Manager User Manager. See AMS Device Manager Books Online for more information.

Procedure

1. Close AMS Device Manager and any related applications (for example, Alert Monitor

or Server Plus Connect, if open.

2. Stop all database connections.

3. Right-click the AMS Device Manager Server icon in the Microsoft Windows system

tray and select Stop AMS Device Manager Server from the context menu.

4. If the database backup file is located on a network drive, copy it to a local drive.

5. Enter Database Restore on the Start screen and click Database Restore.

6. Select the database backup file you want to restore and click Open.

1.5 Uninstall AMS Device Manager

You must uninstall AMS Device Manager if you are upgrading to the current version from versions 10.0 to 12.5. You do not need to uninstall the current AMS Device Manager software if you are upgrading from version 13.0 or higher. AMS Device Manager must always be uninstalled when co-deployed with a DeltaV system being upgraded. See Operating systems to ensure OS support when upgrading AMS Device Manager.

Note

If you have SNAP-ON applications, Web Services, or the AMS Device Manager 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).

Procedure

1. Back up the database (see page 21).

2. Save your license.dat file in a location outside the AMS folder.

3. Right-click the AMS Device Manager Server icon in the Microsoft Windows system

tray and select Stop AMS Device Manager Server from the context menu.

Planning and Installation Guide Introduction

January 2022

4. Open the Windows Control Panel and use Programs and Features to remove AMS

Device Manager.

1.6 Reference documents

After AMS Device Manager is installed, the following user information tools are copied to your PC:

• AMS Device Manager Books Online

• Release Notes

• Supported Device List

1.6.1 AMS Device Manager Books Online

AMS Device Manager Books Online provides detailed reference and procedural information for using AMS Device Manager. AMS Device Manager Books Online explains the features and functions of AMS Device Manager. You should become familiar with AMS Device Manager Books Online and refer to it regularly as you use AMS Device Manager.

1.6.2

1.6.3

You can access AMS Device Manager Books Online in two ways:

• Click the Help menu on the AMS Device Manager toolbar and select AMS Device

Manager Books Online.

• Enter Books Online on the Start screen and click Books Online.

Use the Contents, Index, or Search tab in the left pane to locate specific topics. You can save shortcuts to frequently used topics and access them on the Favorites tab.

Electronic documentation

Two user documents are placed on your station when AMS Device Manager is installed. These documents are available as Portable Document Format (PDF) files, and include the AMS Device Manager Planning and Installation Guide and the Supported Device List.

You need Adobe Reader to view these files. If you do not have a compatible version of Adobe Reader on your PC already, you can download Adobe Reader from www.adobe.com.

To access an electronic document after Adobe Reader is installed, enter Installation

Guide or Supported Device List on the Start screen and click Installation Guide or

Supported Device List.

Release Notes

The Release Notes provide information about the current release of AMS Device Manager, including supported devices, compatibility issues, and known discrepancies and workarounds.

The Release Notes are provided in text (.TXT) format. You can access the Release Notes in two ways:

Introduction Planning and Installation Guide

January 2022

• Enter Release Notes on the Start screen and click Release Notes.

• Double-click the RELNOTES.TXT file located in the AMS folder after installation or on

the AMS Device Manager media

We recommend that you read the Release Notes before using AMS Device Manager.

1.6.4 AMS Device View Help

The AMS Device View Help provides detailed reference and procedural information for using AMS Device View. It explains the features and functions of AMS Device View. You

can access the AMS Device View Help by selecting > from AMS Device View. Use the Search section to find specific topics.

1.6.5

1.6.6

Device manuals

Many device manufacturers provide manuals for their devices in PDF format. Run the AMS_PDF_Installer utility to copy relevant manuals to your hard drive. The utility is located in the Device Documentation Installer folder on the AMS Device Manager media.

After installing device manuals, you access them in AMS Device Manager by right-clicking a device and selecting Help from the context menu. If a device manual is available, it opens in Adobe Reader. If no manual exists for the selected device, AMS Device Manager Books

Online opens. To see a list of device manuals installed on your station, select Help → Device from the AMS Device Manager toolbar. Double-click a device to open the

associated manual.

Product data sheets, security guides, and white papers

AMS Device Manager product data sheets provide product descriptions, features, and benefits. Security guides ensure you plan properly to secure communications with AMS Device Manager and related Emerson software. White papers help you understand AMS Device Manager systems and items important to system planning. Please have the data sheets, security guide, and white papers ready for reference when planning a system. For convenience, some product specifications are included in this guide, but this guide is not intended to duplicate security planning, or reproduce product data sheets or white papers. The data sheets and white papers are available on the Emerson website. The security guide is available with a Guardian subscription. See the AMS Device Manager Product Security Guide that applies to this release of AMS Device Manager.

1.6.7

Knowledge Base Articles

The following Knowledge Base Articles (KBA) provide information on specific AMS Device Manager requirements or components:

• KBA NA-0400-0084 AMS Device Manager Multiplexer System Interface Setup &

Troubleshooting Guide

• KBA NA-0700-0015 Microsoft Security and Critical Updates

• KBA NA-0800-0113 Configuring AMS Device Manager for Cross Domain Functionality

Planning and Installation Guide Introduction

January 2022

• KBA NK-1000-0150 Interoperability of AMS Device Manager Versions with DeltaV

• KBA NK-1300-0268 AMS Device Manager Support in Virtual Environments

• KBA NK-1500-0028 Computers Must Meet a Supported Installation Scenario When Using

AMS Device Manager with DeltaV

• KBA NK-1500-0051 Suggested Memory Configuration for SQL Server When Used With AMS

Device Manager

• KBA NK-1800-0002 Guidelines For Installing A Standard Version Of SQL Server 2014 To Be

Used With AMS Device Manager V14.x

• KBA NK-2100-0182 Updated AMS Device Manager v14.x System Requirements

Introduction Planning and Installation Guide

January 2022

Planning and Installation Guide System requirements

January 2022

2 System 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.

2.1 Sizing considerations

When determining requirements for an AMS Device Manager system, consider the items included in the following tables:

System Sizing Supported Maximum Comments

Total Tag Count? 30,000 tags (per system) and

50 networks (per station)

Wireless Gateway? 16 Wireless Gateways for each

Wireless Interface

WirelessHART Adapters? 15,000 Each WirelessHART Adapter

Total AMS Device Manager stations including the Server Plus?

Supported System Interfaces Total Number of Devices

DeltaV 30,000 (no other interfaces) When installing AMS Device

Wireless Network 30,000 (no other interfaces),

132 (Per System) Although 132 stations are

Connected per Interface

16 wireless gateways for each Wireless Interface.

If the system will support more than 3,000 devices, see the requirements on page 36.

Each Wireless Gateway requires an AMS Tag

requires an AMS Tag

supported, Emerson recommends a maximum of 20 Client SC Stations.

Comments

Manager on a DeltaV system, a licensed AMS Device Manager station (Server Plus or Client SC) must be installed on the ProfessionalPLUS.

Multiplexer Interface 30,000 (no other interfaces),

31 multiplexers per Multiplexer Interface, up to 255 devices per Multiplexer.

Field Communicator • You can only connect one

AMS Trex unit at a time to an AMS Device Manager station using USB.

• You can connect multiple

AMS Trex units to an AMS Device Manager station using WiFi.

In an AMS Device Manager distributed system with crossdomain deployment, AMS Trex must be connected to the Server Plus.

System requirements Planning and Installation Guide

January 2022

Supported System Interfaces Total Number of Devices

Connected per Interface

HART-IP 30,000 devices (no other

interfaces), 16 gateways per network

Networking Considerations Supported Maximum Comments

Number of Network Domains? N/A See KBA NA-0800-0113 for more

information about domains and installing on Domain Controllers.

Number of Network Workgroups?

Number of Ethernet Serial Hubs?

Network Firewalls N/A Complement firewalls with

N/A

antivirus software. If AMS Device Manager is installed on a DeltaV workstation, be sure to install an antivirus software according to the specifications of those systems. See AMS Device Manager Product Security Guide for more information.

Comments

Will Remote Desktop Services or Remote Desktop Session Host be used? (Yes or No)

5 Concurrent Sessions See Support for Remote

Desktop Services and page 33

for information about supported remote desktop and operating systems.

Planning and Installation Guide System requirements

January 2022

2.2 Hardware requirements

2.2.1 PC processing speed, memory, and disk space

Application Type Minimum Requirements

Server Plus Station (standalone or distributed system)

Client SC Station with NO Host Systems (I/O) configured

Client SC Station with Host Systems (I/O) configured

Client SC Station with or without I/O connection with AMS Device View Web Server installed

AMS Device View Web Server (standalone)

Notes: Screen resolution minimum for all stations: SVGA 1024x600 16-bit color

stations.

Use SQL Server full version if you have 10GB or greater database, 3,000 devices or more, or you have more than 10

Modem or calibrator not included in count.

Intel Xeon scalable 8-core, 2.4 GHz 64 GB RAM 100 GB free hard disk space Local SSD SATA hard drive

Intel Core I7, 9th gen, 6-core, 3 GHz 16 GB RAM 10 GB free hard disk space Local SSD SATA hard drive

Intel I7 9th gen, 6-core, 3 GHz 32 GB RAM 10 GB free hard disk space Local SSD SATA hard drive

Intel Core I7, 9th gen, 6-core, 3 GHz 32 GB RAM 50 GB free hard disk space Local SSD SATA hard drive

Intel Core I7, 9th gen, 6-core, 3 GHz 16 GB RAM 10 GB free hard disk space Local SSD SATA hard drive

2.2.2 Serial interfaces

Ethernet serial hubs may be used to add more serial ports when distributing the field devices across multiple AMS Device Manager stations, and are often used when multiple remote systems exist within a plant, and you need to have consolidated information available in a single location such as a maintenance office. Installing Ethernet serial hubs lets virtual COM ports be added to the AMS Device Manager PC and can significantly reduce the required length of the RS-485 network wiring. The HART Multiplexer Interface and documenting calibrators can be used over the existing plant Ethernet.

• An RS-232 serial interface is required for a serial HART multiplexer network or

documenting calibrator.

• A serial port with a dedicated interrupt is required for a serial HART modem.

System requirements Planning and Installation Guide

January 2022

• The use of serial ports on virtual PCs is NOT supported.

2.2.3 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 and pair an AMS Trex Device Communicator to an

AMS Device Manager station. A device cannot be connected to a Trex unit when the USB is plugged in.

• The use of USB ports on VMWare and Hyper-V virtual PCs is supported.

• Some Smart Calibrators may use a USB connection. See Documenting Calibrators

section for details.

2.3 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.

• AMS Device Manager does not support deployment between a network workgroup

and a network domain.

• Named IP services (how PCs identify each other on a network) must be functioning

correctly for stations in an AMS Device Manager distributed system to communicate.

• All stations must be connected to the network before beginning AMS Device Manager

installation. This ensures that all stations can access the AMS Device Manager database. All stations’ computer names should be recorded (see page 65).

• All stations’ PC clocks must be synchronized (many third-party tools are available for

this purpose). Clock synchronization is important because the date and time of an event recorded in the database is based on the clock in the PC that generated that event.

• If using workgroups rather than a DNS network, PC names must be manually added to

the host table of each PC in the distributed network.

For information about working with network firewalls, see page 77.

Note

Consult with your IT department about security issues and any other network operation issues or special requirements for your network.

Planning and Installation Guide System requirements

January 2022

2.3.1 AMS Trex

The AMS Trex Device Communicator uses the Field Communicator license, and can communicate with AMS Device Manager on USB or Wireless. You can connect only one concurrent AMS Trex unit at a time to any AMS Device Manager station using USB. You can connect multiple AMS Trex units to any AMS Device Manager station using WiFi.

If you connect to an Enterprise WiFi network, you will need domain user credentials to connect a Trex unit to the network. In an AMS Device Manager distributed system with cross-domain deployment, AMS Trex must be connected to the Server Plus.

WiFi Protected Access-Enterprise (WPA-Enterprise) is a wireless security mechanism designed for small to large enterprise wireless networks. It is an enhancement to the WPA security protocol with advanced authentication and encryption.

WPA-Enterprise uses the Remote Authentication Dial-in User Service (RADIUS) protocol to manage user authentication.

Figure 2-1: AMS Trex connection points in a workgroup

System requirements Planning and Installation Guide

January 2022

Figure 2-2: AMS Trex connection points in a domain

Planning and Installation Guide System requirements

January 2022

2.4 Software requirements

2.4.1 Operating systems

AMS Device Manager supports the following Windows operating systems:

Note

The AMS Device View web server requires server-class Windows operating systems.

Operating System Version

Windows Server 2012 R2 Standard and Datacenter editions Windows Server 2016 Standard and Datacenter editions Windows Server 2019 Standard and Datacenter editions Windows 10 (not supported for AMS

Device View web server)

Notes

• Only 64-bit versions of the operating systems are supported.

• Desktops, laptops, and tablets with touchscreens are supported on Windows 10.

• AMS Device Manager and associated SNAP-ON applications may not be 64-bit applications but will be able to run on

a 64-bit OS with full functionality.

• Intermixing of the supported operating systems is supported.

• A Server operating system and server-class PC (for example, Dell PowerEdge) are recommended if the database is

expected to be greater than 10 GB due to the SQL Server version required (see page 36); 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.

• 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 for additional operating system configuration considerations.

• AMS Device Manager also supports localized versions of the listed operating systems.

Professional, Enterprise, Enterprise LTSB, and IoT editions

2.4.2

Virtualizations

AMS Device Manager is supported on VMWare and Hyper-V virtual PCs. AMS Device Manager requires a local, dedicated processor, memory, and hard drive for

virtual machines.

Note

All support for virtual PC setup and functionality must come from VMWare or Microsoft support.

Supported features:

• All Ethernet connectivity. This will include but not be limited to: — Ethernet Serial Hubs

— DeltaV systems

System requirements Planning and Installation Guide

January 2022

— Wireless HART networks — HART-IP networks — Other system interfaces that may use Ethernet connectivity

• Smart Calibrators with USB connections

• Supported USB HART modems (Bluetooth HART modems are not currently supported

in a virtual environment)

Note

No physical serial connections will be supported on any AMS Device Manager station that is installed on a virtual PC. This includes, but is not limited to: serial HART modems, RS232 to RS485 converters, and Bluetooth HART modems. For more information regarding AMS Device Manager installed as a Standalone system, please contact your Emerson sales office or the Global Service Center.

2.4.3

2.4.4

Operating system patches and service packs

Newly released Microsoft critical updates and service packs are installed and tested in the AMS Device Manager development labs on supported operating systems. Service pack releases from Microsoft are less frequent but involve many more changes to the operating system. Full support for a new service pack is usually on the next major product release; however early versions of service packs are installed when they are made available from Microsoft, and should an issue be detected, the action we take is very similar to that of critical updates. For more information, see KBA NA-0700-0015 Microsoft Security and Critical Updates.

In addition, users can take advantage of the Guardian Support service and website, which provides fixes, patches and KBAs based on their unique system configuration. For more information, visit https://www.emerson.com/en-us/catalog/ams-

guardiansupportdevicemanager.

Support for Remote Desktop Services

Remote Desktop Services (RDS) is the platform of choice for building virtualization solutions for every end customer need, including delivering individual virtualized applications, providing secure mobile and remote desktop access, and providing end users the ability to run their applications and desktops from the cloud. To use AMS Device Manager 14.5 in a Remote Desktop Services environment, do the following:

• Set up Remote Desktop Services.

• If you are using a Remote Desktop Session Host, install it before AMS Device Manager.

A Remote Desktop Session Host requires a license.

• Remote Desktop Services is limited to 5 concurrent sessions when AMS Device

Manager is installed on Windows server-class computers.

• Ensure that Remote Desktop Services is NOT set to Relaxed Security.

Planning and Installation Guide System requirements

January 2022

Notes

• Do not attempt to install AMS Device Manager on a PC accessed through a Remote

Desktop Services session; this is not a supported installation method and may produce undesirable results.

• If multiple users are running AMS Device Manager on a Remote Desktop Session Host,

and one of the users runs Terminate Servers, the AMS Device Manager application and AMS Device Manager Servers shut down for all users.

• In a Remote Desktop Services environment, SNAP-ON applications may be limited to

only one session at any given time.

• If you are installing a Client SC Station on a licensed Remote Desktop Session Host, a

Client SC Station license is required for each licensed session.

Contact Microsoft for Remote Desktop Services licensing information. Questions about AMS Device Manager licensing requirements should be directed to your local Emerson sales office.

2.4.5

2.4.6

Web browsers

AMS Device Manager supports the following web browsers:

• Microsoft Edge version 89 or higher

• Google Chrome version 89 or higher

When using Google Chrome or Microsoft Edge as a browser for AMS Device View on a PC without AMS Device Manager, you need to download an extension to allow the feature to work properly. https://chrome.google.com/webstore/detail/clickonce-for-google-chro/

kekahkplibinaibelipdcikofmedafmb?hl=en-US If using AMS Device View on a PC without

internet access, you need to use Microsoft Edge. AMS Device View also supports Safari Mobile (iOS 14.0 or newer only).

AMS Device Manager Web Services

AMS Device Manager Web Services provide the ability to import AMS Device Manager data, in XML format, into business applications such as Microsoft Excel. In addition, Computerized Maintenance Management Systems (CMMS) and Enterprise Resource Planning (ERP) systems can use AMS Device Manager Web Services to retrieve data from AMS Device Manager.

Microsoft Internet Information Services (IIS) and AMS Device Manager 14.5 Server Plus Station 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.

The following components will need to be enabled for proper operation.

• ASP.NET

• .NET Extensibility

• Request Filtering

• ISAPI

System requirements Planning and Installation Guide

January 2022

• ISAPI Extensions

Notes

• Some control systems do not allow IIS to be installed on the same PC. Check your

control system documentation to determine IIS compatibility.

• If you want to install AMS Device Manager Web Services on a DeltaV station, it must be

a DeltaV Application or ProfessionalPLUS station.

• You need local administrator permission to install AMS Device Manager Web Services.

2.4.7 .NET Framework

If not found on the PC, AMS Device Manager installs the following .NET Framework components

• Microsoft .NET Framework 4.6.1

• Microsoft .NET Framework 3.5 Service Pack 1.

• (for AMS Device View) Microsoft .NET Core 2.2.0 – Windows Server Hosting (includes

ASP .NET)

2.4.8

Database

AMS Device Manager 14.5 uses a named instance, Emerson2014, of SQL Server 2014 Service Pack 3 for its database. The size of your database determines which edition of SQL Server 2014 Service Pack 3 you must use:

• If your database is less than 10 GB, you can use SQL Server 2014 Express Service Pack 3.

The AMS Device Manager 14.5 setup installs this version automatically.

• If your database is greater than 10 GB or will be at some future time, we recommended

that you install a full version of SQL Server 2014 Service Pack 3 before you install AMS Device Manager.

• If the AMS Device Manager system will support more than 3000 AMS Tags, or have

more than 10 AMS Device Manager stations, a full version of SQL Server 2014 Service Pack 3 is recommended regardless of database size.

A full version of SQL Server 2014 Service Pack 3 must be purchased separately (if you do not already have it). We recommend that the full version of SQL Server 2014 Service Pack 3 is installed on a server operating system.

Notes

• Contact Microsoft for more information about appropriate licensing for a full

installation of SQL Server 2014.

• Additional SQL Server licenses are required when using Client SC Stations. Contact

Microsoft for more information.

• The AMS Device Manager database must be located in the AMS\DB folder on a local

partition of the AMS Device Manager Server Plus Station. Any other location is not supported.

The AMS Device Manager installation program installs SQL Server on your PC as follows:

Planning and Installation Guide System requirements

January 2022

• If SQL Server 2014 Service Pack 3 is not installed, the AMS Device Manager 14.5

installation program will install SQL Server 2014 Express Service Pack 3 with Advanced Services, and create an Emerson2014 named instance.

• If an instance of SQL Server 2014 Service Pack 3 is installed, but not the Emerson2014

named instance, the AMS Device Manager 14.5 installation program will create the Emerson2014 named instance.

• If the SQL Server 2014 Service Pack 3 Emerson2014 named instance is already installed,

the AMS Device Manager 14.5 installation program will continue with the next part of the installation.

• If you have previously installed a full version of SQL Server 2014 Service Pack 3, you

should create the Emerson2014 named instance before installing AMS Device Manager

14.5 (refer to your SQL Server documentation). Otherwise, the AMS Device Manager installation will install SQL Server 2014 Express Service Pack 3.

2.4.9

Microsoft Office

The following Microsoft Office applications are supported:

• Microsoft Word 2013, 2016, 2019 (for Drawings and Notes)

• Microsoft Excel 2013, 2016, 2019 (for Bulk Transfer)

• Microsoft Office 365 (for Drawings and Notes, Bulk Transfer)

Note

All stations in a distributed system must use the same application and version for entering Drawings/Notes.

2.5 Windows security requirements

2.5.1 AMS Device Manager installation

You need Windows system administrator rights to install and configure AMS Device Manager. You also need to review the important security information specified in the "AMS Product Security Guide". Contact Emerson Technical Support for access to this document on Guardian. The document applies to AMS Device Manager and many other AMSbranded products, and provides guidance on what you and your network team need to do to ensure secure installation and operation. TLS 1.0 is required to be enabled. Contact your network administrator for more information.

2.5.2

If AMS Device Manager is being installed on a domain, and will be accessing a domain controller (to support an AMSServiceUser Windows account providing access for all AMS stations on the domain, for instance), you will need to be a member of the domain administrator group to install AMS Device Manager.

AMS Device Manager users

During installation, the AMSDeviceManager Windows user group is created and given access to the AMS folder, subfolders, and files. When an administrator adds existing Windows users in the AMS Device Manager User Manager utility on local or domain PCs

System requirements Planning and Installation Guide

January 2022

(see AMS Device Manager Books Online), these users are automatically added to the AMSDeviceManager Windows user group. However, they may not be able to use all AMS Device Manager features until permissions are assigned to them in User Manager.

For AMS Device Manager stations on a workgroup, Windows users added in the User Manager utility must be manually added to the AMSDeviceManager Windows user group using the Windows Control Panel on the Client SC Stations.

The installation creates a share of the AMS folder. It also allows connected Client SC Stations to use the Drawings/Notes feature of AMS Device Manager. If your situation makes this security configuration undesirable, consult your operating system documentation or your system administrator.

2.5.3 AmsServiceUser

A Windows user account called AMSServiceUser is automatically created on each AMS Device Manager station and added to the AMSDeviceManager Windows user group. The AMSServiceUser account is not created if it exists on the domain controller where AMS Device Manager stations are connected. The local or domain AMSServiceUser accounts are also added to the AMSDeviceManager Windows user group on all AMS Device Manager stations during installation.

2.5.4

Note

If you are installing an AMS Device Manager distributed system on domain controller PCs or a mix of domain controllers and non-domain controller PCs, do all the domain controller installations first (see page 71). When installing on a DeltaV Professional Plus with an IDDC, the AMSServiceUser account is installed on the IDDC, not on the Professional Plus.

This user account runs some of the AMS Device Manager services. 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. You should only run the utility after all AMS Device Manager stations have been installed. Do not use the Windows User Accounts or AMS User Manager to modify this user, or change this password as AMS Device Manager will no longer function.

Note

If the AMS Device Manager Calibration Connector application (see page 75) 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.

AMS Device View security requirements

You need Windows system administrator rights to install and configure the AMS Device View web server. Contact your network administrator if there are other network security requirements before installation.

To access and use AMS Device View, Windows users must be:

• members of the AMSDeviceManager Windows group

Planning and Installation Guide System requirements

January 2022

• enabled in AMS Device Manager User Manager

And have the following permissions in AMS Device Manager User Manager:

• Device Read. Also, if not using a Read-Only server:

• Device Write, to associate a device with a project, remove a device, or mark a device as

complete

• Manage Alert Configurations, to disable alerts in AMS Device View

• System Settings Write, to rename, delete, or complete a project

Users with Plant Location restrictions can only view devices in their assigned area. See AMS Device Manager Books Online for more information on AMS Device Manager security.

2.6 Requirements for system interfaces

Requirements for system interfaces are in addition to the hardware and software requirements for AMS Device Manager.

2.6.1

2.6.2

HART modems

HART modems let AMS Device Manager communicate with HART devices using a PC serial port, PC USB port, or Bluetooth connectivity. Serial and USB HART modems attach directly to a PC or laptop computer. Bluetooth HART modems require a self-contained power source as well as a Bluetooth-ready workstation PC. The PC can have Bluetooth capability built-in or use a Bluetooth adapter and Microsoft Bluetooth software components. HART modems are not supported with USB to RS-232 converters or with Ethernet converters.

You must configure AMS Device Manager to send and receive data to and from the PC serial communications port or USB port (USB HART modem software is required). If a Bluetooth HART modem is used, you must prepare the PC for its use. Contact your IT department for assistance. HART modems also allow multidropping up to 16 HART devices.

Notes

• If your USB or Bluetooth HART modem manufacturer provided supporting driver

software, install it before configuring the modem for use with AMS Device Manager.

• Bluetooth is not natively supported on Windows Server 2012 or Windows Server 2016.

• Installing a HART Modem in Network Configuration requires Windows Administrators

group permissions.

Documenting calibrators

With the optional Calibration Assistant SNAP-ON application, a documenting calibrator can be used to automate the collection of device calibration data.

When the documenting calibrator is connected to AMS Device Manager, test definitions can be checked out (downloaded) to the calibrator. The calibrator is then attached to the corresponding field device, tests are run, and data is collected. This data can then be

System requirements Planning and Installation Guide

January 2022

checked in (uploaded) to AMS Device Manager for electronic record keeping and report generation.

The following documenting calibrators are supported:

• Fluke 729*, 753, 754*

• Druck DPI615, DPI620 CE/IS/Genii+

• Rosemount P330, P370, T460, T490

• Beamex MC6 (MC6-Ex, MC6-T not supported)

• Transmation 195, 196, 197

• BETA Calibrators (BetaFlex*, BetaGauge II, and MasterCal 922) that support protocol

13 or later.

* The drivers for these calibrators support downloading of switch data. The Windows driver for the 754 must be installed before configuring it to be used with AMS Device Manager. To install drivers for these calibrators, see KBA NK-1400-0206.

A USB port and drivers are required to connect Fluke 753 and Fluke 754 Documenting Process Calibrators.

The Beamex MC6 USB driver, located on the AMS Device Manager install media, must be installed first before using the Beamex MC6 with AMS Device Manager. You must select USB from the Com Port dropdown when configuring the calibrator in Network Configuration.

The Beamex MC6 supports downloading test definitions for fieldbus devices. See the AMS Device Manager Supported Device List to determine if a device supports

calibration.

Planning and Installation Guide System requirements

January 2022

2.6.3 DeltaV

A DeltaV control network is an isolated Ethernet local area network (LAN) that provides communication between the controllers and the stations. It uses one or more Ethernet hubs for communication.

DeltaV System Interface station software requirements:

• AMS Device Manager 14.5 can only be installed on the following DeltaV 13.3.1, 14.LTS,

and 14.FP1 and FP2 stations:

DeltaV Workstations AMS Device Manager Station Type

ProfessionalPLUS Station Server Plus Station or Client SC Station

ProfessionalPLUS as Remote Client Server Server Plus Station or Client SC Station

Local Application Station

Remote Application Station Server Plus Station or Client SC Station

Server Plus Station or Client SC Station

Local "Operate" Station

— Professional — Operator — Base — Maintenance

Operator Station as Remote Client Server Client SC Station only

Remote "Operate" Station

— Professional — Operator — Base

Remote Desktop Services is not supported.

Server Plus Station or Client SC Station

Client SC Station only

• The DeltaV System Interface must be configured on a licensed AMS Device Manager

station that is on the DeltaV network.

• AMS Device Manager supports DeltaV version 13.3.1 and later in co-deployed

installations only.

Table 2-1: Supported DeltaV Controllers

Item Type Item Versions*

Controller

MD v13.3.0 or higher

MD+ v13.3.0 or higher

MX v13.3.0 or higher

SD+ v13.3.0 or higher

SX v13.3.0 or higher

MQ v13.3.0 or higher

SQ v13.3.0 or higher

System requirements Planning and Installation Guide

January 2022

Table 2-1: Supported DeltaV Controllers

Item Type Item Versions*

PK v14.3.0 or higher

HART I/O

IS I/O HART

HART AI 8 channel Card, Series1Rev. 2.21 or higher

HART AI 8 channel Card, Series2Rev. 1.26 or higher

HART AI 16 channel Card Rev. 1.17 or higher

HART AO Card, Series 1 Rev. 2.25 or higher

HART AO Card, Series 2 Rev. 1.26 or higher

HART AI 8 channel card S-Series Rev 1.26 or higher

HART AI 16 channel card SSeries

HART AO Card, S-Series Rev. 1.26 or higher

HART AI Redundant High Density S-Series

HART AO Redundant High Density S-Series

IS AI HART 8 channel Card Rev. 2.39 or higher

(continued)

Rev 1.17 or higher

Rev. 1.0 or higher

Zone 1 I/O

Fieldbus I/O

PROFIBUS I/O

Wireless I/O

CHARM I/O

IS AO Hart 8 channel Card Rev. 2.00 or higher

AI/AO Rev 1.14 or higher

Fieldbus H1 Series 1 Rev 1.8 or higher

Fieldbus H1 Series 2 Rev 2.2 or higher

Fieldbus H1 S-Series Integrated Power

Fieldbus H1 S-Series Rev 2.2 or higher

Fieldbus H1 S-Series 4 port Rev 1.0 or higher

PROFIBUS Series 2+ Rev 1.36 or higher

WIOC v13.3.1 or higher

Smart Wireless Gateway v3.95 or higher

CIOC v13.3.1 or higher

CIOC2 v14.3.0 or higher

AI 4-20 mA HART CHARM v1.18 or higher

AO 4-20 mA HART CHARM v1.18 or higher

AI 4-20 mA HART (Intrinsically Safe) IS

AO 4-20 mA HART (Intrinsically Safe) IS

Rev 4.87 or higher

v1.74

v1.76

Planning and Installation Guide System requirements

January 2022

Table 2-1: Supported DeltaV Controllers

Item Type Item Versions*

PROVOX Migration I/O

Controller M-Series Version V13.3 or higher

S-Series V13.3.1 or higher

RS3 Migration I/O

Controller M-Series Version 7.2 or higher

SIS Logic Solver I/O

Logic Solver SLS Version 1.1 or higher

SIS CHARM I/O

Controller SZ V13.3 or higher

Logic Solver CSLS V1.1 or higher

CHARM LS AI 4-20 mA HART V1.15 or higher

LS AI 4-20 mA HART (Intrinsically Safe)

LS DVC HART DTA V1.16 or higher

LS DVC HART (Redundant DTA) V1.16 or higher

(continued)

V1.15 or higher

DeltaV supports:

• FOUNDATION fieldbus devices

• Wired HART Rev. 5, Rev. 6, and Rev. 7 devices

• WirelessHART Rev. 7 devices

• PROFIBUS DPV1 devices

• PROFIBUS PA devices (supported on DeltaV 13.3.1 or higher with a Series 2+ PROFIBUS

DP I/O card and a PROFIBUS DP/PA Coupler on a PROFIBUS DP segment. See PROFIBUS section for supported couplers.)

• HART safety devices connected to DeltaV SIS logic solvers

• HART safety devices connected to DeltaV 13.3.1 or later (SIS) CHARMs logic solvers

DeltaV versions 13.3.1 and later can access devices connected to RS3 and PROVOX I/O systems through the DeltaV Interface for RS3 I/O and DeltaV Interface for PROVOX I/O, respectively. The devices are displayed in the DeltaV network hierarchy in AMS Device Manager. For installation and setup information, refer to the DeltaV Books Online.

To receive alerts from devices connected to PROVOX and RS3 Migration Controllers in your DeltaV network hierarchy, you must run a utility to properly set the DeltaV alert capability (see page 78).

The DeltaV password (if not using the default password) must be entered in the AMS Device Manager Network Configuration utility (see Add a DeltaV network in AMS Device

Manager Books Online).

System requirements Planning and Installation Guide

January 2022

The ValveLink SNAP-ON application is supported for DeltaV and PROVOX I/O cards, but not for RS3 cards.

The DeltaV System Interface supports ValveLink Diagnostics. Analog output modules configured for HART are required on the DeltaV station for communication with HART FIELDVUE digital valve controllers. FOUNDATION fieldbus FIELDVUE digital valve controllers need only be commissioned and ports downloaded.

2.6.4 HART-IP

The HART-IP System Interface lets you use AMS Device Manager to view and configure wired and wireless devices connected to HART-IP gateways. The following HART-IP gateways are supported:

• Triconex CX v11.5

• HIMA HIMax v 5

• Honeywell OneWireless WDMX, WDMY v R240, R300, R310, R320

• Phoenix Contact Ethernet HART Multiplexer including: — GW PL ETH/BASIC-BUS, v 2702321)

2.6.5

— GW PL ETH/UNI-BUS, v 2702233)

• Softing smartLink HW-DP v 2.0

Contact your HART-IP manufacturer for any gateway-specific firmware or software needed to connect to AMS Device Manager.

HART Multiplexer Network

The HART Multiplexer System Interface lets you use AMS Device Manager to communicate with HART devices through a HART multiplexer. HART multiplexers can link many installed HART field devices to an AMS Device Manager station, providing the capability to remotely configure, troubleshoot, and monitor those devices. A typical HART multiplexer network enables one PC COM port to communicate with up to 63 addressable HART multiplexers.

AMS Device Manager supports a variety of multiplexers, each with different capabilities and requirements. Supported multiplexer types can have between 32 and 256 device connections.

A HART multiplexer network requires:

• One serial communication port for each HART multiplexer network.

• An RS-232 to RS-485 converter or a supported Ethernet serial hub

Planning and Installation Guide System requirements

January 2022

Table 2-2: Supported HART Multiplexers

Manufacturer Model Max

Channels

Arcom H-Port 32 Yes Off Contact the

Elcon 1700 32 No Off - HART 6 and 7

2700A 32 No Off - HART 6 and 7

Pepperl + Fuchs

HiDMux2700 32 Yes On The HiDMux2700

Hardware supports Enhanced Polling

Default in AMS Device Manager

Notes

Emerson Global Service Center or your local support office for details on enabling Enhanced Polling for ARCOM H-PORT multiplexers.

devices may experience communication errors.

must be upgraded with firmware version 7 or later to work correctly with AMS Device Manager version

7.0 or higher.

KFD2-HMM-16 256 Yes On See 1 below.

KSD2-GW-xxx Service

Bus

Yes On Appears as HART

Multiplexer 255way. HART 6 and 7 devices may experience communication errors.

System requirements Planning and Installation Guide

January 2022

Table 2-2: Supported HART Multiplexers

Manufacturer Model Max

Channels

MTL/Novatech 4841/4842

(Device Type 15)

256 No Off Novatech

(continued)

Hardware supports Enhanced Polling

Default in AMS Device Manager

Notes

recommends customers with MTL 4841-AMS multiplexers, who want to use enhanced polling, contact them about upgrading to an MTL 4841AMSv7 multiplexer. You will either have to return the MTL 4841-AMS multiplexer for reprogramming or replace your existing multiplexer with a new MTL 4841AMSv7. HART 6 and 7 devices may experience communication errors

4841/4842 (Device Type 16)

4850

4850-TR 32 Yes Off

4851-4852 16 Yes Off

4854 32 Yes Off

8000/8512 256 No Off

256 Yes On Changing the

32 Yes On

damping of a DVC6000 connected to a MTL 4841 multiplexer (4841 rev 1, hardware rev 1, software rev 5) may cause the device to lose communication with the ValveLink SNAP-ON application.

Planning and Installation Guide System requirements

January 2022

Table 2-2: Supported HART Multiplexers

Manufacturer Model Max

Channels

Spectrum Connects (v6.0,

6.1)

Phoenix Contact

GW PL ETH/ BASIC-BUS with GW PL ETH/UNIBUS and GW PL HART4-BUS

256 No Off If you have a

(continued)

Hardware supports Enhanced Polling

Default in AMS Device Manager

Notes

Spectrum CONNECTS multiplexer, you will need to have additional software installed on your PC. Contact Spectrum for details (www.spectrumco ntrols.com).

Burst mode is not supported. Also, problems seen when P&F USB modem installed on the same station. (part numbers 2702321, 2702233,

2702234)

2.6.6

Emerson Machine Automation Solutions

P+F KFD2-HMM-16 multiplexers behave differently than the other multiplexers in duplicate device ID situations. When duplicate devices are attached to these multiplexers, the duplicate device ID icons are not displayed and only one of the duplicate devices will show up in the multiplexer hierarchy. AMS Device Manager cannot determine that multiple devices have the same device ID. However, AMS Device Manager does recognize that the multiplexer thinks it has more devices than what it is telling AMS Device Manager in its device list, and AMS Device Manager logs this information in the Windows Event Log. Revisions 5 - 9 of the P+F KFD2HMM-16 multiplexer are not supported. Appears as HART Multiplexer 255-way.

PACSystems HART Multiplexer

16,384 No Off Virtual Mux (v 1.2)

For specific information about a supported multiplexer, see the manufacturer’s documentation. For more information about multiplexer networks, see KBA NA-0400-0084.

Wireless

The Wireless System Interface allows you to view and configure WirelessHART devices in a Wireless Network. A Wireless Network is made up of one or more wireless gateways and WirelessHART devices.

The Wireless System Interface requires:

System requirements Planning and Installation Guide

January 2022

• An Ethernet adapter to connect to the gateway.

• One or more wireless gateways that allow communication between the AMS Device

Manager station and a collection of wireless devices.

• WirelessHART devices. See the AMS Device Manager Supported Device List for a list of

supported WirelessHART devices.

• A valid SSL certificate (if using the recommended Security Setup utility) allowing the

AMS Device Manager station to securely communicate with the gateway. See AMS Device Manager Books Online and the Smart Wireless Gateway manual for more information about the Security Setup utility and certificate.

AMS Device Manager supports the following wireless gateways:

• 2.4 GHz Rosemount Rev 2 1420 versions 3.9.5 and later

• 2.4 GHz Rosemount Rev 3 1420 versions 4.2.9 and later

• 2.4 GHz Rosemount Rev 4 1420 versions 4.3.17 and later

• 2.4 GHz Rosemount Rev 4 1410/1420 and Cisco 1552WU version 4.4.30 and later

• 2.4 GHz Rosemount Rev 5 1410/1420 and Cisco 1552WU version 4.5.27 and later

Note

The 2.4 GHz Rosemount Rev 2 1420 version 3.9.5 gateway does not support HART 6 devices.

2.7 AMS Device View

Once you have installed the AMS Device View web server. you can use a supported browser to launch AMS Device View screens. Desktop/laptop browsing of AMS Device View data and opening device details screens can only be launched from a Windows PC.

2.7.1

AMS Device Manager compatibility with AMS Device View

AMS Device View requires AMS Device Manager 14.5. You can install AMS Device View on a standalone PC without AMS Device Manager or co-deployed with AMS Device Manager. If you install AMS Device View on a standalone PC or on a Client SC Station, the installation will prompt you to enter the Server Plus Station name or IP address and the AMSDBUser password. If AMS Device View is installed on a non-AMS Device Manager station, you will need to manually install certificates to ensure secure communications. See the videos for AMS Device View on the AMS Device Manager media at \Certificate_Videos.

Note

You do not need to enter the AMSDBUser password if it has not been changed.

2.7.2

DeltaV compatibility with AMS Device View

To deploy AMS Device View on the control network, install the AMS Device View web server on a DeltaV Application Station. Alternatively, it can be installed on the DeltaV ProfessionalPlus station, but this is NOT recommended. If you want to access AMS Device

Planning and Installation Guide System requirements

January 2022

View on the plant network, we recommend that you install the AMS Device View web server on a standalone PC in a demilitarized zone above the control network.

Note

AMS Device View is not supported on any other DeltaV stations. AMS Device View is not supported on a PC with Plant Messenger installed.

System requirements Planning and Installation Guide

January 2022

Planning and Installation Guide Install AMS Device Manager

January 2022

3 Install AMS Device Manager

AMS Device Manager can be installed as a single-station system or as a multi-station, distributed system. The single-station system is a Server Plus Station that maintains the AMS Device Manager database, with no associated Client SC Stations. A distributed AMS Device Manager system is a client/server deployment of AMS Device Manager Stations. It allows multiple AMS Device Manager Stations access to a common database and all connected devices in the distributed system.

A distributed system contains a Server Plus Station and one or more Client SC Stations. Each station has access to a common database located on the Server Plus Station.

The procedures in this chapter are for installing and configuring AMS Device Manager on the following types of stations:

• Server Plus Station

• Client SC Station

For a distributed system to function as intended, all Client SC Stations must have network access to the Server Plus Station. The Server Plus Station must be able to successfully ping each Client SC Station by computer name. You can install a Client SC Station first if that is required for your network configuration (for example, if installing on domain controllers and non-domain controllers). Otherwise, it is recommended that AMS Device Manager software be installed first on the PC to be the Server Plus Station (see page 57), and then on each PC to be used as a Client SC Station (see page 59). All stations must use the same revision of AMS Device Manager software.

If you are installing an AMS Device Manager distributed system on a workgroup, a common username and password is required and should be added to the AMSDeviceManager Windows user group on every AMS Device Manager station on the workgroup.

If you are installing AMS Device Manager on a DeltaV station, see page 74. If you are installing an AMS Device Manager distributed system and the Server Plus Station

is separated from the Client SC Station(s) by a firewall, refer to AMS Device Manager Product Security Guide.

If you are installing AMS Device Manager on a PC that has AMS Wireless Configurator installed, see page 55.

Note

It is recommended that you install AMS Device Manager before installing antivirus software. Check the Knowledge Base Articles if there are known issues with your antivirus software.

Important

Do NOT install AMS Device Manager and Plantweb Optics™ on the same PC.

Install AMS Device Manager Planning and Installation Guide

January 2022

3.1 Upgrade 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).

CAUTION

Before you upgrade, you should back up your database as a precaution against loss of data (see page 21). Make sure you have installed the latest Hotfix bundle for the version you are using before upgrading.

The backup files are not changed during 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.

Upgrading to AMS Device Manager 14.5 from version 13.0 and higher does not require you to uninstall previous versions and restore the database after installation. See Upgrade an AMS Device Manager Server Plus Station or Upgrade an AMS Device Manager Client SC Station.

Upgrading to AMS Device Manager 14.5 from version 12.5 or lower requires you to back up the database and uninstall the previous version.

Planning and Installation Guide Install AMS Device Manager

January 2022

Table 3-1: Upgrade an AMS Device Manager Server Plus Station 13.0 or higher

Server Plus Station to Server Plus Station Server Plus Station to Client SC Station

1. Check in all calibration routes.

2. Clear all existing alerts from Alert Monitor.

3. Back up the database (see page 21).

4. Consolidate existing databases, if necessary (see page

64).

5. Uninstall SNAP-ON applications, (except ValveLink SNAP-ON), Device Description Update Manager, AMS Device Manager Asset Source Interface (ASI), and Web Services, if installed. See the Knowledge Base Article on AMS Device Manager ASI for details on uninstalling that product.

6. Uninstall AMS Device Manager Calibration Connector application, if installed.

7. Uninstall Softing TACC components, if installed (refer to TACC guides downloaded from Softing).

8. Remove any configured HART Over PROFIBUS System Interfaces.

9. Stop any programs or processes that access AMS Device Manager Server .

10. Stop AMS Device Manager Server in system tray if running.

1. Check in all calibration routes.

2. Clear all existing alerts from Alert Monitor.

3. Uninstall SNAP-ON applications, (except ValveLink SNAP-ON) Device Description Update Manager, AMS Device Manager Asset Source Interface, and Web Services, if installed. See the Knowledge Base Article on AMS Device Manager ASI for details on uninstalling that product.

4. Uninstall AMS Device Manager Calibration Connector application, if installed.

5. Uninstall Softing TACC components, if installed (refer to TACC guides downloaded from Softing).

6. Remove any configured HART Over PROFIBUS System Interfaces.

7. Stop any programs or processes that access AMS Device Manager Server.

8. Stop AMS Device Manager Server in system tray if running.

9. Uninstall previous AMS Device Manager Server software (see page 22).

10. Install Client SC Station software (see page 59).

11. Install Server Plus Station software (see page 57).

12. Get new license codes (see page 62).

13. Add or edit users (see AMS Device Manager Books Online).

14. Reapply the DeltaV System Interface1, if applicable.

15. Install required SNAP-ON applications (see page 72).

16. Install AMS Device Manager Calibration Connector application, if applicable.

17. Install new Softing smartLink components, if applicable.

18. Configure HART-IP System Interfaces, if applicable.

19. If the Server Plus will have system interfaces, copy the .cer file found in AMS folder to the AMS folder on all Client SC stations.

20. Install the latest version of AMS Device Manager Asset Source Interface, and Web Services, if required (see

page 73). See the Knowledge Base Article on AMS

Device Manager ASI for details on installing that product.

21. Copy device manuals (see page 24).

11. Get new license codes.

12. Install required SNAP-ON applications (see page

72).

13. Add or edit users (see AMS Device Manager Books Online).

14. Configure required communication interfaces.

15. Install new Softing smartLink components, if applicable.

16. Configure HART-IP System Interfaces, if applicable.

17. If the Client SC will have system interfaces, copy the .cer file found in AMS folder to the AMS folder on the Server Plus station and any other Client SC stations.

18. Copy device manuals (see page 24).

Install AMS Device Manager Planning and Installation Guide

January 2022

Table 3-2: Upgrade an AMS Device Manager Client SC Station 13.0 or higher

Client SC Station to Server Plus Station Client SC Station to Client SC Station

1. Check in all calibration routes.

2. Clear all existing alerts from Alert Monitor.

3. Back up the database (see page 21).

4. Uninstall SNAP-ON applications (except ValveLink SNAP-ON) and Web Services, if installed.

5. Uninstall Softing TACC components, if installed (refer to TACC guides downloaded from Softing).

6. Remove any configured HART Over PROFIBUS System Interfaces.

7. Stop any programs or processes that access AMS Device Manager Server.

8. Stop AMS Device Manager Server in system tray if running.

9. Uninstall previous AMS Device Manager Server software (see page 22).

10. Install Server Plus Station software (see page 57).

11. Get new license codes (see page 62).

12. Add or edit users (see AMS Device Manager Books Online).

13. Configure required communication interfaces1.

14. Install required SNAP-ON applications (see page 72).

15. Install AMS Device Manager Calibration Connector application, if applicable (see page 76).

1. Uninstall SNAP-ON applications (except ValveLink SNAP-ON) if installed.

2. Clear all existing alerts from Alert Monitor.

3. Uninstall Softing TACC components, if installed (refer to TACC guides downloaded from Softing).

4. Remove any configured HART Over PROFIBUS System Interfaces.

5. Stop any programs or processes that access AMS Device Manager Server .

6. Stop AMS Device Manager Server in system tray if running.

7. Install Client SC Station software (see page 59).

8. Add or edit users (see AMS Device Manager Books Online).

9. Reapply the DeltaV System Interface, if applicable1.

10. Install required SNAP-ON applications (see page 72).

11. Install new Softing smartLink components, if applicable.

12. Configure HART-IP System Interfaces, if applicable.

13. If the Client SC will have system interfaces, copy the .cer file found in AMS folder to the AMS folder on the Server Plus station, and other Client SC stations.

14. Copy device manuals (see page 24).

16. Install new Softing smartLink components, if applicable.

17. Configure HART-IP System Interfaces, if applicable.

18. If the Server Plus will have system interfaces, copy the .cer file found in AMS folder to the AMS folder on the Client SC stations.

19. Install latest version of Device Description Update Manager, AMS Device Manager Asset Source Interface, and Web Services, if required (see page

73). See the Knowledge Base Article on AMS Device

Manager ASI for details on installing that product.

20. Copy device manuals (see page 24).

Planning and Installation Guide Install AMS Device Manager

January 2022

Upgrade notes

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.

Manually installed Device Descriptions that are still not included in the AMS Device Manager 14.5 installation must be reinstalled after the upgrade.

Table 3-3: Upgrade from AMS Device Manager 10.0 to 12.5

Upgrade from version 10.x, 11.0, 11.5, or 12.5.x

1. Back up the database (see page 21).

2. Uninstall SNAP-ON applications (except ValveLink SNAP-ON) and Web Services, if installed.

3. Uninstall AMS Device Manager (see page 22).

4. Ensure the PC meets system requirements (see page 27).

5. Install AMS Device Manager 14.5 (see page 57 or page 59, depending on the type of installation needed).

6. Install required SNAP-ON applications (see page 72).

7. Restore your database (see page 22).

Notes

If you are upgrading from a version lower than 10.x, contact your Emerson Sales/Service Office for assistance.

After you have completed the upgrade,

• Configure any required system interface networks and then open AMS Device Manager

14.5. Right-click each of the network icons and select Rebuild Hierarchy followed by Scan → New Devices. If you are using the Alert Monitor feature, click Alert Monitor on the AMS Device Manager toolbar to open the Alert List. Click Station Monitoring on the toolbar and ensure that the station you are monitoring is checked.

• From the Windows Start menu on each station, select AMS Device Manager →

Certificate Manager and Import certificates from any other stations to ensure secure communications between components.

3.1.1

Upgrade from AMS Wireless Configurator

To install an AMS Device Manager Server Plus Station or Client SC Station on a PC that has AMS Wireless Configurator installed:

Procedure

1. Contact your Emerson Sales/Service Office to get new license codes for AMS Device

Manager.

2. Back up the database (see page 21).

3. Right-click the AMS Device Manager Server icon in the Microsoft Windows system

tray and select Stop AMS Device Manager Server from the context menu.

4. Open the Windows Control Panel and use Programs and Features to remove AMS

Wireless Configurator.

Install AMS Device Manager Planning and Installation Guide

January 2022

5. Install AMS Device Manager (see Install Server Plus Station software or Install Client

SC Station software).

6. Do one of the following:

• If you installed a Server Plus Station in the previous step, license AMS Device

Manager (see page 62) and restore your backed-up database (see page 22).

• If you installed a Client SC Station in the previous step, you may need to

consolidate your backed-up AMS Wireless Configurator database with an existing database (see page 64).

3.1.2 Upgrade from AMS Device Configurator for DeltaV

AMS Device Configurator for DeltaV is a limited-feature version of AMS Device Manager provided to DeltaV users, and does not require a license. To upgrade to the full version of AMS Device Manager:

Procedure

1. Contact your Emerson Sales/Service Office to get new license codes for AMS Device Manager.

2. Right-click the AMS Device Manager Server icon in the Microsoft Windows system tray and select Stop AMS Device Manager Server from the context menu.

3. License AMS Device Manager (see page 62).

4. Restart your PC.

5. Start AMS Device Manager.

Planning and Installation Guide Install AMS Device Manager

January 2022

3.2 Install Server Plus Station software

Notes

• If you are upgrading your software and changing the station type, you must uninstall

the earlier version of AMS Device Manager before upgrading to AMS Device Manager

14.5. (See Table 3-1). If changing domains or moving a PC from a workgroup to a domain, you must uninstall and reinstall AMS Device Manager.

• If you are installing an AMS Device Manager distributed system using a domain

controller, see page 71 for other requirements.

Procedure

1. Exit/close all Windows programs, including any running in the background

(including virus scan software).

2. Insert the AMS Device Manager media.

3. When the AMS Device Manager setup starts, click Install AMS Device Manager.

Notes

• If the autorun function is disabled on your PC, double-click D:

\AMSDEVICEMANAGER_SETUP.EXE (where D is the drive letter) and click OK.

• Stopping services may take some time to complete.

4. Click Next.

5. Accept the License Agreement and click Next.

6. Read the Release Notes and click Yes.

7. Optional: If you are upgrading AMS Device Manager from a previous version, click

Yes. If you want to install AMS Device Manager on a different location or install a different AMS Device Manager station type, click No. See Upgrade an AMS Device

Manager system for more information on AMS Device Manager upgrade options.

8. Click Server Plus Station.

9. Select the AMS Device Manager components you want to install:

• HART Modem Driver

• DTM Launcher Application

10. Follow the prompts.

NOTICE

Do not interrupt the installation process, or the software will not be fully installed and will malfunction. The installation process includes some system restarts. Do not remove the media until the installation is complete.

Note

If you are installing on a PC with User Account Control enabled, the User Account Control dialog displays after rebooting the PC. Select Yes to continue with the AMS Device Manager installation.

Install AMS Device Manager Planning and Installation Guide

January 2022

If you do not click Yes within 2 minutes, the dialog closes and to complete the installation you must select Start → All Programs → AMS Device Manager → Continue the AMS Device Manager installation.

11. If you are installing on a Windows PC without .NET Framework 3.5 Service Pack 1 installed, do the following when the Install .NET Framework 3.5 dialog appears:

a) Click Yes.

b) Insert the Windows installation media. c) Browse to the root directory and click Next.

d) Once .NET Framework 3.5 SP1 installation is complete, replace the Windows

installation media with the AMS Device Manager media and click OK.

12. If the Remove old Emerson Instance Name dialog appears, it is recommended to remove old versions to prevent performance issues. Select the instance you want to remove and click Remove. Otherwise, click Skip.

13. Enter a new AMS Device Manager system password. This password must meet OS complexity requirements, and must be identical for all AMS Device Manager stations.

14. License AMS Device Manager (see page 62).

15. If you are installing a distributed system, configure the Server Plus Station to recognize each station connected in the system (see page 63). This step is essential for the other stations to access the Server Plus Station.

16. If your Server Plus station will host system interfaces, copy the .cer file found in the AMS folder to the AMS folder on the Client SC stations.

17. Set up and configure the system interfaces needed on this station (see page 77).

18. Optional: Install the latest versions of any licensed SNAP-ON applications (see page

72).

19. Open AMS Device Manager, right-click each of the network icons and select Rebuild Hierarchy followed by Scan → New Devices.

20. 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 the station you are monitoring is checked. Only stations with system interfaces configured need to be checked.

During installation, the AMSDeviceManager Windows user group is given access to the AMS folder, subfolders, and files. When an administrator adds specific Windows users in the AMS Device Manager User Manager utility, these users are automatically added to the AMSDeviceManager Windows user group. However, they have no ability to use AMS Device Manager features until permissions are assigned to them in User Manager.

The installation creates a share of the AMS folder. This allows connected Client SC Stations to access the Server Plus Station. It also allows connected Client SC Stations to use the Drawings/Notes feature of AMS Device Manager. If your situation makes this security configuration undesirable, consult your operating system documentation or your system administrator.

Planning and Installation Guide Install AMS Device Manager

January 2022

From the Windows Start menu on each station, select AMS Device Manager → Certificate Manager and Import certificates from any other stations to ensure secure communications between components.

Note

The AMS Device Manager installation program turns off Windows Automatic Updates. After AMS Device Manager is installed, check to see that the Windows Automatic Updates function is set as desired.

3.3 Install Client SC Station software

Procedure

1. Verify Client SC Station connectivity. Use the ping command to verify that the designated Client SC Station PC responds

to communications sent to it by the Server Plus Station.

a) At the AMS Device Manager Server Plus Station, enter CMD on the Start

screen.

b) At the command prompt, enter PING <Client SC Station Computer

Name>.

c) Press ENTER. d) Verify that the Client SC Station PC responds to the ping command.

The ping command should return a reply message. If the ping command fails, verify that you entered the correct PC name in the command line. Also verify that your network is functioning properly. Contact your IT department if you cannot establish connectivity.

2. Exit/close all Windows programs, including any running in the background (including virus scan software).

3. Insert the AMS Device Manager media.

4. When the AMS Device Manager setup starts, click Install AMS Device Manager.

Notes

• If the autorun function is disabled on your PC, double-click D:

\AMSDEVICEMANAGER_SETUP.EXE (where D is the drive letter) and click OK.

• Stopping services may take some time to complete.

5. Click Next.

6. Accept the License Agreement and click Next.

7. Read the Release Notes and click Yes.

8. Click Client SC Station.

9. Select the AMS Device Manager components you want to install:

• HART Modem Driver

• DTM Launcher Application

Install AMS Device Manager Planning and Installation Guide

January 2022

10. Follow the prompts.

NOTICE

Note

If you are installing on a PC with User Account Control enabled, the User Account Control dialog displays after rebooting the PC. Select Yes to continue with the AMS Device Manager installation.

11. If you are installing on a Windows PC without .NET Framework 3.5 Service Pack 1 installed, do the following when the Install .NET Framework 3.5 dialog appears:

a) Click Yes.

b) Insert the Windows installation media. c) Browse to the root directory and click Next.

d) Once .NET Framework 3.5 SP1 installation is complete, replace the Windows

installation media with the AMS Device Manager media and click OK.

12. Enter a new AMS Device Manager system password. This password must meet OS complexity requirements, and must be identical for all AMS Device Manager stations.

13. License AMS Device Manager (see page 62).

14. Add the user to the AMSDeviceManager group (from Windows Control Panel launch User Accounts. Select Manage User Accounts. From the Advanced tab, select Advanced, and select Groups. Right-click AMSDeviceManager, and select Add to Group...).

15. If the Client SC station will host system interfaces, copy the .cer file found in AMS folder to the AMS folder on the Server Plus and any Client SC stations.

16. Set up and configure the system interfaces needed on this station (see page 77).

17. Optional: Install the latest versions of any licensed SNAP-ON applications (see page

72).

18. Open AMS Device Manager, right-click each locally configured network icon and select Rebuild Hierarchy and then Scan → New Devices.

19. 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 the station you are monitoring is checked. Only stations with system interfaces configured need to be checked.

Planning and Installation Guide Install AMS Device Manager

January 2022

Notes

• The AMS Device Manager installation program turns off Windows Automatic Updates.

After AMS Device Manager is installed, check to see that the Windows Automatic Updates function is set as desired.

• You must add the Windows user as a user in AMS Device Manager User Manager (see

AMS Device Manager Books Online) or the AMS Device Manager Server icon will not display in the Windows system tray.

• From the Windows Start menu on each station, select AMS Device Manager →

Certificate Manager and Import certificates from any other stations to ensure secure communications between components.

3.4 Install the AMS Device View web server

If your Server Plus PC is on a different domain, follow the cross-domain rules specified in KBA NA-0800-0113 before installing AMS Device View.

Procedure

1. Install IIS.

2. Exit/close all Windows programs, including any running in the background

(including virus scan software).

3. Insert the AMS Device Manager media.

4. In the AMS Device View folder, double-click AMSDeviceView_Setup.exe.

5. If a message about third-party components is displayed, click OK.

6. Restart your PC, if prompted.

7. Click Next.

8. Choose the deployment type.

9. Enter the activation code and click Next.

Note

For information on how to get your activation code, follow the installation prompts.

10. Accept the License Agreement and click Next.

11. Do one of the following:

• Click Next to install AMS Device View in the default location.

• Click Browse to select a different location, and click OK.

12. Click Next.

13. The AMS Device View Server Config dialog is displayed if you are installing on a PC without the Server Plus Station installed. Enter the Server Plus Station PC name or IP address and the AMSDbUser Password and click Configure.

Note

If the AMSDbUser Password has not been changed, leave the default entry and click Configure.

Install AMS Device Manager Planning and Installation Guide

January 2022

14. Click Finish.

15. If co-deployed on an AMS Device Manager station, run Terminate Servers from the AMS menu. If the AMS Device View web server is not on an AMS station, skip to step

18.

16. Run Certificate Manager, and in the Local Certificate Status pane, select the vertical bar menu for the AMSSuite.Client certificate, and choose Export. Copy the .cer file to the /AMS folder on the Server Plus station.

17. On the Server Plus station, run Terminate Servers from the AMS menu. Run Certificate Manager, and from the Install tab, choose the AMSSuite.Client certificate, and select Install. Skip to step 20.

18. Install AMS Device View certificates on the appropriate PCs. Emerson requires secure communications. See the videos for AMS Device View on the AMS Device Manager media at \Certificate_Videos.

19. To associate the installed certificates with AMS Device Manager Database, run AMSDeviceViewCertificateRegistration.exe utility in the\AMS\bin folder.

20. In AMS Device Manager User Manager, add the PC name of the AMS Device View web server, and any usernames on that PC.

3.5 License AMS Device Manager

All licensing for an AMS Device Manager system is done on the Server Plus Station. After installation, start the Licensing Wizard and follow the prompts to gather registration information.

Note

To gather the registration information, you need to know your System ID (supplied with your AMS Device Manager software).

After you register your software, the Registration Center returns your license from the AMS Device Manager registration website at:

https://guardian.emerson.com/Guardian/Pages/AmsRegistration/

When you receive your license, run the Licensing Wizard on the Server Plus Station to enter your license, which enables your system.

Note

During the licensing process, you must have read access to the PC disk drive you installed on (C: drive by default) so that the Licensing Wizard can uniquely identify the PC.

Procedure

1. Enter Licensing Wizard on the Start screen and click Licensing Wizard.

2. Follow the instructions in the Licensing Wizard.

3. If you are installing new license information on an existing station, start AMS Device Manager to see the changes.

Planning and Installation Guide Install AMS Device Manager

January 2022

3.6 License AMS Device View

You need an activation code to install AMS Device View. To get the activation code, email Emerson Worldwide Customer Service or call Toll-Free 888.367.3774 (U.S. and Canada) or +63.2.702.1111 (Rest of World) and provide your AMS Device Manager system ID. Your system ID can be found by opening Help → About AMS Device Manager on your AMS Device Manager system.

3.7 Register your product with SureService

Prerequisites

Install and license your AMS Device Manager stations.

Procedure

1. Run the SureService Registration application from the AMS Device Manager Windows Start menu of the Server Plus station.

2. Retrieve the latest-generated registration file that ends with “SysRegData.epm” in the \AMS\Db\xml\EPM folder.

3. Upload the file on the Guardian website under System Info → Registration.

3.8 Configure and secure a Distributed System

Before you can use your distributed system, you must configure the Server Plus Station so the Client SC Stations can access the Server Plus Station. In addition, any stations with a configured System Interface after copying their certificate to all other stations, must run Certificate Manager on those stations.

Procedure

1. On the Server Plus Station, enter Station Configuration on the Start screen and click Station Configuration.

2. In the Station Configuration dialog, click Add.

3. Enter the computer name of the Client SC Station PC (see page 65), and click OK.

Note

The station name is not case-sensitive. Do not include a domain name or any other characters that are not part of the computer name. Use station names of 15 ISO Latin-1 characters or less.

4. Repeat steps 2 and 3 for each licensed Client SC Station, and click Close when done.

5. Restart AMS Device Manager on the Server Plus station.

6. From each station with a configured System Interface, copy the .cer file found in the /AMS folder to the /AMS folder on all other stations. If you are using corporate certificates, copy the .PFX or .P12 certificate provided by your organization to the /AMS folder.

7. Run Terminate Servers from the AMS folder of the Windows start menu on each station.

Install AMS Device Manager Planning and Installation Guide

January 2022

8. Run Certificate Manager in the AMS folder of the Windows start menu on each station. Follow the prompts on the Install tab.

3.8.1 Consolidate databases

If you have multiple Server Plus Stations, you can consolidate their databases for use in a distributed system.

Procedure

1. Back up the current database on all stations containing a database you want to consolidate (see page 21).

2. Select one of the Server Plus Stations to hold the consolidated database. Import the database information from the other Server Plus Stations one at a time. This may be done using one of the following methods.

Method 1

Use this method when all the stations are connected to the same network and domain and at the same AMS Device Manager revision level.

• Right-click the Plant Database icon on the designated consolidation Server Plus

Station, select Import → From Remote to import the database from the other stations one at a time. Click Help on the Import From Remote System dialog for instructions.

Note

To Import > From Remote, you must have AMS Device Manager System Administration permissions.

Method 2

Use this method when the stations are not connected to a common network.

• From the Plant Database icon on all the non-consolidation Server Plus Stations,

select Export → To <type> Export File to prepare a database merge file. Click Help on the AMS Device Manager Export dialog for instructions.

3. When the databases have been consolidated, perform a database backup of the consolidated database.

4. The AMS Device Manager 14.5 Server Plus Station can be installed using one of the following methods:

• Install AMS Device Manager 14.5 as a station upgrade, if upgrading from version

13 or later which automatically migrates the consolidated database (see page

52).

• Uninstall the 10.0-12.5 station software and install AMS Device Manager 14.5 as

a new Server Plus Station (see page 57). Restore the consolidated database (see

page 22).

Planning and Installation Guide Install AMS Device Manager

January 2022

3.8.2 Consolidate Service Notes

The database backup operation also creates a backup file of service notes. If you would like to consolidate the service notes from multiple AMS Device Manager stations, follow the relevant instructions in the readme file for the Drawings and Notes Management Utility. This information is included in the Tech_Support_Utilities

\DrawingsAndNotesUtility folder on the AMS Device Manager media.

3.8.3 Determine computer names

Computer names are needed to identify the Server Plus Station and the connected Client SC Stations during distributed system installation and configuration (see page 63). Due to a Windows networking requirement, station names must be 15 bytes or less. Please note that some languages have characters that use more than 1 byte.

To find and record a computer name (do not use IP addresses):

1. Right-click the Windows desktop My Computer icon and select .

2. Record the name of each computer that will be part of your distributed system (see the Computer name log example below).

Note

Computer names and DNS names must be the same. “Localhost” cannot be used for AMS Device View. Do not include “\\” in any computer names.

Figure 3-1: Computer name log example

3.9 Modify a Distributed System

Once your distributed system is installed, any changes to its physical configuration may require special procedures in AMS Device Manager. If you are moving the PC where AMS Device Manager is currently installed from a Domain to a Workgroup, or vice-versa, you will need to uninstall and reinstall AMS Device Manager.

To change station types in an existing system, see page 66. For other types of changes, see the following:

• Change a Client SC Station to access a different Server Plus Station.

• Add Client SC Stations.

• Replace a Server Plus Station PC.

Install AMS Device Manager Planning and Installation Guide

January 2022

• Replace a Client SC Station PC.

• Rename a Server Plus Station PC.

• Rename a Client SC Station PC.

• Add a new communication interface.

• Add more tags than currently licensed.

3.9.1 Change station types

If you are changing station types, perform the following appropriate procedures. You may also need to reset your users’ permissions (see page 77).

Change a Server Plus Station to a Client SC Station

Procedure

1. Back up the database (see page 21).

2. Uninstall the previous Server Plus Station software (see page 22).

3. Ensure that a connection can be made to an available Server Plus Station.

4. Install the Client SC Station software (see page 59).

5. Restore or combine the database on another Server Plus Station (see page 22).

3.9.2

Change a Client SC Station to a Server Plus Station

Procedure

1. Contact your Emerson Sales/Service Office to get new license codes for AMS Device Manager.

2. Uninstall the previous Client SC Station software (see page 22).

3. Install the Server Plus Station software (see page 57).

4. License AMS Device Manager (see page 62).

Change a Client SC Station to access a different Server Plus Station

Procedure

1. In Network Configuration on the Client SC Station, remove any configured system interfaces (other than HART Modem and Calibrator).

2. Enter Server Plus Connect on the Start screen and click the Server Plus Connect.

3. In the Server Plus Connect dialog, select a Server Plus Station PC from the dropdown list or enter the name of the PC where the desired Server Plus Station is installed.

4. Click Connect.

Planning and Installation Guide Install AMS Device Manager

January 2022

Note

For more information about the Server Plus Connect utility, refer to AMS Device Manager Books Online.

The Server Plus Connect utility cannot be used on Client SC Stations installed on DeltaV workstations. In these configurations, use the procedure below.

1. Uninstall AMS Device Manager on the Client SC Station (see page 22).

2. Reinstall AMS Device Manager on the Client SC Station and indicate the new Server Plus Station (see page 59).

3.9.3 Add Client SC Stations

To expand an existing distributed system:

Procedure

1. Determine the number of stations covered by your current license (select Help → About from the AMS Device Manager toolbar).

• To add stations that will be covered by your current license, continue with step

3.9.4

• To add more stations than currently licensed, contact your Emerson Sales/

Service office to get new license codes. After you receive your new license codes, run the Licensing Wizard on the Server Plus Station (see page 62) and then continue with step 2.

2. To install AMS Device Manager on the added Client SC Stations, see page 59.

3. Update the Client SC Station configuration on the Server Plus Station (see page 63).

4. To enable the stations in the distributed system to recognize the added Client SC Station, shut down and restart AMS Device Manager on the Server Plus station.

Replace a Server Plus Station PC

Procedure

1. Contact your Emerson Sales/Service Office to get new license codes for AMS Device Manager.

2. Back up the database (see page 21).

3. Uninstall AMS Device Manager from the old PC (see page 22). Rename or disconnect the PC from the network.

4. Connect the new PC to the network and give it the same computer name as the old PC.

Note

If the new Server Plus Station PC has a different computer name, all active alerts that were in the Alert List on the old PC will be lost. In addition, you will be required to run the Server Plus Connect utility on all Client SC Stations to connect to the new Server Plus Station (see page 66).

5. Install Server Plus Station software on the new PC (see page 57).

Install AMS Device Manager Planning and Installation Guide

January 2022

6. License AMS Device Manager (see page 62).

7. Set up the server configuration to recognize each Client SC Station connected in the system (see Configure and secure a Distributed System).

8. Restore the database (see page 22).

3.9.5 Replace a Client SC Station PC

Procedure

1. Uninstall AMS Device Manager from the old PC (see page 22). Disconnect the PC from the network, if appropriate.

2. Connect the new PC to the network.

3. On the Server Plus Station, enter Station Configuration on the Start screen and click Station Configuration.

4. In the Station Configuration dialog, select the name of the old PC and click Remove.

5. In the Station Configuration dialog, click Add.

6. Enter the computer name of the new Client SC Station PC (see page 65 ), and click OK. The station name is not case-sensitive. Do not include a domain name or any other characters that are not part of the computer name.

7. On the new Client SC Station PC, install the Client SC Station software (see page

59).

3.9.6

Rename a Server Plus Station PC

Note

If you have a system interface configured on the Server Plus Station, the Device Monitor List and Alert Monitor alerts will be lost when the PC is renamed.

Procedure

1. Back up the database (see page 21).

2. Record all devices contained in the Device Monitor List.

3. Uninstall AMS Device Manager on the Server Plus Station (see page 22).

4. Rename the Server Plus Station PC:

a) Right-click the Windows desktop My Computer icon. b) Select Properties.

c) On the Computer Name tab, click Change.

d) Enter a new computer name and click OK.

e) Click OK.

5. Install AMS Device Manager on the Server Plus Station (see page 57).

6. Restore the database backed up in step 1 (see page 22).

7. Reinstall the required system interfaces (see page 77) and SNAP-ON applications (see page 72).

Planning and Installation Guide Install AMS Device Manager

January 2022

8. Open AMS Device Manager, right-click each network icon, and select Rebuild Hierarchy and then Scan → New Devices.

9. Add the devices recorded in step 2 to the Device Monitor List (refer to AMS Device Manager Books Online).

3.9.7 Rename a Client SC Station PC

Note

If you have a system interface configured on the Client SC Station, the Device Monitor List and Alert Monitor alerts will be lost when the PC is renamed.

Procedure

1. Record all devices contained in the Device Monitor List.

2. Uninstall AMS Device Manager on the Client SC Station PC (see page 22).

3. Rename the Client SC Station PC:

a) Right-click the Windows desktop My Computer icon. b) Select Properties.

3.9.8

c) On the Computer Name tab, click Change.

d) Enter a new computer name and click OK.

e) Click OK.

4. On the Server Plus Station, open Station Configuration and remove the old name of the Client SC Station PC and add the new name (see page 63).

5. Install AMS Device Manager on the Client SC Station PC (see page 59).

6. Reinstall the required system interfaces (see page 77) and SNAP-ON applications (see page 72).

7. Open AMS Device Manager, right-click each network icon, and select Rebuild Hierarchy and then Scan → New Devices.

8. Add the devices recorded in step 1 to the Device Monitor List on the Client SC Station (refer to AMS Device Manager Books Online).

Add a new communication interface

Procedure

1. Contact your Emerson Sales/Service Office to get a new license code for the desired communication interface.

2. Run the Licensing Wizard on the Server Plus Station (see page 62).

3. Configure the new communication interface (see AMS Device Manager Books Online).

Install AMS Device Manager Planning and Installation Guide

January 2022

3.9.9 Add more tags than currently licensed

Procedure

1. Contact your Emerson Sales/Service Office to get new license codes to cover the number of tags needed.

2. Run the Licensing Wizard on the Server Plus Station (see page 62).

3. Start AMS Device Manager.

4. Install and configure the additional devices.

Planning and Installation Guide Install AMS Device Manager

January 2022

3.10 Installing AMS Device Manager on domain controllers

AMS Device Manager creates Windows user accounts on each station in a distributed system. When AMS Device Manager is installed on a domain controller, these accounts are created as domain users. Communication failures will result if installation is not done correctly as follows:

• If Windows domain controllers are used in a distributed network, the AMS Device

Manager station on the domain controller must be installed first before any other station on the common network domain. 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.

• If installing AMS Device Manager in a domain deployment, and access to an

AMSServiceUser Windows account on the domain controller is required, the Windows user must be a domain administrator for the AMSServiceUser to be installed correctly.

• If AMS Device Manager will be used in a cross-domain configuration, either install an

AMS Device Manager station on the domain controller or if AMS Device Manager will not be installed on a domain controller, create the AmsServiceUser account on the domain controller before installing AMS Device Manager on them. Refer to KBA NA-0800-0113.

3.10.1

3.10.2

Notes

• If AMS Device Manager is installed on the domain controller OR if there is an

AmsServiceUser account on the Domain Controller\Active Directory, there can only be one AMS Device Manager system installed on that domain.

• If AMS Device Manager is NOT installed on the domain controller AND if there is NO

AmsServiceUser account on the Domain Controller\Active Directory, multiple systems can be installed on that domain.

• After installing a Client SC Station on a domain controller together with a DeltaV

ProfessionalPLUS workstation, the AMS Device Manager Server system tray icon may not appear. Log out of the domain controller and log back in to make the AMS Device Manager Server system tray icon appear.

Domain controller security requirements

To launch and run AMS Device Manager, you must be a member of the AMSDeviceManager Windows user group.

Add a user to the AMSDeviceManager group on a domain controller

Note

The following procedure requires network administrator permissions.

Install AMS Device Manager Planning and Installation Guide

January 2022

Procedure

1. Select Start → Settings → Control Panel → Administrative Tools → Active Directory Users and Computers.

2. Select <Domain Name> → Users.

3. Double-click the AMSDeviceManager group.

4. Click Add.

5. Enter the Windows User ID you want to add to the group and click OK.

6. Click OK.

3.11 Install SNAP-ON applications

After you have installed and licensed your AMS Device Manager software, you can install SNAP-ON applications. Each SNAP-ON application is licensed separately and will not run if your station is not licensed for it. Most SNAP-ONs are installed from the AMS Device Manager media; if it is not present, contact the manufacturer to acquire it.

Additional installation requirements may apply to a SNAP-ON application. Before you install a SNAP-ON application, check its documentation to confirm that all installation requirements are satisfied.

Procedure

1. Insert the AMS Device Manager.

2. Browse to \SNAP-ONS And Tools\SNAP-ONS\Installs\<Folder Name> (where <Folder Name> is the name of the folder for the SNAP-ON application to be installed).

3. Double-click the appropriate setup file.

4. Follow the prompts.

Notes

• Most SNAP-ON applications need to be installed on each station in a distributed

system. Calibration Assistant is enabled through licensing–no separate installation is required.

• For all SNAP-ON applications except ValveLink and AMS Wireless, users must also have

Device Write permission (see AMS Device Manager Books Online).

• ValveLink SNAP-ON application user privileges must be enabled in AMS Device

Manager User Manager.

• If a SNAP-ON application is not installed in the C:\Program Files folder, the

AMSDeviceManager Windows user group must be given access to the location.

Planning and Installation Guide Install AMS Device Manager

January 2022

3.12 Install AMS Device Manager Web Services on a station

Procedure

1. Review the AMS Device Manager Web Services software requirements (see page

35).

2. Ensure that appropriate Windows Firewall security settings have been selected (see

page 77).

3. Exit/close all Windows programs, including any running in the background (including antivirus software).

4. Insert the AMS Device Manager media.

5. Browse to D:\SNAP-ONS And Tools\AMSWebServices (where D is the drive letter).

6. Double-click SETUP.EXE.

7. Follow the prompts.

3.13 Mobile workstation

A mobile workstation is an AMS Device Manager Client SC Station connected wirelessly to a LAN. As long as the PC meets the AMS Device Manager requirements (see page 33), it functions like a station connected to a wired Ethernet LAN. However, do not configure system interfaces on a mobile workstation, as this can cause database issues regarding the path of the connected device. If at any time the mobile workstation wireless network connection is lost, you may have to restart AMS Device Manager to reestablish network connectivity.

3.14 Licensing AMS Device Manager 14.5 on DeltaV stations

If you have licensed your AMS Device Manager 14.5 software, you see a full-function application when you launch the product. Otherwise, you can use a limited AMS Device Manager feature set provided with each DeltaV installation. If this is your situation, refer to the DeltaV Books Online for information.

There are several licensing considerations when you install AMS Device Manager on a DeltaV station. To ensure that your installation functions as you expect, please contact your Emerson Sales/Service Office. After you have received the appropriate licensing information and AMS Device Manager setup instructions for your situation, install AMS Device Manager as described beginning on page 74.

Install AMS Device Manager Planning and Installation Guide

January 2022

3.15 Installing AMS Device Manager 14.5 on DeltaV stations

AMS Device Manager 14.5 can be co-deployed only on DeltaV 13.3.1 14.LTS or later stations. To ensure a proper installation, DeltaV must be installed before AMS Device Manager.

Notes

• Any AMS Device Manager station (either Server Plus Station or Client SC Station)

installed on a DeltaV 13.3.1, 14.LTS or later ProfessionalPLUS workstation must be licensed to ensure proper licensing functionality, security, user synchronization between DeltaV and AMS Device Manager, and Device Description (DD) installation.

• Installing a new version of AMS Device Manager does not install new AMS Device

Manager DDs on DeltaV.

• If you are installing AMS Device Manager on any domain controller stations, refer to

page 71.

3.15.1

Before you install AMS Device Manager on your DeltaV stations, ensure that you have all the proper AMS Device Manager and DeltaV licensing and installation instructions (see

page 73).

To install Server Plus Station software on a supported DeltaV station, see page 57. To install Client SC Station software on a supported DeltaV station, see page 59.

DeltaV actions

CAUTION

Do not configure a DeltaV System Interface for the same DeltaV system on more than one AMS Device Manager station.

After installing AMS Device Manager on a DeltaV Station, you must perform a download of the DeltaV workstation (refer to DeltaV Books Online).

Important

Ensure that the AMS Device Manager Server Plus Station is already installed before you download the DeltaV workstation.

Downloading a DeltaV workstation adds DeltaV database account users to the AMS Device Manager database. Creating a new Windows user in DeltaV User Manager also adds that user to the AMSDeviceManager Windows user group. add all desired DeltaV users into the AMS Device Manager Windows group on all stations. Add all desired DeltaV users into the AMS Device Manager Windows group on all stations.

Note

Each time a ProfessionalPLUS Station is downloaded, some DeltaV user permissions overwrite AMS Device Manager user permissions if the User Download checkbox in the DeltaV tab of Tools → Options is selected.

Planning and Installation Guide Install AMS Device Manager

January 2022

3.15.2 DeltaV Upgrade Wizard

The DeltaV Upgrade Wizard automates the process of upgrading a DeltaV Station from an earlier version and ensures that crucial steps are performed. Do not run the DeltaV Upgrade Wizard before uninstalling AMS Device Manager. If you run the DeltaV Upgrade Wizard first, AMS Device Manager will not function as expected and a PC restart may be needed before AMS Device Manager can be uninstalled.

3.15.3 Uninstall DeltaV software

To uninstall DeltaV on a station that has AMS Device Manager co-deployed, you must uninstall AMS Device Manager first and then DeltaV. You can then reinstall AMS Device Manager. If you uninstall DeltaV first, AMS Device Manager will not function as expected.

If you have co-deployed AMS Device Manager on domain controllers and non-domain controllers, you must remove AMS Device Manager from all non-domain controllers first, then from all backup/secondary domain controllers, and then from the primary domain controller. Uninstall DeltaV only after AMS Device Manager has been uninstalled on all PCs.

3.16 Other Applications

3.16.1 DTM Launcher

The DTM Launcher application enables users to install and use certain HART, WirelessHART, and FOUNDATION fieldbus Device Type Manager (DTM) drivers with AMS Device Manager. DTMs are an alternative to the traditional Device Descriptions (DDs) supported in AMS Device Manager. DTMs are provided by various device manufacturers and are configured using the DTM Catalog Manager. For more information, refer to AMS Device Manager Books Online.

AMS Device Manager supports Launcher and Catalog Manager 4.0.0.xxx, with M&M Library version 3.6.20304.39554 (FDT2). You can choose to install the DTM Launcher application during AMS Device Manager installation or install it separately by running

setup.exe from the Install_Files\DTMLauncher folder of AMS Device Manager

media.

Notes

• Do not install other DTM frames as these may cause conflicts with the DTM Launcher

application.

• If you are upgrading to AMS Device Manager 14.5, the DTM Launcher application and

DTM Catalog is removed during installation. You need to reinstall the DTM Launcher application and reconfigure the DTM Catalog Manager.

3.16.2

AMS Device Manager Calibration Connector

AMS Device Manager Calibration Connector is a separately licensed and installed application that integrates with Beamex CMX to provide full-featured calibration management capabilities beyond the basic features available in AMS Device Manager calibration management. AMS Device Manager Calibration Connector provides a solution

Install AMS Device Manager Planning and Installation Guide

January 2022

for users to take advantage of the functionality of other calibration management applications while maintaining the benefits of device configuration and calibration management data synchronization. For more information about AMS Device Manager Calibration Connector, contact your local Emerson Sales/Service Office.

AMS Device Manager Calibration Connector supports:

• Beamex CMX version 2.11.5 with 2.11.7 patch

AMS Device Manager Calibration Connector can only be installed on a Server Plus Station. You must have Windows Administrator permissions to install AMS Device Manager Calibration Connector.

Install AMS Device Manager Calibration Connector

Procedure

1. Insert the AMS Device Manager Calibration Connector DVD in the DVD drive of your PC.

2. Double-click AMSDeviceManagerCalibrationConnector_Setup.exe.

3. Follow the prompts on the installation window.

4. Click Finish when done.

3.16.3

For additional information about using AMS Device Manager Calibration Connector, refer to AMS Device Manager Books Online or AMS Suite Calibration Connector and Beamex CMX Installation and Setup document. Also, refer to your Beamex CMX documentation for more information.

Note

Refer to the AMS Device Manager Supported Device List to determine if a device supports calibration.

User Configuration Reports

The User Configuration Reports tool works with the Bulk Transfer Utility on the AMS Device Manager Server Plus Station. It allows you to verify that multiple devices are configured according to a specified user configuration. The User Configuration Reports tool allows you to check the device configurations of multiple devices and quickly identify any incorrect settings. For more information about user configurations and the Bulk Transfer Utility, see AMS Device Manager Books Online.

The User Configuration Reports tool is installed automatically with an AMS Device Manager Server Plus Station. It requires Advanced Services SQL add-on (which is included in the AMS Device Manager SQL 2014 Express edition on the media).

The User Configuration Reports tool uses AMS Device Manager Generic Export to get device parameter data. If you have a large AMS Device Manager system, or many devices or device parameters, the Generic Export process can take several hours.

Planning and Installation Guide Prepare to use AMS Device Manager

January 2022

4 Prepare to use AMS Device Manager

There are several configuration steps you must take before using AMS Device Manager. If you do not configure your PC and network as described, AMS Device Manager will not function as expected.

4.1 Change Windows Firewall settings

When operating AMS Device Manager on a Windows PC, some changes to Windows Firewall settings may be required. If your PC is adequately protected by a corporate firewall, you may be able to turn off the Windows Firewall protection on your AMS Device Manager PC.

If your AMS Device Manager PC is not protected by a corporate firewall and you have enabled the Windows Firewall, you must change the firewall settings on your PC to allow program and port exceptions that enable AMS Device Manager operation. For assistance configuring your Windows Firewall, contact your IT department.

Note

For more information on security considerations, or for deployment scenarios that require AMS Device Manager Client SC Stations to cross External Firewalls, refer to the AMS Device Manager Security Guide.

4.2 Usernames and passwords

Note

When AMS Device Manager is co-deployed with DeltaV, your DeltaV username and password can also provide AMS Device Manager access.

AMS Device Manager security is based on Windows user authentication. All Windows users using AMS Device Manager must be added in User Manager; if you

install AMS Device Manager, your Windows username is added automatically and given User Manager administrator permissions. The AMS User Manager administrator determines the plant locations and/or functions allowed on a user account. To launch User Manager, enter User Manager on the Start screen and click User Manager.

See AMS Device Manager Books Online for more information on User Manager functionality.

4.3 Configure system interfaces

AMS Device Manager communicates with HART, WirelessHART, FOUNDATION fieldbus, PROFIBUS DPV1 and PROFIBUS PA devices through various system interfaces. If this is a new installation or you are adding interfaces to an existing system, you need to configure the network after you have installed the software. Ensure certificates from the PC hosting the system interface are copied to the AMS folder on other stations in the distributed system, and run Certificate Manager on those stations.

Prepare to use AMS Device Manager Planning and Installation Guide

January 2022

You need to configure the system interfaces that are relevant to each station. You should only configure a particular physical network on one station within the distributed network to avoid the potential for simultaneous device configuration.

To configure a system interface, check the system requirements (see page 39) and refer to the Network configuration overview topic in AMS Device Manager Books Online. Some system interfaces that require additional configuration are discussed in this section.

4.3.1 DeltaV

A DeltaV control network is an isolated Ethernet local area network (LAN) that provides communication between the controllers and the stations. It uses one or more Ethernet hubs for communication.

Note

Do not configure an AMS Device Manager Wireless System Interface if a DeltaV System Interface will be using the same wireless gateway.

For information about AMS Device Manager compatibility with DeltaV, refer to page 41. DeltaV can access devices in RS3 and PROVOX I/O systems through the DeltaV Interface

for RS3 I/O and DeltaV Interface for PROVOX I/O, respectively. The devices are displayed in the DeltaV network hierarchy in AMS Device Manager. For more information, refer to the DeltaV Books Online.

The ValveLink SNAP-ON application is supported for DeltaV and PROVOX I/O cards, but not for RS3 I/O cards.

Prepare the DeltaV system

To prepare a DeltaV control system to communicate with an AMS Device Manager station, you need to:

• Know the node name of the DeltaV ProfessionalPLUS Station you are connecting to. If

you do not know this name, see your system administrator.

• Know the password associated with the DeltaVAdmin account on the ProfessionalPLUS

Station, if it has been changed from the default password.

• Configure a HART-Enabled Channel so that AMS Device Manager knows where to look

for a HART field device. If an I/O channel is enabled for HART but it does not have an associated DeltaV device signal tag, it will not appear in AMS Device Manager.

• Commission any FOUNDATION fieldbus devices you want to be displayed in AMS

Device Manager.

Set DeltaV alert capability

To receive alerts from devices connected to PROVOX and RS3 Migration Controllers in your DeltaV network hierarchy, you must run a utility to properly set the DeltaV alert capability.

Procedure

1. Enter C:\AMS\BIN\DELTAVFASTSCANUTILITY.EXE (where C is the drive

containing the AMS folder) on the Start screen.

Planning and Installation Guide Prepare to use AMS Device Manager

January 2022

2. Uncheck the box for the appropriate DeltaV network.

3. Click Save Changes.

4.4 Add devices to AMS Device Manager

All available information for supported field devices (other than device manuals) is included and installed with the AMS Device Manager application. If it is necessary to install additional devices after the initial installation, refer to Device Type Installation in AMS Device Manager Books Online. Additional device descriptions can be downloaded using this

link: https://www.emerson.com/en-us/catalog/ams-guardiansupportdevicemanager.

4.5 Attach a Roving Station to a Server Plus Station

A Roving Station is a portable PC (laptop or notebook computer) with AMS Device Manager Server Plus Station software installed. A Roving Station is configured as such in the Options for AMS Device Manager dialog (Tools → Options). A Roving Station can be temporarily connected to a stationary Server Plus Station to enable uploading of AMS Device Manager information from the Roving Station. For more information about Roving Stations, refer to AMS Device Manager Books Online.

4.6 AMS Device View

4.6.1

4.6.2

Configure AMS Device View client devices

Note

There is a limit of 20 concurrent clients accessing the AMS Device View server.

There are several configuration tasks you must do before using AMS Device View. If you do not configure your client devices as described, AMS Device View will not function as expected.

Install the latest version of a supported operating system

To allow a browser to access AMS Device View data, you must install the latest version of a supported operating system. This ensures certificates can be installed that enable secure communications. This includes:

• Android and iOS (for mobile browsing of AMS Device View data)

• Windows (for desktop/laptop browsing of AMS Device View data)

See Web Browsers for the list of supported browsers.

Prepare to use AMS Device Manager Planning and Installation Guide

January 2022

4.6.3 Export the AMS Device View certificate

If you are using the Emerson self-signed certificate, and your AMS Device View web server is installed on an AMS station, use Certificate Manager to export the certificate. Otherwise, use this procedure to save the AMS Device View certificate to install on any computer that will be communicating securely with the AMS Device View web server. There are additional procedures. You can access videos about how to do that from the AMS Device Manager media at \Install_Files\Certificate_Videos.

Procedure

1. On the AMS Device View web server, enter certlm.msc on the Start screen and

press Enter.

2. Expand Trusted Root Certification Authorities and select Certificates.

3. Right-click the AmsDeviceView.<servername> certificate and select All Tasks →

Export.

4. Click Next.

5. Select DER encoded binary X.509 (.CER). Next.

6. Browse to a location where you want to save the certificate and enter a file name.

You will be installing this certificate on another PC, or sending it to a mobile device, so make sure the location is accessible.

7. Click Save.

8. Click Next.

9. Click Finish.

4.6.4

Install the AMS Device View certificate on Windows PCs

For AMS Device View to communicate securely with AMS Device Manager, you must export and install Emerson self-signed security certificates from AMS Device Manager Server Plus and AMS Device View PC, and vice-versa. If your AMS Device Manager web server is deployed on an AMS station, you can use Certificate Manager to deploy the certificates. If not, you can access videos about how to do that from the AMS Device Manager media at \Install_Files\Certificate_Videos.

Procedure

1. Copy the certificate file you exported in the AMS Device View web server to your

AMS Device View client PC.

2. Right-click and choose Install Certificate.

3. Select Local Machine and click Next.

4. Click Next.

5. Select Place all certificates in the following store.

6. Click Browse and select Trusted Root Certification Authorities.

7. Click OK.

8. Click Next.

9. Click Finish.

Planning and Installation Guide Prepare to use AMS Device Manager

January 2022

10. If you see a Security warning dialog, click Next.

11. Click OK.

4.6.5 Install the AMS Device View certificate on iOS

Procedure

1. Send the certificate file you exported on the AMS Device View server to an account

accessible on your iOS device.

2. Open the message or email, and tap the attached certificate file.

3. Tap Save to Files.

4. Choose a location and press Save.

5. In the Files app, Tap the .cer file to download its profile.

6. Tap Close.

7. Open the Settings app.

8. Tap Profile Downloaded then Install and enter your passcode. Read the warning,

and tap Install again.

9. Tap Done.

10. Open Settings → General → About → Certificate Trust Settings

11. Enable the AMS Device View certificate under the section Enable Full Trust for Root Certificates. Tap Continue.

4.6.6

Note

When you open AMS Device View, ensure that you use the fully qualified domain name, for example:

https://myserver.mydomain.com/AmsDeviceView

of the AMS Device View web server.

You can now access AMS Device View from the mobile device's browser.

Install the AMS Device View certificate on Android

Procedure

1. Email the certificate file you exported on the AMS Device View server to an account accessible on your Android device.

2. Tap the certificate. An underlined checkmark displays in the menubar.

3. Go to Settings → Security → Encryption & Credentials → Install a Certificate → CA certificate.

4. Tap Install anyway.

5. Tap the certificate file from the list of files in Download. Verify the CA certificate installed popup displays at the bottom of the screen, and in Trusted credentials → User. You can now access AMS Device View from the mobile device's browser.

Prepare to use AMS Device Manager Planning and Installation Guide

January 2022

Note

When you open AMS Device View, ensure that you use the fully qualified domain name, for example:

https://myserver.mydomain.com/AmsDeviceView

of the AMS Device View web server.

4.6.7 View the fully qualified domain name of the AMS Device View web server

This name defines the AMS Device View web server, and is needed in the URL field of the browser when accessing it.

Procedure

1. On the AMS Device View server PC, click Start.

2. Right-click on This PC.

3. Select Properties. The fully qualified domain name is listed in the Full computer name field.

Planning and Installation Guide Troubleshoot installation errors

January 2022

5 Troubleshoot installation errors

If you get error messages during the installation or startup of AMS Device Manager, you may be able to resolve these errors using the troubleshooting procedures in this section.

If you are unable to resolve installation problems after carefully following the installation steps outlined in this guide and using these troubleshooting suggestions, contact your local Emerson Sales/Service Office. Additional Support Center Contact Information can be found here.

To troubleshoot non-installation issues, refer to KBA NK-1400-0417.

5.1 Error messages

Error message / Indication Possible Cause Possible solution

The SQL Server installation fails. Manually install SQL Server

2014 Express Service Pack 3 from the AMS Device Manager media. Run

Install_SQL2014Expres s64bit.bat from the Install_Files \SQL2014SP3Exp\64\SP3

folder. If you do not have Service Pack

3 installed, run

Install_SQL2014SP3Exp ress64bit.bat.The SQL

Server manual installation process requires user input that you must provide. After you install SQL Server, restart the AMS Device Manager installation process.

AMS Device Manager has detected an incorrect version of the database. The version detected is x.x, the correct version should be y.y.

Cannot find server or DNS Error.

Database Verify/Repair was not run before upgrading AMS Device Manager to the current release or AMS Device Manager has detected a fault that occurred during the Verify/ Repair operation.

Run the database conversion utility (AmsConvertDb.exe) from the AMS\Bin folder:

1. Open the AMS\Bin folder.

2. Double-click AmsConvertDb.exe.

If the database conversion utility does not complete successfully, contact your local Emerson Sales/Service Office.

Open port 80 on the Server Plus Station where AMS Device Manager Web Services is configured. See Change

Windows Firewall settings.

Troubleshoot installation errors Planning and Installation Guide

January 2022

Error message / Indication Possible Cause Possible solution

Unable to launch the AMS Device Manager application from the Client SC Station.

“Connecting to OPC Server Failed” when attempting to launch the OPC Client application.

Unable to launch the AMS Device Manager application from the Client SC Station.

AMS Device Manager may be slow to start when launched from the Windows Start menu. The following messages are displayed in the Application event log: Unable to retrieve the current configuration information for server, <PC name>.

Error calling GetServersAsXml.

Open port 135. See Change

Windows Firewall settings.

Add AMSOPC.exe to the exception list. See Change

Windows Firewall settings.

Add sqlserver.exe and sqlbrowser.exe to the exception list. See Change

Windows Firewall settings.

Add AMSServicesHoster.exe to the exception list. See Change

Windows Firewall settings.

Planning and Installation Guide DeltaV system interface deployment concepts

January 2022

A DeltaV system interface deployment

concepts

A.1 Architecture Constraints

In addition to meeting the other installation requirements detailed in this document, the connectivity requirements for AMS Device Manager and DeltaV result in the following architecture constraints:

AMS Device Manager is designed and supported for two installation scenarios when used with DeltaV.

1. For ACN resident machines: The machine must have a supported DeltaV workstation if AMS Device Manager is to be installed. This is due to enhanced domain security features employed in later versions of DeltaV. The scenario of a standalone AMS Device Manager, Server Plus or Client SC resident on the DeltaV ACNs has not been designed or tested for. Settings on a DeltaV node are configured as part of the installation process. When Device Manager is installed on a PC where DeltaV has been installed, all domain security parameters will be properly configured.

2. For non-ACN resident machines: The AMS Device Manager Server Plus or Client SC must be installed in a separate Windows security domain and must have two way trusts established with the applicable DeltaV systems.

Other combinations may be possible, but require site specific security settings that are not covered under standard Guardian Support. Contact your local Emerson business partner for paid for service options for site-specific custom installations.

DeltaV system interface deployment concepts Planning and Installation Guide

January 2022

A.2 AMS Device Manager on Multiple Domain

Networks with a Server Plus on each of the DeltaV Control Networks

Notes

• The DeltaV System Interface must be configured on an AMS Device Manager station

installed on each DeltaV Network and cannot be configured on the same Client SC Station used with Server Plus Connect.

• All AMS Device Manager installations must be at the same version. DeltaV can be

versions 13.3.1, 14.LTS, or 14.FP1or FP2.

• The AMS Device Manager Station installed on the ProfessionalPLUS must be licensed. If

the Server Plus is not installed on the ProfessionalPLUS, an additional license is needed for the Client SC that is installed on the ProfessionalPLUS.

• Each DeltaV network is treated as a separate network and therefore the Cross Domain

requirements in KBA NA-0800-0113 might apply.

• Accessing devices between DeltaV systems or across zones is not supported. Accessing

devices from multiple DeltaV systems or from multiple zones is only supported from the Server Plus station or the Client SC stations on the Plant Network.

Primary Use

This architecture is for a larger user installation (with multiple DeltaV systems, Domains, or Zones) in which the AMS Device Manager Client SC Stations (Non-DeltaV workstations) located on the Plant Network allow users to access devices located on the DeltaV system.

Planning and Installation Guide DeltaV system interface deployment concepts

January 2022

General Deployment Information

In a deployment with multiple control networks, AMS Device Manager Client SC Stations may use the Server Plus Connect functionality. These AMS Device Manager Client SC Stations can connect to either control network as long as all versions of software are the same across the networks. There can be one AMS Device View server and one Read-Only server per distributed system.

Adding Device Files

• The user can add device files at any station in each distributed system. The system then

automatically makes these updates to the other stations in the system, without manual intervention.

• To install properly, the GSD and DD files are needed for PROFIBUS DPV1 and PROFIBUS

PA devices.

• PROFIBUS DP/PA couplers are also needed (see the DeltaV documentation for

supported couplers).

DeltaV system interface deployment concepts Planning and Installation Guide

January 2022

A.3 Single AMS Device Manager distributed

network that supports multiple DeltaV control networks with or without Zones

Notes

• The AMS Device Manager Station installed on the ProfessionalPLUS must be licensed. If

the Server Plus is not installed on the ProfessionalPLUS, an additional license is needed for the Client SC that is installed on the ProfessionalPLUS.

• The DeltaV System Interface must be configured on an AMS Device Manager station

installed on each DeltaV Network/Zone.

• All AMS Device Manager installations must be at the same version. DeltaV can be

versions 13.3.1, 14.LTS, or 14.FP1or FP2.

• Each DeltaV network is treated as a separate network and therefore the Cross Domain

requirements in KBA NA-0800-0113 might apply.

• If the Server Plus Station fails, all Client SC Stations from different DeltaV Zones will lose

communication back to the Server Plus Station. Redundant networking is recommended.

• This architecture includes multiple DeltaV Networks with many devices, therefore a full

version of SQL Server is recommended for improved performance.

• Accessing devices between DeltaV systems or across Zones is not supported. Accessing

devices from multiple DeltaV systems or from multiple zones is only supported from the Server Plus station or the Client SC stations on the Plant Network.

Planning and Installation Guide DeltaV system interface deployment concepts

January 2022

AMS Device Manager supports multiple DeltaV networks or multiple DeltaV Zones/ Network Domain systems with a single AMS Device Manager system connecting to multiple Zones within a DeltaV Zones system, or with an AMS Device Manager system on each Zone in a DeltaV Zones system.

In the case of a single AMS Device Manager system deployed across a single DeltaV Zones system, there is only one AMS Device Manager Server Plus Station, which is connected to the Plant Network. Each DeltaV station can have an AMS Device Manager Client SC Station and must be connected back to the Plant Network.

Primary Use

• To have one main station that consolidates all information but still allows the user write

privileges to any station/system below.

• This architecture is for a user installation in which the AMS Device Manager Server Plus

Station is located on the Plant Network and allows users to access devices located on multiple DeltaV systems or Zones.

• This architecture is valuable for a user who wants to have a single AMS Device Manager

database and perform AMS Device Manager functions from a centralized location. There can be one AMS Device View server and one Read-Only server per distributed system.

Network Domain Deployment

• If the network connection to the AMS Device Manager Server Plus Station is lost, NO

device commissioning or device configuration can be done on the DeltaV network until the network connection has been restored.

Security

• Any user account setup/changes need to be made on all stations. Information relating

to the setup or changes to user account security can be found in AMS Device Manager Books Online.

Adding Device Files

• The user can add device files at any station. The system then automatically makes

these updates to the other stations in the system, without manual intervention.

• To install properly, the GSD and DD files are needed for PROFIBUS DPV1 and PROFIBUS

PA devices.

• PROFIBUS DP/PA couplers are also needed (see DeltaV documentation for supported

couplers).

DeltaV system interface deployment concepts Planning and Installation Guide

January 2022

A.4 AMS Device Manager with DeltaV Control

Networks-Independent Domain Controller

Note

Primary Use

• This architecture is for a customer installation when the DeltaV system is set up with an

Independent Domain Controller.

• This deployment is available with DeltaV 14.LTS, .FP1 or .FP2.

• The version of AMS Device Manager must be compatible with the DeltaV version for

this deployment (i.e. DeltaV 14.LTS, .FP1, .FP2).

Network Domain Deployment

• The IDDC is also supported with the Multiple Domain Networks and Single distributed

system DeltaV deployments.

• When installing AMS Device Manager on DeltaV systems with IDDC, the logged in

Windows user needs to be a Domain Administrator. This is to ensure the proper accounts get created on the IDDC. No other software is required to be installed on the IDDC.

Planning and Installation Guide DeltaV system interface deployment concepts

January 2022

• If the network connection to the Server Plus computer is lost, NO device

commissioning or device configuration can be done on the DeltaV network until the network connection has been restored.

Security

• Security modifications such as adding, removing, or modifying users / privileges must

be made by the user at the DeltaV Pro Plus stations, the AMS Device Manager Server Plus stations, and the other stations on the Network.

• For ACN resident PCs: The PC must have DeltaV and AMS Device Manager installed.

This is due to enhanced security features employed in later versions of DeltaV. The scenario of a standalone AMS Device Manager, Server Plus or Client SC resident on the DeltaV ACNs has not been designed or tested.

• For non-ACN resident PCs: The AMS Device Manager Server Plus or Client SC must be

installed in a separate Windows security domain and must have two-way trusts established with the applicable DeltaV systems.

Adding Device Files

• The user can add devices files an any station except for the Domain Controller. The

system then automatically makes these updates to the other stations in the system, without manual intervention.

• To install properly, the GSD and DD files are needed for PROFIBUS DPV1 and PROFIBUS

PA devices.

• PROFIBUS DP/PA couplers are also needed (see the DeltaV documentation for

supported couplers).

DeltaV system interface deployment concepts Planning and Installation Guide

January 2022

Planning and Installation Guide Other deployment concepts

January 2022

B Other deployment concepts

B.1 AMS Device View

AMS Device View can be deployed read-only, or with the ability to edit some parameters on an AMS Device Manager system following these requirements:

• IIS must be installed on the PC before installing AMS Device View, and must be in the

same time zone as the AMS Device Manager Server Plus Station.

• AMS Device View server must be installed on a supported Windows Server-class

machine.

• Only one AMS Device Manager database is allowed; the AMS Device View Server can

only connect to one (1) Server Plus station.

• Upgrades to AMS Device View require upgrades to AMS Device Manager. Versions

cannot be intermixed.

• AMS Device Manager should be installed or upgraded before installing AMS Device

View, whether deploying on workgroups or a Windows domain.

• You must export and install certificates between AMS Device Manager stations and

AMS Device View server. See the AMS Device View videos for how to do this on your install media \Install_Files\Certificate_Videos.

Deployed on AMS Device Manager Server Plus Station

Figure B-1: AMS Device View server on the AMS Device Manager Server Plus Station

Deployed on a non-AMS Device Manager PC

Note

Emerson does not recommend installing AMS Device View on a domain controller unless DeltaV is also on the same server.

Figure B-2: AMS Device View server not on an AMS Device Manager Station

• A mix of domains and workgroups is not supported. The AMS Device Manager Server

Plus and AMS Device View server must be both on a domain, or both on a workgroup.

Other deployment concepts Planning and Installation Guide

January 2022

• The following restrictions apply when the Windows login to AMS Device View is a local

user account (and not a domain account)

— The AMS Device Manager Server Plus and the AMS Device View server should each

have their own local Windows user for the user account being used to log into AMS Device View. That local user name and password will need to be set to the same values across both servers.

— In AMS Device Manager User Manager, add the AMS Device View server as a

Windows machine.

— In AMS Device Manager User Manager, the user accounts logging into AMS Device

View must be added under the AMS Device Manager Server Plus and the AMS Device View PCs

— In AMS Device Manager User Manager, the Assigned Permissions for the account

under both PCs must be identical

Note

When installing AMS Device View on a different domain than AMS Device Manager Server Plus, refer to KBA NA-0800-0113 Configuring AMS Device Manager for Cross Domain Functionality

Figure B-3: AMS Device View server installed on a different domain than AMS Device Manager Server Plus

Planning and Installation Guide Other deployment concepts

January 2022

B.2 HART-IP Interface

Figure B-4: HART-IP supported Interfaces

Honeywell OneWireless Wireless Device Manager, WDMX, WDMY; OneWireless R240, R300, R310 and R320

Triconex Tricon CX version 11.5 HIMA HIMax major version 5, configured with SilWorx v 5.30 Phoenix Contact Ethernet HART multiplexer GW PL ETH/BASIC-BUS (2702321) and GWPL

ETH/UNI-BUS (2702233)

Notes

• The diagram shows individual networks and is not intended to imply all networks being

connected simultaneously.

• For additional connection details and Windows ports, see AMS Product Security

documentation, and for details on HART-IP systems, contact the manufacturer or your local Emerson impact partner or system integrator.

Other deployment concepts Planning and Installation Guide

January 2022

B.3 HART Interface Solution – External Interfaces

Notes

• This deployment provides AMS Device Manager access to all HART devices connected

to multiplexers.

• The Server Plus Station must be licensed to cover all HART devices.

• For applications where P+F/Elcon customized replacement panels cannot be used, P+F/

Elcon also provide a family of external interface panels. The P+F/Elcon external interface panels are used in conjunction with the DCS or PLC existing termination panels. External interfaced panels are daisy-chained to create the multiplexer network used by AMS Device Manager to gain access to the HART information from the field instruments.

• RS-485 signal from the multiplexer can be connected to an Ethernet serial hub or to an

RS-485/RS-232 converter, for the HART signal to be accepted into the AMS Device Manager PC.

Planning and Installation Guide Other deployment concepts

January 2022

B.4 HART Custom Solution – Integrated HART Panel

Incorporating Multiplexer and Field Termination Panel (FTP)

Notes

• This deployment is typically used on new installations or upgrades where the digital

control system is purchased with a P+F/Elcon panel.

• This deployment can be used to replace existing term panels to add multiplexers to an

existing system.

• This deployment provides AMS Device Manager access to all HART devices connected

to multiplexers.

• The Server Plus Station must be licensed to cover all HART devices.

• The RS-485 signal from the Multiplexer can be connected to an Ethernet serial hub or

to an RS-485/RS-232 converter, for the HART signal to be accepted into the AMS Device Manager PC.

Other deployment concepts Planning and Installation Guide

January 2022

Planning and Installation Guide Version compatibility

January 2022

C Version compatibility

As of the initial release of AMS Device Manager 14.5, the following SNAP-ON applications are supported:

Table C-1: SNAP-ON applications/AMS Device Manager compatibility matrix

SNAP-ON application SNAP-ON application version AMS Device Manager 14.5

ValveLink 13.6 x

AlertTrack 6.7.2.1 x

Rosemount MV Engineering Assistant

AMS Wireless 14.5 x

Masoneilan ValVue HART 2.81.1 x

Masoneilan ValVue FF 2.32.1 x

Meter Verification 3.4.b25.r1 x

QuickCheck 9.3.0.2 x

Flowserve ValveSight 1.0.0.2 (Logix MD HART,

5.5.1 x

6.5.1 x

x Logix420); 1.0.0.10 (Logix MD +); 1.1.1.8 (Logix 3400MD)

Table C-2: DeltaV/AMS Device Manager compatibility matrix

DeltaV Versions AMS Device Manager version 14.5

13.3.1 x

14.LTS x

14.FP1, 14.FP2 x

Note

AMS Device Manager supports DeltaV version 13.3.1, 14.LTS, 14.FP1, 14.FP2 in codeployed installations only.

Version compatibility Planning and Installation Guide

January 2022

100

AMS AMS Device Manager v14.5 Planning and Installation Guide Manuals & Guides

Specifications and Main Features

Frequently Asked Questions

User Manual

Contents

1 Introduction

1.1 Before you begin

1.2 Configuration Assessment Tool

1.3 Installation overviews

Install a standalone AMS Device Manager system

Install a distributed AMS Device Manager system

1.3.3 Install AMS Device Manager on a DeltaV system

1.4 Database operations

Back up a database

1.4.2 Restore a database

1.5 Uninstall AMS Device Manager

1.6 Reference documents

1.6.1 AMS Device Manager Books Online

Electronic documentation

Release Notes

1.6.4 AMS Device View Help

Device manuals

Product data sheets, security guides, and white papers

Knowledge Base Articles

2 System requirements

2.1 Sizing considerations

2.2 Hardware requirements

2.2.1 PC processing speed, memory, and disk space

2.2.2 Serial interfaces

2.2.3 USB interfaces

2.3 Network requirements

2.3.1 AMS Trex

2.4 Software requirements

2.4.1 Operating systems

Virtualizations

Operating system patches and service packs

Support for Remote Desktop Services

Web browsers

AMS Device Manager Web Services

2.4.7 .NET Framework

Database

Microsoft Office

2.5 Windows security requirements

2.5.1 AMS Device Manager installation

AMS Device Manager users

2.5.3 AmsServiceUser

AMS Device View security requirements

2.6 Requirements for system interfaces

HART modems

Documenting calibrators

2.6.3 DeltaV

2.6.4 HART-IP

HART Multiplexer Network

Wireless

2.7 AMS Device View

AMS Device Manager compatibility with AMS Device View

DeltaV compatibility with AMS Device View

3 Install AMS Device Manager

3.1 Upgrade an AMS Device Manager system

Upgrade from AMS Wireless Configurator

3.1.2 Upgrade from AMS Device Configurator for DeltaV

3.2 Install Server Plus Station software

3.3 Install Client SC Station software

3.4 Install the AMS Device View web server

3.5 License AMS Device Manager

3.6 License AMS Device View

3.7 Register your product with SureService

3.8 Configure and secure a Distributed System

3.8.1 Consolidate databases

3.8.2 Consolidate Service Notes

3.8.3 Determine computer names

3.9 Modify a Distributed System

3.9.1 Change station types

Change a Server Plus Station to a Client SC Station

Change a Client SC Station to a Server Plus Station

Change a Client SC Station to access a different Server Plus Station

3.9.3 Add Client SC Stations

Replace a Server Plus Station PC

3.9.5 Replace a Client SC Station PC

Rename a Server Plus Station PC