HWM PCorr+ User manual

1
User Guide: PCorr+ and Permalog+
(Using the HWM WebCorr app).
Permalog+ PCorr+
MAN-2004-0001-C

2
TABLE OF CONTENTS
1Overview ............................................................................................................................4
1.1 System Documentation and Support of Product....................................................4
1.2 System Components..................................................................................................4
1.3 Mobile Phone –Specification....................................................................................4
1.4 Mobile Phone –Swapping Issues .............................................................................5
1.5 WebCorr App –Installation .......................................................................................5
1.6 Patroller ......................................................................................................................5
1.7 PermaNETWeb - Account and Password .................................................................6
1.8 DataGate –Giving the App access to Logger Devices.............................................6
1.9 Logger –Data destination .........................................................................................6
2Running the Software App –First-time setup.................................................................8
2.1 Launching the app .....................................................................................................8
2.2 Setting of App Options ............................................................................................10
2.2.1 App Options –DataGate ..................................................................................10
2.2.2 App Options - Other .........................................................................................11
3Connecting the Patroller and App over Bluetooth .......................................................11
4App –Main Window ........................................................................................................13
5Managing Logger Location and Data.............................................................................15
6App –Database................................................................................................................17
6.1 Database –Patrolled tab .........................................................................................17
6.2 Database –Deployed tab ........................................................................................18
6.3 Database –Recordings tab .....................................................................................19
7App –Local Display Options...........................................................................................20
8App –Lift and Shift ..........................................................................................................20
8.1 Deployment of a Logger Device to a Site (Shift) ....................................................20
8.2 Removal of a Logger Device from a Site (Lift)........................................................27
8.2.1 Options for automated download of a sound recording..............................28
8.2.2 Removing a Logger from Site (Lift) –Without sound download...................29
8.2.3 Removing a Logger from Site (Lift) –With automated sound download.....31
8.2.4 Caution Point: Trying to simultaneously download multiple loggers. .........33
8.3 Lift and Shift –Sound Recording download issues ...............................................33
9App –Patrol .....................................................................................................................34
9.1 Collecting data (Patrol) ............................................................................................35

3
9.2 Collecting data (drive-by patrol) .............................................................................35
9.3 Upload of Patrol Results to DataGate ....................................................................36
10 App –Configure Devices (Logger repetitive function) ..............................................37
10.1 Logger Device configuration –Reading..................................................................37
10.2 Logger Device configuration –Setting ...................................................................38
11 Logger Sound Recordings ...........................................................................................41
11.1 Manual Download of Sound File............................................................................41
11.2 Automated Download of Sound File (Lift & Shift option) .....................................42
11.3 Playing a Sound Recording......................................................................................42
11.4 Manual (Scheduled) Sound Recording ...................................................................42
11.5 Uploading Sound Recordings to DataGate............................................................44
12 PCorr+ –Leak Localisation / Correlation ...................................................................44
13 DataGate –Setup for use with WebCorr and loggers...............................................45
13.1 DataGate –Terminology and Summary.................................................................45
13.2 DataGate –Example Structure for use...................................................................46
13.3 DataGate –Required User Role permissions ........................................................47
13.4 DataGate –Changes made by the WebCorr app ..................................................47
14 Troubleshooting ..........................................................................................................51
14.1 Logger device does not get listed in the app.........................................................51
14.2 Error message during Lift or Shift ..........................................................................51
14.3 Sound file will not upload to DataGate, and displays “E”. ....................................52
14.4 App –Deletion of Database ....................................................................................52
14.5 Phone –Memory Full (Android phone)....................................................................52
14.6 Phone –Memory Full (Apple iPhone).......................................................................53
14.7 How should I handle a Phone Upgrade?................................................................53
14.8 How should I handle a Lost Phone? .......................................................................53
14.8.1 Old phone was synchronised ..........................................................................54
14.8.2 Old phone was not synchronised ...................................................................54
14.8.3 Deleting the app and logger data from an android phone...........................54
14.8.4 Deleting the app and logger data from an Apple iOS phone........................55
14.9 Firmware Upgrade...................................................................................................55

4
1OVERVIEW
1.1 SYSTEM DOCUMENTATION AND SUPPORT OF PRODUCT
Read any “Safety Information” or “Safety Warnings and Approvals Information”
documentation provided with the products prior to using.
Please also refer to the document MAN-031-0003 “User Guide: PCorr+ and PermaLog+ -
(Description and uses)”. This provides a description of PCorr+ and PermaLog+ logger
devices, their functions, how they should be physically handled and examples of their
use (e.g. Drive-by Patrol, Lift and Shift, Investigations).
This manual covers the use of the HWM WebCorr app to both set up the logger devices
and collect data from them.
Note: Your phone may show views not identical to the pictures in this manual.
Pictures in the manual were created from screenshots using an Android phone.
Due to the wide variety of phones available to consumers, variations will exist.
Pictures in the manual are therefore presented for guide-lines only.
HWM will release software updates from time to time. These may also cause
changes to the screen presentation and the functionality of the application.
It is recommended that you enable your phone to allow automatic updates of the
WebCorr app.
HWM also provides support of the product by means of a webpage:
https://www.hwmglobal.com/pcorr-support/
Should you have any questions that are not covered by a manual, or Frequently Asked
Questions (FAQs) provided online, please contact the HWM Technical Support team on
[phone], or email [e-mail]
1.2 SYSTEM COMPONENTS
A system is comprised of:
•A set of logger devices (PCorr+ or Permalog+).
•A compatible Patroller unit (e.g. Patroller 4 radio transceiver with Bluetooth).
•A mobile phone.
•The HWM WebCorr app.
•An internet connection (for the mobile phone).
•A DataGate user-account and password
(for the app to function and access the HWM database).
1.3 MOBILE PHONE –SPECIFICATION
The HWM WebCorr app is available on Android-based mobile phones and also on Apple
iPhone mobile phones.

5
Minimum specification of phone:
Android: Android version 5 (Lollypop) minimum.
Device must have Bluetooth, GPS and Internet capability.
Memory (for application): 80MB
Memory (for data): 0.2MB typical per sound file.
Apple iOS: iOS version 8.0 minimum.
Device must have Bluetooth, GPS and Internet capability.
Memory (for application): 80MB
Memory (for data): 0.2MB typical per sound file.
1.4 MOBILE PHONE –SWAPPING ISSUES
Caution: Once a phone has been used by an installer it will contain data.
The installer should continue to use the same phone. Each time the installer
swaps to using a different phone, unless it is handled carefully there is a risk
of creating data issues due to a disruption in the synchronisation of data
between DataGate and the mobile phone.
(See also sections 14.7 and 14.8 regarding misplaced or new phones).
1.5 WEBCORR APP –INSTALLATION
The app is available for Android phones, from the Google “Play Store”.
The app is available for the Apple iPhone, from the Apple “App Store”.
•Search for and locate the HWM WebCorr app.
•Install the app.
•The installed app will have an icon, as shown, when installed.
Occasionally, updates become available at the stores. It is recommended to install these
updates.
1.6 PATROLLER
The app uses a Bluetooth connection to a compatible Patroller (e.g. HWM Patroller 4).
Refer to the Quick Start Guide of the Patroller device for instructions regarding its
safety, installation and use.
To work, the phone must have Bluetooth enabled and it must be connected to the
Patroller (see section 3). Bluetooth radio has a range limit. Keep the phone close to the
Patroller to ensure the Bluetooth radio connection can function.
The Patroller acts a communications relay between the loggers (using a proprietary
radio-link) and the mobile phone (using a Bluetooth radio-link).
The Patroller is battery powered. It must be turned on to use. It can only communicate
to loggers that are within radio range and also have an active radio-link.

6
1.7 PERMANETWEB -ACCOUNT AND PASSWORD
The WebCorr app operates with HWM’s cloud-based logger database. These are known
as “DataGate” and “PermaNETWeb”. The app uploads its data to this database.
DataGate and PermaNETWeb act as the store and main viewing portal for the data. The
database can be accessed via webpages to view logger locations and results (not
covered in this manual). Other webpages give access to administrative functions (also
not covered in this manual).
A user-account must be used within the phone to give access to the online database.
The account also acts as a security feature, with certain functions of the app hidden (or
disabled) unless the app has recently logged into DataGate. Please contact your system
administrator for the account and password allocated for the user of the phone app.
When the phone app logs in, it receives a token permitting it to be used for a short time.
The app will require the user to log in again once the token expires.
1.8 DATAGATE –GIVING THE APP ACCESS TO LOGGER DEVICES
All PCorr+ and Permalog+ loggers must be registered on DataGate in order for the
WebCorr app to use them. DataGate must be set to give the user of the app the
required permissions to use the loggers.
Note: For a brief description of DataGate, and how to register both the loggers
and also users of WebCorr, see section 13.
There is a security measure within the app, regarding logger data privacy…
The app will ignore any logger devices, or data that it receives from logger devices, that
the user has no permission to use.
Note: If a logger is not appearing on the app it does not imply that it is not functioning
correctly. Check with your system administrator that the logger device is
correctly setup on DataGate for use with your user-account.
1.9 LOGGER –DATA DESTINATION
DataGate and PermaNETWeb webpages are the main viewing portal for logger data.
This implies that the final destination of all logger data is the DataGate system.
The scheme is summarised here…
PCorr+ and Permalog+ logger devices produce measurement data. The logger device
obtains several forms of data, each of which can be considered as a data channel. The
data is meaningless, unless it represents a measurement actually made on the pipe
network. Access to the pipe network is often available through various chambers that
house (and give access to) valves or hydrants. These chambers can be used as an
installation site for a logger device. A site may be one of many in an area or suburb,
with the pipe network interconnecting them. Sites may therefore be collected together
in a group, often referred to as a zone or DMA. Each of these separate entities may be
represented on a database, such as one used by DataGate, which links some of them
to a user of the system.

7
Or, put in reverse order…
•DataGate contains a database.
•A user of Datagate can be linked with multiple DMAs.
•Each DMA can contain multiple sites.
•Each site can have one logger device installed (maximum, at any given time).
•Each logger device can produce multiple channels of data.
•The data of a channel may be a one-off sample, or multiple samples that are
obtained at different times.
The WebCorr app and DataGate are concerned with collecting data from the logger
devices, linking it to the correct site and storing it.
Devices such as PCorr+ and Permalog+ can either be permanently installed or used as a
mobile measuring device.
A mobile logger is time-shared by multiple sites and transferred from one site to
another. The transfer process is known by various terms, including “Lift” and “Shift”.
In the time-share scheme, it is not necessary for a particular logger to be returned to a
previously measured site that requires new data; any equivalent logger may be deployed
to the site for producing new data.
The WebCorr app and DataGate manage the location of the loggers, the data collection
and linking of the data to the correct site. This process relies heavily on the exchange of
data between the WebCorr app and DataGate, in a process known as synchronisation.
Initially, when the app is first installed, DataGate is driving the data exchange and loads
starting-point data into the app. The roles are then reversed… The app drives the data-
exchange and keeps DataGate up to date with any new information.
The phone obtains some initial data from DataGate at each log-in time. This information
includes lists of various parameters, including which logger devices the phone has
access to, what installation sites exist, and which site (if any) a logger is installed at. The
app adds any new information to its internal database.
As the app is put into use, further (newer) information is stored by the phone.
(e.g. New measurements obtained from the loggers and changes in their location of
deployment). Each item of new information is tagged as an unsent data item.
DataGate must be brought up to date with this new information (stored by the app).
This is done as part of the synchronisation process.
Note: It is important to synchronise frequently to avoid loss of data.
Data held within a phone that becomes mis-placed (without it being
synchronised) cannot be recovered.
Some of the data held within the phone is also made visible to users of the app.
This data includes:
•Deployment details (changes of location driven by the app).
•Measurement details (Leak status, Noise Level, Noise Spread) read using the app.
•Sound Recordings obtained using the app.
•Site locations (e.g. via a map display).

8
2RUNNING THE SOFTWARE APP –FIRST-TIME SETUP
Note: HWM revises software from time to time, so the screenshots provided in this
guide may be different from what you experience when you download the app.
2.1 LAUNCHING THE APP
Find the HWM WebCorr app on your mobile phone.
Launch the app by tapping the icon.
The first time an app is run, or after it has been
upgraded to a new version, the phone makes a
sequence of one-off requests.
It may ask the user for permission for the app to use
the phone location services.
Tap on ALLOW…
Note: The phone should be set to give
“high-accuracy”location details to the
app. (This is a setting within the
operating-system of the phone).
The app may also request permission to have access to the
files on the phone.
(The app requires this permission to allow it to store data).
Tap on ALLOW…
You are required to log in, to verify you are a valid user.

9
View and accept the Privacy Notice.
Once accepted, the app will continue to load and operate.
The app must be given the URL of the server, so it can
find the correct internet address to communicate with.
Enter the details provided by your system
administrator.
Tap the “TEST CONNECTION” button; This checks the
mobile phone can connect with the server.
If communication is possible, the app will confirm that
the connection test succeeded.
Note: This process does not authenticate the phone
for use. User details must be entered
at a later stage.
Tap the back-arrow on the top-left of the display.
The user login screen appears.
Enter the Username and Password for the user into
the phone.
These are required for the app to be able to log in.
The tap on the “LOGIN” button.
If log-in is successful,
the phone will do an initial
synchronisation.
*** The initial setup of the phone, including the link to the server is now complete. ***

10
The app will then show the main screen:
More icons will become visible after the app itself is
connected to the Patroller4.
2.2 SETTING OF APP OPTIONS
From the main window, tap on “App Settings”.
The app settings view is divided into several areas:
•Patroller
(Covered in section 3).
•DataGate
(Covered later in this section).
•Lift and Shift
(Covered in section 8.2).
•Other
(Covered later in this section).
2.2.1 App Options –DataGate
“Server URL”will have been completed by the setup
process (see 2.1). Tap on “Test connection” if you wish
to re-run the internet connectivity test.
“Upload of Data to DataGate automatically”:
When set to “Yes” (recommended):
•The app syncs in the background immediately
after each lift or shift.

11
•Manual sync should be done by the user at the start and end of each day,
especially if the user is not using lift and shift functionality daily.
When set to “No”:
•The app will ask the user if it can sync, every time it writes new information into
its database.
“Allow upload by mobile data” is recommended to be set to “Yes”. However, if the user
wishes to delay sending of information until a Wi-Fi connection exists, set to “No”.
2.2.2 App Options - Other
Tap on App Information to see app information
including the software version.
There are links to the HWM website and also the privacy
policy.
Options exist for various functions that may be
requested to help HWM to support the product.
e.g.: Database Backup and Clear.
Upload of Log files to HWM.
3CONNECTING THE PATROLLER AND APP OVER BLUETOOTH
Check the Patroller is switched on prior to trying to connect the app with it.
Tap on “App Settings”.
Find the “Patroller” section within the App Settings
window.
This section shows the connection status.
There is a control to connect (or disconnect).
Tap the “Connect” line to start the connection process.
If required, give permission for the app to use Bluetooth.

12
The app searches for Bluetooth devices and lists them.
The Patroller will be identifiable by the
Bluetooth-ID matching a part of the serial number,
or some other identification on its label.
If the Patroller is not listed, gently swipe the list on the
screen downwards (as shown) to re-start the search
for Bluetooth devices.
When the Patroller is listed, tap the line to attempt to
connect to it.
Progress of the attempt to connect will be shown, along with
a confirmation message when connection is successful.
If the connection attempt is not successful, try again, until the
“Connected to …” message is displayed.
Note: Bluetooth is a short-distance radio link. It is possible
for the link between the phone and the Patroller to
drop for a variety of reasons (e.g. If the phone is taken
too far from the Patroller).
If the link drops, the app will continue to look for the
Patroller for a short time (up to 10 minutes), and will
attempt to reconnect automatically.
When re-connection is successful, a “Connected…”
message appears on the phone display for 5 seconds,
then normal operation resumes.
If the user considers the process is taking too long,
they can cancel the operation and manually re-connect
to the patroller.
When the Patroller is powered over USB is it always on.
If NOT powered by USB, check the Patroller is still on.
Note: If the Patroller is battery powered, it can switch itself off when it has not been
used for some time (approx. 30 minutes); It does this to conserve battery use.
It will also disconnect if the battery runs very low.

13
Once connected, an indication of the battery level of
the Patroller can be obtained.
Tap the “Battery Level”line to get the current level.
OK = More than 15% charged.
Low = Below 15% charged; Charging advised.
Charging = Plugged in and charging.
The user can periodically check the battery level by
returning to this screen.
The status of the “GPS time-sync”is shown
(either “no time-sync” or “time-sync OK”).
GPS can provide a very accurate time to the Patroller,
but when not available the Patroller uses the time
available from the phone.
Tapping the “GPS”line shows more details.
4APP –MAIN WINDOW
The main window of the app is shown opposite.
The window is used to navigate to the various functions
of the app.
In summary…
The “App settings” window concerns:
•Connecting the phone with a Patroller device over a Bluetooth radio connection.
Obtaining status info about Patroller health.
•Setup of the app to use DataGate for authentication and data upload.
•Allowing automatic upload of some data.
•Lift & Shift options for downloading sound files from each logger device.

14
•App information (e.g. Software version).
•Options (mainly used if requested by HWM providing support of the app):
oBackup or erase the app database (measurements and deployments)
from the phone.
oSend event log data to HWM.
The “Patrol” window concerns:
•Obtaining data: Leak-status and measurement summary from devices that come
into radio range during a “patrol” or “drive-by patrol”.
The “Lift and Shift” window concerns:
•Creating new installation sites (if required).
•Deploying logger devices to installation sites.
•Lifting loggers from installation sites to make them available for re-deployment.
•Obtaining data: Leak-status and measurement summary from devices as part of
the Lift process.
•Downloading Sound Recordings from devices (dependant on settings).
The “Database” window concerns:
•The history of logger deployments to sites made by the phone
(Sites that a device has been installed on, start date and end date).
•Leak-status and measurement summary obtained from loggers using the app.
•Sound recordings obtained from logger devices by the app.
•Visible markers of any un-synchronised data, between the phone memory and
DataGate; Synchronisation can be initialised from this window.
Note: The phone has to have actually been “driving” the logger for any entry into
the visible database. Only data from the phone’s actions are displayed.
No historic data is downloaded from DataGate into the displayed database
(although some may be used by the app, invisible to the user).
The “Configure Devices” window concerns:
•Setup of the Patrol Window (radio-link availability) of the logger device.
•Setup of the time that the daily leak-evaluation will run.
•Setup of whether the logger-devices should auto-record the sound upon finding
a new leak.
•A facility to read the settings from a logger device.
The “Sound Recording” window concerns:
•Making a one-off scheduled sound recording at a set time (the regular logger
program is suspended until the 1-off scheduled recording is completed).
•Download of a completed sound recording file.

15
5MANAGING LOGGER LOCATION AND DATA
A “DMA” is a means of grouping sites, typically those interconnected by the pipe
network in a local area.
A “Site” is a location on the pipe network (typically a chamber giving indirect access to
the pipe, via a valve or hydrant) where a monitoring device (logger) can be installed.
From the database point of view, a site can contain zero or one loggers.
The app regards loggers to be in one of three states …
•Deployed.
(i.e. Installed on a Site).
•Non-Deployed.
(i.e. Not installed on a Site; Being stored at an undefined location).
•Non-existent.
(i.e. DataGate has not given the app authority to use the logger. This could be
intentional, or DataGate data is incorrectly set up, or the app requires
synchronisation with DataGate to be able to use newly added logger devices).
The app is so constructed that it shares information with DataGate.
DataGate regards loggers to be in one of two states …
•Deployed.
(i.e. Installed on a Site).
•Non-Deployed.
(i.e. Not installed on a Site; Being stored at an undefined location).
One of the purposes of the app is to feed information into DataGate. The information it
sends includes:
•Changes in a logger location.
•Measurement data collected from a logger.
•Sound files collected from a logger.
The app uses the memory of the phone to locally store data. To do so it creates a local
database. Upon first installing the app, the database is empty. The app has no
knowledge of what logger devices it is going to be managing or where the loggers are
currently located. To obtain this information it must contact DataGate, log into it and
synchronise with it. After the initial synchronisation, the app can update its internal
database with data describing its starting position. From that point on, it will be “in the
driving seat”, storing any location changes or newly collected measurements locally,
pending upload to DataGate. The new information is uploaded to Datagate as part of
the information exchanged during subsequent synchronisations.
Note: It is important to synchronise frequently with DataGate so that office staff can
respond to the leak-status information collected from the loggers in a timely
manner.

16
Note: Any unsynchronised data stored on a misplaced phone becomes lost.
In such a scenario, DataGate may give inaccurate information regarding logger
locations to a replacement phone.
Once the app is operational, and has an initial database, its main activities can be
summarised as follows:
•Only non-deployed (stored) loggers can be installed (deployed).
(This is known within the app as a “Shift”).
A “shift” is required to deploy any logger to its new site; It does not matter if the
installation of the logger is intended to be short-term or long-term.
•Only deployed loggers can be removed from their site (un-deployed).
(This is known within the app as a “Lift”).
•The phone app keeps track of location changes within its local database until it
has uploaded them to DataGate. The location changes then become visible to
other users (e.g. Office staff).
The app keeps track of what information is already sent and what is yet to be
sent.
•Deployment can be to an existing site, as long as the site is unoccupied.
It may also be to a new site; The app can create new sites when required.
The app requires that new sites must be part of a “DMA”. Usually this will be an
existing DMA, but new DMAs can also be created when required.
•Measurement data can be collected from the loggers by either of two activities…
oIf there is no intention to remove the logger from its installation site,
data for the site is collected using a “patrol”.
oIf a logger is being removed from its site, final measurement data for the
site is obtained as part of the “Lift” process.
•Measurement data is saved in the local database until it can be uploaded to
DataGate; The app keeps track of what data is already sent and what is yet to be
sent.
•If there is a sound recording within a logger, it can be downloaded (PCorr+
loggers can contain a maximum of one sound recording).
These are then stored on the phone. They are already time-stamped by the
logger with the recording date and time. The app keeps track of what sound files
are already sent to DataGate and what is yet to be sent.
•The app synchronises with DataGate including an upload of its new data items.
•Measurements or sound recordings made by the loggers whilst in storage may
also be sent by the app to DataGate, but DataGate will discard them; The
loggers were not deployed to any site when the data was obtained.
The app can also be used for additional purposes:
•It can be used to program the loggers in order to set the time of their repetitive
daily activities (leak detection time, etc).

17
•It can be used to temporarily suspend logger’s regular activity in order to make a
one-off scheduled sound recording (PCorr+ only). It can download the sound
recording after it has been made.
•It can be used to put the loggers into a mode suitable for long-term storage.
6APP –DATABASE
From the main window, tap on the “Database” line.
The Database window consists of 3 tabs:
•“Patrolled”
(Lists leak-status measurements).
•“Deployed”
(Lists deployment periods).
•“Recordings”
(Lists sound recordings).
On the Deployed and Recordings tabs, the app lists only data from activities the phone
itself has been responsible for. Initially, no data is listed.
As the app becomes used, each tab will fill with data. When too much data is available
to fit on the screen, it can be scrolled by placing a finger on the screen and moving the
list up or down. The app removes data more than 3 months old to reduce memory use.
6.1 DATABASE –PATROLLED TAB
The “Patrolled” tab contains a list of data items
regarding the leak-state of the logger devices.
The list can be ordered in several ways –choose
from the local options menu.
There is no indication in the list of the site the
logger was on when it made the measurement
(linking to a site is described later).
Note: The list will contain a maximum of one measurement per site per day for each
logger. This is because the normal activity of the logger is to produce just one
leak evaluation per day.
Any unsent data items have an exclamation mark next to them to indicate it is
unsent (see diagram above).

18
Tapping on the Sync icon will initiate a synchronise with Datagate
including sending all unsent data items.
(You may be requested to enter your password and log in as part of the
sync process).
Data that has been sent to DataGate no longer has an
exclamation mark next to it.
“Level” and “Spread” indicate the noise-level and noise-spread of the measurement,
which together form an indication of how persistent a noise-source is.
“State” is the logger judgement of either a leak being present (shown as “L”)
or no leak being present (shown as “N”).
A no-leak status is listed with a white background. A leak status is listed with a coloured
background to draw attention to it.
Linking the logger measurement to the site on which the measurement was made is
readily done using Datagate. It can also be made using the phone by noting the logger
number and the date the measurement was made. The “Deployed” tab data can be
used to identify where the logger was. This should be no issue for a permanently
installed logger, which will still be on the same site. For a mobile (Lift and Shift) logger,
the measurement will have been taken a few seconds before it was lifted from a site,
and the user has to identify the correct time period of deployment.
6.2 DATABASE –DEPLOYED TAB
The “Deployed” tab contains a list of records regarding
the deployment periods of the logger devices.
Each line represents a deployment interval for the
logger.
The serial number is shown, along with an “easy-ID”
(a user-defined name) of the logger device.
The site and address of the deployment are shown.
Tap a line to show more detail, which appears in a
pop-up box.
The app only shows times for actions it itself has driven.
Sites with a deployed logger, but no start or end date have
been uploaded with this information by DataGate.
Sites with the logger deployed by the phone have only a
start time.

19
Sites with the logger deployed and removed by the phone have
both start and end times.
Any unsent deployment data items will have an exclamation mark next to
them in the “deployed” tab list. Sync if required (as described earlier).
Next to the exclamation mark for unsent data is an arrow indicating what
events have not been sent to DataGate.
Up arrow = Lift
Down arrow = Shift
2-headed arrow = Both Lift and Shift.
The sites where loggers are currently installed can be
shown… Tap “Show on Map”.
6.3 DATABASE –RECORDINGS TAB
The “Recordings” tab contains a list of data items
representing sound recordings that have been
downloaded from the logger devices.
Each line shows the logger number, date and time the
recording was made.
Any unsent data items have an exclamation mark next
to them to indicate it is unsent (Not shown).
Sync if required (as described earlier).
Note: Any sound items having an “E”next to them (not shown) indicates an error when
uploading to DataGate. Usually it is because DataGate could not link the sound
recording to a site. Typically, the logger was not deployed when the recording was
made. The user may investigate if the sound file should be re-made.
Linking the logger to the site on which the sound recording was made is readily done
using Datagate. It can also be made on the phone by noting the logger number and also
the date on which the sound recording was made. The “Deployed” tab can be used to
identify where the logger was (but only if the phone itself deployed the logger to the
site).
If the phone cannot identify where the logger was when the sound recording is made, it
will still upload the file and it is left to DataGate to resolve which site the recording was
made on.
This window can also be used to playback sound recordings –See 11.3.

20
7APP –LOCAL DISPLAY OPTIONS
Many windows will have local options for the
information being displayed.
Tap on one of the local options icons
(shown) to select an option for the
current display.
Sometimes a simple “selection menu”
is produced for the user to select from.
At other times a new window will display in order to
make the required selections.
(e.g. the “Grouping and sorting” window, shown
opposite).
8APP –LIFT AND SHIFT
The “Lift and Shift” window is designed primarily for mobile loggers that are time-shared
between multiple sites. Strictly speaking, it is used to manage the location data of all
logger devices. It tracks the location change within the app database whenever the
installer both deploys them to a site and (later) removes them from the site.
When deploying a logger to a site, the app can re-use existing sites or, when necessary,
create new sites within the database for use.
“Shift” is the action of deploying a logger to a site (i.e. Installing it).
“Lift” is the action of removing an installed logger from its site.
The combined process of “Lift and Shift” moves a logger from one site to another within
the database. Invariably, there is a mid-point in the logger relocation process where the
logger is temporarily being stored (e.g. in a vehicle) whilst it is being moved, and the
exact location does not matter since it will not be producing useful data.
Loggers repetitively make measurements, but no measurement is meaningful unless a
logger is actually installed on a site at the time it makes the measurement.
8.1 DEPLOYMENT OF A LOGGER DEVICE TO A SITE (SHIFT)
Select a logger for installation and find a suitable installation site.