...
| Include Page | ||||
|---|---|---|---|---|
|
| Table of Contents |
|---|
How often
...
do loggers upload measurement data
...
into the system?
It depends on the logger type and if whether the logger is connected to power. Generally, CO 03.01/13.01 and CO 03.02/13.02 loggers are used for warehouse monitoring. These loggers uploads upload measurement data every 10 minutes.
For CO 21.01 logger, loggers that are used to monitor stand alone standalone fridges, for example, uploads data upload occurs every 10 minutes if the device is connected to power. If it the device is not connected to power and runs in Power Saving Mode, it uploads will upload data every 24 hours until the battery level is around approximately 35% (up to 180 days). Then, the logger starts to upload data every 48 hours until the battery level is around 5% . (up to 145 days). The logger will then uploads upload data every 96 hours until the battery is empty. Overall, the CO 21.01 could, in theory, operate up to one year on one battery charge. Cellular signal quality and frequent excursion excursions will effect the affect battery endurance.
What is
...
an "Entity"?
The measurement Measurement data can be organized in within a hierarchy and categorized according to collectiona Collection. Each point in the data hierarchy tree is called an Entity. Each Entity can be a Collection, Asset, or Measuring Point.
What is a "Collection"?
A Collection is similar to a Group in the system and can represent a country, region, city, etc.
What is a
...
"Root-
...
Collection"?
A Root-collection Collection is the first Entity or the top Collection in the Entity tree. More than one Root-collection can be created in each customer account. Root-collection can be used to create two separate entity trees in the same customer accountTree.
What is a
...
"Sub-Collection"?
RootA Sub-Collection can have collection(s) under it and sub-collection(S). The collection structure can be used to create a geographical structure around the measurement data for example: 
is Collection that is located under another Collection. For reference see the picture below.
...
Why are there different sub-types of Collections?
Different sub-types of Collections change how the data is shown in the User Interface
Collection (Generic)
Collections and Assets are shown as a folder structure in the Overview Tab.
...
Area Collection
Displays Sub-Collections or Assets on a geographical map.
...
Facility Collection
Gives the option of drawing a schematic of the facility and show current temperature measurements.
...
Do I need to create a complex
...
Entity Tree to represent
...
Sites that I
...
would like to monitor?
No, the entity tree Entity Tree can be a simple as a group collection. Asset directly Collection. Assets are listed under the root collection Collection or skip the root-collection and create asset at the top of the entity tree.
an Asset at the top of the Entity Tree.
...
What is an "Asset"?
An Asset is an Entity for measuring points that measure the same area. For example a fridge, freezer, aisle in a warehouse, etc. Each Asset can contain many measuring points. Average, MKT, minimum, and maximum temperatures are calculated for the Asset.
What is a "Measuring Point"
Measuring Points collect the measured data from a sensor. The Measuring Point is given a name that represents the location of the temperature, for example, "Shelf A1". A temperature logger measures the temperature and uploads the data to the measurement point. The logger can be replaced without losing the measurement history.
What is an "Event"
In FMv2, an Event is created when the temperature is outside the set limits or out of bounds, i.e. the temperature is too low or too high. When the temperature logger senses that the temperature is outside of the set limits, the system creates an Event to identify abnormal temperature. The Event is Ongoing or Active while the temperature is out of bounds.
What is "Aggregation"
An Aggregation is a group or mass of distinct or varied things. In the FMv2 system, an Aggregation that the same type of Events is merged together into one Event, for example, if all loggers inside a freezer measures too high temperature and all of them would activate an Event. In the FMv2 sytstem, these Events would merge into one Event. This is done to reduce the number of alerts that one can receive.
What is "Propagation"?
When the system creates an Event, the Event can propagate up the Entity Tree. For example, there might be a person responsible for temperature monitoring in a single warehouse within one region. This person might subscribe to high severity temperature excursions at the Collection Level. When one measuring point creates a High-Temperature Event, the Event will travel up the Entity Tree, display the Event on the Collection Level, and send out an alert to users who have subscribed to them.