Fiware Data Model Usage - Device Functioning Messages

asked 2018-01-18 15:53:12 +0100

tomsluyts
1 ●1 ●1 ●1

Hi there,

We are currently looking into the implementation of the Fiware data model. First trial would be waste baskets that send data.

They have two types of messages at source.

One is related to fillingLevel, etc -- that one is easy and nicely fits into the WasteContainer data model.

The second type are "alert" and are related to the functioning of the device itself, stuff like batterylevellow, or no_network or something like that.

Our idea is to put that data in a "device" entity with a pointer to it's WasteContainer entity, but is that the right way to go about it? WasteContainer itself doesn't look like the right fit, on the other hand we're also not describing device in the sense of sensors either...

So config, status and alarms would go into the device, measurement from a more business perspective into the entity.

We want to get our model right from in the beginning, so alle help is appreciated!

edit retag flag offensive close merge delete

add a comment

0

answered 2018-01-23 11:43:10 +0100

jmcantera
347 ●21 ●25 ●30

hi,

Good question. You can certainly use a Device entity linked to a WasteContainer entity and use the Device entity to store battery level, configurations and the like.

For certain device conditions that should be alerted, why don't you use the Alert entity type?. The Alert entity type could be extended to cover new Alert categories and subcategories. If you opt for that approach a Pull Request that extends the current Alert data model (with categories and subcategories for alerts originated in devices) will be more than welcome.

Thanks, best