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