This page shows the workflow adopted for some use cases in the AMMOD project.
Use case: Initial registration of the Base Station
For the pilot phase of the AMMOD project, three replicas of AMMOD stations are going to be developed. The associated three base station components are managed manually and registered using the sensor.awi.de sensor registry service.
An initial registration of the tree base stations with basic information has been done with the geo-location information provided by the project coordinator (G. Tschan) in the kml file.
Note: the precision and accuracy of the coordinates is not confirmed (base stations physically not yet finished and deployed).
The three base stations of the test sites are mapped according to the following schema (short name -> test site name). The numbering follows the development order:
- ammod_bs_001 -> Melbgarten
- ammod_bs_002 -> Britz
- ammod_bs_003 -> Energieberg Georgswerder
The contact person for each test site is as follows (see Minutes_AnnCon_20201203-04_ver3.pdf):
- Melbgarten -> Georg Tschan, Module 1, ZFMK - Bonn. G.Tschan@leibniz-zfmk.de
- Britz -> Karl-Heinz Frommolt, Module 5, MfN - Berlin. firstname.lastname@example.org
- Energieberg Georgswerder -> Lukas Schoppmann, Module 6, TUHH, Hamburg. email@example.com
To initialize the development of the AMMOD portal and data upload API, placeholders for the three base stations have been inserted in the sensor registry. A unique numerical identifier, deviceID, is assigned to each base station:
- ammod_bs_001 -> 7390
- ammod_bs_002 -> 7393
- ammod_bs_003 -> 7394
These placeholders for the three base stations can be later expanded hand-in-hand with the development of the base station and its sensors. This is done by the Sensor Registry manager with the information provided by the AMMOD base station operator by means of a dedicated questionnaire document (available here -> AMMOD_sensor_registration).
To each base station, it has given the type of the sensor Station. This means that sensors that belong to a base station can be added as sub-devices in order to have an analogy with the configuration in the field.
All base stations so far in the registry are assigned to the Collection named AMMOD (assigned deviceID of the collection is 21). The deviceID of the AMMOD Collection can be used to retrieve all registered devices using the sensor registry API.
Use case: Initial registration of a Sensor
The registration of a sensor with its characteristics, inputs, outputs, user manual etc., is done manually using sensor.awi.de registry service. A sensor needs to be assigned to a registered base station and will be listed as a sub-device. Sub-devices can themselves have additional sub-devices to form a configuration tree. The registration process of a sensor and its utilization is depicted in the following figure:
The registration is done by the Sensor Registry manager with the information provided by the AMMOD base station operator by means of a dedicated questionnaire document (available here -> AMMOD_sensor_registration). The document contains the explanation of the required information and wherever possible examples of possible inputs. The filled-in document is sent via e-mail to the Sensor Registry manager (firstname.lastname@example.org). At the conclusion of the registration process, a unique numerical identifier (deviceID) is automatically assigned by the sensor.awi.de service. This is then communicated by the Sensor Registry manager to the AMMOD base station operator. deviceID can then be used for the telemetry and metadata sensor data files.
Use case: Register an event/action for a specific sensor
The registration of an Event, i.e. mount/un-mount, maintenance, calibration, etc., is done manually using sensor.awi.de registry service. This is done by the Sensor Registry manager with the information provided by the AMMOD base station operator by means of a dedicated questionnaire document (available here -> AMMOD_registering_actions). Some events will generate a new state of the system, providing automatic versioning identified by a unique handle.
Use case: Changing position of the base station
Each base station registered in Sensor.awi.de must have a reference local frame reporting the location (static in time). Each base station should be equipped with a GPS receiver and be a sub-device of the base station, hence providing the outputs latitude and longitude (dynamic in time). The sensors connected with a base station will inherit the geo-location from the reporting position of the base station.
Open questions to be addressed to the sensors team:
- What is the minimum spatial resolution a sensor is not affected by its geo-location position? E.g. moving the sensor in a radius of 500 meters will not change the measurements?
- Does each sensor need a reference local frame depending on the measurement taken? E.g. camera FOV changes affect the measurement.
The Sensor.awi.de API provides methods for getting the stored reference local frame:
and as well the sensor output: