Honeywell VersatilisTM Transmitter

Release 100

Experion Equipment Health Monitoring

(EHM)

Configuration and User's Guide

34-VT-25-05
February 2023
 DISCLAIMER
This document contains Honeywell proprietary information.
Information contained herein is to be used solely for the purpose
submitted, and no part of this document or its contents shall be
reproduced, published, or disclosed to a third party without the
express permission of Honeywell International Inc.
While this information is presented in good faith and believed to be
accurate, Honeywell disclaims the implied warranties of
merchantability and fitness for a purpose and makes no express
warranties except as may be stated in its written agreement with and
for its customer.
In no event is Honeywell liable to anyone for any direct, special, or
consequential damages. The information and specifications in this
document are subject to change without notice.
Copyright 2023 - Honeywell International Inc.

2
CONTENTS
Chapter 1 - About this guide 5
Revision history 5
Related documents 5
Terms and abbreviations 5

Chapter 2 - Overview 7
Solution components 8
Specifications 9

Chapter 3 - Configuration 10
Topologies 12
Configure Experion EHM 13
User management 15
Configuring equipments 18
Creating Assets at Enterprise Level (Multi-site) 18
Creating a Site 18
Property values of an MQTT channel: 20
Creating Equipment Assets 21
Adding a Detector 21
Additional Configurations 25
Configure session idle timeout 25
Change Keep Alive Timer 25
Change time zone 26

Chapter 4 - Visualization 27
Plant Hierarchy 27
Birds Eye View 27
Drill Down dashboard 28

3
 Trends and Alarms 29
Grouping Trends 31
Trend history retention settings 32

Chapter 5 - Security 34
Physical security 34
Network security 34
VM security 34
MQTT security 35

Chapter 6 - Troubleshooting 36
Chapter 7 - LoRaWAN Uplink Payload Format 39
Notices 55

4
CHAPTER

1 ABOUT THIS GUIDE

This guide provides information to assist you in the configuration

and user management of the Honeywell Experion EHM.

Revision history
Revision Date Description

A February The initial release of the document for

2023 R100.

Related documents
Document
Document Name
Number

Honeywell Versatilis Transmitter Installation and 34-VT-25-01

User's Guide

Honeywell Versatilis Connect App User's Guide 34-VT-25-03

Honeywell Versatilis Transmitter Technical 34-VT-03-01

Specification

Honeywell Experion EHM Technical Specification EP03-070-

520

Terms and abbreviations

Terms Definitions

ATEX Appareils destinés à être utilisés en Atmosphères

Explosives

BLE Bluetooth® Low Energy

5
Chapter 1 - About this guide

Terms Definitions

CCoE Chief Controller of Explosives

CAPEX Capital Expenditures

iOS iPhone Operating System

IIoT Industrial Internet of Things

LoRa "Long Range" Radio Communication Technique

LPWA "Low Power, Wide Area" networking protocol

MPS Molecular Property Spectrometer

OPEX Operational Expenditure

UI User Interface

UOM Unit of Measure

6
CHAPTER

2 OVERVIEW

Experion® Equipment Health Monitoring (EHM) solution is based on

the proven Experion HS platform and can be used by plant managers
and reliability engineers in process manufacturing facilities to
monitor the health of rotating equipment. This enables maximizing
equipment availability and reliability. Built on the proven Experion HS
platform, it is reliable, flexible, easy to use, and scalable for any plant
setup. Honeywell EHM solution enables collection, contextualization,
and visualization of health-related parameters of industrial
equipment.
Key features:
n Secure connectivity to Honeywell Versatilis Transmitters over
MQTT.
n Supports LoRaWAN® communication technology through
Industrial standard Gateways.
n Configure sensor devices with corresponding Assets in a Plant
hierarchy.
n Sensor parameters data visualization using Birds Eye view and
Drilldown device dashboards.
n Live and historical trends of Sensor parameters to troubleshoot
issues.
n Displays equipment health alarms/ events when an alert payload
is received.
n Quick deployment and requires minimal engineering efforts.
n ISO 10816 standard-based Vibration alarm indications.
n A secure solution including User and Asset-based Security.
Architecture Overview:
Experion EHM solution uses proven Experion HS SCADA
functionality to store and organize the data received from Honeywell
Versatilis™ Transmitters. Experion EHM connects to the LoRaWAN
provider’s application server using a secure MQTT interface. EHM
uses web clients for visualization of health data where the collected
data is represented in the context of the industrial equipment it is
connected to. Web clients ensure zero client deployment cost where
any existing nodes within the network on the customer’s enterprise or
OEM system can be used to access data on the go.

7
Chapter 2 - Overview

The collected Equipment health data can also be shared with existing
supervisory control systems and other enterprise-level Management
Information System (MIS) for improved decision-making, thanks to
open yet secure interfaces supported by the Experion platform.

Figure 2-1: Architecture of the Experion EHM solution

For more information on the Architecture of the Honeywell Versatilis
Transmitter, see Experion EHM Technical Specification, EP03-070-
520.

Solution components
The Honeywell Experion EHM solution has four major solution
components such as:

1. Honeywell Versatilis Transmitter measures Surface temperature,

Humidity, Ambient Pressure, Ambient Temperature, Triaxial
Accelerometer, and Acoustics of the equipment.
For more information on configuring sensor parameters and
mounting options, see Honeywell Versatilis Transmitter
Installation and User's Guide, 34-VT-25-01.
2. Honeywell Versatilis Connect App provides the flexibility and
scalability to perform the complete device configuration,
simplifies maintenance tasks, and thereby saves time.
3. Secure communication gateway and provider supporting LoRa
wireless technology and LoRaWAN stack, connecting Versatilis
Transmitters to Honeywell EHM SCADA.
4. Experion EHM SCADA for visualization, web-based clients with
intuitive visualization of equipment health parameters, live and

8
 Chapter 2 - Overview

historical health trends.

Figure 2-2: Experion EHM solution components

For more information on Experion EHM solution, see Experion EHM
Technical Specification, EP03-070-520.

Specifications
The PC specifications to host the Experion EHM and/or LoRaWAN
server as VM are as follows:

Table 2-1: Specifications

Parameters Description

Operating Windows 10 Enterprise 2019 LTSC

system

Storage space 500 GB SSD/HDD

RAM 32GB

Processor Single or multiple Intel 2.5GHz, Octa Core or

greater.

Networking 1GBPS or 100 MBPS Ethernet

9
CHAPTER

3 CONFIGURATION

The following figure and table help the user to understand the
various process involved, right from the configuration of the
Honeywell Versatilis Transmitter to accessing the analytic solutions.

Figure 3-1: Honeywell Versatilis Transmitter configuration flow

Items Description

1 The Honeywell Versatilis Transmitter measures six

parameters on the target machine, which are as follows:

lSurface temperature
l Ambient Humidity

l Ambient temperature

l Ambient pressure

l Vibration

l Audio acoustics

For more information on set-up and available mounting

adapters, see Honeywell Versatilis Transmitter Installation
and User's Guide, 34-VT-25-01.

2 Honeywell Versatilis Connect App: The Honeywell

Versatilis Connect App enables users to connect to the

10
Chapter 3 - Configuration

Items Description

Honeywell Versatilis Transmitter through BLE using a

tablet, or smartphone. It helps user to configure the
sensor parameters to track the health of target equipment
which is installed/ fitted in the process industries.
For more information on configuring sensor parameters
in Connect app, see Online configuration section in
Honeywell Versatilis Connect App User's Guide 34-VT-25-
03.

3 LoRa Gateway:
Configure the LoRa Gateway in packet forwarder mode to
direct the LoRaWAN packets to the LoRaWAN server,
LoRaWAN IP address and server settings.
For more information on how to set up the LoRa Gateway,
refer the respective manufacturer's product
documentation.

4 LoRaWAN: The payload formatter within the third-party

LoRaWAN Infrastructure formats the incoming data from
LoRa gateways and securely transfers it through the
MQTT protocol to the Experion EHM.

1. Configure the LoRaWAN provider (e.g TTN, Chirpstack,

etc.) to start receiving data from the gateway and
exposing it over MQTT.
2. Configure gateway in LoRaWAN server.
3. Configure and activate the device based on the
selected activation mode and specify the RX1 delay &
RX2 frequency as xxxMHz based on the channel plan.
4. Apply the payload decoder.
5. After successfully configuring the device, ensure the
data is received as per the JSON format as shown in
Expected Periodic Event.

NOTE: Verify the device data on the

LoRaWAN provider by comparing the packet details
with the configured sensor parameters in the
Connect app.

5 Experion EHM

11
 Topologies

TOPOLOGIES
The below topologies explain the supported deployment options:

a. Single PC deployment:

The list of actions users need to perform to set up LoRaWAN

provider on-premises:

l A physical PC with the required specifications.

l A licensed VMWare Workstation Pro (recommended 17 or

above) is installed on the PC.
l A LoRaWAN provider that provides Network Server, Application
Server and optionally Join Server capabilities.
l A VM created with Ubuntu 22.04 or later OS.
The following figure describes the single PC deployment topology
of the Experion EHM setup:

Figure 3-2: Experion EHM and LoRaWAN on a

single machine
b. Dual PC deployment:
The list of actions users need to perform to set up LoRaWAN
provider on-premises:

l A physical PC with the required specifications.

l A licensed VMWare Workstation Pro (recommended 17 or

above) is installed on the PC.
l A LoRaWAN network service or Enterprise version from the
LoRaWAN service provider of your choice.

12
Topologies

Experion EHM application as VM and LoRaWAN on the separate

physical machine as shown in the following figure:

Figure 3-3: Experion EHM VM and LoRaWAN on

a separate machine

NOTE: Ensure that machines are deployed in the recommended

topology keeping the local security standards/ policies in
consideration.

Decoder:
Decoder is used to decode the LoRaWAN packet information into a
format such as JSON so that the user can interpret the data.
For more information on Experion interface expectations from the
decoder, see the sample of the LoRaWAN Packet Decoder and
LoRaWAN Uplink Payload Format.

Configure Experion EHM

Prerequisites:
n A PC with licensed VMWare Workstation 17 Pro or later software
installed.
n Configure the VM networks in VMWare Workstation Pro 17: Open
VMWare Workstation Pro 17 > Edit > VM network editor >

> Configure VMnet port as Host only.

n Copy the TAR file (provided by Honeywell in a flash drive along
with the transmitter) to the local storage (assuming the folder is
C:\ExperionEHM) and unzip the Experion EHM TAR file & extract
the OVA package.

13
 Topologies

n Decrypt the OVA package using the decryption key received from
Honeywell.

NOTE: Decryption key is provided in a printed format

separately. This key will permit users to unlock and access
the Experion EHM.

To import the OVA file in VMWare Workstation Pro 17 follow the

below procedure:

1. Open the VMWare Workstation Pro 17, and go to File > Open
which redirects to the local drive.
2. Select and double-click the VMware Virtual Machine
Configuration file from the extracted folder. The below screen
appears, select ExperionEHM > Power on this virtual machine.

Figure 3-4: ExperionEHM VM powering on

3. On the user login screen, enter the login credentials:
User name: Honeywell
Default Password: HONEXPEHM#1
Click OK. You are prompted to change the default password to a
new password if you are logging in for the first time.

The password is successfully updated and the Experion EHM VM

screen appears.

4. Click Windows > search & open Configuration Studio and connect
to the ExperionEHM server, the Configuration Explorer screen
appears.

14
Topologies

User management
User Management enables you to create users with different roles to
restrict access to various Experion EHM applications.
Based on the requirement you can create users with roles such as
Manager, Engineer, Supervisor, and Operator.

NOTE: The Administrator/ Manager has the privilege to create

the appropriate user groups such as Engineers, Supervisor and
Operators.

By default, the Honeywell user with Product Administrator role is

created while setting up Experion EHM.

NOTE: The Honeywell user further allows us to create other roles

such as Engineer, Supervisor, and Operator.

Click Windows > search and open Computer Management, the below
Computer Management screen appears which has the standard
groups (predefined by Honeywell).

Figure 3-5: Computer Management screen

15
 Topologies

To create users in the Experion EHM:

1. In the Computer Management > Local Users and Groups > Users,
the user group screen appears, right-click and select New User.
2. The New User pop-up appears, specify the user details such as
User name, Full name, password & confirm password and click
Create then Close.

NOTE: Enable Password never expires and other password

restrictions as needed.

Figure 3-6: Example of New user creation

The user (an example is shown as Operator1) is successfully
created and is displayed in the list of users.

3. Double-click on the created user, the properties pop-up appears,

and then select Member Of > Add.
4. A Select Groups pop-up appears click Advanced > Find out. The
search results display the list of user groups as shown below.

16
Topologies

Figure 3-7: Pop-up of Search Groups

5. Select Local Operators from the list, click OK > Apply and then OK.
Likewise create users like the Supervisor, Engineer & Manager
and assign them to the standard groups such as Local
Supervisor, Local Engineer & Product Administrator.
Accessibility Level

1. Engineers and Managers can use Configuration Studio to

configure the Experion EHM and its communications.
2. Operators and Supervisors can use the Experion EHM displays to
monitor the status of Equipment Assets and Honeywell Versatilis
Transmitter Detectors.

17
 Topologies

Configuring equipments
Creating Assets at Enterprise Level (Multi-site)
To add assets in the Enterprise Model Builder:

In the Configuration Studio, click . The System Name screen

appears, select Server> System Tasks> Configure assets for this
system.
The Enterprise Model Builder-Asset screen appears, select Assets >
right-click New ASSET.

Creating a Site
In the Configuration Studio, go to Control Strategy > SCADA Control>
Build channels the below Quick Builder screen appears, then select
Equipment.

From the list of Health Monitoring library, drag and drop the Site on
the Equipment list. A Create Equipment pop-up appears specify the
required details, and click OK.
The following screen appears, specify the property values for the new
equipment in the template:

18
Topologies

Figure 3-8: Screen of creating a site

NOTE: A channel is automatically created by specifying the

Channel Name in the Site template. To edit the property values
select and double-click on the channel. For more information,
see Property values of channel.

Table 3-1: Values of Creating a site

Items Description

Main SiteName: Specify the name of the site being

created. The site includes the assets on
which the detectors are mounted.

Asset Name: Select the associated asset

from the dropdown list

Communications Channel Name: Enter the required channel

in the value i.e., the channel name in which
the site is to be included.

MQTT Broker URL: The IP address (including

port details) of the VM on which the network
server is hosted.

The site is successfully created.

19
 Topologies

Property values of an MQTT channel:

Property Description

Name Specify the unique name for the channel.

Maximum of 10 alpha numeric characters.

Description (Optional) A description of the channel.

Maximum of 132 alphanumeric characters
including spaces.

Associated The Tag Name of the asset to be associated with

Asset the server.

Marginal The communication alarm marginal limit at

Alarm Limit which the channel is declared to be marginal i.e.,
Specify the threshold for the marginal alarm,
wherein when the Total Errors (related to
connections) exceeds the specified value, the
marginal alarm triggers. The alert indicates that
your channel communication is deteriorating

Fail Alarm The communication alarm marginal limit at

Limit which the channel is declared to be marginal i.e.,
Specify the threshold for the fail alarm (higher
value than the marginal alarm limit), wherein
when the Total Errors (related to connections)
exceeds the specified value, the fail alarm
triggers. The alert indicates that your channel
communication is seized.

Diagnostic The period, in seconds, between diagnostics

Scan Rate scans that verify communication integrity with
the LoRaWAN network server.

Keep Alive The maximum time that can pass without

Timer communication to maintain the connection. The
default value is 60 seconds.

MQTT Broker Provide the LoRaWAN server IP address along

URL with the port number.

20
Topologies

Creating Equipment Assets

To add an Equipment Asset to the site:
From the list of Health Monitoring library, drag and drop the required
asset such as Motor/ Compressor/ Gearbox / Pump on the
Equipment Library. A Create Equipment pop-up with the selected
asset template appears, specify the required details, and click OK.

The asset is successfully added to the site.

Adding a Detector
To add a detector on the equipment asset:
From the list of Health Monitoring library, drag and drop the Detector
on the Equipment Library. A Create Equipment pop-up appears,
specify the required details, and click OK.

21
 Topologies

Figure 3-9: Screen of adding a detector

Table 3-2: Adding detector

Items Description

Main Name: Specify the value i.e., the name of the

detector as needed.

Associated Asset: Select the associated asset

from the dropdown list.

Device Name: The Device Name must be

similar as specified in the LoRaWAN
network.

Communications Controller: Every newly created channel

automatically creates its controller which
enables the users to retrieve data from
channel to controller. Specify the name as
needed.

Channel Name: Select the required channel

from the dropdown list, to receive the data
from the network server for the particular
detector being added.

22
Topologies

Items Description

NOTE: Once the channel information

is specified and the detector is added
to the equipment pane, the server will
not permit changing the channel
name.
Remove the detector from the
equipment pane and re-add it if the
name of the channel has to be altered.

The detector is successfully added to the channel.

NOTE: The Point references are the sensor parameters that are
configured to the detector/ device using Honeywell Versatilis
Connect app. These point references are automatically
populated/downloaded to the newly added detector once the
communication is successfully established. For more
information on how to configure sensor parameters, see
"Honeywell Versatilis Connect app User's Guide, 34-VT-25-03".

Assigning Relationships(plant hierarchy):

Follow the below steps to build a connection between the added
detector and the asset.

1. Double-click the asset, the below screen appears click the

Relationships tab.
2. Click Add and specify the related details such as the related asset
(on which the detector is placed).

3. Click Details which displays all the communication entries that

need to be specified such as Asset ID, Location of the asset, Type
and Model of the asset.
The below figure briefs about the connection established between

23
 Topologies

the Detector, Asset and the Site.

Download configuration to the server:

Select the controller and follow the below procedure

n
Click (download) on the top ribbon of Configuration Studio.
n A pop-up appears, select the required server and click Download.
n A Result pop-up appears stating download is successful, click OK.
Follow the same procedure for newly created assets, sites and
channels to download the parameters by selecting individuals.

24
Topologies

Additional Configurations
Configure session idle timeout

NOTE: The default session idle timeout is 5 minutes, user can

change the timeout as per the requirements without exceeding
60 minutes.

The session idle timeout is configurable by updating the settings.json

file located in the C:\ProgramData\Honeywell\Experion
PKS\Server\Cuneus folder. Add a new property “sessionidletimeout”
and time in minutes as shown in the below syntax.

NOTE: Ensure to add comma(,) at the end of the previous syntax

before adding a new property i.e., sessionidletimeout and restart
the VM Server to update the changes.

Change Keep Alive Timer

The default Keep Alive Timer is 400 seconds and users have to
access the device controller's definition and change the Keep Alive
Timer based on the LoRa interval that was configured in the
Honeywell Versatilis Connect app for that device.
It is recommended to set the Keep Alive Timer value 2X times the
standard publish rate in sec. For example, if the standard LoRa
publish time is 30 minutes then set the Keep Alive Timer to 3600
seconds.
To change the Keep Alive Timer, select the controller from the
equipment pane and edit the Definition as shown in the below figure.

25
 Topologies

Figure 3-10: Definition screen

Change time zone

Change time zone settings by below procedure:
Click Windows > open Command Prompt as Administrator and type
tzutil /g then press Enter which displays the current standard time
details. Type tzutil /l then press enter which displays all available
time zones.
To set the time zone with daylight saving time, you need to write
tzutil /s “Time Zone” on the command line and press Enter.
For example, to set the time zone (UTC+05:30) Chennai, Kolkata,
Mumbai, New Delhi. Enter the command tzutil /s “India Standard
Time” and press Enter.

26
CHAPTER

4 VISUALIZATION

To view the template of the device:

n Click Windows > Microsoft Edge. The browser screen is opened
where the ExperionEHM web-based dashboard link is
bookmarked.
n Double-click the ExperionEHM bookmark, the web browser
dashboard screen appears (See Plant Hierarchy).

Plant Hierarchy
Users can view the Honeywell Versatilis devices under specific assets
involving Enterprise > Site> Area > Process cell > Asset > Device.

Figure 4-1: Plant Hierarchy

Birds Eye View

The Birds Eye view provides an enterprise-wide summary of
equipment, covering equipment level summary, alarms summary,
and drill down of detected issues.
To view the Birds Eye view of a site, double-click the required site.
Likewise, double-click equipment assets to view the summary of
devices in a site.

27
Chapter 4 - Visualization

NOTE: Site level view represents number of assets that have

issues but not total number of Issues and Asset level view
represents number of equipments that have issues.

The following figure briefs about Birds Eye view of a site:

Figure 4-2: Birds Eye view dashboard

Select individual equipment asset to detailed drill down view and
monitor the health of the target equipment.

Drill Down dashboard

Drill Down dashboards are used to give a detailed view of the sensor
parameters for an individual asset in a site.
The following figure briefs about the Drill Down dashboard of an
asset:

Figure 4-3: Drill Down dashboard

28
 Chapter 4 - Visualization

Trends and Alarms

Trends:
The Trend is useful to monitor and compare historical data for a
group of parameters in a graphical view. Trends make it easy to
identify problematic periods and dig deeper to address their potential
cause.

n
To monitor trends at the site level, click .
n Trends can also be displayed by choosing periods and intervals.
Alarms:
The alarms display the detected issues of the equipment which can
be segregated into Identified, Acknowledged, and Shelved.
n Identified:
n Acknowledged: Indicates that the alarms have been examined and
can be moved marked as acknowledged.
n Shelved: The alarms that keep on triggering on day to day basis
and are not critical can be suppressed by moving them to the
shelved list.

Figure 4-4: Trends and Alarms of the asset

29
Chapter 4 - Visualization

Table 4-1: Alarms

Alarm identification Description

Active alarm which is unacknowledged

Blinking Yellow

Acknowledged active alarm

Solid Yellow

Active alarm after the reset and also not

available.

A break is noticed in the trend indicates

PV is out of range and experion considers
Blinking Red as a bad value and it is not displayed in
the trends.

Colour-coded Vibration Alarms:

30
 Chapter 4 - Visualization

Grouping Trends
Users have the privilege to view or monitor trends of specific
parameters for equipment assets in the site by creating a Trend
group.
To create Trend Group:

1. In the Station > Configure > Trends and Groups Displays > Trends,
the following screen appears click on the empty title and create a
trend group.

Figure 4-5: Trends grouping screen

2. Click on ... at Point ID, a Point Browser pop-up select the

parameters and click Apply > Close.

3. From the dropdown at the Parameter, select PV and enable

Individual scales in EU.
Likewise, add all the Point IDs which you wish to include in the
group and click View Trend.

31
Chapter 4 - Visualization

The following trends screen explains an example of a trend group:

Trend history retention settings

Users can adjust history retention periods, including the duration
and number of samples, with the sysbld utility.
Follow the below steps to adjust history trends for a longer duration:

1. Click Windows > Honeywell Experion Tools > Start/ Stop Experion
PKS Server Utility. The Experion PKS Server pop-up appears.

2. Click > Advanced> Fullmode and enable Database Only.

NOTE: Calculate the disk storage before making any

changes. For more information on calculating disk spacing,
see Honeywell Experion User Documentation > Server and
Client Overview and Planning guide.

32
 Chapter 4 - Visualization

3. Open the command prompt and run sysbld -preserve -history, the
below screen appears type Y and press Enter until you reach the
History prompt.

Figure 4-6: Command prompt running sysbld

4. At the History prompt, enter 43200 to change the default record
rate (i.e., 1442) and press Enter until you notice Initializing history
and events files are running.

Figure 4-7: History record setting

The history retention changes are implemented and the SYSBLD
complete status is shown in the command prompt.

33
CHAPTER

5 SECURITY

Honeywell recommends implementing IPSEC to protect network

communications. Customers must implement physical access to the
servers and ensure that components and files are protected from
unauthorized access.
Follow company-mandated and country-specific security measures
applicable to your site in addition to these measures.

Physical security
n Ensure that the latest anti-virus software is installed.
n Enable the windows authentication mechanisms.
n Honeywell recommends having a strong password policy set for
all Windows nodes that connect to Honeywell Experion EHM
software. It is highly recommended to change the password at
regular intervals.
n It is highly recommended to avoid using self-signed certificates.
Use digital certificates issued by a trusted third-party Certificate
Authority.

Network security
By segregating the company’s site network into smaller (sub)
networks and by enforcing a rule set controlling which computing
devices are permitted to communicate with other computing devices,
the methods and level of access to sensitive information can be
minimized and an intruder’s ability to move across networks is
limited.
For more information, see VMWare workstation documentation.

VM security
n Perform an anti-virus scan on the pen drive/ flash drive before
inserting it into the physical machine on which the Experion EHM
is residing.

34
Chapter 5 - Security

n If the Honeywell Experion EHM is subject to physical threats, keys

can be protected in tamper-resistant storage (secure element),
where the extraction is extremely difficult.

MQTT security
n Experion EHM Enterprise dashboard components are installed on
the server on L4 Layer and should not be exposed on the internet.
For securing the Enterprise dashboard APIs, it is recommended
that the service communication is secured with HTTPS.

35
CHAPTER

6 TROUBLESHOOTING

The following table provides various troubleshooting scenarios in the

case of error or unexpected behavior and their corresponding
troubleshooting tips:

Table 6-1: Troubleshooting information

Problem Troubleshooting

Experion server and l Restart Experion server.

Channel gets freeze
l Reboot the system.

Time Go to Virtual Machine Settings> Options >

synchronization in VMWare tools and enable 'synchronize
Experion and guest time with the host'.
LoRaWAN

The individual This works as intended due to the PV is out-

parameter trend is of-range. Verify the alarms.
not displayed even
during healthy
communication

Cannot download Check whether the operator account you

parameters from used to log on to Configuration Studio has
Configuration the engr or mngr security level.
Studio to a server

Text overlapping in Adjust the screen resolution.

the web browser
dashboard

Change time zone See Change time zone.

User-configured Change the security level to "Mngr" and

channel and default enable all the channels manually from the
EHM channel do not following path:
enable Open Station> Configure> System

36
Chapter 6 - Troubleshooting

Problem Troubleshooting

Hardware> SCADA Controllers.

Re-initiate failed Experion performs a diagnostic scan for

device every 60 secs to re-initiate the
communication communication.

NOTE: Users can enable the Device

condition toggle button manually to
re-initiate the communication.

Device lost Set the Keep Alive Timer to 9999 under

communication Definition. For more information, see
frequently Change Keep Alive Timer.

Assets not "Scope of responsibility to Flex station

accessible by depends on the selection of asset profiles in
Operator Configuration Studio/ Stations.
If the assignment is direct, users can
change the level of access for each asset,
network node and system component you
want to assign to the flex station.
If an assignment is an asset profile, if the
station is currently running its scope of
responsibility will change according to the
change in asset profile. "

Server connection l Refresh the tab. If the issue persists,

lost / unexpected relaunch the Experion dashboard.
log out
l Manually configure the Session idle
timeout. For more information, see
Configure Idle session timeout.

Alarm data shows 0 The device is not supporting this feature.

Trend break-down Ensure Experion servers and host PC have

the same time stamps.

Alarm time stamp is The diagnostic scan is performed for every

not updating even if 8 hours that reports the alarm status.
the alarm triggers

37
 Chapter 6 - Troubleshooting

Problem Troubleshooting

multiple times Hence the alarm is not returned to normal

and the shown values are essentially live
values.

No data is displayed l Ensure the gateway and LoRaWAN server

are on the same network.

l Check gateway configurations such as

LoRa mode should be packet forwarder,
network settings must be manual, and
server settings must be LoRaWAN server
machine IP.
l Check the LoRaWAN server, if the
gateway & LoRa regions are configured
properly and the device is sending data
packets to the server.
l The device name must be identical as
mentioned in the MQTT broker.
l Verify the IP address and port details are
mentioned correctly as per the LoRaWAN
server.
l Check MQTT channel in the
ExperionEHM is healthy and running.

38
CHAPTER

7 LORAWAN UPLINK PAYLOAD FORMAT

MQTT Data:
Experion EHM expects the MQTT data to be available in the following
format:

Expected
MQTT topic Description
name

var_Ambient_ Maximum Ambient Temperature recorded since

Temp_Max the last data published by the device.

var_Ambient_ Minimum Ambient Temperature recorded since

Temp_Min the last data published by the device.

var_Ambient_ Average Ambient Temperature recorded since the

Temp_Avg last data published by the device.

var_Surface_ Maximum Surface Temperature recorded since

Temp_Max the last data published by the device.

var_Surface_ Minimum Surface Temperature recorded since

Temp_Min the last data published by the device.

var_Surface_ Average Surface Temperature recorded since the

Temp_Avg last data published by the device.

var_Ambient_ Maximum Ambient Pressure recorded since the

Pressure_Max last data published by the device.

var_Ambient_ Minimum Ambient Pressure recorded since the

Pressure_Min last data published by the device.

var_Ambient_ Average Ambient Pressure recorded since the last

Pressure_Avg data published by the device.

var_Ambient_ Maximum Ambient Humidity recorded since the

Humidity_Max last data published by the device.

var_Ambient_ Minimum Ambient Humidity recorded since the

39
Chapter 7 - LoRaWAN Uplink Payload Format

Expected
MQTT topic Description
name

Humidity_Min last data published by the device.

var_Ambient_ Average Ambient Humidity recorded since the last

Humidity_Avg data published by the device.

var_Vib_Accel_ Maximum Vibration X-Axis Acceleration recorded

X_Axis_Max since the last data published by the device.

var_Vib_Accel_ Minimum Vibration X-Axis Acceleration recorded

X_Axis_Min since the last data published by the device.

var_Vib_Accel_ RMS Vibration X-Axis Acceleration recorded since

X_Axis_RMS the last data published by the device.

var_Vib_Accel_ Maximum Vibration Y- Axis Acceleration recorded

Y_Axis_Max since the last data published by the device.

var_Vib_Accel_ Minimum Vibration Y- Axis Acceleration recorded

Y_Axis_Min since the last data published by the device.

var_Vib_Accel_ RMS Vibration Y- Axis Acceleration recorded since

Y_Axis_RMS the last data published by the device.

var_Vib_Accel_ Maximum Vibration Z- Axis Acceleration recorded

Z_Axis_Max since the last data published by the device.

var_Vib_Accel_ Minimum Vibration Z- Axis Acceleration recorded

Z_Axis_Min since the last data published by the device.

var_Vib_Accel_ RMS Vibration Z-Axis Acceleration recorded since

Z_Axis_RMS the last data published by the device.

var_Vib_ Maximum Vibration X-Axis Velocity recorded

Velocity_X_ since the last data published by the device.
Axis_Max

var_Vib_ Minimum Vibration X-Axis Velocity recorded since

Velocity_X_ the last data published by the device.
Axis_Min

var_Vib_ RMS Vibration X-Axis Velocity recorded since the

Velocity_X_ last data published by the device.

40
 Chapter 7 - LoRaWAN Uplink Payload Format

Expected
MQTT topic Description
name

Axis_RMS

var_Vib_ Maximum Vibration Y- Axis Velocity recorded

Velocity_Y_ since the last data published by the device.
Axis_Max

var_Vib_ Minimum Vibration Y- Axis Velocity recorded

Velocity_Y_ since the last data published by the device.
Axis_Min

var_Vib_ RMS Vibration Y- Axis Velocity recorded since the

Velocity_Y_ last data published by the device.
Axis_RMS

var_Vib_ Maximum Vibration Z- Axis Velocity recorded

Velocity_Z_ since the last data published by the device.
Axis_Max

var_Vib_ Minimum Vibration Z- Axis Velocity recorded

Velocity_Z_ since the last data published by the device.
Axis_Min

var_Vib_ RMS Vibration Z-Axis Velocity recorded since the

Velocity_Z_ last data published by the device.
Axis_RMS

var_Audio_Max Maximum Audio Acoustics recorded since the last

data published by the device.

var_Audio_Min Minimum Audio Acoustics recorded since the last

data published by the device.

var_Audio_ dBSPL Audio Acoustics recorded since the last

dBSPL data published by the device.

var_ Remaining battery percentage.

Remaining_
battery_perc

Example:
{

41
Chapter 7 - LoRaWAN Uplink Payload Format

"deduplicationId": "a4e3d513-9e28-423f-93d0-75f5c734b5db",
"time": "2023-03-10T08:56:30.472+00:00",
"deviceInfo":
{ "tenantId": "52f14cd4-c6f1-4fbd-8f87-4025e1d49242",
"tenantName": "LoRaWAN_tenant",
"applicationId": "34929bf1-a361-445b-a1bd-d6a3dc9162fb",
"applicationName": "Experion-EHM Integration Test",
"deviceProfileId": "12326133-22af-492e-9d64-d7160b2838da",
"deviceProfileName": "ExperionEHM",
"deviceName": "Test_Device",
"devEui": "3f113f113f113f11",
"tags": {} },
"devAddr": "3f113f11",
"adr": true,
"dr": 0,
"fCnt": 14221,
"fPort": 2,
"confirmed": false,
"data":
"LvAKZBcXFxcXF9jY2CkoKAAAAAAAAAAAAAEAAAEBAQEBATZBNgYA
AAAAAAAAAAAAAAAA",
"object": {
"var_Vib_Velocity_Y_Axis_RMS": 0.1,
"var_Audio_Min": 54,
"var_Vib_Velocity_X_Axis_RMS": 0,
"var_Vib_Velocity_Y_Axis_Min": 0.1,
"var_Ambient_Humidity_Max": 41,
"var_Audio_Max": 65,
"var_Ambient_Temp_Max": 23,
"var_Ambient_Humidity_Min": 40,
"var_Vib_Accel_X_Axis_RMS": 0,

42
 Chapter 7 - LoRaWAN Uplink Payload Format

"var_Vib_Velocity_Z_Axis_Max": 0.1,
"var_Vib_Accel_Z_Axis_Max": 0,
"var_Vib_Accel_Y_Axis_Max": 0,
"var_Surface_Temp_Min": 23,
"var_Vib_Velocity_Y_Axis_Max": 0.1,
"var_Vib_Accel_Z_Axis_RMS": 0,
"var_Ambient_Temp_Min": 23,
"var_Ambient_Pressure_Min": 948,
"var_Vib_Accel_Z_Axis_Min": 0,
"var_Remaining_battery_perc": 6,
"var_Ambient_Temp_Avg": 23,
"timestamp": 1678438446,
"var_Ambient_Humidity_Avg": 40,
"var_Vib_Accel_X_Axis_Max": 0,
"var_Vib_Velocity_X_Axis_Max": 0.1,
"var_Surface_Temp_Max": 23,
"var_Audio_dBSPL": 54,
"var_Surface_Temp_Avg": 23,
"var_Vib_Accel_Y_Axis_Min": 0,
"var_Vib_Accel_X_Axis_Min": 0,
"var_Vib_Velocity_Z_Axis_Min": 0.1,
"var_Ambient_Pressure_Max": 948,
"var_Vib_Velocity_X_Axis_Min": 0,
"var_Vib_Accel_Y_Axis_RMS": 0,
"var_Ambient_Pressure_Avg": 948,
"var_Vib_Velocity_Z_Axis_RMS": 0.1
},
"rxInfo": [
{
"gatewayId": "00800000a000a27f",

43
Chapter 7 - LoRaWAN Uplink Payload Format

"uplinkId": 50419,
"time": "2023-03-10T08:56:30.472695+00:00",
"timeSinceGpsEpoch": "1362473808.472s",
"rssi": -96,
"snr": -15.5,
"channel": 5,
"rfChain": 1,
"location": {
"latitude": 17.41945,
"longitude": 78.34555,
"altitude": 531
},
"context": "jPdJRA==",
"metadata": {
"region_common_name": "EU868",
"region_name": "eu868"
}
}
],
"txInfo": {
"frequency": 867500000,
"modulation": {
"lora": {
"bandwidth": 125000,
"spreadingFactor": 12,
"codeRate": "CR_4_5"
}
}
}
}

44
 Chapter 7 - LoRaWAN Uplink Payload Format

Event Details:
Experion expects on-detection Event details to be provided in the
following format:

Expected Event
Description
name

event_Ambient_ Ambient Temperature value when the alarm is

Temp_Data raised.

event_Ambient_ The type of alarm generated for Ambient

Temp_Type Temperature

event_Surface_ Surface Temperature value when the alarm is

Temp_Data raised.

event_Surface_ The type of alarm generated for Surface

Temp_Type Temperature

event_Ambient_ Ambient Pressure value when the alarm is

Pressure_Data raised.

event_Ambient_ The type of alarm generated for Ambient

Pressure_Type Pressure.

event_Ambient_ Ambient Humidity value when the alarm is

Humidity_Data raised.

event_Ambient_ The type of alarm generated for Ambient

Humidity_Type Humidity.

event_Vib_ The type of alarm generated for Vibration

Accel_X_Axis_ Acceleration on the X-Axis.
Type

event_Vib_ The type of frequency trigger band1 alarm

Accel_X_Axis_ generated for Vibration Acceleration on the X-
Freq1 Axis.

event_Vib_ The type of amplitude band1 alarm generated

Accel_X_Axis_ for Vibration Acceleration on the X-Axis.
Amp1

event_Vib_ The type of frequency trigger band2 alarm

Accel_X_Axis_ generated for Vibration Acceleration on the X-

45
Chapter 7 - LoRaWAN Uplink Payload Format

Expected Event
Description
name

Freq2 Axis.

event_Vib_ The type of amplitude band2 alarm generated

Accel_X_Axis_ for Vibration Acceleration on the X-Axis.
Amp2

event_Vib_ The type of frequency trigger band3 alarm

Accel_X_Axis_ generated for Vibration Acceleration on the X-
Freq3 Axis.

event_Vib_ The type of amplitude band3 alarm generated

Accel_X_Axis_ for Vibration Acceleration on the X-Axis.
Amp3

event_Vib_ The type of alarm generated for Vibration

Accel_Y_Axis_ Acceleration on the Y-Axis.
Type

event_Vib_ The type of frequency trigger band1 alarm

Accel_Y_Axis_ generated for Vibration Acceleration on the Y-
Freq1 Axis.

event_Vib_ The type of amplitude band1 alarm generated

Accel_Y_Axis_ for Vibration Acceleration on the Y-Axis.
Amp1

event_Vib_ The type of frequency trigger band2 alarm

Accel_Y_Axis_ generated for Vibration Acceleration on the Y-
Freq2 Axis.

event_Vib_ The type of amplitude band2 alarm generated

Accel_Y_Axis_ for Vibration Acceleration on the Y-Axis.
Amp2

event_Vib_ The type of frequency trigger band3 alarm

Accel_Y_Axis_ generated for Vibration Acceleration on the Y-
Freq3 Axis.

event_Vib_ The type of amplitude band3 alarm generated

Accel_Y_Axis_ for Vibration Acceleration on the Y-Axis.
Amp3

46
 Chapter 7 - LoRaWAN Uplink Payload Format

Expected Event
Description
name

event_Vib_ The type of alarm generated for Vibration

Accel_Z_Axis_ Acceleration on the Z-Axis.
Type

event_Vib_ The type of frequency trigger band1 alarm

Accel_Z_Axis_ generated for Vibration Acceleration on the Z-
Freq1 Axis.

event_Vib_ The type of amplitude band1 alarm generated

Accel_Z_Axis_ for Vibration Acceleration on the Z-Axis.
Amp1

event_Vib_ The type of frequency trigger band2 alarm

Accel_Z_Axis_ generated for Vibration Acceleration on the Z-
Freq2 Axis.

event_Vib_ The type of amplitude band2 alarm generated

Accel_Z_Axis_ for Vibration Acceleration on the Z-Axis.
Amp2

event_Vib_ The type of frequency trigger band3 alarm

Accel_Z_Axis_ generated for Vibration Acceleration on the Z-
Freq3 Axis.

event_Vib_ The type of amplitude band3 alarm generated

Accel_Z_Axis_ for Vibration Acceleration on the Z-Axis.
Amp3

event_Vib_ The type of alarm generated for Vibration

Velocity_X_Axis_ Velocity on the X-Axis.
Type

event_Vib_ The type of frequency trigger band1 alarm

Velocity_X_Axis_ generated for Vibration Velocity on the X-Axis.
Freq1

event_Vib_ The type of amplitude band1 alarm generated

Velocity_X_Axis_ for Vibration Velocity on the X-Axis.
Amp1

event_Vib_ The type of frequency trigger band2 alarm

47
Chapter 7 - LoRaWAN Uplink Payload Format

Expected Event
Description
name

Velocity_X_Axis_ generated for Vibration Velocity on the X-Axis.

Freq2

event_Vib_ The type of amplitude band2 alarm generated

Velocity_X_Axis_ for Vibration Velocity on the X-Axis.
Amp2

event_Vib_ The type frequency trigger band3 alarm

Velocity_X_Axis_ generated for Vibration Velocity on the X-Axis.
Freq3

event_Vib_ The type of amplitude band3 alarm generated

Velocity_X_Axis_ for Vibration Velocity on the X-Axis.
Amp3

event_Vib_ The type of alarm generated for Vibration

Velocity_Y_Axis_ Velocity on the Y-Axis.
Type

event_Vib_ The type of frequency trigger band1 alarm

Velocity_Y_Axis_ generated for Vibration Velocity on the Y-Axis.
Freq1

event_Vib_ The type of amplitude band1 alarm generated

Velocity_Y_Axis_ for Vibration Velocity on the Y-Axis.
Amp1

event_Vib_ The type of frequency trigger band2 alarm

Velocity_Y_Axis_ generated for Vibration Velocity on the Y-Axis.
Freq2

event_Vib_ The type of amplitude band2 alarm generated

Velocity_Y_Axis_ for Vibration Velocity on the Y-Axis.
Amp2

event_Vib_ The frequency trigger band3 alarm generated

Velocity_Y_Axis_ for Vibration Velocity on the Y-Axis.
Freq3

event_Vib_ The type of amplitude band3 alarm generated

Velocity_Y_Axis_ for Vibration Velocity on the Y-Axis.
Amp3

48
 Chapter 7 - LoRaWAN Uplink Payload Format

Expected Event
Description
name

event_Vib_ The type of alarm generated for Vibration

Velocity_Z_Axis_ Velocity on the Z-Axis.
Type

event_Vib_ The frequency trigger band1 alarm generated

Velocity_Z_Axis_ for Vibration Velocity on the Z-Axis.
Freq1

event_Vib_ The type of amplitude band1 alarm generated

Velocity_Z_Axis_ for Vibration Velocity on the Z-Axis.
Amp1

event_Vib_ The frequency trigger band2 alarm generated

Velocity_Z_Axis_ for Vibration Velocity on the Z-Axis.
Freq2

event_Vib_ The type of amplitude band2 alarm generated

Velocity_Z_Axis_ for Vibration Velocity on the Z-Axis.
Amp2

event_Vib_ The frequency trigger band3 alarm generated

Velocity_Z_Axis_ for Vibration Velocity on the Z-Axis.
Freq3

event_Vib_ The type of amplitude band3 alarm generated

Velocity_Z_Axis_ for Vibration Velocity on the Z-Axis.
Amp3

event_Audio_ The type of alarm generated for Audio acoustics.

Type

event_Audio_ The type of frequency trigger alarm generated

Freq1 for Audio acoustics.

event_Audio_ The type of amplitude alarm generated for

Amp1 Audio acoustics.

Example:
{
"deduplicationId": "a2a60595-a6ae-4e5d-93c1-5c6ce0d756ba",
"time": "2023-03-10T04:13:39.373+00:00",

49
Chapter 7 - LoRaWAN Uplink Payload Format

"deviceInfo": { "tenantId": "52f14cd4-c6f1-4fbd-8f87-4025e1d49242",

"tenantName": "LoRaWAN_tenant",
"applicationId": "34929bf1-a361-445b-a1bd-d6a3dc9162fb",
"applicationName": "Test1",
"deviceProfileId": "12326133-22af-492e-9d64-d7160b2838da",
"deviceProfileName": "ExperionEHM",
"deviceName": "Test_Device",
"devEui": "7102710271027102",
"tags": {}
},
"devAddr": "71027102",
"adr": true, "dr": 0,
"fCnt": 11019,
"fPort": 8,
"confirmed": true,
"data": "jURtOAAC",
"object": {
"timestamp": 946685069,
"event_Ambient_Temp_Type": 2,
"event_Ambient_Temp_Data": null
},
"rxInfo": [
{ "gatewayId": "00800000a000a27f",
"uplinkId": 24553,
"time": "2023-03-10T04:13:39.373388+00:00",
"timeSinceGpsEpoch": "1362456837.373s",
"rssi": -101,
"snr": -15,
"location": {
"latitude": 17.41945,

50
 Chapter 7 - LoRaWAN Uplink Payload Format

"longitude": 78.34555,
"altitude": 531
},
"context": "/UkPfA==",
"metadata": {
"region_common_name": "EU868",
"region_name": "eu868"
}
}
],
"txInfo": {
"frequency": 868100000,
"modulation": {
"lora": {
"bandwidth": 125000,
"spreadingFactor": 12,
"codeRate": "CR_4_5"
}
}
}
}

Periodic Event and Diagnostic Details:

Experion expects Periodic Event and Diagnostic details to be
provided in the following format:

Expected periodic event

Description
and diagnostic details

event_Ambient_Temp_Type The status of each alarm type for

Ambient Temperature.

event_Surface_Temp_Type The status of each alarm type for

51
Chapter 7 - LoRaWAN Uplink Payload Format

Expected periodic event

Description
and diagnostic details

Surface Temperature.

event_Ambient_Pressure_ The status of each alarm type for

Type Ambient Pressure.

event_Ambient_Humidity_ The status of each alarm type for

Type Ambient Humidity.

event_Vib_Accel_X_Axis_ The status of each alarm type for X-

Type Axis Vibration Acceleration.

event_Vib_Accel_Y_Axis_ The status of each alarm type for Y-

Type Axis Vibration Acceleration.

event_Vib_Accel_Z_Axis_ The status of each alarm type for Z-

Type Axis Vibration Acceleration.

event_Vib_Velocity_X_Axis_ The status of each alarm type for X-

Type Axis Vibration Velocity.

event_Vib_Velocity_Y_Axis_ The status of each alarm type for Y-

Type Axis Vibration Velocity.

event_Vib_Velocity_Z_Axis_ The status of each alarm type for Z-

Type Axis Vibration Velocity.

event_Audio_Type The status of each alarm type for

Audio acoustics.

Diag_Status Status of the Diagnostic parameters.

NOTE: In Experion EHM Application, the Diagnostic bit's 7th bit

will get set in LoRa packet when battery percentage drops below
20%.

Example:
{
"deduplicationId": "a4d2ecb2-085f-4187-9821-363560c7e7fd",
"time": "2023-03-10T12:27:18.528025170+00:00",
"deviceInfo": {

52
 Chapter 7 - LoRaWAN Uplink Payload Format

"tenantId": "52f14cd4-c6f1-4fbd-8f87-4025e1d49242",
"tenantName": "LoRaWAN_tenant",
"applicationId": "f5499769-20e9-482c-999a-d84a5ade9b19",
"applicationName": "Test1",
"deviceProfileId": "12326133-22af-492e-9d64-d7160b2838da",
"deviceProfileName": "ExperionEHM",
"deviceName": "Test_Device",
"devEui": "bfc060fbfbfc7147",
"tags": {}
},
"devAddr": "71d271d2",
"adr": true, "dr": 0,
"fPort": 11,
"confirmed": true,
"data": "EyILZAAAAAAAAAAAAAAAAAAA",
"object": {
"event_Vib_Accel_Z_Axis_Type": 0, "event_Vib_Accel_Y_Axis_Type": 0,
"event_Vib_Velocity_X_Axis_Type": 0,
"Diag_Status": 0,
"event_Battery_Type": 0,
"event_Vib_Accel_X_Axis_Type": 0,
"event_Vib_Velocity_Y_Axis_Type": 0,
"event_Audio_Type": 0,
"event_Ambient_Humidity_Type": 0,
"event_Ambient_Pressure_Type": 0,
"event_Ambient_Temp_Type": 0,
"timestamp": 1678451219,
"event_Vib_Velocity_Z_Axis_Type": 0,
"event_Surface_Temp_Type": 0
},

53
Chapter 7 - LoRaWAN Uplink Payload Format

"rxInfo": [
{
"gatewayId": "00800000a000a280",
"uplinkId": 63124,
"rssi": -59, "snr": 8,
"channel": 5,
"rfChain": 1,
"location": {},
"context": "Lgh23A==",
"metadata": {
"region_name": "eu868",
"region_common_name": "EU868"
}
}
],
"txInfo": {
"frequency": 867500000,
"modulation": {
"lora": {
"bandwidth": 125000,
"spreadingFactor": 12,
"codeRate": "CR_4_5"
}
}
}
}

54
CHAPTER

8 NOTICES

Trademarks
Microsoft is a registered trademark or trademark of Microsoft
Corporation in the United States and/or other countries.
Trademarks that appear in this document are used only to the benefit
of the trademark owner, with no intention of trademark infringement.

Other trademarks
Other brands or trademarks are trademarks of their respective
owners.
Trademarks that appear in this document are used only to the benefit
of the trademark owner, with no intention of trademark infringement.

Third-party licenses
This product may contain or be derived from materials, including
software, of third parties. The third party materials may be subject to
licenses, notices, restrictions and obligations imposed by the
licensor. The licenses, notices, restrictions and obligations, if any,
may be found in the materials accompanying the product, in the
documents or files accompanying such third party materials, in a file
named third_party_licenses on the media containing the product.

Documentation feedback
You can find the most up-to-date documents in the Support section
of the Honeywell Process Solutions website at:
https://process.honeywell.com
If you have comments about Honeywell Process Solutions
documentation, send your feedback to: [email protected]
Use this email address to provide feedback, or to report errors and
omissions in the documentation. For immediate help with a technical
problem, contact HPS Technical Support through your local
Customer Contact Center, or by raising a support request on the
Honeywell Process Solutions Support website.

55
Notices

How to report a security vulnerability

For the purpose of submission, a security vulnerability is defined as a
software defect or weakness that can be exploited to reduce the
operational or security capabilities of the software.
Honeywell investigates all reports of security vulnerabilities affecting
Honeywell products and services.
To report a potential security vulnerability against any Honeywell
product, please follow the instructions at:
https://www.honeywell.com/us/en/product-security.

Support
For support, contact your local Honeywell Process Solutions
Customer Contact Center (CCC). To find your local CCC visit the
website, https://process.honeywell.com/us/en/contact-us.

Training classes
Honeywell holds technical training classes that are taught by process
control systems experts. For more information about these classes,
contact your Honeywell representative, or see
http://www.automationcollege.com.

Factory Information
Honeywell International (India) Pvt. Ltd., Plot No. 2, Gat No. 181,
Village Fulgaon, Tal-Haveli, Pune, Maharashtra, 412216, India.

56