Overview Account Data Model Hierarchy

FAI provides end-to-end remote monitoring solutions consisting of a Wavelet data acquisition device, one or more sensors, wireless connectivity, and data and device management software. FAI's Wavelet device and software (IoT Platform) provide input for decision makers with continuous data on the state of their infrastructure and dispersed assets. The FAI solution is intended and engineered for passive monitoring and is not intended for control of critical assets and processes.

Overview

The platform is offered as:

  • A web-based, cloud solution (FAI Cloud)

  • An on-premises solution (FAI Local)

  • A direct device-to-MQTT Broker solution (FAI Lite)

Each Wavelet device integrates several sensors and is installed on existing customer infrastructure. It samples data from connected sensors at a configurable rate and logs this data, which is then transmitted to the FAI Cloud server at a configurable transmission rate.

FAI Cloud Server

Cloud Server

FAI Cloud Server with Agent

Cloud Server with Agent

FAI Local Server

FAI Local Server

Figures:

  • Figure 1: FAI Cloud server: FAI Cloud

  • Figure 2: FAI Cloud with an Agent in the customer's network that connects to a SCADA system

  • Figure 3: On-premises server: FAI Local

Account Hierarchy for FAI Cloud and FAI Local

A system (Account) is organized hierarchically:

  • Account

    • Collection(s)

      • Site(s)

        • Device(s)

          • Data stream(s)

Example: The My_Account Account includes a single Collection My_org, managing a single Site My_Site, which contains a single device My_Device_number. This device is connected to a Flow sensor, and includes Battery Life and Communication streams. The sensor sends sample data to the My_Device_number device.

Notes:

  • The Collection level is optional. If omitted, all Sites fall under the Account level (common in small Accounts).

  • The Device level is also optional. Data streams can exist directly under a Site.

  • Each Account hierarchy matches the actual device and sensor deployment.

  • Account owners can add Collections and assign/unassign Sites to/from Collections.

FAI Data Model

Sensor measurements are stored hierarchically to match the device deployment.

Entities:

  • Site: Logical entity representing a Wavelet installation location (one device per Site).

  • Device: Physical Wavelet device in the field, generating/transmitting data from integrated sensors.

  • Channel: Physical input for raw sensor values (Raw Value column in Samples table).

  • Stream: Logical output of final sensor parameter values (Final Value column), assigned to a channel and unique to a Site.

  • Sample: Measurement at a specific moment in time.

What's What - Unique Identification

Each Site, device, channel, and stream has a unique ID in the Account's Collection.

Where to Find IDs:

  • Site, Device, Stream IDs: Hover over icons in the Site Tree pane.

  • Channel ID: Hover over the sensor type in the STREAM MANAGEMENT table (Type column).

Examples:

Data Model Entity
Where to Find Its ID

Site

Site ID: 8314

Device

Device ID: 8295

Stream

Stream ID: 79743

Channel

Channel ID: 132210

Device-Communication Identifiers

  • AK-ID: Unique identifier on the device's microcontroller unit (MCU).

  • IMEI/MEID: Unique numbers identifying a physical device.

  • ICCID: 18-22 digit SIM card identifier including country, network, and card number. Typically found on the back of the SIM card or packaging.

Last updated