System Guide

Rev 3
July 2025

AMS Machine Works v2.0

System Guide
Copyright
© 2025 by Emerson. All rights reserved.

No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any
language in any form by any means without the written permission of Emerson.

Disclaimer
This manual is provided for informational purposes. EMERSON MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS
MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. Emerson shall not be liable for errors, omissions, or inconsistencies that may be contained herein or for incidental or
consequential damages in connection with the furnishing, performance, or use of this material. Information in this document is
subject to change without notice and does not represent a commitment on the part of Emerson. The information in this manual is
not all-inclusive and cannot cover all unique situations.

Patents
The product(s) described in this manual are covered under existing and pending patents.

Where to get help

Emerson provides a variety of ways to reach your Product Support team to get the answers you need when you need them:

Phone Toll free 1 800 833 8314 (U.S. and Canada)

+1 512 832 3774 (Latin America)
+63 2 8702 1111 (Asia Pacific, Europe, and Middle East)
Email [email protected]
Web http://www.emerson.com/en-us/contact-us

To search for documentation visit https://www.emerson.com/.

To view toll free numbers for specific countries, visit http://www.emerson.com/technicalsupport.

2
System Guide Contents
July 2025

Contents
Chapter 1 Introduction.................................................................................................................. 7
1.1 Symbols............................................................................................................................................7

Chapter 2 System Planning............................................................................................................ 9

2.1 Planning Steps..................................................................................................................................9
2.2 AMS Machine Works Architecture.................................................................................................. 11
2.2.1 AMS Machine Works Application Layer........................................................................................ 13
2.2.2 AMS Machine Works Core............................................................................................................13
2.2.3 Agent Layer................................................................................................................................. 18
2.2.4 Hardware Layer........................................................................................................................... 18
2.3 Deployment Scenarios................................................................................................................... 19
2.3.1 Typical Deployment Scenarios.....................................................................................................20
2.3.2 MongoDB Database Deployments...............................................................................................23
2.3.3 Unsupported Deployment Scenarios........................................................................................... 25
2.4 System Requirements.................................................................................................................... 25
2.4.1 System Scalability........................................................................................................................31
2.4.2 Update Rates...............................................................................................................................38
2.4.3 Compatibility.............................................................................................................................. 40
2.5 AMS Machine Works Security......................................................................................................... 43
2.5.1 Network Port Availability............................................................................................................. 43

Chapter 3 Installation Procedures................................................................................................ 45

3.1 Pre-Installation Steps......................................................................................................................45
3.1.1 Server Installation Pre-Check....................................................................................................... 46
3.1.2 Stop Automatic Updates............................................................................................................. 49
3.1.3 Locate the Installer...................................................................................................................... 50
3.2 AMS Machine Works Server Installation.......................................................................................... 51
3.2.1 Launch Installer........................................................................................................................... 51
3.2.2 Software License Agreement....................................................................................................... 53
3.2.3 Choose AMS Machine Works Server Installation.......................................................................... 54
3.2.4 Enter a Server Name.................................................................................................................... 55
3.2.5 Choose Internal vs. External MongoDB Server..............................................................................56
3.2.6 Provide Passwords or Connection String......................................................................................58
3.2.7 Choose the Installation Drive....................................................................................................... 63
3.2.8 Select which Agents to Install...................................................................................................... 64
3.2.9 Confirm Installation.....................................................................................................................66
3.2.10 Complete the Reboot Cycle.......................................................................................................67
3.3 Agent Server Installation................................................................................................................ 69
3.3.1 Launch Installer........................................................................................................................... 70

AMS Machine Works v2.0 iii

Contents System Guide
July 2025

3.3.2 Software License Agreement....................................................................................................... 71

3.3.3 Choose Agent Server Installation................................................................................................. 72
3.3.4 Connect to a Server..................................................................................................................... 73
3.3.5 Choose the Installation Drive....................................................................................................... 74
3.3.6 Select which Agents to Install...................................................................................................... 75
3.3.7 Confirm Installation.....................................................................................................................77
3.3.8 Complete the Reboot Cycle......................................................................................................... 78
3.4 External MongoDB Server Installation.............................................................................................80
3.5 Post-Installation Steps.................................................................................................................... 93
3.5.1 Check Services.............................................................................................................................94
3.5.2 Deconflict Ports...........................................................................................................................96
3.5.3 Restart Automatic Updates......................................................................................................... 97
3.5.4 Enable Domain User Login........................................................................................................... 97
3.5.5 Add AMS Machine Works Certificates.......................................................................................... 98
3.5.6 First Launch of AMS Machine Works............................................................................................ 99
3.5.7 Set Data Retention Policy and Create Backups...........................................................................100
3.5.8 Install the Vibration Analyzer - VibApp.......................................................................................100
3.5.9 Install CSI USB Drivers................................................................................................................101
3.5.10 Monitor DSS Processing Capacity............................................................................................ 102

Chapter 4 Maintenance and Migration....................................................................................... 105

4.1 Uninstallation Options..................................................................................................................105
4.1.1 Uninstall AMS Machine Works v2.0............................................................................................105
4.2 Modification Options....................................................................................................................110
4.2.1 Modify an AMS Machine Works v2.0 Installation........................................................................110
4.3 Backup and Restore Procedures....................................................................................................114
4.3.1 Manual Backup of the MongoDB Database................................................................................ 114
4.4 Update from v1.8 to v2.0..............................................................................................................115
4.4.1 Update AMS Machine Works from v1.8 to v2.0..........................................................................115

Chapter 5 Support Tools.............................................................................................................121

5.1 Pre-Installation Checklist Tool...................................................................................................... 121
5.2 Sending Log Files to Emerson Product Support.............................................................................124
5.2.1 Installation Logs Compressor.....................................................................................................124
5.2.2 Service Logs Compressor...........................................................................................................125
5.3 Data Retention Policy Tool........................................................................................................... 125
5.3.1 Schedule the Data Retention Policy Tool................................................................................... 128
5.4 Uninstall Cleaner Utility................................................................................................................ 131

Chapter 6 OPC UA Server............................................................................................................ 135

6.1 Manage Certificates in OPC UA Clients and Servers.......................................................................135
6.2 Configure an OPC UA Client..........................................................................................................136
6.3 OPC Tag Information and Tree Structure...................................................................................... 143

iv AMS Machine Works v2.0

System Guide Contents
July 2025

Chapter 7 Troubleshooting........................................................................................................ 145

7.1 Installation Troubleshooting.........................................................................................................145
7.2 OPC UA Server Troubleshooting .................................................................................................. 145
7.3 Security Troubleshooting............................................................................................................. 145
7.4 Vibration Analyzer Troubleshooting............................................................................................. 146

Index .................................................................................................................................. 147

AMS Machine Works v2.0 v

Contents System Guide
July 2025

vi AMS Machine Works v2.0

System Guide Introduction
July 2025

1 Introduction
Software Description
AMS Machine Works is the next generation machinery condition monitoring and analysis
software from Emerson. AMS Machine Works combines state-of-the-art technology,
predictive maintenance techniques, and comprehensive vibration analysis tools to provide
clear and accurate monitoring of the condition of the machinery in your facility.
AMS Machine Works helps to improve safety and increase profitability by providing a
modern software solution capable of predicting faults before they happen and saving you
from the costs associated with unplanned downtime.

What's in this installation

This version of AMS Machine Works comes with a single installer that will provide options
to install all of the AMS Machine Works web modules, two databases (PostgreSQL and
MongoDB), the Vibration Analyzer (VibApp), and every type of Agent.
Some of the components, VibApp and Agent, can have a distributed deployment which
depends on the networking requirements.
To meet the requirements of complex network topologies you can deploy each type of
Agent more than once on your network, but only one of each type of Agent is allowed on a
particular server at a time.
The main measurement data storage is handled by MongoDB, which is deployed on the
same server as the AMS Machine Works server by default. MongoDB can also be deployed
on an external server or on a cloud server. Refer to this guide for more details.

About this manual

This guide is intended for system administrators to help plan, install, and set up the
software. Emerson recommends that system administrators refer to this document when
setting up the system.

Other relevant documents

• Online Help – provides instructions and reference information for using the software
after installation. This is built into the software and accessed by clicking in the user
toolbar
• Release Notes – contains what is new and notes pertaining to the release
• Knowledge Base Articles (KBA) – documents published to address known issues,
frequently asked questions, history traces, system requirements, how-to information,
and application-specific content

1.1 Symbols
Note
This symbol marks passages that contain important information.

AMS Machine Works v2.0 7

Introduction System Guide
July 2025

CAUTION
This symbol marks operations that can lead to malfunctions or faulty measurements, but
will not damage the device.

8 AMS Machine Works v2.0

System Guide System Planning
July 2025

2 System Planning
AMS Machine Works is comprised of four main types of components:
1. AMS Machine Works Components — These are the central components of the
system. See: AMS Machine Works Application Layer
2. Agent Components — Agent components provide a connection between
measurement devices and the central system components. See: Agent Layer
3. Database Components — There are two database components used with AMS
Machine Works. See: Database Components
4. Other Components — These components are installed as dependencies of the other
elements of the AMS Machine Works architecture.
See: AMS Machine Works Architecture
These components can be installed on the same server, or different servers, depending on
the deployment scenario, network requirements, and setup. See: Deployment Scenarios
Before you install any of the system components, you must plan your installation using:
the system requirements, recommended system deployment scenarios, and the
guidelines provided in this chapter. Follow the Planning Steps to plan your system
properly.

2.1 Planning Steps

These steps guide you through the process of gathering the requirements of your
installation, and gathering the information necessary for performing the installation.

Procedure
1. Determine the data sources that you want to bring into AMS Machine Works and
check if they are compatible. See: Device Compatibility.
Depending on the type of data source, install the appropriate Agent to bring the
right data source into AMS Machine Works. See: Agent Layer .
2. Confirm the system will not exceed scalability limitations. See: System Scalability.
3. Determine your network setup and gather connection information and
authorizations.
Note
Your network setup affects the deployment of the AMS Machine Works
components. See: Deployment Scenarios. The installations have prompts for
information about the location of other services. Before you run the installation
wizard on each server, you need to have all the information about:
a. Network locations where the services will be installed.
b. Log in names and the associated passwords.
c. Connection strings.

AMS Machine Works v2.0 9

System Planning System Guide
July 2025

4. Determine any network architecture restrictions in your network.

Your network architecture affects what firewall exceptions you need to define. See:
AMS Machine Works Security
5. Determine your database requirements.
The AMS Machine Works MongoDB database for measurements can be either
Internal or External. See: Database Components
6. Check the System Requirements.
7. Check Network Port Availability requirements.
8. Plan to integrate security certificate installation with software installation. See: AMS
Machine Works Security
9. Ensure any systems you plan to interface with AMS Machine Works are ready.
a) Before interfacing Emerson Wireless Gateway devices with AMS Machine
Works:
1. Ensure that all the devices which connect through the Emerson
Wireless Gateway are configured for data collection by using either:
a. AMS Device Manager with AMS Wireless SNAP-ON — This
software reduces commissioning and maintenance expenses
while improving plant availability and reliability.
b. AMS Wireless Configurator — This is provided with Emerson
Wireless Gateway, refer to the Emerson Wireless Gateway
documentation for details.
c. AMS Trex Device Communicator

b) Before interfacing AMS Asset Monitor devices with AMS Machine Works,
access the AMS Asset Monitor Web Interface and ensure that the device has
been fully configured.
1. An AMS Machine Works interface must be set and enabled.
2. An AMS Machine Works user must be created.

c) Before interfacing AMS 6500 ATG devices with AMS Machine Works, ensure
that the devices are configured for data collection with AMS Machine Studio.
1. An AMS 6500 ATG unit license must be installed for each CP or CC
card.
2. Modbus port must be set and enabled.
3. Collection tasks must be set on the AMS 6500 ATG unit.

d) Before interfacing with AMS 2140 Machinery Health Analyzer units, ensure
that the devices are configured to work with AMS Machine Works.
1. Your AMS 2140 Machinery Health Analyzer should have version
1.3.13.0 firmware, or later.

10 AMS Machine Works v2.0

System Guide System Planning
July 2025

10. Determine if you need to read data from AMS Machine Works using an OPC UA
Server client.

2.2 AMS Machine Works Architecture

AMS Machine Works has a modular architecture which supports communication and
deployment in complex network topologies.
The Internal location is the computer or virtual machine where the AMS Machine Works
Core is installed. Every other location is an External location. See: Deployment Scenarios

Note
One part of the AMS Machine Works Core, the MongoDB measurement database, can be
installed on an External computer or virtual machine.

AMS Machine Works Architecture

AMS Machine Works has four main architectural layers:

AMS Machine Works v2.0 11

System Planning System Guide
July 2025

Figure 2-1: AMS Machine Works Architecture Diagram

A. AMS Machine Works Application Layer — This layer contains web applications for data presentation,
configuration, maintenance, security, and data integration. See: AMS Machine Works Application Layer
B. AMS Machine Works Core — This layer processes the vibration data for health, alerts, aggregation, and
calculating derived measurements. Manages machine trains, monitors alerts, and assesses the health of
assets. See: AMS Machine Works Core
A. AMS Machine Works Service Layer
A. Windows Services
B. Other Components
B. Data Transport and Storage Layer
A. Database Components
B. RabbitMQ

12 AMS Machine Works v2.0

System Guide System Planning
July 2025

C. Integration and Abstraction Layer

C. Agent Layer — This layer connects the AMS Machine Works Service Layer to the Hardware Layer.
Native measurements, device health, and status information data are sent to the Core Module. See: Agent
Layer
D. Hardware Layer — This layer contains all the physical devices which are installed in the site you are
monitoring. See: Hardware Layer

2.2.1 AMS Machine Works Application Layer

The AMS Machine Works Application Layer are the browser based user interfaces to the
functionality built into the AMS Machine Works Core. The Application Layer components
communicate with the Core by using the https protocol.
Table 2-1: AMS Machine Works Application Layer Components
Core Component Description
Network Device Module The Network Device Module provides functionality for
connecting to Measurement Devices through different
types of Agents.
Design Studio The Design Studio provides the functionality to define every
aspect of a Machine Train.
Machinery Health The Machinery Health provides functionality for viewing
every Machine Train, and for highlighting each Machine
Train that needs closer observation.
Portable Device Module The Portable Device Module component provides the
functionality for connecting to and managing AMS 2140
Machinery Health Analyzer portable units.
User Manager The User Manager provides functionality for adding,
removing, and managing every User in the system in each
type of Role.

Vibration Analyzer, also known as VibApp is a thick-client web application you can use to
VibApp. perform detailed analysis on vibration data stored in the
measurement database. It can be installed on the AMS
Machine Works Server or separately installed on any client
computer that will be used for detailed analysis of vibration
data.
Online Help The Online Help component provides information about the
operation of AMS Machine Works.
Your Account The Your Account module allows you to view basic
information about your account, choose a profile picture,
and to reset your password

2.2.2 AMS Machine Works Core

The computer or virtual machine which has the AMS Machine Works Core components is
called the Internal location. Every other location is an External location.
The AMS Machine Works Core contains three main levels:

AMS Machine Works v2.0 13

System Planning System Guide
July 2025

1. AMS Machine Works Service Layer — This layer has specialized services and
modules for interacting with the AMS Machine Works Application Layer.
2. Data Transport and Storage Layer —
a. Data Transport — AMS Machine Works uses RabbitMQ to provide a robust
asynchronous communication between services.
b. Data Storage — AMS Machine Works uses two databases:
1. PostgreSQL — for storing configuration data.
2. MongoDB — for storing measurement data.

Note
The MongoDB can be located on an External computer or virtual
machine. See: Database Components

3. Integration and Abstraction Layer — This layer provides a stable interface between
the Agents and the various data transport and storage technologies.

AMS Machine Works IIS Application Pools and Applications

AMS Machine Works uses the following Internet Information Services (IIS) application
pools and one site, EmersonCSI . See: AMS Machine Works Architecture

Note
When components are installed on separate servers, the EmersonCSI base website
references the DefaultAppPool application pool.

Table 2-2: AMS Machine Works IIS Application Pools and Applications
Application Pool Applications
AMS_MW_DesignStudio /CTBAB
/design-studio
AMS_MW_EmersonCSI Root Application
AMS_MW_HistorianNext /HistorianNext
AMS_MW_IdSrv /CIDS
AMS_MW_MachineryHealth /CTVAB
/machinery-health
AMS_MW_NetworkDevice /network-device
/OAB
AMS_MW_OMG /OMG
AMS_MW_PAG /PAG
AMS_MW_PIG /PIG
AMS_MW_PortablesApp /PortablesApp
AMS_MW_Status /CSB
/Status

14 AMS Machine Works v2.0

System Guide System Planning
July 2025

Table 2-2: AMS Machine Works IIS Application Pools and Applications (continued)
Application Pool Applications
AMS_MW_UserManager /CUMAB
/user-manager
AMS_MW_VibApp /VibApp

Note
AMS_MW_IdSrv is used to send email messages for functions such as Reset Password.
To use your own SMTP server please consult with Product Support.

Windows Services
The following Windows Services are installed on a computer for each AMS Machine Works
component.
Table 2-3: AMS Machine Works Components and Associated Windows Services
AMS Machine Works Component Windows Service Name
AMS Machine Works Asset Monitor Agent Emerson MW Asset Monitor Agent
AMS Machine Works ATG Agent Emerson MW ATG Agent
AMS Machine Works Wireless Agent Emerson MW Wireless Agent
AMS Machine Works Portables Edge Agent Emerson MW Portables Edge Agent
AMS Machine Works Emerson MW Core Data Shovel Service
Emerson MW Core License Manager
Emerson MW Core Train Service
Emerson MW Data Integration Module OPC Server
Emerson MW Online Device Service
Emerson MW Portables Agent Configuration Service
Emerson MW Portables Authorization Service
Emerson MW Portables Device Configuration Service
Emerson MW Portables Library Service
Emerson MW Portables Module Integration Service
Emerson MW Portables Route Configuration Service
Emerson MW Route Factory
Emerson MW Portables Transaction Orchestrator

Database Components
With AMS Machine Works v2.0, two types of databases are deployed:
1. A PostgreSQL 17 database for storing configuration information about the AMS
Machine Works application.

AMS Machine Works v2.0 15

System Planning System Guide
July 2025

2. A MongoDB 8.0.4 2008R2Plus SSL (64 bit) database for storing measurement data.
There are three MongoDB database deployment options:
a. Single Server Deployment — The MongoDB database is on the same machine
as the AMS Machine Works software. The AMS Machine Works installer
handles the MongoDB database configuration. See: MongoDB Single Server
Deployment — Internal
b. External Server Deployment — The MongoDB database is on an external
server within the same network as the AMS Machine Works server machine.
See: MongoDB External Server Deployment
c. Cloud Server Deployment — The MongoDB database, in this case MongoDB
Atlas, is on an external server accessed through the internet. See: MongoDB
Atlas Cloud Server Deployment

You should choose an External MongoDB Server Installation when some or all of the
following conditions are met:
• Your previous installation of AMS Machine Works required either an External MongoDB
Server or an External SQL Server.
• Your network administration policies require physical or logical separation of servers.
• Your data retention policies require data storage greater than can easily be supported
on the computer acting as your AMS Machine Works server.
• When the 'XL' size of a single server no longer meets your needs. Processor and
Memory Specifications

Database Component Names

This section describes the database and data file locations in the installation.
The software installation process deploys a database into a PostgreSQL Server instance
named PostgreSQL 17, which is located at:
C: Program Files\PostgreSQL\17\

This database contains all the AMS Machine Works configuration data in a database
named mwcore.
The software installation process deploys four MongoDB databases. The location can be
specified during installation. The default folder is:
C:\EMERSONMW\Data

Table 2-4: Databases

Database Module Database Name
mwcore
PostgreSQL 17
mwidentity

16 AMS Machine Works v2.0

System Guide System Planning
July 2025

Table 2-4: Databases (continued)

Database Module Database Name
(Recommended) MongoDB EmersonMWCore
8.0.4 2008R2Plus SSL (64 bit)
EmersonMWcoreData
MongoDB 6.0.20 2008R2Plus
SSL (64 bit)1 EmersonMWLicenses

Note EmersonMWOnline
Depending on your
EmersonMWPortables
configuration, your MongoDB
database can be on an external
server. See: External MongoDB
Server Installation

1 This version is provided to maintain compatibility with Windows Server 2016 systems.

For more information on different recovery models see: Backup and Restore Procedures

Other Components
An AMS Machine Works installation includes other components which are dependencies
of the system:
1. Microsoft .NET framework
a. Microsoft .NET 8.0.18 - Windows Server Hosting
b. Microsoft .NET Runtime -8.0.18 (x64)
c. Microsoft .NET Runtime -8.0.18 (x86)
d. Microsoft ASP.NET Core 8.0.18 - Shared Framework (x64)
e. Microsoft ASP.NET Core 8.0.18 - Shared Framework (x86)
f. Microsoft Windows Desktop Runtime - 8.0.18 (x64) - (When the AMS 2140
Agent is installed.)

2. Microsoft Visual C++ Redistributable

a. Microsoft Visual C++ 2015-2022 Redistributable (x64)
b. Microsoft Visual C++ 2015-2022 Redistributable (x86)

3. RabbitMQ Server 4.1.1

4. Erlang OTP 27.3.4 (15.2.7)
5. Sentinel RMS License Manager 10.2.0
6. MongoDB 8.0.4 2008R2Plus SSL (64 bit) See: Database Components
Note
MongoDB 6.0.20 2008R2Plus SSL (64 bit) is used for Windows Server 2016
Standard or Datacenter installations. See: Database Components

7. PostgreSQL 17 See: Database Components

AMS Machine Works v2.0 17

System Planning System Guide
July 2025

2.2.3 Agent Layer

The Agent components provide connectivity between different types of measurement
devices in the Hardware Layer and the AMS Machine Works Core.
Agent components are distributable, and can be installed either on an Internal or an
External server. Multiple instances of each Agent type can be present on your network,
but only one instance of an Agent can exist on each physical or virtual machine. See:
Deployment Scenarios
Note
To increase the system's performance, Emerson recommends that you only install the
components that you need.

Table 2-5: AMS Machine Works Agent Server Components

Component 1 Description
Emerson Wireless Gateway Agent The Emerson Wireless Gateway Agent is a Windows service
that connects to Emerson Wireless Gateway units via the
HART-IP protocol. These units connect to wireless devices
such as:
• AMS 9420 Wireless Vibration Transmitter
• AMS Wireless Vibration Monitor

AMS Asset Monitor Agent The AMS Asset Monitor Agent is a Windows service that
brings data into AMS Machine Works from AMS Asset
Monitor units via the Web Socket protocol.

AMS 6500 ATG Agent The AMS 6500 ATG Agent is a Windows service that brings
data into AMS Machine Works from sensors connected to
AMS 6500 ATG systems. Communications between AMS
6500 ATG units and AMS Machine Works uses two ports:
1. Modbus TCP/IP Port

2. ATG Service Port

AMS 2140 Agent The AMS 2140 Agent is a Windows service that brings data
into AMS Machine Works from portable AMS 2140
Machinery Health Analyzer units. Communications between
AMS 2140 units and AMS Machine Works can use either:
1. CSI USB Driver

2. Web Socket

1 If installed on a separate server, the certificate must be exported and installed on the AMS
Machine Works server.

2.2.4 Hardware Layer

AMS Machine Works supports the following hardware connections via the appropriate
type of Agent:
• Emerson Wireless Gateway Agent — This Agent connects to Emerson Wireless
Gateway units.

18 AMS Machine Works v2.0

System Guide System Planning
July 2025

— Emerson Wireless Gateway — The gateway provides connectivity to two types of

wireless measurement devices:
• AMS 9420 Wireless Vibration Transmitters — The AMS 9420 Wireless Vibration
Transmitter is an installation-ready solution that monitors vibration and
temperature in hard-to-reach locations. It also provides a variety of transmitter
and sensor configurations.
• AMS Wireless Vibration Monitors — The AMS Wireless Vibration Monitor is an
installation-ready solution that monitors vibration and temperature in rotating
equipment in hard-to-reach locations.
• AMS Asset Monitor Agent — This Agent connects to:
— AMS Asset Monitor — Each AMS Asset Monitor unit contains a custom
configuration of CHARMs.
• AMS 6500 ATG Agent — This Agent connects to:
— AMS 6500 ATG — Each AMS 6500 ATG unit contains a custom configuration of
cards.
• AMS 2140 Agent — This Agent connects to:
— AMS 2140 — Each portable AMS 2140 unit can connect to a variety of sensors
located in your installation.

2.3 Deployment Scenarios

AMS Machine Works is comprised of three main types of components, AMS Machine
Works web components, Agent components, and database components. The
components can be installed on the same server, or different servers, depending on the
deployment scenario, network requirements, and setup.
AMS Machine Works can be deployed with DeltaV, Ovation, and Plantweb Optics in the
following combinations:
1. All software in the same Domain.
2. All software in the same Workgroup.
3. Heterogeneous mixes with some pieces of software in different domains and/or
workgroups.
Note
All piece of software must be deployed on different machines.

The most common deployment scenarios are shown in network diagrams. See: Typical
Deployment Scenarios
Some scenarios are not possible or unsupported. See: Unsupported Deployment Scenarios
Note
If your organization requires a different deployment scenario that is not shown, please
contact your Emerson representative.

AMS Machine Works v2.0 19

System Planning System Guide
July 2025

2.3.1 Typical Deployment Scenarios

AMS Machine Works is typically installed in complex network environments which are
separated by network firewalls, and access between levels is granted via ports, proxy
servers, or a combination of both.
The different components of AMS Machine Works can be spread over different network
levels according to your needs.
The diagrams presented below represent some of the most commonly used deployment
scenarios, but many other deployment scenarios are theoretically possible.

Figure 2-2: Single Server with Client Access from Plant LAN

20 AMS Machine Works v2.0

System Guide System Planning
July 2025

Figure 2-3: Single Server with Client Access from Business WAN

AMS Machine Works v2.0 21

System Planning System Guide
July 2025

Figure 2-4: Standard Architecture

22 AMS Machine Works v2.0

System Guide System Planning
July 2025

Figure 2-5: Enterprise Deployment

2.3.2 MongoDB Database Deployments

MongoDB Single Server Deployment — Internal
An internal MongoDB Database installation is the default configuration. To deploy the
database on the same server as the AMS Machine Works software you should proceed with
the Internal option when installing AMS Machine Works.
A MongoDB 8.0.4 2008R2Plus SSL (64 bit) database will be automatically installed and
configured.
Before you begin the installation process you should verify that a MongoDB database is
not currently installed on that machine. See: AMS Machine Works Server Installation
Note
Installation will fail if a version of the MongoDB database already exists on the machine.

AMS Machine Works v2.0 23

System Planning System Guide
July 2025

When the MongoDB is created the following actions are completed by the installer:
• A MongoDB 8.0.4 2008R2Plus SSL (64 bit) database is created and configured by
default.
• A MongoDB 6.0.20 2008R2Plus SSL (64 bit) database is created and configured for
Windows Server 2016 Standard or Datacenter installations.
• The MongoDB database is configured to use port 27018.
• A MongoDB database administrator user is created.
• A MongoDB database user is created for AMS Machine Works services to use for
communicating with the MongoDB database server.

MongoDB External Server Deployment

An external Mongo DB database server deployment requires that a MongoDB database
server has previously been fully configured, and network access is available. You must
choose the External option in the installer. External installation requires specific server
configuration and database management to be performed by your database
administrator.
When you choose to use an external MongoDB deployment these configuration and
management steps include:
• Creating a MongoDB database user on the external server machine with the
appropriate privileges for AMS Machine Works services to use for communicating with
the MongoDB database server. See: External MongoDB Server Installation
• Ensuring network connectivity between the AMS Machine Works server and MongoDB
database server.
• Providing a certificate file for the MongoDB database.
Note
Depending on the database configuration, the connection string entered during the
software installation process will have different parameters.

MongoDB Atlas Cloud Server Deployment

A MongoDB Atlas cloud server deployment requires that a MongoDB Atlas cloud database
server has previously been fully configured, and network access is available. You should
choose the External option in the installer. External installation requires specific server
configuration and database management to be performed by your database
administrator.
When you choose to use an external MongoDB Atlas cloud deployment these
configuration and management steps include:
• Creating a MongoDB database user on the external cloud server machine with the
appropriate privileges for AMS Machine Works services to use for communicating with
the MongoDB Atlas cloud database server. See: External MongoDB Server Installation
• Ensuring network connectivity between the AMS Machine Works server and the
MongoDB Atlas cloud server.
• Adding the IP address of the AMS Machine Works server to the Access List of the
MongoDB Atlas cloud server.

24 AMS Machine Works v2.0

System Guide System Planning
July 2025

Note
Depending on the database configuration, the connection string entered during the
software installation process will have different parameters.

2.3.3 Unsupported Deployment Scenarios

The following installation scenarios are not supported in AMS Machine Works v2.0:
• AMS Machine Works v2.0 cannot be installed by a Non-administrator. - The
installation always requires administrator privileges.
• AMS Machine Works v2.0 cannot be installed partially by one user, and the rest as
a different user. - The installation has to be completed by one user with administrator
privileges.
• AMS Machine Works v2.0 cannot be installed by procedures other than those
found in the AMS Machine Works v2.0 System Guide. - The Installation procedures
detailed in this System Guide are the only guaranteed method of installing AMS
Machine Works v2.0.
• AMS Machine Works v2.0 cannot be installed on a FIPS enabled machine, (FIPS
Compliance). - FIPS is not supported in AMS Machine Works v2.0.
• Upgrading a demo version of the software to a full version is not supported. - A
demo software version cannot be upgraded to a full AMS Machine Works v2.0 version.
A new installation is required.
• AMS Machine Works v2.0 cannot be installed with any version of AMS Machinery
Manager.
• AMS Machine Works v2.0 cannot be installed on the same server as AMS Optics. -
AMS Optics and AMS Machine Works have to be installed on separate servers.

2.4 System Requirements

AMS Machine Works has been tested to ensure performance for Small, Medium, Large,
and Extra-Large deployments within the scope of software and hardware combinations
outlined in this section.

AMS Machine Works Server

Note
Use system specifications marked "recommended" for deployments including AMS Asset
Monitor, Emerson Wireless Gateway, and other devices.

Operating system Windows Server 2022 Standard or Datacenter

Windows Server 2019 Standard or Datacenter
Windows Server 2016 Standard or Datacenter
CPU architecture 64-bit
Internet Information v8.5, v10 (supplied with OS)
Services (IIS)

AMS Machine Works v2.0 25

System Planning System Guide
July 2025

Browsers Google Chrome (latest version)

Microsoft Edge (latest version)
Processor1 Large and Extra-Large Systems — 3.2 GHz, 8-core processor, Intel
Xeon-scalable (Gold) or faster (recommended)
Small and Medium Systems — 2.4 GHz, 6-core processor, Intel
Xeon-scalable (Gold) or faster (minimum)
RAM1 Large and Extra-Large Systems — 64 GB
Medium Systems — 32 GB
Small Systems — 16 GB
Hard drive2 SSD hard drive (recommended)
SAS hard drive (10K RPM) (minimum)
Available disk space 1 TB (recommended)
500 GB (minimum)
100 GB (for wireless-only setup)
Screen resolution 4K UHD (3840 x 2160 pixels)
SXGA (1280 x 1024 pixels) (minimum)
Network 2 x 1 GB NIC (use 2 NICs to isolate Level 3 traffic from Level 2 traffic)
(recommended)
1 x 1 GB NIC (supported)

1 Refer to Processor and Memory Specifications for more details.

2 Refer to Storage Type Requirements by System Profile for more details.

AMS Machine Works Agent Server

Operating system 1 Windows Server 2022 Standard or Datacenter

Windows Server 2019 Standard or Datacenter
Windows Server 2016 Standard or Datacenter
CPU architecture 64-bit
Internet Information v8.5, v10 (supplied with OS)
Services (IIS)
Processor2 Two Agent Systems — 2.4 GHz, 6-core processor Intel Xeon-scalable
or faster
Single Agent Systems — 2.4 GHz, 4-core processor Intel Xeon-
scalable or faster
RAM2 Two Agent Systems — 32 GB
Single Agent Systems — 16 GB
Hard drive3 SSD hard drive (recommended)
SAS hard drive (10K RPM) (minimum)
Available disk space 10 GB (Emerson Wireless Gateway Agent)
10 GB (AMS Asset Monitor Agent)
(AMS 6500 ATG Agent)
(AMS 2140 Agent)

26 AMS Machine Works v2.0

System Guide System Planning
July 2025

Network 2 x 1 GB NIC (use 2 NICs to isolate Level 3 traffic from Level 2 traffic)
(recommended)
1 x 1 GB NIC (supported)

1 Windows 10, or Windows 11 is sufficient for a Portables Agent.

2 Refer to Processor and Memory Specifications for more details.
3 Refer to Storage Type Requirements by System Profile for more details.

AMS Machine Works Vibration Analyzer Client

Operating system Windows Server 2022 Standard or Datacenter

Windows Server 2019 Standard
Windows Server 2016 Standard
Windows 11
Windows 10 Pro
Windows 10 Enterprise
CPU architecture 64-bit
Internet Information v8.5, v10 (supplied with OS)
Services (IIS)
Processor 2.2 GHz, 4-core processor
Intel Xeon, Intel Core i5 6th Gen (i5 6400T) or better
RAM 16 GB (recommended)
8 GB (minimum)
Hard drive SAS hard drive (10K RPM)
Available disk space 100 GB
Screen resolution 4K UHD (3840 x 2160 pixels)
SXGA (1280 x 1024 pixels) (minimum)

External MongoDB Server

1

Operating system Windows Server 2022 Standard or Datacenter

Windows Server 2019 Standard or Datacenter
Windows Server 2016 Standard or Datacenter
CPU architecture 64-bit
Internet Information v8.5, v10 (supplied with OS)
Services (IIS)
MongoDB Server1 (Recommended) MongoDB 8.0.4 2008R2Plus SSL (64 bit)
MongoDB 6.0.20 2008R2Plus SSL (64 bit)2
Processor 2.4 GHz, 4-core processor, Intel Xeon-scalable or faster
RAM Large and Extra-Large Systems — 32 GB
Small and Medium Systems — 16 GB

1 External MongoDB Server requirements will scale upwards from these values as the processing requirements and storage capacity grows.

AMS Machine Works v2.0 27

System Planning System Guide
July 2025

Hard drive SSD hard drive, separated for OS and Data

Available disk space Refer to Storage Capacity Requirements by System Profile
Network 2 x 1 GB NIC

1 See: External MongoDB Server Installation

2 This version is provided to maintain compatibility with Windows Server 2016 systems.

Additional specifications

Ethernet One or more Ethernet Network Interface Card (NIC)

2 x 1 GB NIC (use 2 NICs to isolate Level 3 traffic from Level 2 traffic)
(recommended)
1 x 1 GB NIC (supported)
Internet connectivity A high-speed internet connection is recommended to download
installations, patches, and register software. (Alternatively, you can
download the software, patches, and registration file to the server
using a storage device.)
Supported virtualization • VMware 6 to VMware 8
• Hyper-V 2016, Hyper-V 2019, Hyper-V 2022

Supported antivirus • Symantec™ Endpoint Protection

software
• McAfee™ Endpoint
• Norton™ Security with Backup
• CrowdStrike

CAUTION
Computers with system components installed must have:
• their system clocks synchronized.
• their date/time in the same format.
Communication can be blocked if there are system clock discrepancies. (Many third-party
tools are available to synchronize system clocks.) System clocks do not need to be
synchronized for PCs with browser-only access.

Anti-virus exclusion list

To optimize performance, exclude the following applications, files, and folders in your
anti-virus software.
Note
Files with these extensions should be excluded in the locations listed in the table:
bak, bcp, c, cft, chk, cmtx, csv, dll, dri, edb, idx, jrs, ldf, log, mdf, ndf, obj, out, pdb, pol,
prc, pre, sch, sql, sqlaudit, sdb, trc, trg, trn, xel, xem, xml

28 AMS Machine Works v2.0

System Guide System Planning
July 2025

Component Item Path (default locations)

Applications C:\Windows\System32\inetsrv\w3wp.exe
(*.exe) C:\Windows\SysWOW64\inetsrv\w3wp.exe
Program Files C:\Program Files\Emerson\AMS Machine
Works\*
AMS Machine
Works Web C:\EMERSONMW\*
Services and C:\Program Files (x86)\Emerson\*
Service Layer
(embedded) C:\inetpub\wwwroot\EmersonCSI\*
Log files C:\inetpub\wwwroot\EmersonCSI\Logs\*
C:\inetpub\wwwroot\EmersonCSI\WebLogs\*
Cachecow C:\Windows\Temp\ARES\Cache\*
MongoDB Program Files C:\Program Files\MongoDB\Server\8.0\bin
\*1
AMS Asset Program Files C:\Program Files\Emerson\AMS Machine
Monitor Agent Works\AMA\*
Emerson Wireless Program Files C:\Program Files\Emerson\AMS Machine
Agent Works\EWA\*
AMS 6500 ATG Program Files C:\Program Files\Emerson\AMS Machine
Agent Works\ATGA\*
AMS 2140 Program Files C:\Program Files\Emerson\AMS Machine
Machinery Health Works\PEA\*
Analyzer Agent
Applications C:\Program Files\PostgreSQL\17\bin
(*.exe) \pg_ctl.exe
PostgreSQL
Program Files C:\Program Files\PostgreSQL\17\*
Applications
(*.exe)
Program Files C:\ProgramData\Emerson\AMSMachineWorks
OPC UA
\Data\DOPC\pki\server\trusted\certs\*
C:\ProgramData\Emerson\AMSMachineWorks
\Data\DOPC\pki\user\trusted\certs\*
RabbitMQ Applications C:\Program Files\Erlang OTP
\erts-15.2.2\bin\erlsrv.exe
Program Files C:\Program Files\RabbitMQ Server
\rabbitmq_server-4.0.6\*
Windows Windows C:\Windows\SoftwareDistribution
exclusion for \DataStore\*
Windows Update
C:\Windows\System32\GroupPolicy\User\*
C:\Windows\System32\GroupPolicy\Machine
\*

AMS Machine Works v2.0 29

System Planning System Guide
July 2025

1 If your installation uses MongoDB 6.0.20 2008R2Plus SSL (64 bit) to maintain compatibility with
Windows Server 2016 systems, the filepath will be: C:\Program Files\MongoDB
\Server\6.0\bin\*

30 AMS Machine Works v2.0

System Guide System Planning
July 2025

2.4.1 System Scalability

Table 2-6: AMS Machine Works System Scalability
Components AMS Machine Works

Server Specifications

Assets 2000 machine trains with network devices

Concurrent users 15

Concurrent VibApp users 10

Devices1

600 devices maximum per system connected across 50 Emerson Wireless

AMS 9420
Gateways
Wireless Vibration Transmitter
600 devices maximum per AMS Machine Works Wireless Agent

400 AMS Asset Monitors maximum per system and per AMS Asset
AMS Asset Monitor
Monitor Agent

5000 devices maximum per system connected across 120 Emerson

AMS Wireless Vibration Monitor Wireless Gateways
One AMS Machine Works Wireless Agent can be installed per server.

AMS 6500 ATG 100 Single Rack Systems2

AMS 2140 Machinery Health Maximum number of concurrent users: 15

Analyzer Maximum number of simultaneous data transfers: 2

Devices per Emerson Wireless Gateway

• 1420 — max. 50 devices

• 1410B — max. 50 devices

AMS 9420 • 1410S — max. 50 devices

Wireless Vibration Transmitter • Theoretical maximum in ideal conditions: 100 devices per 1410S
(Dual Antenna)3
With 50 devices connected through Antenna One, plus 50 devices
connected through Antenna Two.

• 1420 — max. 50 devices

• 1410B — max. 50 devices
• 1410S — max. 200 devices
AMS Wireless Vibration Monitor
• Theoretical maximum in ideal conditions: 400 devices per 1410S
(Dual Antenna)3
With 200 devices connected through Antenna One, plus 200 devices
connected through Antenna Two.

OPC UA

Number of Assets 2000 Assets

Number of Total Monitored Tags 20000 Monitored Tags

Number of Clients 2 Clients

1 Refer to Update Rates.

2 1. 11 Universal Measurement Cards

2. 22 Channels

AMS Machine Works v2.0 31

System Planning System Guide
July 2025

3 Based on testing with 400 devices connected to a Dual Antenna 1410S Emerson Wireless
Gateway in the following configuration:
1. Antenna One: AMS Wireless Vibration Monitor — 155 units, AMS 9420 — 45 units
2. Antenna Two: AMS Wireless Vibration Monitor — 189 units, AMS 9420 — 11 units
Collection Schedules as tested:
1. AMS Wireless Vibration Monitor: Scalars 144 times/day, Spectra 4 times/day, Thumbnails 4
times/day, Waveforms 1/day.
2. AMS 9420: Scalars 3 times/day, Energy Bands 3 times/day, Burst Variables 144 times/day,
Waveforms & Spectra 1 time/day.

Processor and Memory Specifications

Depending on your system profile and scale, your processor and memory needs will
change for each machine. Refer to the tables for resources, after selecting the number of
servers described in Number of Agent Servers per System Profile. If the system will include
an AMS Asset Monitor Agent Server or other device types, then the specifications should
reflect the higher value of Table 2-7, Table 2-8, and Table 2-9
Table 2-7: Processor specifications for system profiles with an Emerson Wireless
Gateway Agent Server
System AMS Machine Works Server Emerson Wireless Gateway Agent
Profile Server
Processor Cores RAM Processors Cores RAM
(minimum) (minimum)
Small (S) 2.4 GHz 6 16 GB 2.4 GHz 4 16 GB
Medium 2.4 GHz 6 32 GB 2.4 GHz 4 16 GB
(M)
Large (L) 3.2 GHz 8 32 GB 2.4 GHz 41 16 GB
62
Extra Large 3.2 GHz 8 32 GB 2.4 GHz 41 16 GB
(XL) 64 GB2 62

1 Minimum
2 Recommended

Table 2-8: Processor specifications for system profiles with an AMS Asset Monitor
Agent Server
System AMS Machine Works Server AMS Asset Monitor Agent Server
Profile
Processor Cores RAM Processors Core RAM
(minimum) (minimum)
Small (S) 2.4 GHz 6 16 GB 2.4 GHz 4 16 GB
Medium 3.2 GHz 8 32 GB 2.4 GHz 4 16 GB
(M)
Large (L) 3.2 GHz 8 32 GB 2.4 GHz 4 16 GB

32 AMS Machine Works v2.0

System Guide System Planning
July 2025

Table 2-9: Processor specifications for system profiles with an AMS 6500 ATG Agent
Server
System AMS Machine Works Server AMS 6500 ATG Agent Server
Profile
Processor Cores RAM Processors Cores RAM
(minimum) (minimum)
Small (S) 2.4 GHz 6 16 GB 2.4 GHz 4 16 GB
Medium 2.4 GHz 6 32 GB 2.4 GHz 4 16 GB
(M)
Large (L) 3.2 GHz 8 32 GB 2.4 GHz 41 16 GB
62
Extra Large 3.2 GHz 8 32 GB 2.4 GHz 413 16 GB
(XL) 64 GB2 62

1 Minimum
2 Recommended
3 Minimum

AMS Machine Works v2.0 33

System Planning System Guide
July 2025

Number of Agent Servers per System Profile

When planning your system, consider the number of devices you will add over time, and
set up the appropriate number of AMS Machine Works Agent servers. Also, consider the
number of measurements each device will take to plan how many vibration tags you need
for your system. A vibration tag is a data point that collects spectral and waveform data.
All other data is not considered a tag and does not count against the total number of tags
required for the system. The maximum number of vibration tags is 20 000. The tables in
this section are based on Update Rates.
Note
Consult your Emerson representative about device limits and Agent server requirements
for a system with a combination of monitoring devices.

Note
The tables in this section assume a distributed deployment, which has 2 servers, one for
AMS Machine Works, and one for an External MongoDB server. See: MongoDB Database
Deployments

AMS Asset Monitor

Table 2-10: AMS Asset Monitor Agent Servers required per amount of AMS Asset Monitors
System Profile AMS Asset Monitors Vibration tags (maximum) AMS Asset Monitor Agent
Servers
Small (S) 0-80 960 1
Medium (M) 81-160 1920 1
Large (L) 161-300 3600 1
Extra Large (XL) 301-400 4800 1

Note
• One AMS Asset Monitor Agent Server can support up to 400 AMS Asset Monitors.
• One AMS Asset Monitor has a maximum of 12 vibration CHARMs.
• One vibration CHARM constitutes one vibration tag, including installed spare CHARMs.
• The maximum number of AMS Asset Monitors supported in AMS Machine Works is
400.

Emerson Wireless Gateway

Table 2-11: Number of AMS Wireless Vibration Monitors and Vibration Tag Consumption by System
Profile
System Profile AMS Wireless Vibration Vibration Tag Emerson Wireless
Monitors Consumption Gateway Agent Servers
Small (S) 1-600 3-1800 1
Medium (M) 601-1200 1803-3600 1
Large (L) 1201-2400 3603-7200 1

34 AMS Machine Works v2.0

System Guide System Planning
July 2025

Table 2-11: Number of AMS Wireless Vibration Monitors and Vibration Tag Consumption by System
Profile (continued)
System Profile AMS Wireless Vibration Vibration Tag Emerson Wireless
Monitors Consumption Gateway Agent Servers
Extra Large (XL) 2401-5000 7203-15000 11

1 More Emerson Wireless Gateway Agent Servers might be required to meet network topology requirements such as
devices being located in separate locations with their own local networks.

Note
• One AMS Wireless Vibration Monitor uses three vibration tags, one per axis.
• The maximum number of AMS Wireless Vibration Monitors supported in AMS Machine
Works is 5000.

Table 2-12: Emerson Wireless Gateway Agent Servers required per amount of AMS 9420 Units
System Profile AMS 9420s Vibration tags (maximum) Emerson Wireless
Gateway Agent Servers
Small (S) 0-600 1200 1

Note
• One Emerson Wireless Gateway Agent server can accommodate connections to up to
600 AMS 9420 units.
• One AMS 9420 constitutes a maximum of two vibration tags, one per sensor.
• The maximum number of AMS 9420s supported in AMS Machine Works is 600.

AMS 6500 ATG

Table 2-13: AMS 6500 ATG Agent Servers required per System Profile
System Profile AMS 6500 ATG (single Vibration tags AMS 6500 ATG Agent
rack)1 (maximum)2 Servers3
Small (S) 1-5 22-110 1
Medium (M) 6-20 132-440 1
Large (L) 21-50 462-1100 1
Extra Large (XL) 51-100 1122-2200 1

1 1. 11 Universal Measurement Cards

2. 22 Channels
2 Assuming:
1. 11 Universal Measurement Cards
2. 22 Channels
3 More AMS 6500 ATG Agent Servers might be required to meet network topology requirements such as devices being
located in separate locations with their own local networks.

AMS Machine Works v2.0 35

System Planning System Guide
July 2025

AMS 2140
AMS Machine Works does not have a technical limit for the number of AMS 2140 Agent
servers, but our recommend maximum is 10. The number of AMS 2140 Agents is set by
the network topology requirements.

Storage Type Requirements by System Profile

The type of hard disk, either magnetic or solid state drive is recommended based on your
system profile. While the amount of data you can store is limited by disk size, the write
speed is a very important factor for system performance. All systems are recommended to
use a solid-state drive with mixed use and write optimized settings for improved
performance.
Table 2-14: Storage Requirements for Emerson Wireless Gateway Agent Servers with
AMS 9420 and AMS Wireless Vibration Monitor
System Profile Magnetic Drive Solid-State Drive
SAS (10K RPM) Mixed Use / Write Optimized
Small (S) Acceptable Recommended
Medium (M) Acceptable Recommended
Large (L) Not Recommended Recommended
Extra Large (XL) Not Recommended Recommended

Table 2-15: Storage Requirements for AMS Asset Monitor

System Profile Magnetic Drive Solid State Drive
SAS (10K RPM) Mixed Use / Write Optimized
Small (S) Acceptable Recommended
Medium (M) Not Recommended Recommended
Large (L) Not Recommended Recommended
Extra Large (XL) Not Recommended Recommended

Table 2-16: Storage Requirements for AMS 6500 ATG

System Profile Magnetic Drive Solid State Drive
SAS (10K RPM) Mixed Use / Write Optimized
Small (S) Acceptable Recommended
Medium (M) Not Recommended Recommended
Large (L) Not Recommended Recommended
Extra Large (XL) Not Recommended Recommended

Table 2-17: Storage Requirements for AMS 2140

System Profile Magnetic Drive Solid State Drive
SAS (10K RPM) Mixed Use / Write Optimized
Small (S) Acceptable Recommended

36 AMS Machine Works v2.0

System Guide System Planning
July 2025

Table 2-17: Storage Requirements for AMS 2140 (continued)

System Profile Magnetic Drive Solid State Drive
SAS (10K RPM) Mixed Use / Write Optimized
Medium (M) Not Recommended Recommended
Large (L) Not Recommended Recommended
Extra Large (XL) Not Recommended Recommended

Storage Capacity Requirements by System Profile

There are two types of databases used with AMS Machine Works:
1. Configuration settings, which are stored in a PostgreSQL database.
2. Measurement data storage, which is stored in a MongoDB database.
The measurement data storage grows over time, and grows faster as the update rates of
the measurement devices increase. The storage requirements given below are based on
the use of the recommended update rates for each type of measurement device.
See: Update Rates
Table 2-18: Long term storage capacity requirements for Wireless systems with AMS 9420 and AMS
Wireless Vibration Monitor
System Profile AMS 9420 AMS Wireless Data Storage
Vibration
Monitor 1-3 Years 3-5 Years 5-10 Years

Small (S) 0-500 0-600 500 GB 850 GB 1.6 TB

Medium (M) 501-600 601-1200 1.0 TB 1.7 TB 3.5 TB
Large (L) - 1201-1800 2.0 TB 3.4 TB 7.0 TB
Extra Large (XL) - 1801-4000 4.0 TB 6.8 TB 14.0 TB

Table 2-19: Long term storage capacity requirements for AMS Asset Monitor
System Profile AMS Asset Monitor Data Storage
1-3 Years 3-5 Years 5-10 Years
Small (S) <81 1.0 TB 2.5 TB 5.0 TB
Medium (M) 81-160 2.5 TB 4.0 TB 7.5 TB
Large (L) 161-300 4.0 TB 6.4 TB 12.0 TB
Extra Large (XL) 301-400 5.0 TB 8.0 TB 15.0 TB

Table 2-20: Long term storage capacity requirements for AMS 6500 ATG
System Profile AMS 6500 ATG1 Data Storage
1-3 Years 3-5 Years 5-10 Years
Small (S) 1-5 0.5 - 1.5 TB 1.5 - 2.5 TB 2.5 - 5.0 TB
Medium (M) 6-20 2.0 - 6.0 TB 6.0 - 10 TB 10 - 20 TB

AMS Machine Works v2.0 37

System Planning System Guide
July 2025

Table 2-20: Long term storage capacity requirements for AMS 6500 ATG (continued)
System Profile AMS 6500 ATG1 Data Storage
1-3 Years 3-5 Years 5-10 Years
Large (L) 21-50 2.5 - 7.5 TB 7.5 - 12.5 TB 12.5 - 25 TB
Extra Large (XL) 51-100 5.0 - 15.0 TB 15.0 - 25 TB 25.0 - 50.0 TB

1 Based on the recommended update rates.

Table 2-21: Long term storage capacity requirements for AMS 2140
System Profile AMS 2140 Data Storage
1-3 Years 3-5 Years 5-10 Years
Small (S) 1.0 TB 2.5 TB 5.0 TB
Medium (M) 2.5 TB 4.0 TB 7.5 TB
Large (L) 4.0 TB 6.4 TB 12.0 TB
Extra Large (XL) 5.0 TB 8.0 TB 15.0 TB

2.4.2 Update Rates

Every type of measurement device produces more data for storage as the Update Rate
increases. The recommended storage requirements for each type of device according to
the Update Rate are given in the following sections.

AMS Asset Monitor Update Rates

Data update rates are configured in each AMS Asset Monitor individually with
Table 2-22: AMS Asset Monitor Data Storage and Update Rates
Update Rates
Fastest1 Slowest Default Recommended
Scalars 1 min 1 hour 30 min 15 min
Data
Type Waveform / 1 hour 1 month Disabled 1 day
Spectrum

1 Using the fastest rate should only be used with a single AMS Asset Monitor at a time.

38 AMS Machine Works v2.0

System Guide System Planning
July 2025

AMS Wireless Vibration Monitor Update Rates

These are the AMS Wireless Vibration Monitor scalability limitations:
• Overall AMS Machine Works System Maximum Device Limit: 5000 devices
• Maximum number of devices supported at the fastest rates: 200 devices

Table 2-23: AMS Wireless Vibration Monitor Update Rates

Update Rates1
Fastest2 Slowest Default3 Recommended1
Scalars4 1 min5 22 hours 1 hour 1 hour

Data Thumbnails 6 hours 31 days Disabled 6 hours

Type Spectra 6 hours 31 days Disabled 1 day
Waveforms 1 day 31 days Disabled 7 days

1 Applies to all the applicable measurements across all channels per device. For example, for
spectra, it will be all available spectra (X, Y, Z) per channel.
2 Use only with a maximum of 200 devices, and never more than 10 devices from the same
gateway.
3 The rate is set when the device is discovered, but the values listed here are the factory defaults for
this type of device. These can be modified with the AMS Device Manager.
4 With AMS Machine Works, setting an update rate for scalars of over an hour is only possible by
using the AMS Device Manager to modify the device directly. (Slowest: 22 hours)
5 Not recommended. Depending on your network reliability and speed, there may be some gaps in
data collection. Only use this setting temporarily, and only when absolutely required.

AMS 9420 Update Rates

These are the AMS 9420 data performance and scalability limitations:
• Overall AMS Machine Works System Maximum Device Limit: 600 devices
• Maximum number of devices supported at the fastest rates: 60 devices
Table 2-24: AMS 9420 Update Rates
Update Rates1
Fastest2 Slowest Default Recommended1
Burst 1 min3 1 day 1 hour 1 hour
Variables
Scalars4 8 hours 31 days Disabled Disabled5
Data Energy 8 hours 31 days Disabled 8 hours
Type Bands
Waveforms 1 day 31 days Disabled 7 days
&
Spectra

1 Applies to all the applicable measurements across all channels per device.

AMS Machine Works v2.0 39

System Planning System Guide
July 2025

2 Use only with a maximum of 60 devices, and never more than 10 devices from the same
gateway.
3 Not recommended. Depending on your network reliability and speed, there may be some gaps in
data collection. Only use this setting temporarily, and only when absolutely required.
4 Scalars are published at rate which is stored in the device. This rate can be set by the AMS
Machine Works software.
5 In most cases Scalar collection contains the same parameters as Burst Variables collection and
can be kept disabled. However, some older firmware versions of an AMS 9420 may not publish
all scalar parameters. In that case, the remaining parameters can be collected using Scalar
collection with an appropriate schedule.

AMS 6500 ATG Update Rates

Collection tasks for AMS 6500 ATG units are configured in AMS Machine Studio.
Table 2-25: AMS 6500 ATG Update Rates
Update Rates
Data Type
Shortest Default Longest Recommended
Primary Scalar 1 sec (disabled) 1 month 60 sec
Secondary Scalar 15 sec (disabled) 1 month 600 sec
Diagnostics 600 sec 900 sec 168 hours 600 sec
Transient Waveform1 60 min 24 hours 1 month 8 hours

1 Transient Waveforms can be collected on demand, or collection can be triggered by a store on

alert setting. These factors can increase the amount of data collected.

2.4.3 Compatibility
AMS Machine Works supports interactions between a wide range of devices, agents,
Emerson software and hardware, and 3rd party software.

Device Compatibility
This version of AMS Machine Works supports the following types of devices with specific
versions of firmware.

Emerson Wireless Gateway

• Supported model numbers:
— Rosemount 1420 Smart Wireless Gateway hardware version 4.0 with firmware
versions 4.x.xx, or later, are supported.
— Rosemount 1410 Smart Wireless Gateway hardware version 4.0 with firmware
versions 4.6.64, or later, are supported.

AMS Wireless Vibration Monitor

• Supported model numbers:
— AMS Machine Works supports the AMS Wireless Vibration Monitor Hardware Rev 3.
— AMS Machine Works supports the AMS Wireless Vibration Monitor Hardware Rev 1.

40 AMS Machine Works v2.0

System Guide System Planning
July 2025

AMS 9420 Wireless Vibration Transmitter

The following versions of the AMS 9420 are supported:
1. AMS 9420 Wireless Vibration Transmitter — Device Revision 4
Note
You can view the revision information from a Field Communicator or from AMS Device
Manager. See the AMS 9420 Reference Manual for more information.

AMS Asset Monitor

• Supported firmware version numbers:
— AMS Machine Works supports AMS Asset Monitor v2.1.x devices.
— AMS Machine Works supports AMS Asset Monitor v3.0.8 to v3.0.x devices.
— AMS Machine Works supports AMS Asset Monitor v3.1 to v3.1.x devices.
Note
If a device was added to AMS Machine Works with unsupported firmware, the
recommended best practice is to remove the device, upgrade the firmware, and then add
the device to AMS Machine Works again.

AMS 6500 ATG

• Supported ATG 6500 Cards:
— A6500-CC v3.3.0
— A6500-CP v1.0.0
— A6500-UM v3.5.0
— A6500-TP v3.2.0
— A6500-RC: not supported
AMS Machine Works supports AMS Machine Studio v4.1.
Note
AMS Machine Studio v4.1.0 is required to configure the A6500-CP v1.0.0 card.

AMS 2140 Machinery Health Analyzer

• Supported firmware versions:
— AMS 2140 with firmware version 1.3.13.0, or later.
Note
To use Stand Alone Data Transfer (SADT) with your AMS 2140 Machinery Health Analyzer
refer to knowledge base article: NK-2200-0246

OPC UA Software Compatibility

All OPC UA compliant clients are supported, and the following software versions have
been tested.

AMS Machine Works v2.0 41

System Planning System Guide
July 2025

Table 2-26: Tested OPC UA Software

Item Tested versions
OPC UA Expert v1.4.4 or latest
OPC UA Clients Integration Objects
Prosys

Emerson Software Co-Deployment

The Emerson Software Co-Deployment table lists the supported combinations of some
Emerson products. Even when is it theoretically possible, Emerson does not recommend
deploying AMS Machine Works on the same computer with these applications.
Co-deployment means having both pieces of software installed on the same network.
Table 2-27: Emerson Software Co-Deployment
Legend:✔ Supported - X Not Supported - N/A Not Applicable

AMS AMS Optics AMS AMS Device DeltaV Ovation Plantweb Insight
Machine Machinery Manager
Works Manager
Application
Component
s
AMS ✔ X X X ✔ N/A
Machine Both can not Only on
Works Server be installed Approved
on the same Architecture.
server.
Emerson ✔ X X ✔ N/A N/A
Wireless Both can not Can be
Gateway be installed installed on a
Agent on the same DeltaV
server. Application
Station.
AMS Asset ✔ X X X N/A N/A
Monitor Both can not
Agent be installed
on the same
server.
AMS 6500 ✔ X X X N/A N/A
ATG Agent Both can not
be installed
on the same
server.
AMS ✔ X X X N/A N/A
Portables Both can not
Agent be installed
on the same
server.

42 AMS Machine Works v2.0

System Guide System Planning
July 2025

2.5 AMS Machine Works Security

Emerson recommends working with qualified IT personnel to ensure that your installation
complies with both the network security policy for your plant and industry best practices.
For more detailed information about cyber security refer to the AMS Product Security
Documentation (AMS-SEC-PSG-001).
Verify your:
1. Network Port Availability
After verifying that all of the security and communication requirements have been met
continue your installation.

2.5.1 Network Port Availability

• During default installation, IIS is automatically installed and configured to use the
Default Site. (Ports: 80 and 443)
• Clients and servers utilizing the Vibration Analyzer application must ensure that Port
8888 is available, as it is specifically designated for authentication.
• If ports: 80 and 443 are already in use by a previous installation of IIS you can
either:
1. If the Default Site is unused, you can delete the Default Site.
2. Configure the Default Site to use other ports.
See: Installation Troubleshooting
• During default installation of a Portables Agent Server, port: 10077 is set for
communication with AMS 2140 Machinery Health Analyzer units. You can choose
another port if port: 10077 is in use.
• You can also use non-default ports if your existing system and network requires it. Your
network administrator must configure firewall rules to allow traffic to pass through the
non-default ports. It is best practice to use port numbers above 1024 and to use non-
restricted ports.

AMS Machine Works v2.0 43

System Planning System Guide
July 2025

44 AMS Machine Works v2.0

System Guide Installation Procedures
July 2025

3 Installation Procedures
AMS Machine Works is a modular system which can be installed on a single server, or
distributed across various network topologies. See: Typical Deployment Scenarios
For more information on unsupported scenarios refer to Unsupported Deployment
Scenarios. If a scenario you are looking for is not listed in that section, work with your
Emerson representative to review your preferred deployment scenario and determine if it
is possible.
Note
There is a migration path from AMS Machine Works v1.8 to AMS Machine Works v2.0. See:
Update from v1.8 to v2.0

The installation process has three phases for a new installation:

1. Pre-Installation Steps — These are the steps that you must follow to properly
prepare for installing AMS Machine Works.
2. Install Servers — These steps will enable you to configure any of the Typical
Deployment Scenarios.
a. Install an AMS Machine Works Server — AMS Machine Works Server
Installation
b. (Optional) Install an External Agent Server — Agent Server Installation
c. (Optional) Install an External MongoDB Server — External MongoDB Server
Installation

3. Post-Installation Steps — These are the steps that you must follow to properly start,
register, and initially configure your AMS Machine Works server.

3.1 Pre-Installation Steps

The pre-installation steps should be performed after you have finished your System
Planning, and before you perform any installation steps.

Prerequisites
Design and plan your system. See: Planning Steps.

Procedure
1. (Optional) If you are using an External MongoDB Server, ensure that you have
administrator privileges on that machine.
a) Perform your External MongoDB Server Installation BEFORE installing the
AMS Machine Works Server.
b) Import the public key certificate from the External MongoDB Server, and
install it.

2. (Optional) If you are using External Agent Servers, ensure that you have
administrator privileges on all the machines.

AMS Machine Works v2.0 45

Installation Procedures System Guide
July 2025

Note
Perform your Agent Server Installation AFTER installing the AMS Machine Works
Server.

3. Server Installation Pre-Check

4. Stop Automatic Updates
5. Locate the Installer

3.1.1 Server Installation Pre-Check

Prior to beginning the installation process, you must ensure that the server is properly
prepared for an AMS Machine Works installation.

Procedure
1. Server names:
The server names for the AMS Machine Works Server and any associated AMS
Machine Works Agent Server(s) must meet the following criteria:
• It must be at least 1 character, but not more than 14.
• It cannot contain any of the following characters:
— backslash \
— slash mark /
— colon :
— asterisk *
— question mark ?
— quotation mark "
— less than sign <
— greater than sign >
— vertical bar |
— underscores _
— comma ,
— tilde ∼
— semicolon ;
— exclamation mark !
— at sign @
— number sign #
— dollar sign $
— percent %
— caret ^
— ampersand &

46 AMS Machine Works v2.0

System Guide Installation Procedures
July 2025

— apostrophe '
— period .
— parentheses ( )
— braces { }
— white space ( blank )

2. Check the Properties for all the drives you intend to install any element of AMS
Machine Works on. These drives cannot have the Compress this drive to save
space option checked.

CAUTION
AMS Machine Works does not support installations on compressed drives.

3. Check Server Time:

Make sure that the time and time-zones are correct before proceeding.

CAUTION
If you have multiple servers, make sure all the times and time-zones match.

.
4. Administrator Account:
Make sure that the user account being used for installation is an Administrator on
every server associated with this AMS Machine Works installation.
a. AMS Machine Works Server
b. MongoDB Server — (Optional) Only necessary if you are using an External
MongoDB Server.
c. AMS Machine Works Agent Server(s) — (Optional) Only necessary if you are
using External Agent Server(s).
To check the user, select Computer Management → Local Users and Groups →
Groups → Administrators.
Verify that the user performing this installation is a member of this group.
Note
Alternatively, the user can be added to a Domain Group which is part of the
Administrators Group. If you are unsure, check with your Network Administrator.

AMS Machine Works v2.0 47

Installation Procedures System Guide
July 2025

Figure 3-1: Administrator Properties

5. Group Policies:
a) Open the Local Group Policy Editor and select: Local Computer Policy →
Computer Configuration → Windows Settings → Security Settings →
Local Policies → User Rights Assignment
b) Ensure that the user has the following rights:
1. Backup files and directories
2. Debug programs
3. Manage auditing and security log

Figure 3-2: Local Group Policy Editor

6. Hardware Details:
a) Open System Information → System Summary:
b) Check Processor, and confirm that the number of Processors and Cores
meets the minimum requirements for your installation size.
Note
If you have multiple processors the cores will be added together.

c) Check Installed Physical Memory (RAM), and confirm that the amount
meets the minimum requirements for your installation size.

48 AMS Machine Works v2.0

System Guide Installation Procedures
July 2025

Figure 3-3: System Summary

7. Choose a Default Web Browser. Select System Settings → Default apps → Web
browser
• Google Chrome
• Microsoft Edge

Figure 3-4: Choose a Default Web Browser

CAUTION
Only Google Chrome and Microsoft Edge are supported. Use of other browsers
may have unknown effects.

3.1.2 Stop Automatic Updates

The installation process for AMS Machine Works proceeds in stages and requires some
reboots. All automatic updates for other software, including Windows Update, should be
stopped or disabled for the duration of the installation process to ensure the stability and
security of your system.
Your IT department might not permit you to stop or disable Windows Update or other
automatic update services on your server. If it is not possible to stop or disable automatic

AMS Machine Works v2.0 49

Installation Procedures System Guide
July 2025

updates, Emmerson recommends that you first check for updates and apply them before
installing AMS Machine Works.

Prerequisites
Determine if your IT department allows automatic updates to be temporarily disabled.

Procedure
1. Make a list of the update services you plan to stop.
2. Use the update services prior to stopping them.
3. Verify that your system is stable.
4. Stop every update service that you can.
Make a Stopped Update Services List of the update services that you were able to
pause. You will use this list after the installation is complete in the post-installation
step Restart Automatic Updates.

Postrequisites
Proceed to Locate the Installer.

3.1.3 Locate the Installer

To avoid errors and unnecessary updates you must ensure that you have the most recent
version of the AMS Machine Works installation package.

Procedure
1. Log into the server you want to install AMS Machine Works on with an
Administrator account.
2. Find your installation package from local media or online:
• Locate the installer on some local device.
• Locate the correct version in your Guardian account at: https://
guardian.emerson.com/

CAUTION
You must keep the installer package that you used to install AMS Machine Works,
because you must use this exact version of the installer to Uninstall or Modify your
installation.

3. Before extracting, right-click on the file and select Properties. Check the Unblock
checkbox, and click Apply.

Figure 3-5: File Properties

4. Extract the AMS Machine Works installation files to a top level folder.

50 AMS Machine Works v2.0

System Guide Installation Procedures
July 2025

CAUTION
Long file path names can result in errors during installation. (Max length: 256
characters)

Need help?
A Blocked file will usually result in an error.

Figure 3-6: Error pop-up

To recover from this error, delete the extracted folder, Unblock the file, and re-
extract the installation files as shown in the previous step.

3.2 AMS Machine Works Server Installation

This is a general overview of the AMS Machine Works Server installation process.

Procedure
1. (Optional) If your system will use an External MongoDB Server you must perform
this installation first. External MongoDB Server Installation
2. Launch Installer
3. Software License Agreement
4. Choose AMS Machine Works Server Installation
5. Enter a Server Name
6. Choose Internal vs. External MongoDB Server
7. Provide Passwords or Connection String
8. Choose the Installation Drive
9. Select which Agents to Install
10. Confirm Installation
11. Complete the Reboot Cycle

3.2.1 Launch Installer

The Installer_2.0.XXX package must be properly decompressed, unblocked, and located
before you run it.

Prerequisites
Complete all the Pre-Installation Steps.

AMS Machine Works v2.0 51

Installation Procedures System Guide
July 2025

CAUTION
Run setup.exe from a folder close to the root of your file system. Long path names can
result in the installer failing.

CAUTION
It is strongly recommended that you pause Windows Automatic Updates during the
installation process. Failure to do so may lead to inconsistent results. See: Stop Automatic
Updates

Procedure
1. Right-click on setup.exe, and click Run as administrator.
a) If the User Access Control window appears, click Yes to allow setup.exe to
install.

Figure 3-7: User Access Control

b) AMS Machine Works uses port 80 and port 443 by default. If these ports are
in use you must configure different ports. See: Network Port Availability

Figure 3-8: Warnings: AMS Machine Works Web Services Ports in Use

2. Click Next to continue.

52 AMS Machine Works v2.0

System Guide Installation Procedures
July 2025

Figure 3-9: AMS Machine Works v2.0 – InstallShield Wizard

3. Continue to the next step: Software License Agreement

3.2.2 Software License Agreement

Prerequisites
You must complete the previous step, Launch Installer, before you can begin the
installation process.

Procedure
1. Read the Software License Agreement.
2. (Optional) Click Print to print a copy of the Software License Agreement for your
records.
3. Click the checkbox next to I accept the terms of the license agreement.

AMS Machine Works v2.0 53

Installation Procedures System Guide
July 2025

Figure 3-10: InstallShield Wizard - License Agreement

4. Click Next to continue.

Postrequisites
Depending on which scenario you are using, the next step to this is either:
1. (Scenario One) When performing an AMS Machine Works Server installation:
Choose AMS Machine Works Server Installation
2. (Scenario Two) When performing an Agent Server installation: Choose Agent Server
Installation

3.2.3 Choose AMS Machine Works Server Installation

The AMS Machine Works Server installation process produces a fully functional system.
The system can be located on one server, or distributed across multiple servers.

Prerequisites
You must complete the previous step: Software License Agreement

Procedure
1. Select AMS Machine Works Server for a new installation, then click Next to
continue.

54 AMS Machine Works v2.0

System Guide Installation Procedures
July 2025

Figure 3-11: InstallShield Wizard - Select which type of server to install.

2. Click Next to continue to the next step: Enter a Server Name

3.2.4 Enter a Server Name

The Server Name is how other elements of the system can refer to the main AMS Machine
Works Server.
There are three different formats for giving the Server Name:
1. The local Computer Name given in the computer's settings.
2. The IP address of the computer.
3. The fully qualified domain name, FQDN.
Note
If you have a FQDN (Fully Qualified Domain Name) network, you must enter the Full
computer name for the AMS Machine Works server here. On the AMS Machine
Works server select This PC → Properties to find this information.

Prerequisites
You must complete the previous step: Choose AMS Machine Works Server Installation

Procedure
1. (Default: Automatically filled with your computer's name.) Enter a name for your
AMS Machine Works Server.

AMS Machine Works v2.0 55

Installation Procedures System Guide
July 2025

Figure 3-12: InstallShield Wizard - Name the Server

2. Click Next to continue to the next step: Choose Internal vs. External MongoDB
Server

3.2.5 Choose Internal vs. External MongoDB Server

In this step you must choose which type of MongoDB installation to use:
1. Internal Scenario Internal MongoDB — (Default) The MongoDB database will be
installed on the same server as AMS Machine Works.
2. External Scenario External MongoDB — The MongoDB database must be pre-
installed on a remote server, or in the cloud.

Prerequisites

Attention
When you choose an External MongoDB installation, the External MongoDB Server
Installation must be complete before proceeding to the next step.

Procedure
1. (Internal Scenario) (Default) Select Internal to proceed with the default
configuration and install the MongoDB on the same server as AMS Machine Works.

56 AMS Machine Works v2.0

System Guide Installation Procedures
July 2025

Figure 3-13: InstallShield Wizard - Select Internal

2. (External Scenario) Select External to proceed with connecting to an External

MongoDB on a remote server, or in the cloud.

Figure 3-14: InstallShield Wizard - Select External

3. Click Next to proceed to the next step, Provide Passwords or Connection String.

Postrequisites

Attention
When you choose an External MongoDB installation, the External MongoDB Server
Installation must be complete before proceeding to the next step.

AMS Machine Works v2.0 57

Installation Procedures System Guide
July 2025

3.2.6 Provide Passwords or Connection String

In the previous step, Choose Internal vs. External MongoDB Server, you choose between
two deployment scenarios; using an Internal MongoDB Server, or using an External
MongoDB Server.
Depending on which scenario you chose, you must perform different steps in this task:
1. Internal MongoDB Server — (Internal MongoDB Scenario) Enter the MongoDB
passwords.
2. External MongoDB Server — (External MongoDB Scenario) Enter and test the
MongoDB connection string.
Note
To use an External MongoDB Server, it must be installed before this step can be
completed. See: External MongoDB Server Installation

Prerequisites
You must complete the previous step, Choose Internal vs. External MongoDB Server,
before proceeding.

Procedure
1. (Internal MongoDB Scenario) Enter the passwords you need for the two Internal
MongoDB accounts, admin, and mwservice.

CAUTION
All MongoDB passwords:
a. Must meet the Local Security Policy of the server.
b. Should not contain the following special characters: %, /, :, @, <blank space>

a) Enter a MongoDB password for the admin user twice, and then click Next to
continue.

58 AMS Machine Works v2.0

System Guide Installation Procedures
July 2025

Figure 3-15: InstallShield Wizard - Enter the MongoDB admin password.

b) Enter a MongoDB password for the mwservice user twice, and then click
Next to continue.

Figure 3-16: InstallShield Wizard - Enter MongoDB mwservice password.

2. (External MongoDB Scenario) Enter the External MongoDB connection string. See:
External MongoDB Server Installation
a) Enter the External MongoDB connection string.

AMS Machine Works v2.0 59

Installation Procedures System Guide
July 2025

Figure 3-17: InstallShield Wizard - Enter the External MongoDB

connection string.

Note
The recommended connection string to the External MongoDB is through
the mwservice user configured during the External MongoDB Server
Installation process. This user only has read and write privileges configured.
In general, the connection string follows the form:
mongodb://<user>:<password>@<servername>:<port>/?
authSource=admin&tls=true
Our recommendation is:
mongodb://mwservice:<password>@<servername>:27018/?
authSource=admin&tls=true
Where:
1. <password> is the password set for the mwservice user during the
External MongoDB Server Installation.
2. <servername> is the name of the External MongoDB server.

3. Click Test Connection to test the connection string.

a) Paths for certificate files are not supported in AMS Machine Works,
restructure your connection string.

60 AMS Machine Works v2.0

System Guide Installation Procedures
July 2025

Attention
Connection strings that specify a certificate file will not work with AMS
Machine Works. The certificate files must be installed manually. See:
External MongoDB Server Installation

Figure 3-18: Not supported: Paths for Certificate Files

b) Your connection string can fail for a variety of other reasons.

Figure 3-19: External MongoDB connection: Failed

Note
The connection can fail for a variety of reasons, for example:
• Server name wrong.
• Server powered down.
• No network connection.
• Wrong user name and password combination.

c) Your connection succeeded and you can proceed.

Figure 3-20: External MongoDB connection: Success

4. Enter the passwords you need for the two PostgreSQL database accounts postgres,
and mwservice.

AMS Machine Works v2.0 61

Installation Procedures System Guide
July 2025

CAUTION
All PostgreSQL passwords:
a. Must meet the Local Security Policy of the server.
b. Cannot contain the following special characters:
• ' <single quotation mark>
• " <double quotation mark>

a) For the administrator account, postgres, enter a PostgreSQL password twice,

and then click Next to continue.

Figure 3-21: InstallShield Wizard - Enter PostgreSQL administrator

password.

b) For the user account, mwservice, enter a PostgreSQL password twice, and
then click Next to continue.

62 AMS Machine Works v2.0

System Guide Installation Procedures
July 2025

Figure 3-22: InstallShield Wizard - Enter PostgreSQL mwservice

password.

Postrequisites
Proceed to the next step, Choose the Installation Drive.

3.2.7 Choose the Installation Drive

We recommended installing AMS Machine Works on a different drive than the boot drive.
Depending on which installation scenario you are using, different components will be
installed on the drive that you select in this step:
1. Scenario One — AMS Machine Works Server installation.
a. (Optional) If your installation is using an Internal MongoDB database for
measurement data, it will be stored on this drive.
b. Your PostgreSQL database with configuration information.
c. The AMS Machine Works Server

2. Scenario Two — Agent Server installation.

a. One of each type of Agent Server. (Total number of Agent Servers: Min. One
Agent Server, Max. Four Agent Servers.)

Note
For more information about the recommended disk space see: Storage Capacity
Requirements by System Profile.

Prerequisites
The step previous to this is:

AMS Machine Works v2.0 63

Installation Procedures System Guide
July 2025

1. Scenario One — AMS Machine Works Server installation: Provide Passwords or

Connection String
2. Scenario Two — Agent Server installation: Connect to a Server

Procedure
1. Select which drive to install on.

Figure 3-23: InstallShield Wizard - Select which drive to install on.

2. Click Next to continue to the next step: Select which Agents to Install

3.2.8 Select which Agents to Install

An Agent can be installed internally as part of a full AMS Machine Works Server
installation, or performed later as an external Agent Server installation.

Prerequisites
The previous step is: Choose the Installation Drive

Procedure
1. Select every type of Agent which you will need to access the devices on your
network.

64 AMS Machine Works v2.0

System Guide Installation Procedures
July 2025

Figure 3-24: InstallShield Wizard - Agent Selection

Note
You must install each specific type of Agent to be able to access those device types.

Note
If an option is grey, that Agent is already present on that machine.

Note
If you are performing an external Agent Server installation, you must select at least
one type of Agent to install.

Note
If you select a Portables Agent you must Install CSI USB Drivers.

Figure 3-25: CSI USB Driver required for Portables Agent

2. When you are installing a Portables Agent you must specify which port to
communicate on. (Default port: 10077)

AMS Machine Works v2.0 65

Installation Procedures System Guide
July 2025

Figure 3-26: InstallShield Wizard - Portables Agent Port Configuration

a) (Optional) If you require USB to connect to your AMS 2140 Machinery Health
Analyzer to AMS Machine Works, you must have the CSI USB Driver
installed. You must perform the following post-installation step: Install CSI
USB Drivers

3. Click Next to continue to the next step: Confirm Installation

3.2.9 Confirm Installation

Prerequisites
You must complete the previous step, Select which Agents to Install, before you can begin
the installation process.

Procedure
The configuration is complete, click Install to start the installation process.

66 AMS Machine Works v2.0

System Guide Installation Procedures
July 2025

Figure 3-27: InstallShield Wizard - Configuration is complete, begin the installation

process.

Postrequisites
Once the installation process begins your machine may need to reboot several times. See:
Complete the Reboot Cycle

3.2.10 Complete the Reboot Cycle

The installation process might require one or more reboots, continue to reboot your
system as instructed by the installer.

Prerequisites
You must complete the previous step, Confirm Installation, before the installation reboot
cycle begins.

Procedure
1. The installer has been fully configured, and is ready to begin the installation process
and reboot cycle. Click Reboot to proceed.

AMS Machine Works v2.0 67

Installation Procedures System Guide
July 2025

Figure 3-28: AMS Machine Works 2.0 — Setup Configured / First Reboot

2. The installer goes through the tasks you have configured for your installation. The
number of reboots that are required depends on your Windows configuration. Click
Reboot to proceed.

Figure 3-29: AMS Machine Works 2.0 — Installation in Progress

3. When the installation is complete you will be prompted to reboot one last time.
Click Reboot to proceed.

68 AMS Machine Works v2.0

System Guide Installation Procedures
July 2025

Figure 3-30: AMS Machine Works 2.0 — Installation Complete / Final Reboot

Postrequisites
The installation is now complete. Please continue to Post-Installation Steps.

3.3 Agent Server Installation

This is a general overview of the Agent Server installation process. An Agent Server of
each type can be added anywhere on your network where one is not present, even on the
main AMS Machine Works Server. Multiple copies of an Agent Server can be present on
your network, but only one of each type is allowed on a particular machine.

Prerequisites
1. An AMS Machine Works Server must be installed and operating on your network
before you can perform an Agent Server installation.
2. Export the certificate from the AMS Machine Works Server to the Agent Server. See:
Add AMS Machine Works Certificates

Procedure
1. Launch Installer
2. Software License Agreement
3. Choose Agent Server Installation
4. Connect to a Server
5. Choose the Installation Drive
6. Select which Agents to Install
7. Confirm Installation
8. Complete the Reboot Cycle

AMS Machine Works v2.0 69

Installation Procedures System Guide
July 2025

3.3.1 Launch Installer

The Installer_2.0.XXX package must be properly decompressed, unblocked, and located
before you run it.

Prerequisites
Complete all the Pre-Installation Steps.

CAUTION
Run setup.exe from a folder close to the root of your file system. Long path names can
result in the installer failing.

CAUTION
It is strongly recommended that you pause Windows Automatic Updates during the
installation process. Failure to do so may lead to inconsistent results. See: Stop Automatic
Updates

Procedure
1. Right-click on setup.exe, and click Run as administrator.
a) If the User Access Control window appears, click Yes to allow setup.exe to
install.

Figure 3-31: User Access Control

b) AMS Machine Works uses port 80 and port 443 by default. If these ports are
in use you must configure different ports. See: Network Port Availability

70 AMS Machine Works v2.0

System Guide Installation Procedures
July 2025

Figure 3-32: Warnings: AMS Machine Works Web Services Ports in Use

2. Click Next to continue.

Figure 3-33: AMS Machine Works v2.0 – InstallShield Wizard

3. Continue to the next step: Software License Agreement

3.3.2 Software License Agreement

Prerequisites
You must complete the previous step, Launch Installer, before you can begin the
installation process.

Procedure
1. Read the Software License Agreement.
2. (Optional) Click Print to print a copy of the Software License Agreement for your
records.
3. Click the checkbox next to I accept the terms of the license agreement.

AMS Machine Works v2.0 71

Installation Procedures System Guide
July 2025

Figure 3-34: InstallShield Wizard - License Agreement

4. Click Next to continue.

Postrequisites
Depending on which scenario you are using, the next step to this is either:
1. (Scenario One) When performing an AMS Machine Works Server installation:
Choose AMS Machine Works Server Installation
2. (Scenario Two) When performing an Agent Server installation: Choose Agent Server
Installation

3.3.3 Choose Agent Server Installation

The Agent Server installation process produces a server with from one to four types of
Agent. An Agent Server installation can be located anywhere in your network.

Note
If you are adding another Agent to an existing installation, select Agent Server.

Prerequisites
You must complete the previous step: Software License Agreement

Procedure
1. Select Agent Server for a new installation.

72 AMS Machine Works v2.0

System Guide Installation Procedures
July 2025

Figure 3-35: InstallShield Wizard - Select the Agent Server installation option.

2. Click Next to continue to the next step: Connect to a Server

3.3.4 Connect to a Server

The Server Name is how other elements of the system can refer to the main AMS Machine
Works Server.
There are three different formats for giving the Server Name:
1. The Computer Name given in the AMS Machine Works Server computer's settings.
2. The fully qualified domain name, FQDN, of the AMS Machine Works Server
computer.
Note
If you have a FQDN (Fully Qualified Domain Name) network, you must enter the Full
computer name for the AMS Machine Works server here. On the AMS Machine
Works server select AMS Machine Works Server → Properties to find this
information.

3. The IP address of the AMS Machine Works Server computer.

Prerequisites
You must complete the previous step: Choose Agent Server Installation

Procedure
1. Enter the Server Name and Port number of the AMS Machine Works Server you
want to connect to.

AMS Machine Works v2.0 73

Installation Procedures System Guide
July 2025

Figure 3-36: InstallShield Wizard - Enter the AMS Machine Works Server Name

Note
The default Port is 443. If this port is unavailable consult the Network Port
Availability section.

2. Click Next to continue to the next step: Set Data Retention Policy and Create
Backups

3.3.5 Choose the Installation Drive

We recommended installing AMS Machine Works on a different drive than the boot drive.
Depending on which installation scenario you are using, different components will be
installed on the drive that you select in this step:
1. Scenario One — AMS Machine Works Server installation.
a. (Optional) If your installation is using an Internal MongoDB database for
measurement data, it will be stored on this drive.
b. Your PostgreSQL database with configuration information.
c. The AMS Machine Works Server

2. Scenario Two — Agent Server installation.

a. One of each type of Agent Server. (Total number of Agent Servers: Min. One
Agent Server, Max. Four Agent Servers.)

Note
For more information about the recommended disk space see: Storage Capacity
Requirements by System Profile.

Prerequisites
The step previous to this is:

74 AMS Machine Works v2.0

System Guide Installation Procedures
July 2025

1. Scenario One — AMS Machine Works Server installation: Provide Passwords or

Connection String
2. Scenario Two — Agent Server installation: Connect to a Server

Procedure
1. Select which drive to install on.

Figure 3-37: InstallShield Wizard - Select which drive to install on.

2. Click Next to continue to the next step: Select which Agents to Install

3.3.6 Select which Agents to Install

An Agent can be installed internally as part of a full AMS Machine Works Server
installation, or performed later as an external Agent Server installation.

Prerequisites
The previous step is: Choose the Installation Drive

Procedure
1. Select every type of Agent which you will need to access the devices on your
network.

AMS Machine Works v2.0 75

Installation Procedures System Guide
July 2025

Figure 3-38: InstallShield Wizard - Agent Selection

Note
You must install each specific type of Agent to be able to access those device types.

Note
If an option is grey, that Agent is already present on that machine.

Note
If you are performing an external Agent Server installation, you must select at least
one type of Agent to install.

Note
If you select a Portables Agent you must Install CSI USB Drivers.

Figure 3-39: CSI USB Driver required for Portables Agent

2. When you are installing a Portables Agent you must specify which port to
communicate on. (Default port: 10077)

76 AMS Machine Works v2.0

System Guide Installation Procedures
July 2025

Figure 3-40: InstallShield Wizard - Portables Agent Port Configuration

a) (Optional) If you require USB to connect to your AMS 2140 Machinery Health
Analyzer to AMS Machine Works, you must have the CSI USB Driver
installed. You must perform the following post-installation step: Install CSI
USB Drivers

3. Click Next to continue to the next step: Confirm Installation

3.3.7 Confirm Installation

Prerequisites
You must complete the previous step, Select which Agents to Install, before you can begin
the installation process.

Procedure
The configuration is complete, click Install to start the installation process.

AMS Machine Works v2.0 77

Installation Procedures System Guide
July 2025

Figure 3-41: InstallShield Wizard - Configuration is complete, begin the installation

process.

Postrequisites
Once the installation process begins your machine may need to reboot several times. See:
Complete the Reboot Cycle

3.3.8 Complete the Reboot Cycle

The installation process might require one or more reboots, continue to reboot your
system as instructed by the installer.

Prerequisites
You must complete the previous step, Confirm Installation, before the installation reboot
cycle begins.

Procedure
1. The installer has been fully configured, and is ready to begin the installation process
and reboot cycle. Click Reboot to proceed.

78 AMS Machine Works v2.0

System Guide Installation Procedures
July 2025

Figure 3-42: AMS Machine Works 2.0 — Setup Configured / First Reboot

2. The installer goes through the tasks you have configured for your installation. The
number of reboots that are required depends on your Windows configuration. Click
Reboot to proceed.

Figure 3-43: AMS Machine Works 2.0 — Installation in Progress

3. When the installation is complete you will be prompted to reboot one last time.
Click Reboot to proceed.

AMS Machine Works v2.0 79

Installation Procedures System Guide
July 2025

Figure 3-44: AMS Machine Works 2.0 — Installation Complete / Final Reboot

Postrequisites
The installation is now complete. Please continue to Post-Installation Steps.

3.4 External MongoDB Server Installation

This procedure provides instructions for installing a new External MongoDB Server.
The default installation is to have an Internal MongoDB database which is automatically
configured. If you need to install an External MongoDB Database Server, follow these
steps.

Prerequisites
1. Ensure that the machine meets the minimum specification for an External
MongoDB Server.
2. Ensure that the machine does not have a previous installation of MongoDB.
3. Get the MongoDB installer from one of the following locations:
a. (Recommended) MongoDB 8.0.4
1. AMS Machine Works v2.0 installer package — ..\dep\_Support
\MongoDB\mongodb-windows-x86_64-8.0.4-signed.msi

2. Online — Download the installation file for MongoDB 8.0.4 to the

machine. https://fastdl.mongodb.org/windows/mongodb-windows-
x86_64-8.0.4-signed.msi

b. (Only for Windows Server 2016) MongoDB 6.0.20

1. AMS Machine Works v2.0 installer package — ..\dep\_Support
\MongoDB\mongodb-windows-x86_64-6.0.20-signed.msi

80 AMS Machine Works v2.0

System Guide Installation Procedures
July 2025

2. Online — Download the installation file for MongoDB 6.0.20 to the

machine. https://fastdl.mongodb.org/windows/mongodb-windows-
x86_64-6.0.20-signed.msi

Procedure
1. Run the MongoDB installer, and then click Next.

Figure 3-45: Welcome Screen

2. Accept the terms in the License Agreement, and then click Next.

Figure 3-46: License Agreement

3. Choose the Setup Type for your MongoDB, and then click Next.

AMS Machine Works v2.0 81

Installation Procedures System Guide
July 2025

Note
The Complete option is recommended. For Custom options contact your System
Administrator.

Figure 3-47: Choose Setup Type

4. Configure the MongoDB Server, and then click Next.

Note
Recommendation:
a. Accept the default options to install MongoD as a service named MongoDB.
b. Run the MongoDB service as a Network Service user.
c. Install the Data Directory and the Log Directory on a drive other than C: , and
establish a backup schedule for this drive.
For other configuration options contact your System Administrator.

82 AMS Machine Works v2.0

System Guide Installation Procedures
July 2025

Figure 3-48: Service Configuration

5. (Optional) Select Install MongoDB Compass

Note
Installing MongoDB Compass is recommended for preparing, configuring, and
managing the database.

Note
If the automatic installation of MongoDB Compass fails, for example because of
corporate security policies, then you must install it manually. The installer is located
at: ..\dep\_Support\MongoDB\mongodb-compass-1.45.2-win32-
x64.exe .
If you want to perform additional installations of MongoDB Compass, for example
on the AMS Machine Works server, you can manually perform this installation in
multiple places.

6. Click Next.

AMS Machine Works v2.0 83

Installation Procedures System Guide
July 2025

Figure 3-49: Install MongoDB Compass

7. Confirm your installation choices, and then click Install.

Note
You can use the Back and Next keys to review your choices and then return to this
screen.

Figure 3-50: Install this Configuration

8. When the installation is complete click Finish.

84 AMS Machine Works v2.0

System Guide Installation Procedures
July 2025

Figure 3-51: Finish Installation

9. Run MongoDB Compass.

Figure 3-52: Run MongoDB Compass

Note
If you did not install MongoDB Compass as was recommended in one of the
previous steps:
• Either, contact your System Administrator about how to proceed.
• Or, download and install MongoDB Compass now.

10. Click + Add new connection → Save & Connect.

AMS Machine Works v2.0 85

Installation Procedures System Guide
July 2025

Figure 3-53: New Connection

11. Click on the connection: localhost:27017

Figure 3-54: Access the MongoDB Shell

12. Click on >_ Open MongoDB shell at the top of the window to expand the MongoDB
command line interface.

86 AMS Machine Works v2.0

System Guide Installation Procedures
July 2025

Figure 3-55: Access the MongoDB Shell

13. Switch to the Admin database by entering the command: use admin.

Figure 3-56: Enter the 'use admin' Command

14. Enter and modify the text below to create an admin user for managing the
MongoDB.

db.createUser(
{
user: "admin",
pwd: "Password123",
roles: [
{ role: 'readWriteAnyDatabase', db: 'admin' },
{ role: 'userAdminAnyDatabase', db: 'admin' },
{ role: 'dbAdminAnyDatabase', db: 'admin' },
{ role: 'root', db: 'admin' }

AMS Machine Works v2.0 87

Installation Procedures System Guide
July 2025

]
}
)

Note
Text entered into the MongoDB shell is case sensitive.

Note
The example password, "Password123", should be replaced with a password which
meets your organization's security policies.

CAUTION
To ensure compatibility, MongoDB passwords should not contain the following
special characters:
%, /, :, @, <blank space>

Figure 3-57: Create an Admin User to Manage the MongoDB

15. Enter and modify the text below to create a database user for the AMS Machine
Works services, the mwservice user.
Note
This user requires readWrite privileges for the following databases:
• EmersonMWcoreData
• EmersonMWCore
• EmersonMWOnline
• EmersonMWPortables
• EmersonMWLicense

db.createUser(
{

88 AMS Machine Works v2.0

System Guide Installation Procedures
July 2025

user: "mwservice",
pwd: "Password123",
roles: [
{ role: "readWrite", db: "EmersonMWcoreData" },
{ role: "readWrite", db: "EmersonMWCore" },
{ role: "readWrite", db: "EmersonMWOnline" },
{ role: "readWrite", db: "EmersonMWPortables" },
{ role: "readWrite", db: "EmersonMWLicense" }
]
}
)

Note
Text entered into the MongoDB shell is case sensitive.

Note
The example password, "Password123", should be replaced with a password which
meets your organization's security policies.

CAUTION
To ensure compatibility, MongoDB passwords should not contain the following
special characters:
%, /, :, @, <blank space>

Figure 3-58: Create a Database User for AMS Machine Works Services

16. Open the default mongod.cfg file.

a. The default location of the file for MongoDB 8.0.4: C:\Program Files
\MongoDB\Server\8.0\bin

AMS Machine Works v2.0 89

Installation Procedures System Guide
July 2025

b. The default location of the file for MongoDB 6.0.20: C:\Program Files
\MongoDB\Server\6.0\bin

Figure 3-59: Example MongoDB Configuration File for MongoDB 8.0.4 —

mongod.cfg

# mongod.conf

# for documentation of all options, see:

# http://docs.mongodb.org/manual/reference/configuration-
options/

# Where and how to store data.

storage:
dbPath: C:\Program Files\MongoDB\Server\8.0\data

# where to write logging data.

systemLog:
destination: file
logAppend: true
path: C:\Program Files\MongoDB\Server\8.0\log\mongod.log

# network interfaces
net:
port: 27017
bindIp: 127.0.0.1

#processManagement:

#security:

#operationProfiling:

#replication:

#sharding:

## Enterprise-Only Options:

#auditLog:

90 AMS Machine Works v2.0

System Guide Installation Procedures
July 2025

Figure 3-60: Example MongoDB Configuration File for MongoDB 6.0.20 —

mongod.cfg

# mongod.conf

# for documentation of all options, see:

# http://docs.mongodb.org/manual/reference/configuration-
options/

# Where and how to store data.

storage:
dbPath: C:\Program Files\MongoDB\Server\6.0\data
journal:
enabled: true
# engine:
# wiredTiger:

# where to write logging data.

systemLog:
destination: file
logAppend: true
path: C:\Program Files\MongoDB\Server\6.0\log\mongod.log

# network interfaces
net:
port: 27017
bindIp: 127.0.0.1

#processManagement:

#security:

#operationProfiling:

#replication:

#sharding:

## Enterprise-Only Options:

#auditLog:

#snmp:

17. Modify the # network interfaces and #security sections of the mongod.cfg
file.

AMS Machine Works v2.0 91

Installation Procedures System Guide
July 2025

Figure 3-61: Recommended Configuration

# network interfaces section

# network interfaces
net:
port: 27018
bindIp: 0.0.0.0
tls:
mode: preferTLS
certificateKeyFile: C:\Program Files\MongoDB\Server
\8.0\bin\<Your_MongoDB_Server_Cert>.pem
CAFile: C:\Program Files\MongoDB\Server\8.0\bin
\<Your_CA_Server_Cert>.pem
allowConnectionsWithoutCertificates: true

#security section

security:
authorization: enabled

Note
• <Your_MongoDB_Server_Cert>.pem file must be provided by a Certification
Authority.
• <Your_CA_Server_Cert>.pem file must be provided by a Certification Authority.
• Remember to remove the comment symbol,

, in front of

security:

or an error will occur.

• Do not use the Tab key to indent the configuration file, only use the Space key.
Using the Tab key will result in a configuration error.
• The default port is recommended to be changed from 27017 to another port
number.
• Setting the bindIp to 0.0.0.0 allows it to bind an IP address other than localhost.
• If authorization is not enabled, any user can access the MongoDB database.

Note
The MongoDB Atlas cloud solution also requires a user that has the proper
permissions for the Emerson databases. The MongoDB Atlas cloud solution has a
graphical interface for configuring these options. These options should be
configured to the same values as shown above. Please seek the assistance of your
System Administrator, and refer to your MongoDB Atlas cloud documentation for
how to perform these steps.

92 AMS Machine Works v2.0

System Guide Installation Procedures
July 2025

In general, the connection string follows the form:

mongodb://<user>:<password>@<servername>:<port>/?
authSource=admin&tls=true

Our recommendation is:

mongodb://mwservice:<password>@<servername>:27018/?
authSource=admin&tls=true

Where:
a. <password> is the password set for the mwservice user.
b. <servername> is the name of the External MongoDB server.

Attention
Connection strings that specify a .pem file will not work with AMS Machine
Works. The .pem files must be installed manually.

18. Obtain a certificate from your trusted Certificate Authority and copy it to the
following locations:
a) C:\Program Files\MongoDB\Server\8.0\bin
\<Your_MongoDB_Server_Cert>.pem
b) C:\Program Files\MongoDB\Server\8.0\bin\<Your_CA_Server_Cert>.pem

Attention
MongoDB no longer supports a configuration that enables TLS without explicitly
specifying a chain of trust.

Note
If your installation uses another path for the certificates, this change must be used
in your mongod.cfg file.

19. Restart the MongoDB Server (MongoDB) service.

The MongoDB server is now correctly configured and running.

3.5 Post-Installation Steps

After installation is complete, there are some additional setup and configuration steps to
perform before the system is ready to be used. You can refer to the sections indicated
below, and to the AMS Machine Works User Guide, or to the AMS Machine Works Online
Help, for more information.

Procedure
1. For AMS Machine Works to function properly certain Windows services must be
running. See: Check Services
2. For AMS Machine Works to function properly the ports which are used for
communication cannot be in use by other applications. See: Deconflict Ports

AMS Machine Works v2.0 93

Installation Procedures System Guide
July 2025

3. To ensure the stability of the installation process you previously must have paused
the automatic update services on your server. You must now Restart Automatic
Updates.
4. To enable the use of the domain user accounts on your server to access AMS
Machine Works installation you must Enable Domain User Login
5. Add AMS Machine Works Certificates
6. When you launch AMS Machine Works for the first time, log in with the default
password and then set a custom password. See: First Launch of AMS Machine Works
7. (Optional) You should set a backup policy and a data retention policy See: Set Data
Retention Policy and Create Backups
8. (Optional) If you need to use an OPC UA client, ensure that you have an OPC license
in the User Manager module of AMS Machine Works. See: OPC UA Server
9. AMS Machine Works is integrated with a sophisticated analysis tool, the Vibration
Analyzer, or VibApp. You should install this application to get insights into your
data. See: Install the Vibration Analyzer - VibApp
10. (Optional) If your AMS Machine works system needs to communicate with AMS
2140 Machinery Health Analyzer handheld units via a USB connection, you must
install the CSI USB Driver on the system(s) you will use to connect to AMS Machine
Works. See: Install CSI USB Drivers
11. Monitor the performance of your system to ensure that you do not enter a critical
overload or have data loss. See: Monitor DSS Processing Capacity
You are now ready to start using AMS Machine Works.

3.5.1 Check Services

Procedure
1. After rebooting your system and logging in, wait for about 5 to 7 minutes so that all
the services have some time to start. Next, open Windows Services and check that
the service is running for each Agent that you installed.

Note
The following services have a delayed start setting:
• Emerson MW Asset Monitor Agent
• Emerson MW Wireless Agent
• Emerson MW ATG Agent

94 AMS Machine Works v2.0

System Guide Installation Procedures
July 2025

Figure 3-62: Windows services

2. Check that the following services are running:

a. Emerson MW Core Data Shovel Service
b. Emerson MW Core License Manager
c. Emerson MW Core Train Service
d. Emerson MW Data Integration Module OPC Server
e. Emerson MW Online Device Service
f. Emerson MW Portables Agent Configuration Service
g. Emerson MW Portables Authorization Service
h. Emerson MW Portables Device Configuration Service
i. Emerson MW Portables Library Service
j. Emerson MW Portables Module Integration Service
k. Emerson MW Portables Route Configuration Service
l. Emerson MW Portables Route Factory
m. Emerson MW Portables Transaction Orchestrator
n. Agent Services:
1. Emerson MW Asset Monitor Agent
2. Emerson MW ATG Agent
3. Emerson MW Portables Edge Agent
4. Emerson MW Wireless Agent
Note
1. Agent Services will only be present if they have been installed on this
machine.

AMS Machine Works v2.0 95

Installation Procedures System Guide
July 2025

2. Agent Services will only be running after they have been registered in
the Network Device Module, for most agents, or in the Portable
Device Module for the Emerson MW Portable Edge Agent.

o. MongoDB Services:
1. MongoDB Server (MongoDB)

p. PostgreSQL Services:
1. postgresql-x64-17-PostgreSQL Server 17

q. RabbitMQ services:
1. RabbitMQ

3.5.2 Deconflict Ports

The default ports for AMS Machine Works are 80 and 443.
Port 8888 is required for the Vibration Analyzer,VibApp, application to operate.
If these ports are not available, or in use by another application, you must change which
ports you will use.

Prerequisites
Note the numbers of some available ports.

Procedure
1. (Optional) If Port 8888 is in use by another application, that application must be
reconfigured to use another port.
2. Launch the Internet Information Services (IIS) Manager.
3. In the Connections pane expand Your_Server_Name.
4. In the Connections pane expand the Sites under Your_Server_Name.
5. In the Connections pane, right click EmersonCSI → Edit Bindings....
6. (Optional) If port 80 is in use:
a) In the Site Bindings window, select port 80 and click Edit .
b) In the Edit Site Binding window, enter another port number, and then click
OK.

7. (Optional) If port 443 is in use:

a) In the Site Bindings window, select port 443 and click Edit .
b) In the Edit Site Binding window, enter another port number, and then click
OK.
AMS Machine Works should now operate normally with deconflicted ports.

96 AMS Machine Works v2.0

System Guide Installation Procedures
July 2025

3.5.3 Restart Automatic Updates

Emerson recommends stopping automatic updates before installation. See: Stop
Automatic Updates

Prerequisites
Locate the Stopped Update Services List you made in the Stop Automatic Updates task.

Procedure
1. Restart the services in your Stopped Update Services List.
The automatic update services that you paused should now be running again.
2. Verify that the services are running.

3.5.4 Enable Domain User Login

You can use the domain user accounts on the server computer to log in to AMS Machine
Works.

Prerequisites
1. Log on to the computer with the same Administrator account that you used to
install AMS Machine Works.
2. Open Windows → Internet Properties → Security Tab → Trusted Sites

Figure 3-63: Internet Properties Dialog

Procedure
1. Click Custom Level.

AMS Machine Works v2.0 97

Installation Procedures System Guide
July 2025

Figure 3-64: Security Settings - Trusted Sites Zone

2. Scroll down to the User Authentication section.

3. Select Automatic logon will current user name and password.
4. Click OK.

Figure 3-65: Confirm Change — Warning!

5. Click Yes.
6. In the Internet Properties dialog, click Apply.
7. To close the Internet Properties dialog, click OK.
You should now be able to log in to AMS Machine Works with Domain User
accounts.

3.5.5 Add AMS Machine Works Certificates

A certificate is required for secure communication. You must add a certificate from your
AMS Machine Works installation to every External Agent Server that you create.
AMS Machine Works supports the use of TLS 1.3, and uses this standard by default.
Windows Server versions prior to Windows 2022, and other supported operating systems,
can only use TLS 1.2. The TLS protocol automatically negotiates the highest mutually
supported version of the protocol to use.
The AMS 2140 Health Analyzer only supports TLS 1.1. (See the AMS Machine Works User
Guide for more details.)

Prerequisites
1. You will need Administrator access on all the affected machines.
2. In Windows open: Manage computer certificates.

98 AMS Machine Works v2.0

System Guide Installation Procedures
July 2025

Procedure
1. To open the Certificate Export Wizard choose: Trusted Root Certification
Authorities → Certificates → AMS Machine Works 2.0
<YOUR_COMPUTER_NAME> → All Tasks → Export...
2. In the Certificate Export Wizard, choose: Next → No, do not export the private
key → DER encoded binary X.509 (.CER) → Next.
3. Click Browse and then choose a location and enter a File name for the certificate.
4. Choose: Save
5. Choose: Next
6. Review the certificate's settings.
• If the settings are not correct, click Cancel.
• If the settings are correct, click Finish.

7. Install AMS Machine Works server certificate where necessary. See: AMS Machine
Works Security
A certificate is necessary on every External Agent Server.

Note
This includes PCs used to connect with AMS 2140 Health Analyzer units. See the
User Guide for more details.

3.5.6 First Launch of AMS Machine Works

After installation, you can launch AMS Machine Works using the desktop shortcut. You will
be asked to log in to the Administrator account.

Prerequisites
• Use Google Chrome for optimal performance. AMS Machine Works web applications
use web technologies that are no longer supported in Internet Explorer 11. See:
Troubleshooting
• Security certificates must be installed. See: AMS Machine Works Security
• If you are launching AMS Machine Works for the first time after an update, you must
clear all browser caches before reconnecting to AMS Machine Works. See: Update from
v1.8 to v2.0

Procedure
1. Open a web browser. (Recommended: Google Chrome or Microsoft Edge)
2. In the web browser address field, enter the URL for the User Manager: For example,
https://[server]/user-manager

Where [server] is the computer name of the AMS Machine Works server.2

3. If this is the first time you have launched AMS Machine Works from a client
computer, install the certificate.

2 If a port number is required, also include the port number, for example, https://[server]:443/user-manager.

AMS Machine Works v2.0 99

Installation Procedures System Guide
July 2025

Install the AMS Machine Works certificate so you can perform actions such as
adding asset sources. See: AMS Machine Works Security
4. Open the User Manager in the web browser then enter the initial credentials:
Username : admin
Password : Emerson#1

5. After you log in you should change your password.

Note
Some users set the 'new' password to Emerson#1, but this is against recommended
security practices.

6. Next, you must register your AMS Machine Works license. Refer to the User Guide
Online Help for instructions.

3.5.7 Set Data Retention Policy and Create Backups

Once your AMS Machine Works installation is running it is time to create a backup process
and schedule. The simplest method is to perform a Full Machine Backup.

Note
You can manually control data retention, or schedule data retention for your MongoDB
databases with the Data Retention Policy Tool.

Prerequisites
Contact your System Administrator to determine your organization's data retention
policy.

Procedure
1. Implement your organization's data retention policy.
2. Maintain regular backups of your data.

3.5.8 Install the Vibration Analyzer - VibApp

The AMS Machine Works Vibration Analyzer lets you analyze vibration data collected in
AMS Machine Works from connected devices. This is a Windows application that can be
installed on client computers and also on the AMS Machine Works server.
Note
If you install AMS Machine Works Vibration Analyzer on the server, an extra step is required
to authenticate and launch. You must add the server name to the browser's list of trusted
sites. Refer to your browser's documentation to add a trusted site.

Prerequisites
• Turn off automatic Windows updates during installation or upgrade. Pausing updates
will reduce the number of restarts during the installation process. In Windows
Settings, select Advanced, and choose to pause updates and select a date to resume
updates.

100 AMS Machine Works v2.0

System Guide Installation Procedures
July 2025

Procedure
1. Open a browser, type https://[server]:[port number]/VibApp.
Where [server] is the computer name of the server where AMS Machine Works is
installed and [port number], if required, is the port number assigned.

Note
Enter the server name set during installation of AMS Machine Works.

Note
The Vibration Analyzer installer is also available as a .exe file at: (Installer
Folder)/Products/AMS Machine Works Vibration Analysis Service

2. Click Install on the Vibration Analyzer installation page.

3. Run the application.
4. Note
If you are prompted to upgrade the installation, this indicates that you have already
installed the application.

When prompted, enter the name of the AMS Machine Works server, and then click
Next.

Note
Use the same server name as the AMS Machine Works configuration, and when
installing or upgrading components. For example, when you choose the Use Server
Name option in the Server and Port Binding Configuration screen during the
installation, you must enter the name of the AMS Machine Works server.
Failure to use the same configuration as the AMS Machine Works server when
installing or upgrading components may cause the installation to fail and you will
need to uninstall and reinstall the software to configure the same server setting.

5. Click Next.
6. Click Install.
7. Click Finish when done.

3.5.9 Install CSI USB Drivers

You can install the USB drivers on any computer where you need to connect an AMS 2140
Machinery Health Analyzer unit.
Note
The USB drivers for the AMS 2140 Machinery Health Analyzer are installed automatically
with AMS Machinery Manager or AMS Standalone Data Transfer.

Prerequisites
Locate the AMS Machine Works installation package.

AMS Machine Works v2.0 101

Installation Procedures System Guide
July 2025

Procedure
1. Browse to the folder: C:\..\Installer_2.0.0.XXX\dep\_Support
\CSIUSBDriver\

Note
a. C:\..\ — The drive letter and the folder path are where you decompressed
the installer package.
b. 2.0.0.XXX — XXX is the specific build number of your version of AMS
Machine Works v2.0.

2. Right click on the setup.exe application and select Run as administrator.

3. Read and accept the license agreement.
4. Follow the instructions presented by the installation program.
5. When Windows Security prompts for permission, click Install.
6. Click Finish to complete your installation.

3.5.10 Monitor DSS Processing Capacity

The DSS / Data Shovel Service can become a bottleneck to overall system performance.
DSS is the Emerson MW Core Data Shovel Service in the Services app.
AMS Machine Works has a group of KPIs for monitoring this service. Normally, these KPIs
should have values near to 100% remaining capacity.

CAUTION
When any one of these KPIs has less than 10% of capacity remaining:
• The system is in critical overload.
• There is a risk of data loss.

Prerequisites
1. AMS Machine Works must be installed and running.
2. You must be logged into the machine where AMS Machine Works is installed.

Procedure
1. Open the DSS Processing Capacity KPIs in your browser: http://
localhost:5006/status/dashboard.html

Note
The URL must begin with http, https is not supported.

102 AMS Machine Works v2.0

System Guide Installation Procedures
July 2025

Figure 3-66: DSS Processing Capacity KPIs

• Measurement DB — Displays the amount of capacity remaining in the DSS

queue for writing to the measurement database.
• Alarm Evaluation — Displays the amount of capacity remaining in the DSS
queue for evaluating alarms.
• Derivative Calculations — Displays the amount of capacity remaining in the DSS
queue for calculating derivatives.
• OPC UA Data — Displays the amount of capacity remaining in the DSS queue for
publishing data to OPC UA.
• Health Updates — Displays the amount of capacity remaining in the DSS queue
for updating the hierarchy whenever an alert is triggered.
• Auto Refresh toggle — (Default: Off) Click to toggle between On/Off. When
Auto Refresh is On, it will update every 5 seconds.

2. Periodically monitor the DSS Processing Capacity.

a) If any value trends towards or below 10% of remaining capacity, contact
Emerson Support. See: Sending Log Files to Emerson Product Support

AMS Machine Works v2.0 103

Installation Procedures System Guide
July 2025

104 AMS Machine Works v2.0

System Guide Maintenance and Migration
July 2025

4 Maintenance and Migration

The AMS Machine Works v2.0 installer supports uninstallation and modification options
for v2.0, and an update path from v1.8 to v2.0.
Maintenance and Migration Tasks:
1. Uninstall — See: Uninstall AMS Machine Works v2.0
2. Modify — See: Modify an AMS Machine Works v2.0 Installation
3. Backup and Restore — See: Backup and Restore Procedures
Note
You should follow your organization's policies for performing backups. A Full
Machine Backup is recommended.

4. Update from v1.8 to v2.0 — See: Update from v1.8 to v2.0

4.1 Uninstallation Options

There is an uninstallation procedure for AMS Machine Works v2.0, Uninstall AMS Machine
Works v2.0.
There is an uninstallation procedure for each version of AMS Machine Works which has a
migration path to AMS Machine Works v2.0:
1. Migration from AMS Machine Works v1.7.2 is not currently supported.
2. Migration from AMS Machine Works v1.7.5 is not currently supported.

4.1.1 Uninstall AMS Machine Works v2.0

AMS Machine Works v2.0 can be uninstalled by running the installation application.
The installer application is located where you decompressed it:
C:\..\MachineWorksInstaller\setup.exe

Note
You must use the same version of the installer to uninstall AMS Machine Works as you
used for installation.

Note
Uninstallation by the Windows Add or remove programs control panel will work if the
proper version of the installer is unavailable.

Prerequisites
1. AMS Machine Works v2.0 must be installed on your computer system.
2. You must use the same version of the installer to uninstall AMS Machine Works as
you used for installation.

AMS Machine Works v2.0 105

Maintenance and Migration System Guide
July 2025

Procedure
1. Run setup.exe as an Administrator.
2. Choose Remove → Next to remove every AMS Machine Works component.

Figure 4-1: Remove Installation

3. Click Uninstall to begin the uninstallation process.

Figure 4-2: Confirm Uninstallation

4. Click Reboot when you are prompted.

Note
The number of reboot cycles varies depending on the elements that you have
installed.

Reboot as many times as you are prompted.

106 AMS Machine Works v2.0

System Guide Maintenance and Migration
July 2025

Need help?
Error occurred: Uninstallation failed. Exit code: 1638.
Reboot and retry
This error can be caused by using a different installer to run the uninstallation
process.
Check that you are using the same installer program that you installed AMS
Machine Works with.

5. Delete the AMS Machine Works configuration files manually.

a) Delete the folder containing the configuration data located at:
C:\ProgramData\Emerson

6. Uninstall Sentinel RMS License Manager 10.2.0:

a) Open Apps & features.
b) Select Sentinel RMS License Manager 10.2.0 → Uninstall.
c) Click Uninstall in the popup window to confirm.

7. Uninstall PostgreSQL 17:

a) Open Apps & features.
b) Select PostgreSQL 17 → Uninstall.
c) Click Uninstall in the popup window to confirm.
d) Select Entire application → Next.

Figure 4-3: Data Directory - Not Removed Warning

The data directory has not been removed. A popup is shown giving the
location of the data directory.
e) Click OK to proceed, and click OK in the next window to complete the
uninstallation.
PostgreSQL 17 is uninstalled, and your AMS Machine Works configuration
data is located at: C:\Program Files\PostgreSQL\17\data
f) Either delete or backup the data at: C:\Program Files\PostgreSQL
\17\data

g) Either delete or backup the data at: C:\Program Files\PostgreSQL

8. Uninstall MongoDB:

Note
The version of MongoDB that is installed depends on your operating system. See:
Database Components

AMS Machine Works v2.0 107

Maintenance and Migration System Guide
July 2025

a) Open Apps & features.

b) Select MongoDB → Uninstall.
c) Click Uninstall in the popup window to confirm.
MongoDB is uninstalled and your AMS Machine Works measurement data
and logs are located at: C:\EMERSONMW\
d) Either delete or backup the data at: C:\EMERSONMW\

9. Uninstall RabbitMQ Server 4.1.1:

a) Open Apps & features.
b) Select RabbitMQ Server 4.1.1 → Uninstall.
c) Click Uninstall in the popup window to confirm.
d) Click Uninstall in the second popup window to confirm.
The uninstallation process begins.
e) (Optional) Click Show details to see what the uninstallation process is doing.
f) Click Next in the next window.
Rabbit MQ files still remain on your system at:
C:\Users\Administrator\AppData\Roaming\RabbitMQ

g) Click Finish to finish the uninstallation process.

10. Uninstall Erlang OTP 27.3.4 (15.2.7):

a) Open Apps & features.
b) Select Erlang OTP 27.3.4 (15.2.7) → Uninstall.
c) Click Uninstall in the popup window to confirm.
d) Click Uninstall in the second popup window to confirm.
The uninstallation process begins.
e) (Optional) Click Show details to see what the uninstallation process is doing.
f) Click Close to finish the uninstallation process.

11. Check the Task Manager for the following processes, erlsrv and erl.
a) If they are running, stop erlsrv and erl.

12. (Optional) Any files that were not removed by the uninstall functions in Apps &
Features control panel should be removed.
• (Automatic Option) Use the Uninstall Cleaner Utility. See: Uninstall Cleaner
Utility
• (Manual Option) Continue the instructions below, and delete these files
manually.

13. Open the Command Prompt for your computer.

108 AMS Machine Works v2.0

System Guide Maintenance and Migration
July 2025

a) Type the command: tasklist |findstr "epmd"

b) Make note of the PID for "epmd.exe": Your_PID
The second column contains the PID:
epmd.exe 5744 Services 0 3,088 K

In this example: Your_PID = 5744, but it is different on every computer.

c) Type the command: taskkill /f /pid Your_PID

SUCCESS: The process with PID Your_PID has been
terminated.

14. Delete the following folders:

a) Delete: C:\Program Files\RabbitMQ Server
b) Delete: C:\Program Files\Erlang OTP

15. Delete the data at:

a) Delete: C:Users\Administrator\AppData\Roaming\RabbitMQ
b) Delete: C:Users\Administrator\.erlang.cookie
c) Delete: C:Windows\System32\config\systemprofile
\.erlang.cookie

Note
Administrator is the name of the default administrator, if you used another
administrator account to perform the installation, then the filepath will use that
name.
For example: C:\Users\Other_Administrator\AppData\Roaming
\RabbitMQ

16. Run the Windows Registry Editor, and delete the following registry entries.
a) Use the Registry Editor to delete the first Ericsson folder:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Ericsson

b) Use the Registry Editor to delete the second Ericsson folder:

HKEY_LOCAL_MACHINE\SOFTWARE\Ericsson

c) (Optional) Use the Registry Editor to delete the RabbitMQ folder if it exists:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services
\RabbitMQ

17. (Optional) Remove the AMS Machine Works server certificate.

18. (Optional) Remove the External MongoDB certificate, if you use an External
MongoDB.
19. Restart your computer.

AMS Machine Works v2.0 109

Maintenance and Migration System Guide
July 2025

4.2 Modification Options

When you run the AMS Machine Works installer on a system which has an AMS Machine
Works v2.0 installation on it, you have the option to modify your installation by adding
one or more Agents to the computer. See: Modify an AMS Machine Works v2.0 Installation

4.2.1 Modify an AMS Machine Works v2.0 Installation

You can add Agents to an AMS Machine Works installation or to an Agent Server
installation.
Only one copy of an Agent can be on a server at a time.

Prerequisites
1. You can modify:
a. An AMS Machine Works server installation. See: AMS Machine Works Server
Installation
b. An Agent server installation. See: Agent Server Installation

2. You must use the same version of the installer to modify AMS Machine Works as
you used for installation.

Procedure
1. Run setup.exe as an Administrator.
2. Choose Modify → Next to settings to modify or agents to add to your AMS Machine
Works installation.

Figure 4-4: Modify Installation

3. Set the Computer Name and Port for the AMS Machine Works server.

110 AMS Machine Works v2.0

System Guide Maintenance and Migration
July 2025

Figure 4-5: Set Computer Name and Port

a) The computer name can be specified as:

• Computer Name — (Default) The device name of the server computer.
(Available in Windows → Settings.)
• IP Address — The IP Address of the server computer. (Available in
Windows → Settings.)
• FQDN — The Fully Qualified Domain Name or Full device name of the
server computer. (Available in Windows → Settings.)

b) The computer port number can be from 1 to 65535. (Default port: 443)

4. Choose which types of Agent to install.

Note
Agents listed with a filled in checkbox and grey text are already present on this
server.

AMS Machine Works v2.0 111

Maintenance and Migration System Guide
July 2025

Figure 4-6: Install Additional Agents

a) (Optional) To connect to an AMS 2140 unit via USB, you will need to install
the CSI USB driver manually. See: Install CSI USB Drivers

Figure 4-7: Install CSI USB Driver Reminder

a) (Optional) If you require USB to connect to your AMS 2140 Machinery Health
Analyzer to AMS Machine Works, you must have the CSI USB Driver
installed. You must perform the following post-installation step: Install CSI
USB Drivers

5. (Optional) When you are installing a Portables Edge Agent you must specify which
port to communicate on. (Default port: 10077)

112 AMS Machine Works v2.0

System Guide Maintenance and Migration
July 2025

Figure 4-8: Portables Edge Agent Port Configuration

6. Click Install to begin the installation process.

Figure 4-9: Confirm Installation

7. Click Reboot when you are prompted.

Note
The number of reboots that are required depends on your Windows configuration.

Reboot as many times as you are prompted.

Need help?
Error occurred: Uninstallation failed. Exit code: 1638.
Reboot and retry

AMS Machine Works v2.0 113

Maintenance and Migration System Guide
July 2025

This error can be caused by using a different installer to run the uninstallation
process.
Check that you are using the same installer program that you installed AMS
Machine Works with.

4.3 Backup and Restore Procedures

A full system backup and restore procedure is the simplest and most effective method for
backing up your AMS Machine Works system. You should follow your organization's
policies for performing backups. A Full Machine Backup is recommended.
The PostgreSQL database does not have any specific instructions for backup, restore, or
maintenance procedures. Expert users can use the administration tool pgadmin4-9.1-
x64.exe provided in the installer at: ../<Installer>/dep/_Support/PostgreSQL/
pgadmin4-9.1-x64.exe

Backups
To perform backups of an Internal MongoDB database, see: Manual Backup of the
MongoDB Database
An External MongoDB installation requires maintenance by a database administrator.
Backups are expected to be performed by the database administrator. Please contact your
database administrator or IT department for proper backup procedures as they relate to
your overall backup strategy. See: Manual Backup of the MongoDB Database

Restore
If you need to restore any of the databases, contact your IT department to guide you on
the proper restore procedure.

4.3.1 Manual Backup of the MongoDB Database

To backup an Internal MongoDB or External MongoDB installation you need to use your
password and connection string with the mongodump.exe tool.

Prerequisites
Download and extract the mongodump.exe tool from the MongoDB website:
1. https://www.mongodb.com/docs/database-tools/mongodump/
2. https://www.mongodb.com
3. Or search for 'mongodump' in the search engine of your choice.

Procedure
1. Open the terminal application.
2. Change the directory to the location where the mongodump.exe was extracted.

114 AMS Machine Works v2.0

System Guide Maintenance and Migration
July 2025

Note
For more information about the mongodump.exe tool, please refer to the
MongoDB documentation website.

3. As an administrator user for the MongoDB database, run the mongodump.exe tool
with the following command:
mongodump.exe "mongodb://
<ADMIN_ACCOUNT_NAME>:<ADMIN_ACCOUT_PASSWORD>@localhost:27018/?
authSource=admin"

Postrequisites
To perform a restore operation please contact your system administrator and search the
MongoDB documentation website for mongorestore.

4.4 Update from v1.8 to v2.0

The installer package supports a migration path from AMS Machine Works v1.8 to v2.0.
The update affects:
1. AMS Machine Works v1.8 — Updates to version 2.0.
2. Asset Monitor Agent (AMA) v1.8 — Updates to version 2.0.
3. AMS 6500 ATG Agent v1.8 (ATGA) — Updates to version 2.0.
4. Emerson Wireless Gateway Agent v1.8 (EWA) — Updates to version 2.0.
5. RabbitMQ 4.0.6 — Updates to 4.1.1.
6. Erlang OTP 27.2.4 — Updates to 27.3.4.

4.4.1 Update AMS Machine Works from v1.8 to v2.0

Follow these steps to update AMS Machine Works v1.8 to v2.0.
Note
These steps do not update the AMS Portables Agent (PEA), that update must be
performed manually. See: Update the Portables Edge Agent from v1.8 to v2.0

Prerequisites
1. AMS Machine Works v1.8 must be installed.
2. Get the installer package. See: Locate the Installer

CAUTION
It is strongly recommended that you pause Windows Automatic Updates during the
installation process. Failure to do so may lead to inconsistent results. See: Stop
Automatic Updates

AMS Machine Works v2.0 115

Maintenance and Migration System Guide
July 2025

Procedure
1. If your AMS Machine Works system includes any External Agent Servers, you must
stop every External Agent Server now. Open the Services app, and stop the
following services:
a.
b. Emerson MW Asset Monitor Agent
c. Emerson MW ATG Agent
d. Emerson MW Portables Edge Agent
e. Emerson MW Wireless Agent

Note
If a service is not present then that Agent was not installed, and no action needs to
be taken.

2. In the installer folder, run setup.exe as an Administrator.

CAUTION
Run setup.exe from a folder close to the root of your file system. Long path
names can result in the installer failing.

3. If one of the following error screens is shown, contact Emerson Product Support.
See: Sending Log Files to Emerson Product Support

Figure 4-10: Updater Error Messages

• Error Preparing Update

• Error Preparing Backup

4. Read the update instructions, then click Next to continue.

116 AMS Machine Works v2.0

System Guide Maintenance and Migration
July 2025

Figure 4-11: Update Information

5. The update is ready to begin, click Update to continue.

Figure 4-12: Update Confirmation

6. Complete the reboot cycle. See: Complete the Reboot Cycle

7. Run the Update.exe tool found in the installation media at: <Installer>\dep
\_Support\RabbitMQ\Update.exe
8. Run the installer program, Setup.exe, on every system with an External Agent
Server
a) Export the new security certificates to every External Agent Server. See: Add
AMS Machine Works Certificates
b) Run this updater on every External Agent Server which has:

AMS Machine Works v2.0 117

Maintenance and Migration System Guide
July 2025

1. Asset Monitor Agent (AMA)

2. AMS 6500 ATG Agent v1.8 (ATGA)
3. Emerson Wireless Gateway Agent v1.8 (EWA)

c) Follow a separate procedure on every External Agent Server with a Portables

Agent installed. See: Update the Portables Edge Agent from v1.8 to v2.0

9. Recreate a User in the Machine Works OPC UA User group if you had one
configured before the update. See: Manage Certificates in OPC UA Clients and
Servers
10. The AMS Machine Works Vibration Analyzer (VibApp) must be uninstalled.
a) On your computer, open 'Add or remove programs'.
b) Select AMS Machine Works Vibration Analyzer, and click Uninstall.

11. Clear the cache of every browser used with AMS Machine Works before connecting
to the updated version of AMS Machine Works.

Figure 4-13: Delete Browsing Data

• Set Time range to: All time

• Select Cached images and files

CAUTION
Not clearing the browser caches can lead to incorrect system performance and the
loss of data.

12. Install the AMS Machine Works Vibration Analyzer again. See: Install the Vibration
Analyzer - VibApp

Update the Portables Edge Agent from v1.8 to v2.0

The Portable Agent must be manually updated from version 1.8 to version 2.0. Some steps
must be performed with tools from the operating system, and other steps must be
performed in the AMS Machine Works user interface.
The Portables Edge Agent must be updated in every location where it is installed.

118 AMS Machine Works v2.0

System Guide Maintenance and Migration
July 2025

Prerequisites
1. AMS Machine Works v2.0 must be installed. See: Update AMS Machine Works from
v1.8 to v2.0
2. AMS Machine Works v2.0 security certificates must be exported to every external
location where a Portables Edge Agent is going to be installed. See: Add AMS
Machine Works Certificates

Procedure
1. Disconnect every portable device in the AMS Machine Works user interface.
a) Launch the Portable Device Module.
b) Open the Devices tab.
c) Click Disconnect Device for every device which has a green or yellow status
in the Device List sidepanel.

2. Delete every Portable Agent in the AMS Machine Works user interface.
a) Launch the Portable Device Module.
b) Open the Agents tab.
c) For every Agent in the Agent List side panel, select Vertical Ellipsis → Delete
Agent

3. Open the Services app on every affected computer.

4. Stop the Emerson MW Portables Edge Agent service.
5. Uninstall the AMS Machine Works Portables Edge Agent.
a) Open the Add or remove programs control panel on your computer.
b) Search for AMS Machine Works Portables Edge Agent.
c) Click Uninstall.

6. Install the new Portables Edge Agent in every location where it is needed.
• For machines with no AMS Machine Works software installed, see: Agent Server
Installation
• For machines with some AMS Machine Works v2.0 software installed, see:
Modify an AMS Machine Works v2.0 Installation

7. Confirm that the security certificates have been updated.

8. Restore every Portable Agent in the AMS Machine Works interface. See: AMS
Machine Works User Guide, "Add and register an agent".
9. Reconnect every Device in the AMS Machine Works interface.
10. Every measurement point with a Portable Alert Set assigned to it must be
registered.
a) Every measurement point must be added a route.

AMS Machine Works v2.0 119

Maintenance and Migration System Guide
July 2025

Note
1. A maximum of 1040 measurement points can be included in a single
route.
2. Form as many routes as you need to include every measurement
point with a Portable Alert Set assigned to it.
3. For example, you can create a set of routes named from Temp Route
1 to Temp Route X.

b) To register the measurement points, click the Export Route control in the
Routes section of the Portable Device Module for every route.

Note
• This process can take a long time to complete. Perform this action at a
time when your system is not under a heavy load, for example, overnight.
• The process to generate a .rdf file will time out on the first time you use
the Export Route function.

11. When the registration process completes for every Temp Route X, check that
every measurement point was registered.
a) Click Export Route for every Temp Route X again.
This should complete quickly and generate a .rdf file.

Need help?
If a .rdf file is still not generated, wait some time and repeat this step.

12. For each measurement point on a component with an Alert Set configured:
a) Click the X next to the name of the Alert Set to clear the Portable Alert Set.
b) Select the same Alert Set from the dropdown list.

Note
The Parameter Sets do not have to be cleared and reset.

13. Repeat the previous step for every Component contained in every Machine Train /
Roll / Pulley Section contained in every level of your Folder / Site / Default
Enterprise hierarchy.

CAUTION
Any Alert Set which is not manually cleared and reset will not function correctly and
the Alert will not function.

120 AMS Machine Works v2.0

System Guide Support Tools
July 2025

5 Support Tools
A group of support tools and utilities is included with the installation package in the
SupportTools folder.

Note
The ..Installer_2.0.0.XXX\SupportTools folder is in the hierarchy created when
you unzipped the Installer_2.0.0.XXX.zip file. See: Installation Procedures

Each of these applications is dedicated to a specific purpose:

• The Pre-Installation Checklist tool checks for common problems which can disrupt or
halt the installation process. See: Pre-Installation Checklist Tool
• Contacting Emerson Product Support See: Sending Log Files to Emerson Product
Support
— The Installation Logs Compressor creates a compressed .zip file of the installation
logs which you can send to Emerson Product Support. See: Installation Logs
Compressor
— The Service Logs Compressor creates a compressed .zip file of the service logs
which you can send to Emerson Product Support. See: Service Logs Compressor
• The Data Retention Policy Tool enables you to manage how long your MongoDB
database retains measurement data. See: Data Retention Policy Tool
• The Uninstall Cleaner Utility aids you in ensuring that your system is free of any
components or files which may affect your system, or that could create errors when
upgrading or reinstalling AMS Machine Works. See: Uninstall Cleaner Utility
Note
For additional information on some common problems, read the Troubleshooting section.

5.1 Pre-Installation Checklist Tool

The Pre-Installation Checklist tool checks for common problems which can disrupt or halt
the installation process. It is located at:
C:\\..\SupportTools\PreInstallationChecklist.exe

Note
The Pre-Installation Checklist tool should be run prior to using the AMS Machine Works
installer. The tool should be used on every machine where you plan to use the AMS
Machine Works installer.

Procedure
1. Launch the PreInstallationChecklist.exe application from the
SupportTools folder to begin the analysis.

AMS Machine Works v2.0 121

Support Tools System Guide
July 2025

Figure 5-1: Initial Analysis

2. (Optional) Press the 'Y' key to perform an antivirus test, or press the 'N' key to skip
this test.
Note
Pressing the '?' key displays a short help text.

Attention
Antivirus software should be disabled while running the AMS Machine Works
Installer.

Figure 5-2: Perform Antivirus Test

a) Every antivirus system reacts differently. The example below shows the
response of Windows Defender.

Figure 5-3: Evaluation of Antivirus Test Results: One

122 AMS Machine Works v2.0

System Guide Support Tools
July 2025

Note
The test involves creating a non-volatile file in your default application
for .txt files, which may trigger an antivirus reaction. (See: www.eicar.com)
Antivirus reactions are different for each antivirus software, the response
pictured is for Notepad and Windows Defender.

b) If the test did not trigger an antivirus reaction, click N to proceed. Click Y to
indicate that an antivirus response occurred, and you will proceed and also
receive a warning to turn off your antivirus software during the installation
process.

Figure 5-4: Evaluation of Antivirus Test Results: Two

3. Press Enter to exit this application.

The application produces an output file: PreInstallationChecklist.txt. The
outcomes of these checks have lines beginning with [OK], [!!], or [XXX].
• [OK] indicates an acceptable outcome.
• [!!] indicates a warning about an unusual setting, but installation can proceed.
• [XXX] indicates a setting which must be corrected before proceeding with installation.

Figure 5-5: Example Output File

Note
The PreInstallationChecklist.exe application is typically located in the
SupportTools folder, and it will save its output to the same location. If you run the
application from another location it will save its output there.

AMS Machine Works v2.0 123

Support Tools System Guide
July 2025

5.2 Sending Log Files to Emerson Product Support

When users provide Emerson Product Support with detailed information, such as
screenshots and log files, the speed and effectiveness of Emerson Support's response is
greatly increased.
Users should take screenshots of any error messages that occur either during installation
or while using AMS Machine Works.

Preparing the Logs

There are two tools that enable you to get more detailed information from your
application logs and your service logs.
Follow the instructions found here:
1. Installation Logs Compressor
2. Service Logs Compressor

Sending the Installation Logs, Service Logs, and Screenshots to Emerson Product
Support
Gather the screenshots and compressed log files in one directory.
When you contact Emerson Product Support, they will provide a link to a SharePoint
location where the log files can be uploaded.
Contact Information
Services are delivered through our global services network.
1. To contact your local Emerson Sales and Service provider, click Contact Us.
2. To contact the Global Service Center, click Technical Support.

5.2.1 Installation Logs Compressor

The Installation Logs Compressor creates a compressed .zip file of the installation logs
which you can send to Product Support. The application is located at ..\SupportTools
\InstallationLogsCompressor.exe. You can run this application on any machine
where the AMS Machine Works Installer was used at least once.
Note
This utility works on both installation types:
1. AMS Machine Works Server
2. Agent Server

This application produces a file, InstallLogs_*computerName*.zip, which you can

send to Customer Support. The part of the file name, *computerName*, is the specified
by the computer the utility is run on.

Procedure
1. Run the application located at ..\SupportTools
\InstallationLogsCompressor.exe on the affected machine.

124 AMS Machine Works v2.0

System Guide Support Tools
July 2025

2. The application will run and then exit silently.

A file, named InstallLogs_*computerName*.zip, is created.

Note
The InstallationLogsCompressor.exe application is typically located in the
SupportTools folder, but it will save its output to the same location it is run from. For
example, if you run the application from the desktop, it will save its output there.

5.2.2 Service Logs Compressor

The Service Logs Compressor creates a compressed .zip file of the service logs which you
can send to Product Support. The application is located at ..\SupportTools
\ServiceLogsCompressor.exe. You can run this application on any machine where an
AMS Machine Works installation exists.
Note
This utility works on both installation types:
1. AMS Machine Works Server
2. Agent Server

This application produces a file, AMSMWLogs_*computerName*.zip, which you can send

to Product Support. The part of the file name, *computerName*, is the specified by the
computer the utility is run on.

Procedure
1. Run the application located at ..\SupportTools
\ServiceLogsCompressor.exe on the affected machine.
2. Input the number of days of logs to compress. (Default: 5)
A file, named AMSMWLogs_*computerName*.zip, is created.

Note
The ServiceLogsCompressor.exe application is typically located in the
SupportTools folder, but it will save its output to the same location it is run from. For
example, if you run the application from the desktop, it will save its output there.

5.3 Data Retention Policy Tool

The Data Retention Policy Tool is a tool which is used to set retention limits for data in the
MongoDB databases associated with your AMS Machine Works system.

CAUTION
This tool can delete your entire database. To ensure data integrity you should first perform
a Manual Backup of the MongoDB Database.

The tool runs in either from the command line or in Interactive Mode.

AMS Machine Works v2.0 125

Support Tools System Guide
July 2025

Running the Data Retention Policy Tool from the command line with the --non-
interactive flag is recommended preparation for using the tool as a scheduled task.
See: Schedule the Data Retention Policy Tool
To operate the Data Retention Policy Tool in Interactive Mode, follow the on-screen
prompts for instructions.

Command Line Options

From the command line the tool can be run with a combination of options, and can also
be set up as a scheduled task.
Tool name: MW.Utils.RetentionTool.exe
Tool location: C:\ProgramData\Emerson\AMS Machine Works Retention Tool
Command Line Tool options:
• -? | -h | -help — Show the help information.
• -b | --block-data — Set this option to remove block data.
• -c | --cut-off <date> — Measurement data older than the <date> (YYYY-MM-
DD) will be removed.
• -c | --cut-off <value> — Measurement data older than a number of time units
ago <value> will be removed.
Note
The <value> is set in units of days (D), months (M), or years (Y). For example:
— -c 3D
— -c 5M
— -c 7Y

• -cns | --connection-string <value> — Give the connection string for your

MongoDB database.
Note
The <value> of standard connection strings follows the form:
1. Internal MongoDB — mongodb://mwservice:<password>@localhost:27018/?
authSource=admin
2. External MongoDB — mongodb://
mwservice:<password>@<servername>:27018/?authSource=admin&tls=true

• -db | --database — Set the database to remove data from, typically

EmersonMWcoreData

Note
1. EmersonMWcoreData – The measurements, both scalars and block data.
2. EmersonMWCore — Do not modify this database unless you are a trained
service engineer with a specific reason.

126 AMS Machine Works v2.0

System Guide Support Tools
July 2025

3. EmersonMWOnline — Do not modify this database unless you are a trained

service engineer with a specific reason.
4. EmersonMWPortables — Do not modify this database unless you are a trained
service engineer with a specific reason.
5. EmersonMWLicense — Do not modify this database unless you are a trained
service engineer with a specific reason.

• --non-interactive — Turns off the default interactive mode.

• -r <number> — Set the time window resolution in minutes for thinning scalar data,
the <number> can be from 1 to 4 digits. Data is thinned to a maximum of 4 points,
(first point, last point, minimum point, maximum point), per the next larger time
period. For example, with r = 5 minutes, you will have a maximum of 4 points per 60
minutes.
The default window resolutions are:
— 0 — Removes data with a resolution <= 0 minutes, i.e., raw data. Leaves a
maximum of 4 points per 5 minutes.
— 5 — Removes data with a resolution <= 5 minutes. Leaves a maximum of 4 points
per 60 minutes.
— 60 — Removes data with a resolution <= 60 minutes. Leaves a maximum of 4
points per 240 minutes.
— 240 — Removes data with a resolution <= 240 minutes. Leaves a maximum of 4
points per 2880 minutes.
— 2880 — Removes data with a resolution <= 2880 minutes, i.e., all data.
• -s | --scalars — Set this option to remove scalar data.

Note
When you use the -s flag you must also use the -r flag to specify the amount of data
thinning to perform.

Usage and Examples

General usage: MW.Utils.RetentionTool.exe --non-interactive -db
EmersonMWcoreData -cns <connection string> <action flags>

Internal MongoDB Example: MW.Utils.RetentionTool.exe --non-interactive

-db EmersonMWcoreData -cns mongodb://mwservice:Abcd123!
@localhost:27018/?authSource=admin -s -r 2880 -c 2025-02-03

This command would cut off all scalar data older than February 3rd, 2025.
External MongoDB example: MW.Utils.RetentionTool.exe --non-interactive
-db EmersonMWcoreData -cns mongodb://mwservice:Abcd123!
@<server>:27018/?authSource=admin&tls=true -b -s -r 2880 -c 90

Where <server> is the name of your External MongoDB server. See: External MongoDB
Server Installation

AMS Machine Works v2.0 127

Support Tools System Guide
July 2025

This command would cut of both block data and scalar data older than 90 days.

5.3.1 Schedule the Data Retention Policy Tool

When you have determined a data retention policy that you want to automatically
implement, the operating system's Task Scheduler can schedule this.

Procedure
1. Determine which options you want to use with the Data Retention Policy Tool.
2. Launch the operating system's Task Scheduler, and click Create Basic Task... .

Figure 5-6: Task Scheduler

3. Enter a name and description for this task, and then click Next to continue.

Figure 5-7: Add a Name and Description

4. Set the period for your task, and then click Next to continue.

128 AMS Machine Works v2.0

System Guide Support Tools
July 2025

Figure 5-8: Set Period

5. Refine the period for the task, and then click Next to continue.

Figure 5-9: Refine Period

6. Set the type of Action to Start a program, and then click Next to continue.

AMS Machine Works v2.0 129

Support Tools System Guide
July 2025

Figure 5-10: Select Action as "Start a program"

7. Browse to the tool location: C:\ProgramData\Emerson\AMS Machine Works

Retention Tool, select MW.Utils.RetentionTool.exe, and click Open to
continue.

Figure 5-11: Browse to the AMS Machine Works Retention Tool folder.

8. Add the command line arguments you need to use for your installation, and then
click Next to continue.

130 AMS Machine Works v2.0

System Guide Support Tools
July 2025

Figure 5-12: Set Command Line Arguments

9. Review the task summary. If you are satisfied, then click Finish to complete the
process.

Figure 5-13: Review the Task Summary

5.4 Uninstall Cleaner Utility

The Uninstall Cleaner automatically detects and removes components left over by the
AMS Machine Works uninstallation process. See: Uninstall AMS Machine Works v2.0.
The application is located at ..\SupportTools\UninstallCleaner.exe. You can run
this application on any machine where an AMS Machine Works installation exists.
Note
This utility works on both installation types:
1. AMS Machine Works Server

AMS Machine Works v2.0 131

Support Tools System Guide
July 2025

2. Agent Server

The application detects if any AMS Machine Works components or 3rd Party components
remain on the system.

Prerequisites
Remove all AMS Machine Works components and 3rd Party components.

Procedure
1. Run the application located at ..\SupportTools\UninstallCleaner.exe on
the affected machine.
Need help?
a. If the UninstallCleaner.exe displays a list of program to remove, close
the program and refer to the uninstallation steps in this manual. See:
Uninstall AMS Machine Works v2.0

Figure 5-14: Remove Applications

b. If the UninstallCleaner.exe displays a list of processes to stop, close the

program and refer to the uninstallation steps in this manual. See: Uninstall
AMS Machine Works v2.0

Figure 5-15: Stop Processes

2. When the application displays a list of files to delete, and processes to stop, decide
if you want to delete the listed files.

CAUTION
This action will delete all of your data. Back up any databases that you might need.

132 AMS Machine Works v2.0

System Guide Support Tools
July 2025

Figure 5-16: Proceed to Delete Files

• N — (Default) By default no action will be taken.

• Y — Stop the processes listed and delete the files listed.
• ? — Display the help information.

When you choose Y, the files are deleted, and the processes are stopped.

AMS Machine Works v2.0 133

Support Tools System Guide
July 2025

134 AMS Machine Works v2.0

System Guide OPC UA Server
July 2025

6 OPC UA Server
AMS Machine Works includes OPC UA Server functionality running as a service to provide
secure communication between devices which support the OPC UA standard. The service
automatically launched if you have an active license for it.

Figure 6-1: OPC Service Name

Emerson MW Data Integration Module OPC Server

Figure 6-2: OPC Service Application

C:\Program Files\Emerson\AMS Machine Works\DOPC
\MW.Dim.OpcServer.exe

OPC Server functionality is not a standard part of every AMS Machine Works license. To
check if your installation has this functionality enabled go to the User Manager module in
AMS Machine Works and click the LICENSES tab.
You can upgrade your AMS Machine Works license at any time.
If you upgrade your AMS Machine Works license, you need to Reboot your server for the
functionality to become available.

6.1 Manage Certificates in OPC UA Clients and

Servers
To connect an OPC UA client to the AMS Machine Works OPC UA Server, you need to
generate a certificate in your client then add it as a trusted certificate for the server if a
user wants to use a certificate for user authentication.
The process has a few general steps:

Procedure
1. Generate a certificate in a compatible OPC client. See: OPC UA Software
Compatibility
a) With UaExpert, which is used in the Configure an OPC UA Client example
below, the file path is: C:\Users\Administrator\AppData\Roaming
\unifiedautomation\uaexpert\PKI\own\certs

2. (Optional) If you want users to use login and password authentication, then in the
operating system's Computer Management utility, add a User to the Machine
Works OPC UA Users group.

AMS Machine Works v2.0 135

OPC UA Server System Guide
July 2025

Figure 6-3: Add a User to the Group

3. Copy the certificate generated in Step 1 from the folder it was saved to.
a) Paste the certificate into: C:\ProgramData\Emerson\AMSMachineWorks
\Data\DOPC\pki\server\trusted\certs\

b) (Optional) If you want a user to use certificate based authentication, paste

the certificate into: C:\ProgramData\Emerson\AMSMachineWorks\Data
\DOPC\pki\user\trusted\certs\

Postrequisites
For an example installation with details see: Configure an OPC UA Client

6.2 Configure an OPC UA Client

This example shows how to connect a particular OPC UA client, UaExpert, to the AMS
Machine Works OPC UA Server,

Emerson MW Data Integration Module OPC Server

Other clients are also compatible. See: OPC UA Software Compatibility

Prerequisites
• Click the LICENSES tab in the User Manager to confirm that the OPC UA Server license
is enabled.
• Complete the steps found in: Manage Certificates in OPC UA Clients and Servers

136 AMS Machine Works v2.0

System Guide OPC UA Server
July 2025

• Server Information — From your OPC UA Client, supply the connection information of
the OPC UA Server. The URL for the OPC UA Server is opc.tcp://[server]:4840, where
[server] is the computer's name, IP address, or localhost of the AMS Machine Works
server.
• Security Settings — From your OPC UA client, select the security policy and message
security mode that applies to your network. The OPC UA Server supports these security
settings:
— Security Policy
• Aes256-Sha256-RsaPss
• Aes128-Sha256-RsaOaep
• Basic256Sha256
— Message Security Mode
• Sign
• Sign and Encrypt
• Encrypt Authentication Settings — An OPC UA client may be able to connect to the
OPC UA server via a predetermined username and password, or through certificate
validation. To enable an OPC UA client to connect to the server via username and
password, an Administrator must add the user to the Machine Works OPC UA Users
Windows Group.

Procedure
1. Download, install, and then run UaExpert from unified-automation.com. Enter
some value into the Organization field and then click OK to continue.

Figure 6-4: Start UaExpert

Note
This is third party software which is shown only for demonstration purposes. Other
clients are also compatible. See: OPC UA Software Compatibility

2. Select Server → Add... to begin configuring the server connection.

AMS Machine Works v2.0 137

OPC UA Server System Guide
July 2025

Figure 6-5: Add a Server

3. In the Custom Discovery section, double click the + symbol to add a server.

138 AMS Machine Works v2.0

System Guide OPC UA Server
July 2025

Figure 6-6: Click Custom Discovery

A popup window will open for you to enter the URL for the OPC UA Server.
4. Enter the server name, IP, or localhost, followed by :4840 and then click OK to
continue.

AMS Machine Works v2.0 139

OPC UA Server System Guide
July 2025

Figure 6-7: Enter URL

5. Configure the Security Settings, User, and Password.

140 AMS Machine Works v2.0

System Guide OPC UA Server
July 2025

Figure 6-8: Configure Settings

a) Select your Security Policy and Message Security Mode.

b) Enter the User name, select Store, and enter the Password.

Note
This is the User that you added in the Manage Certificates in OPC UA Clients
and Servers steps.

c) (Optional) Click Connect Automatically so that this server is always

connected.
d) Click OK to save your changes and continue.

AMS Machine Works v2.0 141

OPC UA Server System Guide
July 2025

You are now ready to connect to the server and acquire the hierarchy.
6. Right click on the server you have configured and select Connect.

Figure 6-9: Connect to Server

The client is now fully configured, and you can interact with the AMS Machine Works
hierarchy as shown in the bottom left of the window.

Figure 6-10: Configured Client with Hierarchy

142 AMS Machine Works v2.0

System Guide OPC UA Server
July 2025

6.3 OPC Tag Information and Tree Structure

The names of the OPC tags are usually dependent on the configuration of a system.
Virtually all data acquired by AMS Machine Works is available through OPC.
Hierarchy and node names, which reflect the hierarchy and structure in other parts of the
system, are automatically updated.
All nodes are identified by a UUID, or by an opaque byte string. IDs are unambiguous and
immutable, even if a node is renamed or relocated within the hierarchy.
At the top level of the OPC hierarchy tree (the server name), these tags are available:
Table 6-1: Example Nodes in the OPC Hierarchy
OPC Browse Path Node Description
The root node of the AMS Machine Works
AMS Machine Works system.

The Network Devices node contains sub-nodes

AMS Machine Works\Network for each type of Device or Gateway.
Devices

The Asset Monitors node contains sub-nodes

AMS Machine Works\Network for all the Asset Monitors defined in the system.
Devices\Asset Monitors

The Wireless Gateways node contains sub-

AMS Machine Works\Network nodes for all the Wireless Gateways defined in
Devices\Wireless Gateways
the system..

The name and device structure of a particular

AMS Machine Works\Network Asset Monitor, which was set in the Network
Devices\Asset Monitors\
Device Module.
[Device]

The name of a particular Wireless Gateway,

AMS Machine Works\Network which was set in the Network Device Module.
Devices\Wireless Gateways\
[Gateway]

The name of a particular Wireless Device, which

AMS Machine Works\Network was set in the Network Device Module.
Devices\Wireless Gateways\
[Gateway]\[Wireless Device]

The Health information about this Device.

AMS Machine Works\Network
Devices\Asset Monitors\
[Device]\Health

The Health information about this

AMS Machine Works\Network Measurement Source.
Devices\Asset Monitors\
[Device]\[Measurement Source]
\Health

AMS Machine Works v2.0 143

OPC UA Server System Guide
July 2025

Table 6-1: Example Nodes in the OPC Hierarchy (continued)

OPC Browse Path Node Description
A Measurement value from a specific
AMS Machine Works\Network Measurement Source in a specific Device.
Devices\Asset Monitors\
[Device]\[Measurement Source]\
[Measurement]

The internal temperature of a Device.

AMS Machine Works\Network
Devices\Asset Monitors\
[Device]\Temperature

This node contains the root of your Location

AMS Machine Works\[Site] hierarchy. The Site name is set in the Asset
Explorer module, and has an initial value of,
'Default Site'.
This node contains the name of a Location as
AMS Machine Works\[Site]\ defined in the Asset Explorer. A Location can
[Location]
contain multiple Location nodes, as well as
multiple Machine Train nodes.

This node contains the name and structure of a

AMS Machine Works\[Site]\ Machine Train as defined in the Asset Explorer.
[Location]\[Machine Train]

The overall Health data for a specific Machine

AMS Machine Works\[Site]\ Train in a specific Location.
[Location]\[Machine Train]
\Health

An Asset name as defined in the Machine

AMS Machine Works\[Site]\ Configuration Process, for example the name of
[Location]\[Machine Train]\
[Asset] a motor, gearbox, or pump.

The Health information of a specific Asset.

AMS Machine Works\[Site]\
[Location]\[Machine Train]\
[Asset]\Health

A specific Measurement Location name such as

AMS Machine Works\[Site]\ Inboard, Outboard, or a Custom Location.
[Location]\[Machine Train]\
[Asset]\[Measurement Location]

A Measurement from a specific Measurement

AMS Machine Works\[Site]\ Location.
[Location]\[Machine Train]\
[Asset]\[Measurement Location]
\[Measurement]

144 AMS Machine Works v2.0

System Guide Troubleshooting
July 2025

7 Troubleshooting
This section presents troubleshooting tips. You can also refer to Knowledge Base Articles for additional
troubleshooting tips.

7.1 Installation Troubleshooting

Any future issues with the installer that cannot be handled at the time of installation will be added here.
Table 7-1: Installation troubleshooting
Error Background Solution
None No unhandled errors to No issues to solve.
report.

7.2 OPC UA Server Troubleshooting

Table 7-2: OPC UA Server Troubleshooting
Error Background Solution
The hierarchy and After installing or First Solution: Allow several minutes after installing or rebooting
associated data are out rebooting of the AMS the AMS Machine Works server before attempting to connect
of sync between the OPC Machine Works server, it OPC UA clients.
UA client and the Train can take several minutes
to build the plant Second Solution: If several minutes have passed and the data in
Builder and / or the
hierarchy in the OPC UA the OPC UA client is still not in sync with the data in the software,
Network Device Module
client. do the following:
after the server reboots.
1. In Services on the AMS Machine Works server, locate:
Emerson MW Data Integration Module OPC
Server

2. Stop the service.

3. Restart the service.
4. Allow several minutes for the systems to sync.

7.3 Security Troubleshooting

Table 7-3: SSL and Certificates
Error Background Solution
Any issues not covered in For further information about any security issues refer to: AMS
either: Product Security Documentation (AMS-SEC-PSG-001)
1. AMS Machine
Works Security
2. Add AMS Machine
Works Certificates

AMS Machine Works v2.0 145

Troubleshooting System Guide
July 2025

7.4 Vibration Analyzer Troubleshooting

There are no currently known issues.
Table 7-4: Vibration Analyzer Troubleshooting
Error Background Solution

146 AMS Machine Works v2.0

System Guide Index
July 2025

Index
A Installation Procedures (continued)
Pre-Installation Steps (continued)
AMS Machine Works IIS Application Pools and Applications Server Installation Pre-Check 46
14 Stop Automatic Updates 49
Introduction
Symbols 7
C
Compatibility M
Device Compatibility 40
Emerson Software Co-Deployment 42 Maintenance and Migration
OPC UA Software 41 Backup and Restore Procedures
Manual Backup of the MongoDB Database 114
Modification Options
I Modify an AMS Machine Works v2.0 Installation
Installation Procedures 110
Agent Server Installation 69 Uninstallation Options
AMS Machine Works Server Installation Uninstall AMS Machine Works v2.0 105
Choose AMS Machine Works Server Installation Update from v1.8 to v2.0
54 Update AMS Machine Works
Choose Internal vs. External MongoDB Server 56 Update the Portables Edge Agent 118
Choose the Installation Drive 63, 74
Complete the Reboot Cycle 67, 78 O
Confirm Installation 66, 77
Enter a Server Name 55 OPC UA Server
Launch Installer 51, 70 Configure OPC UA Client 136
Provide Passwords or Connection String 58 Manage Certificates 135
Select which Agents Servers to Install 64, 75 OPC Tag Information 143
Software License Agreement 53, 71 OPC Tree Structure 143
External Agent Server Installation
Choose Agent Server Installation 72
Choose the Installation Drive 63, 74
S
Complete the Reboot Cycle 67, 78 Support Tools
Confirm Installation 66, 77 Data Retention Policy Tool
Connect to a Server 73 Set a Schedule 128
Launch Installer 51, 70 Pre-Installation Checklist Tool 121
Select which Agents Servers to Install 64, 75 Sending Log Files to Emerson Product Support
Software License Agreement 53, 71 Installation Logs Compressor 124
External MongoDB Server Installation 80 Service Logs Compressor 125
Post-Installation Steps Uninstall Cleaner Utility 131
Add AMS Machine Works Certificates 98 System Planning
Check Services 94 AMS Machine Works Architecture
Deconflict Posts 96 Agent Layer 18
Enable Domain User Login 97 AMS Machine Works Application Layer 13
First Launch of AMS Machine Works 99 AMS Machine Works Core 13
Install CSI USB Drivers 101 Hardware Layer 18
Install the Vibration Analyzer - VibApp 100 AMS Machine Works Security 43
Monitor DSS Processing Capacity 102 Compatibility 40
Restart Automatic Updates 97 Database Components 15
Set Data Retention Policy and Create Backups Database deployment
100 MongoDB Database Deployments 23
Pre-Installation Steps Deployment Scenarios
Locate the Installer 50 Typical Deployment Scenarios 20

AMS Machine Works v2.0 147

Index System Guide
July 2025

System Planning (continued)

Deployment Scenarios (continued)
Unsupported Deployment Scenarios 25
Network Port Availability 43
Other Components 17
Planning Steps 9
System Requirements
System Scalability
Number of Agent Servers per System Profile
34
Processor and Memory Specifications 32
Storage Capacity Requirements by System
Profile 37
Storage Type Requirements by System
Profile 36
Update Rates
AMS 6500 ATG Update Rates 40
AMS 9420 Update Rates 39
AMS Asset Monitor Update Rates 38
AMS Wireless Vibration Monitor Update
Rates 39
System Scalability 31
Windows Services 15

T
Troubleshooting
Installation Troubleshooting 145
OPC UA Server Troubleshooting 145
Security Troubleshooting 145
Vibration Analyzer Troubleshooting 146

148 AMS Machine Works v2.0

System Guide
July 2025

AMS Machine Works v2.0 149

 Rev. 3
2025

Emerson
835 Innovation Drive
Knoxville, TN 37932 USA
T +1 865-675-2400
F +1 865-218-1401
www.Emerson.com

©2025, Emerson.
The contents of this publication are presented for informational purposes only, and while every
effort has been made to ensure their accuracy, they are not to be construed as warranties or
guarantees, express or implied, regarding the products or services described herein or their use or
applicability. All sales are governed by our terms and conditions, which are available on request. We
reserve the right to modify or improve the designs or specifications of our products at any time
without notice.

All rights reserved. AMS is a mark of one of the Emerson group of companies. The Emerson logo is a
trademark and service mark of Emerson Electric Co. All other marks are the property of their
respective owners.