Functional principle

In the graphic below, all of the components that are part of the myDatanet illustrated in grey. All other components must be provided/created by the customer.

Functional principle

1 Jellox Pulse with integrated managed service SIM chip
2 myDatanet server the data is transferred to
3 Client that accesses the interface of the myDatanet server via the web browser
4 Customer-specific server that provides clients with their own interface. The customer-specific server obtains the data via the API interface of the myDatanet server (see API).
5 Client, on which a PC program is running, that obtains its data via the API interface of the myDatanet server (see API)
6 Client that accesses the interface of the customer-specific server via the web browser

Functions and components provided by myDatanet :

  • Jellox Pulse

    It is a compact device used for connecting water or energy meters as well as digital contacts (IN1-4) to the myDatanet server (M1/NB1/NB2).

  • Managed Service

    Managed Service is the basis for operating the devices and provides a wide range of services. Managed Service includes updates for device firmware, mobile data transmission on a global scale and free support - providing you with one contact person for the entire solution.

  • myDatanet server

    Database for saving the measurement data and configurations. Data is either accessed via the API (see API) or the web interface of the server.

Functions and components provided by the customer:

  • Water meter with pulse output as well as digital contacts

    Counter that has a switching contact compatible with the specifications listed in chapter "Technical details about the inputs" (see Technical details about the inputs)

    Digital switching contact compatible with the specifications listed in chapter "Technical details about the inputs" (see Technical details about the inputs)

  • Customer-specific server with web interface for the clients (optional)

    It can be used to create an individual web interface for the clients. In this case the data is read from the customer specific server via the API interface (see API) on the myDatanet server.