MSA Grid-FieldServer Manager Start-Up Guide

Operating Manual
MSA Grid – FieldServer Manager
Revision: 4.F
Document No.: T18661
Print Spec: 10000005389 (F)
MSAsafety.com
MSA Safety U.S. Support Information: EMEA Support Information:
1000 Cranberry Woods Drive +1 408 964-4443 +31 33 808 0590
Cranberry Township, PA 16066 USA +1 800 727-4377 Email:
Email: smc-support@msasafety.com smc-support.emea@msasafety.com
For your local MSA contacts, please go to our website www.MSAsafety.com
© MSA 2022. All rights reserved

Contents
1 Connecting to the FieldServer (for Field Installers) 7

1.1 Discover the IP Address of the FieldServer 7
2 Registering and Logging in (for Field Installers) 8

2.1 Create a FieldServer Manager Account 8
2.2 Login Details 9
2.2.1 New User Setup 9
2.3 Registration Process 11
2.4 Setting Time Zone 16
3 Using Customer Application Features 17

3.1 Generate Data Logging with System View 17
3.2 Data Log Viewer 20
3.3 Send a Snapshot of the Device Data with Device View 23
4 Logging into and Using the FieldServer Manager 24

4.1 Account Management 25
4.1.1 Editing the FieldServer Manager Profile 26
4.1.2 Changing the Password 26
4.2 FieldServer Management 27
4.2.1 Map Elements 27
4.2.2 FieldServer Data Table and Map 28
4.2.3 Individual FieldServer Details 29
4.2.4 Connecting to a FieldServer 30
4.2.5 Accessing FieldServers with the Optional Proxy Tunnel 31
4.2.6 Data Logs 32
4.3 FieldServer Events 33
4.3.1 Configure a Notification Delivery 34
4.3.2 Using System View Events to Generate FieldServer Events 35
4.4 General Notes for Using the FieldServer Manager 39
5 Additional FieldServer Manager Instructions for Administrators 40

5.1 Account Management 40
5.1.1 Add Custom Logo 41
5.1.2 Privacy Settings: Configure Visibility 41
5.2 FieldServer Management 42
5.2.1 Individual FieldServer Details 42
5.3 User Management 45
5.3.1 Managing Registered Users 46
5.4 Audit Logs 49
5.5 Webhooks 50
5.5.1 Description 50
5.5.2 Setup 51
5.5.3 My Webhooks 53
5.5.4 Edit a Webhook 53
5.5.5 Integration Information 55
5.5.6 Notifications Payload Sample (HTTP POST) 56
3 MSA Grid – FieldServer Manager

5.5.7 Standard Webhook Authentication Mechanism 57
6 Troubleshooting 58
6.1 Device Management Map 58
6.1.1 Device Pin Turns Gray Unexpectedly 58
6.1.2 Scroll Wheel Doesn’t Change Map Magnification 58
6.2 Lost FieldServer Manager Login Password 58
6.3 Connection Problems 59
6.3.1 The FieldServer Manager Cannot Remotely Connect to a Device 59
6.3.2 General Connection Notes 59
6.3.3 FieldServer Manager Connection Problems 60
6.4 Internet Browser Software Support 61
6.5 Data Retention when FieldServer Manager Connectivity is Lost 61
7 Useful Features 62
7.1 Security 62
7.1.1 PC to FieldServer Manager 62
7.1.2 FieldServer to FieldServer Manager 62
7.1.3 Viewing the Certificate 63
7.1.4 Certified by Provensec 65
7.2 Data Table Features 66
7.2.1 Additional Filter Options 66
7.2.2 Exporting Data 67
7.3 Device Management Map Controls 68
7.3.1 Mouse 68
7.3.2 Additional Controls 68
7.4 Session Time Out 68
7.5 User Roles – Type and Hierarchy 69
7.6 Using the Virtual Points Feature for Advanced Profile Configuration 71
7.6.1 Virtual Points Interface 72
7.6.2 Create or Edit a Virtual Points File 74
7.6.3 Import/Export Virtual Points for Profiles 75
7.7 Unix Time Stamp Information 77
7.7.1 Definition of a Unix Time Stamp 77
7.7.2 Unix Time Stamp Example 78
7.8 Webhook Access by Role 79
7.9 Give Administrator Users Access to a Webhook 80
7.10 Notification Message Descriptions 81
8 Limited 2 Year Warranty 82
MSA Grid – FieldServer Manager 4

Assumptions
The following items should be completed before moving forward with MSA Grid – FieldServer Manager registration.
• FieldServer products intended for FieldServer Manager registration must already be installed and running.
• FieldServer Gateway(s) and/or Router(s) are connected to the internet.
• The manufacturer’s FieldServer Manager Administrator has already set up an account.
• The field installer has received FieldServer Manager login information from the Administrator.

A Quick Start Guide for Field Installation
Connecting to the FieldServer
• Type the FieldServer IP Address into a web browser.

• Once connected, the FS-GUI or customer applications will be displayed.
Registering on FieldServer Manager
• Obtain FS Manager login details from support.

• Go to the FS Manager registration page and fill in ALL relevant information.
◦ For FS-GUI, click the FieldServer Manager button on the top right corner of the page.
◦ For the BACnet IoT Gateway, BACnet Router and the EZ Gateways, click the FieldServer Manager tab on the
left side of the page.
Accessing the FieldServer Manager
• Go to www.fieldpop.io and type in the appropriate login information as per registration login.
◦ For end users, contact the OEM for login details.
• Confirm the registered FieldServer is viewable from the Device Management tab.
Using the FieldServer Manager
• FieldServer Management
• User Management (Admin only)
• FieldServer Events
• Audit Logs
• Data Logs (Admin only)

1 Connecting to the FieldServer (for Field Installers)
Find the supplied IP Address for the FieldServer and type the IP Address into the local PC’s browser address bar to move
onto registering the FieldServer.
NOTE: The default IP Address for a ProtoAir, ProtoNode, ProtoCarrier or ProtoCessor are 192.168.1.24 with a
Subnet Mask of 255.255.255.0. All other FieldServer gateways have a default IP Address of 192.168.2.101 with
a Subnet Mask of 255.255.255.0. If the PC and FieldServer have different Subnets, assign a static IP Address
to the PC on the 192.168.1.xxx network.
If the FieldServer IP Address is unknown, follow the directions to discover an existing IP Address in the next section
(Section 1.1 Discover the IP Address of the FieldServer).
To change the FieldServer network settings, find directions in the specific FieldServer’s start-up guide.
NOTE: The FieldServer Manager uses TCP ports 10000, 80 and 443 by default.
1.1 Discover the IP Address of the FieldServer
• Check that a Cat-5 Ethernet cable (straight through or cross-over) is connected between the local PC and FieldServer
or the local PC is connected to the same Ethernet Network as the FieldServer.
• Ensure that FieldServer Toolbox is loaded onto the local PC. Otherwise, download the
FieldServer-Toolbox.zip via the MSA Safety website.
◦ Extract the executable file and complete the installation
• Double click on the FS Toolbox Utility and click Discover Now on the splash page.
• Check the FieldServer IP Addresses from the device listings.
• Type the appropriate IP Address into the browser address bar or click the Connect button to move onto registering the
FieldServer.

2 Registering and Logging in (for Field Installers)
If existing login details were received from the manufacturer’s support team, record the information and move on to Section
2.3 Registration Process. Otherwise continue to create a FieldServer Manager account.
2.1 Create a FieldServer Manager Account
A FieldServer Manager account is required to register a device onto the device cloud. If a FieldServer Manager account has
been previously setup or a Welcome to FieldServer Manager email was received, skip to Section 2.2 Login Details.
• To create new FieldServer Manager user credentials, follow the instructions in Section 2.3 Registration Process until
the User Credentials page is reached and then continue with the instructions below.
• Click the “Create an FieldServer Manager account” button, under the New Users heading.
• Enter the field installer’s email address into the window that appears.
• Click the “Create Account” button.

• Once this process is complete, continue to Section 2.2.1 New User Setup for new user setup instructions.

2.2 Login Details
If existing login details were received from the manufacturer’s support team, record the information and move on to Section
2.3 Registration Process. Otherwise continue to new user setup.
2.2.1 New User Setup
When a new user is generated, a “Welcome to FieldServer Manager” email will be automatically sent out to set up login
information.
Follow the instructions below to set up login details:
• Find the “Welcome to FieldServer Manager” email.
NOTE: If no email was received, check the spam/junk folder for an email from notification@fieldpop.io. Contact
the manufacturer’s support team if no email is found.

• Click the “Complete Registration” button to go to the FieldServer Manager webpage and set up user details.
• Fill in the name, phone number, password fields and click the checkbox to agree to the privacy policy and terms of
service.
NOTE: If access to data logs using RESTful API is needed, do not include “#” in the password.
• Click “Save” to finalize the user details.
• Click “OK” when the Success message appears.
• Record the email account used and password for future use.

2.3 Registration Process
• Find the FieldServer Manager icon using one of the cases described below:
• On the FS-GUI screen, click the FieldServer Manager icon on the top right corner of the page
NOTE: If the gateway opens on the Web Configurator page, the “Diagnostics and Debugging” button in the
bottom right corner of the page must be clicked to access FS-GUI.
◦ For FieldServers with customer application features, BACnet IoT Gateway, BACnet Router and any EZ Gateway,
click the FieldServer Manager tab

• The following page will appear, click the Get Started button to register the device.
NOTE: If a warning message appears instead of this page, see Section 6.3.3 FieldServer Manager Connection
Problems.

• To register, fill in the user details, site details, gateway details and FieldServer Manager account credentials.
◦ Enter user details and click Next
◦ Enter the site details by entering the physical address fields or the latitude and longitude then click Next

◦ Enter Name and Description (required) then click Next
◦ Enter user credentials and click Register Device

• Once the device has successfully been registered, a confirmation window will appear. Click the Close button and the
following screen will appear listing the device details and additional information auto-populated by the FieldServer.
NOTE: Update these details at any time by going to the FieldServer Manager tab or button and clicking the
Update Device Details button.

2.4 Setting Time Zone
The time zone of the FieldServer should be set to generate accurate data.
• Navigate to the FS-GUI page using one of the following methods:

◦ From Web Configurator – click the “Diagnostics and Debugging” button on the bottom right corner of the page
NOTE: The Web Configurator page shows the FieldServer parameters to configure. See gateway start-up guide
for additional information.
◦ If there is no “Diagnostics and Debugging” button in the bottom right corner of the page, check for a “Diagnostics”
tab along the top of the page or a “Diagnostics” link next to the copyright statement at the bottom center of the
page
• Click Setup on the navigation tree.
• Click “Time Settings”.
• Select the appropriate time zone then click Submit.

3 Using Customer Application Features
System View (Device List tab), Data Log Viewer (Data Log Viewer tab) and Event Logger (Event Log tab) are part
of the optional Application Engine platform, which allows local applications to easily browse and manage
FieldServer information or settings. These applications also have the option to supply FieldServer data to the
FieldServer Manager.
If the customer’s FieldServer uses these local applications, login to the FieldServer by entering the IP Address into a
browser on the local PC to see the pages described below.
NOTE: For instructions on using the Virtual Points feature go to Section 7.6 Using the Virtual Points Feature for
Advanced Profile Configuration.
3.1 Generate Data Logging with System View
• Once the device has appeared on the system view page, click on the device.
NOTE: A device will not appear on the system view on first login. The gateway must be configured before
devices can be seen in system view. Follow the gateway configuration instructions found in the
corresponding gateway start-up guide. If the start-up guide is not on hand, look up the guide online via the
MSA Safety website.
NOTE: The System View shows if a device is online or offline by highlighting the device green if online and
showing no highlight if offline. See example below.

◦ Clicking on the device will open the device view page, which shows all the data elements that can be gathered
from the device, location and status
• Click on the graph icon ( ) to the left of the listed data elements to open the Data Logging window.

• Select the type of logging for the data point and set the logging interval.
NOTE: The Data Log Viewer can log up to 3,000 values per data point with 2,500 points logged per minute if
data logging is set to Periodic or 140 points logged per minute if set to COV.
• Click Save to set the data logging settings and move on to Section 3.2 Data Log Viewer.
NOTE: Data is recorded for up to 30 days.

3.2 Data Log Viewer
NOTE: The Data Log Viewer can store up to 1,000 data points.
• Click the Data Log Viewer tab on the left side of the page.
• Click on the Settings button ( ) to set up data to graph.
• Click the checkbox next to the data element to graph.

◦ Any combination of elements can be selected
NOTE: A data element is only visible when it is set for data logging as shown in Section 3.1 Generate Data
Logging with System View.

• Click Submit to generate a graph for each element selected.
◦ To delete a log, check the boxes next to the properties to delete and click the Clear Logs button; then click “Yes” to
confirm
◦ After a few seconds, the graph should appear
• See below for instructions on controlling graphs:
To view individual values of data, scroll across the graph to show a text box that states each exact point and the location
of that point on the graph via a blue dot.
To view a graph of only select dates/time frames, move the cursor towards the miniature version of the graph that is
shown just below the full size graph. Hover the cursor over the miniature graph so that the cursor becomes a crosshair ( ).
Click and hold near the beginning or ending time frame desired, then drag the crosshair towards the ending or beginning
time frame; all within the confines of the miniature graph.

The full size version of the graph will populate accordingly.
Any additional edits to the time frame can be adjusted by clicking and dragging the wedge markers on either side of the
highlighted portion of the miniature graph.
To go back to the full graph, click on any faded portion of the miniature graph.
NOTE: The data selected in the Data Log Viewer is also available via the RESTful API, contact FieldServer
Technical Support for a copy of the RESTful API Start-up Guide.

3.3 Send a Snapshot of the Device Data with Device View
To get a snapshot of the summarized device data, follow the instructions below.
• Ensure that the FieldServer is registered to the FieldServer Manager (Section 2.3 Registration Process)
• Connect to the FieldServer via browser.
• Enter the Device View page via System View.
◦ Click the Device List tab (System View) then click on one device name
• Scroll to the bottom of the page to find the “Send Snapshot” field, enter an email address and click “Send” to receive
the data summary from the device.
• An email with the snapshot as an attached .txt file will appear in the previously referenced inbox.

4 Logging into and Using the FieldServer Manager
After the FieldServer is registered, go to www.fieldpop.io and type in the appropriate login information as per registration
credentials. For features exclusive to administrator accounts see Section 5 Additional FieldServer Manager
Instructions for Administrators.
For new users, the instructions for login and password setup are shown in Section 2.2.1 New User Setup.
If the login password is lost, see Section 6.2 Lost FieldServer Manager Login Password for recovery instructions.
NOTE: Sections 4.2 – 4.4 represent each of the tabs that appear at the top of the page once logged into the
FieldServer Manager and describe their functions. For information and instructions on Webhooks, request the
Webhooks Start-up Guide from support.

4.1 Account Management
Account management can be done on any screen by simply clicking on the user name in the top right corner of the page.
Once the user name has been clicked, the dropdown menu with options to edit Profile, Change Password and Logout will
appear.
See the subsections that follow for Account Management features and instructions.

4.1.1 Editing the FieldServer Manager Profile
• Click “Profile” in the dropdown menu.

• Enter or alter the cloud profile details as needed.
• Then click “Save” to update the new cloud profile information.
4.1.2 Changing the Password
To change the password, fill in the password information as needed.
NOTE: Hover over the password strength to see comments related to the entered password.

4.2 FieldServer Management
Gives an overview of devices registered to FieldServer Manager. This page includes the following features:
4.2.1 Map Elements
The map shows the location of all the devices registered on the FieldServer Manager using map pins.
Each pin is color-coded to show the device status. The table shows which device status each color represents.
Color Status
Grey Offline
Green Normal
Yellow Warning
Red Alarm
Blue Trouble
NOTE: See Section 7.3 Device Management Map Controls for details on map navigation.

4.2.2 FieldServer Data Table and Map
The FieldServer Data Table shows a list of Admin, Managers, Users and enterprise customers’ devices that are currently
registered on a FieldServer Manager account based on the permission level of the person logged in.
Registered FieldServers are shown in the data table on the left side of the screen. Individual FieldServers can selected and
filtered via data value search bars or selection via the pins on the map (grouped pins will separate when clicked).
The following fields are displayed and can be used as filters to find a specific FieldServers:
• Company
• FieldServer Name
• Description
• MAC Address
• State
• Product Name
• Product Version
• FieldServer ID
• Installer Company
• Installer Name
• Installation Date
NOTE: If certain fields are not present, they may be hidden. To make them viewable follow the Data Table
Dropdown Menu instructions in Section 7.2 Data Table Features.

4.2.3 Individual FieldServer Details
Click on the selected entry in the data table or click on its pin in the map to bring up the specific FieldServer’s general
information.
Click the Installer Information tab to open the installation information, including: installation date, company, phone number,
email and physical location.

4.2.4 Connecting to a FieldServer
• Once a specific FieldServer is selected and if it is available online the Connect button will be visible.
• Click on “Connect” to remotely access a device via HTTPS in a new tab.

4.2.5 Accessing FieldServers with the Optional Proxy Tunnel
NOTE: The Proxy Tunnel feature is optional and must be requested before shipment of hardware from smc-
support@msasafety.com.
• Once logged onto the FieldServer Manager, follow the instructions in Section 4.2.2 FieldServer Data Table and Map
and select a FieldServer that support the Proxy Tunnel.
• Click the Proxy Tunnel tab to open the Proxy Tunnel details.
• Create links to devices on the network by defining the Name, IP Address, Port and Path (if needed) and clicking the
Add button on the bottom row.
◦ An entry will be added to the list below based on the entered information
• Click the Connect button to access that device or click the trash can icon to delete the entry.

4.2.6 Data Logs
Click on the Data Logs tab to access and download the data logs for the FieldServer.
• Fill in the information as needed, selecting the data’s date range, format (JSON or CSV) and whether the file is
generated as a zip file.
◦ The date and time you select will assume the browser's time zone
• Click Download to generate and download the file to the local PC.
NOTE: Data Logs are time stamped in seconds form January 1st, 1970. See Section 7.7 Unix Time Stamp
Information for information on tracking time using a Unix time stamp.
NOTE: Go here to convert data log times to date format. To convert to local time, you must add the local time
zone offset. For spreadsheet conversions see the example shown here.

4.3 FieldServer Events
This page shows the FieldServer Events for all devices.
The following fields are displayed and can be used as filters to find a specific event:
• Event Type
• Event Message
• FieldServer Name
• MAC Address
• Company
• Date
For explanations of event messages, see Section 7.10 Notification Message Descriptions.

4.3.1 Configure a Notification Delivery
Notifications can be configured to be sent via email and/or SMS.
• Click the Notification Settings button on the top right side of the page.
• Click the corresponding checkbox to have notifications sent as email or SMS.

• Browse and select the device(s) for notification.
◦ The “*Events” section allows filtering by a specific event type as well
• Click “Save” to update settings.

4.3.2 Using System View Events to Generate FieldServer Events
System View and Event Logger are part of the optional Application Engine platform, which allows local
applications to easily browse and manage FieldServer information or settings.
If the customer’s FieldServer uses these local applications, login to the FieldServer by entering the IP Address into a
browser on the local PC to see the pages described below.
Creating Events
• Once the device has appeared on the system view page, click on the device name.
NOTE: The System View shows if a device is online or offline by highlighting the device (a color based on its
status) if online and showing no highlight if offline. See example below.

◦ Clicking on the device will open the device view page, which shows all the data elements that can be gathered
from the device, location and status.
• Click on the bell icon ( ) next to a data element to attach an event and open the Event Settings window.
NOTE: Event Settings allow the FieldServer to go into Trouble, Warning or Alarm status based on the
parameters entered for the data element selected. These events appear on the FieldServer Event Logger page
and populate onto the FieldServer Manager’s FieldServer Events page if the FieldServer is registered.

• Click the Add Event button to create a new event.
The following parameters are available for Event configuration:
Type – select between Alarm, Waring or Trouble
Condition – select condition that activates the alarm
Value – enter the value that applies to the selected condition
Deadband – (only available if applicable) the minimum difference in value necessary to take the alarm from active to
inactive
Suppress Condition Checkbox – enables a suppress condition which prevents an alarm from going active when this
condition for a different data element is met; once enabled Suppress Condition parameters will become available
The following parameters are available for the Suppress Condition:
Point Name – select a different data element to apply this condition
Condition – select condition that prevents alarm activation
Value – enter the value that applies to the selected condition
Deadband – the minimum difference in value necessary to remove the suppress condition
• Once all parameters are entered, click Save to set the event.
• Repeat these steps to add more events as needed.

Existing Events can be viewed back on the Event Settings window.
• Click the trashcan icon ( ) on the right side of the specific event’s row to delete an event
Viewing FieldServer Events
• Alarm Events can be viewed on the device by clicking on the Event Log tab to open the Event Logger Page.
• On the FieldServer Manager, this information can be viewed on the FieldServer Events page if the device is registered
(Section 4.3 FieldServer Events).
• Additionally, device status information will populate on the Device Management page via color coded icons (Section
4.2.1 Map Elements).

4.4 General Notes for Using the FieldServer Manager
• See Data Table Features (Section 7.2 Data Table Features) for information on how to filter or export data for the
sections that follow.
• See Section 7.4 Session Time Out for FieldServer Manager Session Time Out details.

5 Additional FieldServer Manager Instructions for Administrators
5.1 Account Management
Account management can be done on any screen by simply clicking on the user icon in the top right corner of the page.
Once the icon has been clicked, the dropdown menu with options to edit the Profile, Change password, Add custom logo,
Privacy settings and Log out will appear.
See the subsections that follow for administrator Account Management features and instructions.

5.1.1 Add Custom Logo
The logo can be customized by uploading a new company logo.
To upload a new company logo:

• Click the pencil icon to open a browser window.
• Select the image to upload.
• Click “Update” to make changes or “Cancel” stop the change.
5.1.2 Privacy Settings: Configure Visibility
The following setting options give MSA Safety basic to full access to devices connected to the FieldServer Manager.
NOTE: If support is needed, MSA Safety Technical Support may require that these settings are changed to
assist in the troubleshooting process.

5.2 FieldServer Management
5.2.1 Individual FieldServer Details
Click on the selected entry in the data table or click on its pin in the map to bring up the specific FieldServer’s general
information.
Click the Installer Information tab to open the installation information, including: installation date, company, phone number,
email and physical location.

Firmware Update
NOTE: Only an Enterprise Administrator can upgrade the firmware.
The Firmware update process is as follows:
• MSA Safety sends the OEM a new firmware version for testing.
• The OEM Admin uploads a new firmware version once they have qualified it. The firmware is uploaded by clicking the
Upload Firmware button located on FieldServer management page (Section 4.2.1 Map Elements), selecting the
.img or .bin file (supplied by MSA Safety) and clicking Upload.
• When the Enterprise Administrator logs in and selects a device, there will be a Upgrade Firmware button at the
bottom of the general information tab.
Clicking on this button will show a list of firmware versions that have been uploaded by the OEM Administrator.
• After selecting the version and clicking the Upgrade button, confirm the update by clicking the Submit button in the
next window. The device will be updated and restarted.

Deregister a Device from the FieldServer Manager
NOTE: Only an Administrator can deregister a device from the FieldServer Manager.
The only way to remove a device from the FieldServer Manager platform is to deregister it by doing the following:
• Log onto the FieldServer Manager platform with Administrator credentials.

• On the FieldServer Management page, find and then select the FieldServer you wish to deregister. (Section 4.2.1
Map Elements).
• Click on the Deregister button that appears at the bottom of the General Information tab.
• Then click the Deregister button on the pop-up window that appears.

5.3 User Management
This page shows all registered user details.
The following fields are viewable and can be used as filters:

• First Name
• Last Name
• Company
• Role
• Email
• Edit
• FieldVEU Role

5.3.1 Managing Registered Users
NOTE: For detailed information about user roles see Section 7.5 User Roles – Type and Hierarchy.
The User Management page also allows the following functions:
Add a New User
• Click the “Add New User” button on the top right side of the page.
• Fill in the new user’s email and role.
NOTE: Go to Section 7.5 User Roles – Type and Hierarchy for details on what functions apply to specific roles.
NOTE: If the “Role” field is set to “OEM Admin” the “Company” field will appear. This allows selection of an
existing company on the system (via dropdown menu) or adding a new company by clicking the “+” sign and
typing in the company name desired.
• Click “Create” to generate the new user and send out a FieldServer Manager welcome email.
NOTE: The FieldServer Manager will automatically send an email to the newly created user for account setup.
See Section 2.2.1 New User Setup for walkthrough instructions.

Assign or Remove Devices for an Existing User
• Click the Edit icon ( ) in any user row to edit the details for that user.
• Scroll down to the Assigned FieldServers section.

• Fill in the listed checkboxes to assign devices or deselect checkboxes already ticked to remove.
• Click the Save button to record the details.

Edit an Existing User
• Click the Edit icon ( ) for any user row to edit the details for that user.
• Change all necessary fields.

• Scroll to the bottom and click the Save button to record the updated details.
Delete a User
• Click the Delete User button at the bottom of the specific user’s edit screen.
• Click “Delete User” on the warning screen to confirm deletion.

5.4 Audit Logs
This page shows the events for each user on FieldServer Manager and lists the relevant details.
The following fields are viewable and can be used as filters:

• User
• Role
• Message
• Date
Additionally, the Date filter includes the ability to search between dates and times to get a snapshot of a specific time frame
of events.
NOTE: See Section 7.7 Unix Time Stamp Information for information on tracking time using a Unix time stamp.

5.5 Webhooks
5.5.1 Description
NOTE: One or multiple FieldServers with Data Log Viewer functionality must be registered to the FieldServer
Manager to use Webhooks. For general FieldServer Manager registration and use instructions, see the MSA
Grid - FieldServer Manager Start-up Guide.
The FieldServer Manager Platform runs a key component called the Data Log Viewer. The Data Log Viewer component
keeps track of all the subscribed gateways’ data logs and performs the following:
• Stores data log files on the FieldServer Manager server.

• Publishes data changes on the FieldServer Manager server for use by other components such as Webhooks.
When the Webhooks component receives new FieldServer gateway data logs the Webhooks component performs the
following procedure:
1. Determines which Webhook destinations or URLs request this data.
2. Transforms the data to a format compatible with the receiving 3rd party.
3. Posts the transformed data to the interested server URLs.

5.5.2 Setup
Login to the FieldServer Manager and follow these steps to configure a Webhook:
1. On the FieldServer Manager landing page, click on the Webhooks tab.
2. Once on the Webhooks page, click the New Webhook button, found on the top right of the page.

3. When the Webhook Configuration Window appears, select a partner server that will receive the data logs to reveal
the full configuration window.
4. Populate the fields as needed to connect to the partner server.
NOTE: These fields will change from one partner to the next.
5. Select the FieldServer gateways (already registered to the FieldServer Manager) to monitor from the listings under
the “Select Devices” heading.
NOTE: To display the Device ID column click in the top right corner of the device selection table and click on
Device ID in the dropdown menu.
NOTE: Use the field above the listings to search by Device Name, MAC Address, Description or Device ID.
6. Then click the Save button.
Once Webhook configuration is complete, the server will attempt to connect with the server.

5.5.3 My Webhooks
Once a Webhook exists it will appear in the owner’s My Webhooks section on the Webhooks page.
5.5.4 Edit a Webhook
Click the pencil icon ( ) on the desired Webhook and then change the Configuration settings as needed. Click the Save
button to keep the changes.

Delete a Webhook
Click the trashcan icon ( ) on the desired Webhook and then click the Yes button on the warning window to delete it.
View Webhook Logs
Click the log icon ( ) on the desired Webhook to view the messages related to that Webhook.

5.5.5 Integration Information
Standard Webhook Message Structure

This section will provide structural information for messages passed to a remote sever for the following payload types:
• Live Data Payloads
• Historical Data Payloads
• Device Notification Payloads
Authentication mechanism information is also included to provide an example when a user needs to specify an
authentication token.
Initiate Module Discovery

The ping payload only gets posted when the user creates a webhook for the first time or edits a webhook setting. This is a
basic mechanism to check that our connection to the remote server is successful or not.
{
"type": "ping"
}
The rest of the payloads always have the following core structure:
{
“deviceId”: “”, // Unique ID of the device registered on FieldServer Manager
“type”: “”, // Type of data being posted (liveData, notificaiton, historian)
“data”: {}, // The main information that this payload is trying to serve
}
Historical Data Payload Sample (HTTP POST)

The “data” object is in the form of a nested object. Each leaf of the tree in this object contains an array of values and
timestamps.
A timestamp is the Epoch time in milliseconds.

{
"deviceId": "myUniqueDeviceId",
"type": "historian",
"data": {
"BAC_IP_Falcon_Hydronic_1_": {
"BURNER_ENABLE": [
{
"value": 0,
"timestamp": 1544164781100
},
{
"value": 1,
"timestamp": 1544164781535
}
],
"Main_Valve": [
{
"value": 1,
"timestamp": 1544164740000
},
{
"value": 0,
"timestamp": 1544164771534
}
],
}
}

Live Data Payload Sample (HTTP POST)
The “data” object is in the form of a nested object. Each leaf of the tree in this object contains a single object with a value and
a timestamp.
A timestamp is the Epoch time in milliseconds.

{
"deviceId": "myUniqueDeviceId",
"type": "liveData",
"data": {
"BAC_IP_Falcon_Hydronic_1_": {
"BURNER_ENABLE": {
"value": 0,
"timestamp": 1544164781535
},
"Main_Valve": {
"value": 12,
"timestamp": 1544164781535
},
},
}
5.5.6 Notifications Payload Sample (HTTP POST)
The “data” object contains a single flat object that includes the following keys:
• notificationMessage
• notificationType
• macAddress
• oem
• company
• eventDate
{
"deviceId": "paperjackal_Hy-",
"type": "notification",
"data": {
"notificationMessage": "System Status Change: Normal >>> Alarm",
"notificationType": "System Status",
"macAddress": "00:50:4E:60:00:30",
"oem": "SMC",
"company": "SMC",
"eventDate": "Fri, 07 Dec 2018 07:01:00 GMT"
},
}

5.5.7 Standard Webhook Authentication Mechanism
When a user specifies a security token for their webhook configuration, it will pass a message header called ‘m-signature’.
This contains the HMAC hex digest of the JSON message body converted into a string format. The HMAC hex digest is
generated using the sha512 hash function and the security token as the HMAC key.
Below is a sample of the header structure:

POST /payload HTTP/1.1
Host: localhost:4567
m-signature:
e945c57533152b578a07903a9d8bd48b41897733e1845a4b434ec8809956928aa2864e9756746ff00baf88c64b735b53ae14f77188122b7a6ecb1d686c3
bfacf
Content-Type: application/json
Content-Length: 22
{
"type": "ping"
}

6 Troubleshooting
6.1 Device Management Map
6.1.1 Device Pin Turns Gray Unexpectedly
If a device pin turns gray on the Device Management Page:
• Check FieldServer is connected to the internet.

• Ensure power LED is lit on the FieldServer.
6.1.2 Scroll Wheel Doesn’t Change Map Magnification
If the mouse scroll wheel is used and the Device Management Map shows the message “Use ctrl + scroll to zoom the map”,
hold down the Ctrl key while using the wheel to zoom in or out of the map.
6.2 Lost FieldServer Manager Login Password
If the password is lost, follow the below instructions:
• Click “Forgot Password” on the FieldServer Manager Login Screen.
• Once the Password Reset Window appears, enter the email address of the FieldServer Manager account and click
Submit. Then close the window that appears.
• Click on the “Reset Your Password” button in the email sent from notification@fieldpop.io to reset the FieldServer
Manager password.
• Enter and confirm the new password then click Save.

6.3 Connection Problems
6.3.1 The FieldServer Manager Cannot Remotely Connect to a Device
Check if the screen below appears when trying to remotely connect to a device. If so, try clearing the DNS cache (in the cmd
window type "ipconfig /flushdns") or validate the local computer’s DNS against the network DNS settings. Contact technical
support if the problem persists.
6.3.2 General Connection Notes
• It is important to check that the FieldServer’s network settings are set up with the following Domain Name Server
(DNS) settings for proper communication:
◦ DNS1 = 8.8.8.8
◦ DNS2 = 8.8.4.4
• Any time changes to the network settings are done, remember to click “Update IP Settings” and then power cycle or
soft reboot the FieldServer to save the new settings.
• The FieldServer Manager uses TCP ports 10000, 80 and 443 by default.

6.3.3 FieldServer Manager Connection Problems
If there is a problem with connecting to the FieldServer Manager a warning will appear.
Follow the directions presented in the warning message and check that the DNS settings meet the requirements mentioned
in Section 6.3.2 General Connection Notes.

6.4 Internet Browser Software Support
The following web browsers are supported:

• Chrome Rev. 57 and higher
• Firefox Rev. 35 and higher
• Microsoft Edge Rev. 41 and higher
• Safari Rev. 3 and higher
NOTE: Internet Explorer is no longer supported as recommended by Microsoft.
NOTE: Computer and network firewalls must be opened for Port 80 to allow FieldServer GUI to function.
6.5 Data Retention when FieldServer Manager Connectivity is Lost
When connectivity is lost to the FieldServer Manager, the registered assets have an in-memory cache that stores up to 500
values. When connectivity is restored, these values are pushed to the FieldServer Manager.
NOTE: The in-memory cache will be cleared when the registered asset is restarted.

7 Useful Features
7.1 Security
FieldServer Manager to FieldServer and FieldServer to browser connections are secured with HTTPS, which uses TLS/SSL
(Transport Layer Security/Secure Sockets Layer). The HTTPS certificate is issued by SSL.com. Details are viewable via
any local PC browser by following the instructions found in Section 7.1.3 Viewing the Certificate.
NOTE: The FieldServer Manager keeps information private between individual OEMs and individual enterprise
users. There is no bleed between different OEMs and different enterprise users.
7.1.1 PC to FieldServer Manager
To browse the FieldServer Manager via PC, type the following into the internet browser: www.fieldpop.io (port 10000, 80
and 443).
7.1.2 FieldServer to FieldServer Manager
To allow the FieldServer to connect to the FieldServer Manager, use the following domain: www.fieldpop.io (port 10000, 80
and 443).
To connect to a FieldServer via FieldServer Manager, a device tunnel is created that has a unique subdomain in the URL.
Therefore, the best way to configure a firewall rule is to use a wildcard domain: *.tunnel.fieldpop.io (port 443).
Additional security can be added by allowing the FieldServer to exclusively access the *.fieldpop.io. This provision can be
set up in the customer’s firewall.

7.1.3 Viewing the Certificate
• Open a web browser on the local PC and go to www.fieldpop.io.

• Move the cursor to the padlock icon ( ) next to the website address.
• Click the padlock icon to open a dropdown menu for website information and browser settings.

• Review the information and click the Certificate button.
• Examine the certificate as needed.
NOTE: To download the certificate, click the Details tab and click the ‘Copy to File’ button.

7.1.4 Certified by Provensec
The FieldServer Manager Platform was certified secure by Provensec, an industry-recognized leader in cyber security
testing and risk management services. See certificate below.

7.2 Data Table Features
The following features are available on any Data Table Page.
7.2.1 Additional Filter Options
Column Field Search – Details can be typed into the text box at the top of each column to find entries.
Column Dropdown Menu – When clicking into the Field Search box for certain data values, a dropdown menu will appear
that allows selection of specific entries of the data, limiting the displayed entries to just those that apply. For example,
clicking company allows selecting a specific company so that all users listed are just those from that company. The User
Role data value also allows filtering by specific entries.
Column Order – Click a column’s title text to sort data entries in ascending or descending order by that data value. This will
make an arrow appear to the right of the column title text that was selected. This arrow will point up for deciding and point
down for ascending.

Data Table Dropdown Menu – Click on the gray menu icon on the top right corner of the desired data table. This will open
a dropdown list that lists the columns available for this specific data table. Columns clicked will be hidden or added to the
table depending on whether they are present in the table or not.
7.2.2 Exporting Data
• Click on the blue “Export Options” button on the bottom right corner of any Data Table page.
• Choose one of the export file options below:

◦ Export visible data as CSV
NOTE: If any columns have been made invisible via the additional filter options shown in Section 7.2.1
Additional Filter Options then the export options that reference “visible data” will not include those columns.
• The data file will automatically download to the local computer’s default “Downloads” folder.

7.3 Device Management Map Controls
7.3.1 Mouse
NOTE: For the mouse control descriptions below, “left” and “right” refer to the left and right mouse buttons.
• Left click and hold – This allows dragging to orient the map as desired.
• Double left click – Zoom in one interval.
• Double right click – Zoom out one interval.
• Scroll wheel – Roll forward to zoom in and roll back to zoom out.
NOTE: If the scroll wheel stops changing the map magnification, see Section 6.1.2 Scroll Wheel Doesn’t
Change Map Magnification.
7.3.2 Additional Controls
The following icons are located in the bottom right corner of the Device Management Map and include their function
description below:
Zoom In – Based on current center of screen
Zoom Out – Based on current center of screen
Full Screen – Open map in full screen view
Exit Full Screen – Exit the map full screen view
Reset Map – Resets the map back to default zoom settings and refreshes FieldServer table
Note: If you can't find your FieldServer in the FieldServer Management table, try resetting the map display with
the Reset Map button in the bottom right corner of the map.
7.4 Session Time Out
If the FieldServer Manager is left open without any input a pop up a reminder will occur 10 min after last input and state that
log out will occur in 5 minutes.
The FieldServer Manager will automatically show the following window if no input is received after 15 minutes:
To log back on, click OK to be sent back to the login screen and log in as normal.

7.5 User Roles – Type and Hierarchy
The following explains what the different types of FieldServer Manager user roles are and what functions they allow. There
are three types of roles: Admin, Manager and User. There are also two levels of hierarchy: OEM and Enterprise
Customer. OEM accounts are a level of hierarchy above Enterprise Customer accounts. Only an OEM can be a
manager.
Admin can:
• Register or deregister devices
• Create Admin or User accounts on the same level of hierarchy
• Change the role of existing users between Admin and User
• View all devices accessible to the Admin’s organization
• Assign a device to a User on the same level of hierarchy, granting access to view the device
User can:
• Register or deregister devices (Users can only deregister devices of which they have access)
• View and edit device(s) that are assigned to the User’s account by an Admin of the same company
OEM Admin can:
• Change the privacy settings for their company (Section 5.1.2 Privacy Settings: Configure Visibility)
• Customize the FieldServer Manager company logo (Section 5.1.1 Add Custom Logo)
• Upload new firmware to the FieldServer Manager
• Create Enterprise Customer Admin accounts
• Add a new company to the FieldServer Manager system by creating a new Enterprise Customer Admin
• Assign a device to an Enterprise Customer Admin, making the device visible to all of that company’s Enterprise
Customer Admins
• Assign organizations to an OEM Manager
• Not view, create or modify Enterprise Customer Users
Enterprise Customer Admin can:
• Update the firmware of a device via the FieldServer Manager
• View and edit device(s) that are registered to the Enterprise Customer Admin’s organization
• Not view, create or modify OEM Admins and OEM Users

OEM Manager can:
• Create Enterprise Customer Admin or OEM User accounts
• Modify Enterprise Customer Admin or OEM User accounts within an organization that has been previously assigned
to the OEM Manager
• Add a new company to the FieldServer Manager system by creating a new Enterprise Customer Admin
• Assign a device to an Enterprise Customer Admin (in an organization assigned to or created by the OEM Manager),
making the device visible to that company’s Enterprise Customer Admins
• Assign a device to an OEM User, granting the user access to view the device
• View and edit device(s) that are registered to the organizations assigned to the OEM Manager, devices created by the
OEM Manager or devices directly assigned by the OEM Admin
• Not view or modify users, devices or organizations that aren’t part of the organizations assigned to the OEM Manager,
created by the OEM Manager or directly assigned by the OEM Admin
On the FieldServer Manager website, devices are associated with the company and hierarchy level of the account that
registered it. This includes which roles will be able to view the device.
• If an OEM User registers a device, the device is also immediately assigned to that user. This allows all OEM Admins
to view the device.
• If an OEM Admin registers a device, it is assigned to the OEM Admin’s company and becomes visible to all OEM
Admins of that company only. An OEM Admin can then assign that device to an OEM User, who is then allowed to
view the device along with all the OEM Admins of that company. If the OEM Admin then assigns that device to an
Enterprise Admin, that device will become associated with the Enterprise Customer Admins which means all
Enterprise Customer Admins of that company can now also see the device.
• If an Enterprise Customer User registers a device, that user will automatically be assigned that device. The
registering Enterprise Customer User and all Enterprise Customer Admins will be able to view the device.

7.6 Using the Virtual Points Feature for Advanced Profile Configuration
Virtual Points allow the user to add calculations to an existing FieldServer’s profile(s) points. See the help button mentioned
in Section 7.6.1 Virtual Points Interface for further details.
NOTE: Only available if using Customer Application Features. See Section 3 Using Customer Application
Features for other functions.
• Navigate to the Virtual Points tab by clicking on the Settings tab on the left side of the screen.
◦ Once selected the arrow on the right side of the Settings tab will turn to face downward, revealing the
Configuration, Virtual Points and Network tabs.
• Click the Virtual Points tab to open the Virtual Points page for advanced profile configuration.
NOTE: All pre-loaded profiles for the FieldServer are shown on this page.

7.6.1 Virtual Points Interface
The Virtual Points page allows users to edit virtual point coding for each profile in a web GUI environment that includes
helpful functions.
To edit an existing profile, click on one of the pre-loaded FieldServer profiles.
The button functions are explained below (all are found above the Virtual Points viewer – Section 7.6.2 Create or Edit a
Virtual Points File):
– Click the Help button to open a window describing the basics of what can be done with Virtual Points
and some coding examples of different functions.
– Click the “+ JSONLogic” button to add generic JSON logic coding to further define.
– Click the “+ Analytics” button to add generic analytics coding for a user to further define.
– Click the Editor Mode button to view Virtual Points in “Code” mode or “Tree” mode.
NOTE: Code mode is the default.
Virtual Points Viewer in Code Mode
When in “Code” mode the Virtual Points viewer displays all coding notation.
The icons on the top left corner of the viewer are explained below:
– Click the indent format icon to change the Virtual Points coding to an indented view where a new line is started after
a comma is used or a bracket is opened. If a bracket is closed it is isolated on the next line.
NOTE: Indent format is the default setting.
– Click the compact format icon to remove all formatting and spacing to show all Virtual Points as a single string.
– Click the repair JSON code icon to automatically fix quotes/escape characters, remove comments/ JSONP notation,
and turn JavaScript objects into JSON.

Virtual Points Viewer in Tree Mode
When in “Tree” mode the Virtual Points viewer displays functions in branches. Click right-facing arrows to expand specific
branches. Search for text in the Virtual Points by using the search bar found in the top right of the viewer.
The icons on the top left corner of the viewer are explained below:
– Click expand icon to open all branches of the Virtual Points.
– Click the collapse icon to close all branches of the Virtual Points.
– Click the sort icon to open the Sort window. Select the field to sort by, choose between ascending and descending,
then click Ok to perform the sort.
– Click the filter icon to open the Transform window. Fill in the fields as needed to filter, sort, transform Virtual Points. If
further explanation is necessary, follow the link at the top of the window for an interactive tutorial.

7.6.2 Create or Edit a Virtual Points File
To create or edit a profile logic file, it is important to have JSON programming knowledge and experience. It is
recommended that only a JSON programmer create or edit code.
Before coding can begin:
• Follow the instructions in Section 7.6 Using the Virtual Points Feature for Advanced Profile Configuration to navigate
to the Virtual Points tab.
• Find and click the profile to add or edit JSON logic from the profile list.
• This will open the Virtual Points viewer, review the features detailed in Section 7.6.1 Virtual Points Interface and look
at the information shown by clicking the Help button to become familiar with how the Virtual Points viewer works.
• Review the view modes in Section 7.6.1 Virtual Points Interface to decide which mode is preferable and select it.
Create a new profile logic file:
• When starting new profile logic, use the “+ JSONLogic” button to create a logic framework and fill in the details as
needed (if more information on JSON is needed go here for some JSON basics and examples).
• Then, if analytics are required, use the “+ Analytics” button to insert the framework for a generic calculation and
complete the definitions.
• When coding is finished, click the Save button below the Virtual Points viewer.
Edit an existing profile logic file:
• Simply open the desired profile logic file in the Virtual Points viewer and locate where changes must be made (the
Tree editor mode includes a search feature that may help).
• Make changes to the definitions, add or remove logic sets and analytics.
• When adjustments are finished, click the Save button below the Virtual Points viewer.

7.6.3 Import/Export Virtual Points for Profiles
The Virtual Points page enables the import and export of profile logic files.
Export all profile logic files:

• To export all loaded profile logic files, click the “Export All Profile Logic Files” button that is shown above the profile
listings in Section 7.6 Using the Virtual Points Feature for Advanced Profile Configuration.
◦ A .zip file that contains all the profile logic files will automatically download to the default folder on the local PC
• Archive or use as needed.
Export a single profile logic file:

• To export a loaded profile logic file, click the desired profile to export in the profile listings on the Virtual Points page
(Section 7.6 Using the Virtual Points Feature for Advanced Profile Configuration).
◦ This will open the Virtual Points viewer to the right of the profile listings

• Then click the Export Logic File button ( ), found above the Virtual Points viewer.
◦ A .json file of the profile logic will automatically download to the default folder on the local PC
• Archive or use as needed.
Import Virtual Points from a JSON file to add to an existing profile:

• Select the profile to add Virtual Points to from the profile listings on the page (Section 7.6 Using the Virtual Points
Feature for Advanced Profile Configuration).
• To import a .json file, click the Import Logic File button ( ) above the Virtual Points viewer.
• An Import window will appear, select the .json file and click the Submit button.
◦ The Virtual Points viewer will populate with the imported file’s code
• Click the Save button below the viewer to record the new Virtual Points for the profile.

7.7 Unix Time Stamp Information
7.7.1 Definition of a Unix Time Stamp
The Unix time stamp is a way to track time as a running total of seconds. This count starts at the Unix Epoch on January 1st,
1970 at UTC. This means the Unix time stamp is just the number of seconds between a particular date and the Unix Epoch.
It is also important to note that this point in time does not change no matter where you are located on the globe. This is very
useful to computer systems for tracking and sorting dated information in dynamic and distributed applications both online
and client side.
The FieldServer Manager timestamp appearing in the downloaded *.csv data log files is a Unix 10-digit serial timestamp
format, in units of seconds passed since the date of Zero Hours January 1, 1970. The FieldServer Manager generates the
timestamp based on GMT, so the time and date need to be adjusted to local user’s offset from GMT.
Three actions are used to transform the serial timestamp to time and date in Excel:
1. Format a column for date. (choose desired date format)
2. Format a column for time. (choose desired time format)
3. Copy the (same) conversion formula into the desired time and date result columns.
Cell Formula, *WITH* GMT-Local adjustment:
“= (<timestampcell>/86400) + 25569 + (GMT_Offset/24)”
Global index to GMT Offset values:
https://greenwichmeantime.com/time-zone/definition/
GMT_Offset for PST = -8 (hours)
Example for PST:
“= (A1/86400) + 25569 + (-8/24)”
This means that a generalized endUser data formatting tool made for Excel must have the GMT_Offset as an input to match
localUser time.
The formula below DOES NOT adjust for GMT Offset:
Cell Formula: “= (<timestampcell>/86400) + DATE(1970,1,1)”
Ex: “= (A1/86400) + DATE(1970,1,1)”
Unix time stamp is also called Epoch time or POSIX time which is wildly used in many operating systems or file formats.

7.7.2 Unix Time Stamp Example
The Unix time stamp at the time of this writing is:
1566592842 seconds since Jan 01 1970 (UTC).
This epoch translates to:
08/23/2019 @ 8:40pm (UTC)
2019-08-23T20:40:42+00:00 in ISO 8601
Fri, 23 Aug 2019 20:40:42 +0000 in RFC 822, 1036, 1123, 2822
Friday, 23-Aug-19 20:40:42 UTC in RFC 2822
2019-08-23T20:40:42+00:00 in RFC 3339

7.8 Webhook Access by Role
The Webhook page interface changes depending on the role of the user.
For an “OEM User” only access to the user’s owned Webhooks is available:
An administrator has access to a search bar and navigation tree to find other users’ Webhooks:

7.9 Give Administrator Users Access to a Webhook
To give Administrator users view/edit privileges for a Webhook owned by another user, the owner must go into the Webhook
Configuration Window and tick the checkbox that says “‘Allow admin access”.

7.10 Notification Message Descriptions
The following tables lists notification messages that can appear with a brief explanation of each.
Notification Message Explanation

FieldPoP Connection Established Device connected to the FieldServer Manager.
FieldPoP Connection Lost Device disconnected from the FieldServer Manager.
There was a timing issue so the data was not uploaded to the
Missed events due to time sync error FieldServer Manager. The data will be uploaded on the next 15 minute
cloud push cycle.
System Status Change; The system changed from status state 1 to status state 2. The legal
<status state 1> to <status state 2> values are: Normal, Warning and Alarm.
<DeviceName>, <PointName>,
<PropertyName>; Event removed: <status state The point status changed from status state 1 to status state 2.
1> to <status state 2>
<DeviceName>:
The device status changed from status state 1 to status state 2.
<status state 1> to <status state 2>
<DeviceName>, <PointName>;
The point status changed from status state 1 to status state 2 due to the
>= 60: <status state 1> to
condition that the value is larger than or equal to 60.
<status state 2>
<DeviceName>, <PointName>,
The point status changed from status state 1 to status state 2 due to the
<PropertyName>; <= 70: <status state 1> to
condition that the value is less than or equal to 70.
<status state 2>
Normal There are no active events.
Alarm There is an active Alarm condition met.
Warning There is an active Warning condition met.

8 Limited 2 Year Warranty
MSA Safety warrants its products to be free from defects in workmanship or material under normal use and service for two
years after date of shipment. MSA Safety will repair or replace any equipment found to be defective during the warranty
period. Final determination of the nature and responsibility for defective or damaged equipment will be made by MSA Safety
personnel.
All warranties hereunder are contingent upon proper use in the application for which the product was intended and do not
cover products which have been modified or repaired without MSA Safety’s approval or which have been subjected to
accident, improper maintenance, installation or application; or on which original identification marks have been removed or
altered. This Limited Warranty also will not apply to interconnecting cables or wires, consumables or to any damage
resulting from battery leakage.
In all cases MSA Safety’s responsibility and liability under this warranty shall be limited to the cost of the equipment. The
purchaser must obtain shipping instructions for the prepaid return of any item under this warranty provision and compliance
with such instruction shall be a condition of this warranty.
Except for the express warranty stated above, MSA Safety disclaims all warranties with regard to the products sold
hereunder including all implied warranties of merchantability and fitness and the express warranties stated herein are in lieu
of all obligations or liabilities on the part of MSA Safety for damages including, but not limited to, consequential damages
arising out of/or in connection with the use or performance of the product.

MSA Grid-FieldServer Manager Start-Up Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MSA Grid-FieldServer Manager Start-Up Guide

Uploaded by

Copyright:

Available Formats

Operating Manual

MSA Grid – FieldServer Manager

Document No.: T18661

Print Spec: 10000005389 (F)

For your local MSA contacts, please go to our website www.MSAsafety.com

© MSA 2022. All rights reserved

1 Connecting to the FieldServer (for Field Installers) 7

2 Registering and Logging in (for Field Installers) 8

3 Using Customer Application Features 17

4 Logging into and Using the FieldServer Manager 24

5 Additional FieldServer Manager Instructions for Administrators 40

3 MSA Grid – FieldServer Manager

8 Limited 2 Year Warranty 82

MSA Grid – FieldServer Manager 4

5 MSA Grid – FieldServer Manager

Connecting to the FieldServer

• Type the FieldServer IP Address into a web browser.

Registering on FieldServer Manager

• Obtain FS Manager login details from support.

Accessing the FieldServer Manager

Using the FieldServer Manager

MSA Grid – FieldServer Manager 6

1.1 Discover the IP Address of the FieldServer

7 MSA Grid – FieldServer Manager

2.1 Create a FieldServer Manager Account

• Click the “Create Account” button.

MSA Grid – FieldServer Manager 8

2.2.1 New User Setup

Follow the instructions below to set up login details:

• Find the “Welcome to FieldServer Manager” email.

9 MSA Grid – FieldServer Manager

MSA Grid – FieldServer Manager 10

11 MSA Grid – FieldServer Manager

MSA Grid – FieldServer Manager 12

13 MSA Grid – FieldServer Manager

◦ Enter user credentials and click Register Device

MSA Grid – FieldServer Manager 14

15 MSA Grid – FieldServer Manager

• Navigate to the FS-GUI page using one of the following methods:

MSA Grid – FieldServer Manager 16

3.1 Generate Data Logging with System View

17 MSA Grid – FieldServer Manager

MSA Grid – FieldServer Manager 18

NOTE: Data is recorded for up to 30 days.

19 MSA Grid – FieldServer Manager

• Click on the Settings button ( ) to set up data to graph.

• Click the checkbox next to the data element to graph.

MSA Grid – FieldServer Manager 20

◦ After a few seconds, the graph should appear

• See below for instructions on controlling graphs:

21 MSA Grid – FieldServer Manager

MSA Grid – FieldServer Manager 22

23 MSA Grid – FieldServer Manager

MSA Grid – FieldServer Manager 24

25 MSA Grid – FieldServer Manager

• Click “Profile” in the dropdown menu.

• Then click “Save” to update the new cloud profile information.

4.1.2 Changing the Password

To change the password, fill in the password information as needed.

MSA Grid – FieldServer Manager 26

4.2.1 Map Elements

27 MSA Grid – FieldServer Manager

MSA Grid – FieldServer Manager 28