Details
-
Type:
extRequest
-
Status: Closed
-
Priority:
Major
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
Labels:None
Description
Hello,
My name is Rodrigo Tirapegui and I am an electronic engineer working at
Smartmation S.A., a local Argentine company dedicated to developing
solutions for public street lighting.
We have just developed a street light controller product based on NBIoT and
LoRa technologies, and a street light control cabinet, based on NBIoT
technology too (https://www.smartmation.com/).
Both products are intended to monitor and control the public lighting
infrastructure, detect irregularities in operational or consumption
malfunctions, as well as compiling consumption and saving reports.
We are currently evaluating making the products "FIWARE-Ready", by allowing
them to communicate indirectly (using an IoT Agent) with the FIWARE Context
Broker.
Since devices use a proprietary communication protocol, we think the
best approach to commit the objective is to develop our custom FIWARE IoT
Agent to deal with southbound communications from the FIWARE Context Broker
to the devices, and also translate northbound communications into NGSI
commands.This way, integrators should be able to receive measurements and
send commands from/to devices through NGSI API.
In this sense, I have had a look at "FIWARE Street Lighting Data Models" (
https://github.com/smart-data-models/dataModel.Streetlighting), which I
consider partially represent the products developed: as they are both
sensors and actuators, I consider that a greater number of data models are
necessary to be able to represent them in a complete way.
So the question that arises is whether FIWARE has a greater number of
standard data models to describe both products; for example to describe the
mandatory commands that must be supported (turn on, turn off, set dimming
level, configure switching points calendar, etc) or the way to inform
reports (consumption, alarms, switching point timestamps, etc), similarly
to other standards (for example, Zigbee through the "Zigbee Cluster
Library" document).
If the answer to the previous question is no, would it be correct to define
by myself the commands set and all the necessary data models that the
products should use, expecting them to be incorporated later as official
"FIWARE Data Models" under the
"Street Lighting domain"?
Thanks!
*Rodrigo Tirapegui · Electronic Engineer *
rtirapegui@smartmation.com <fgargiulo@smartmation.com> · Mobile: +54 911
3450 2229
Arribeños 3619 Piso 10 · (C1429BKQ) · CABA · Argentina
Phone: +54 11 5263 0307 · *www.smartmation.com
<http://www.smartmation.com/>*
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
fiware-tech-help mailing list
fiware-tech-help@lists.fiware.org
To unsubscribe from fiware-tech-help mailing list, go to the information page of the list at:
https://lists.fiware.org/listinfo/fiware-tech-help
[Created via e-mail received from: Rodrigo Tirapegui <rtirapegui@smartmation.com>]
Activity
First of all thanks for the mail which is quite interesting. Having
said that let me share some of the existing initiatives 1) It is not
only in the streelight domain detected the need that some of the
sensors or element are also active elements (actuators), this would
lead to some common elements for several data models regarding this
ability of been active.2) Currently it is not decided what option
shoudl face this. there are already several availablea) Include a
common actuator parameters in every data model which is possibly to
work like an actuator, like the location commons or GSMA commons
already available at commons-schema.jsonb) To create separate data
models for the passive element (device) and for the active element
(actuator)c) To create the active properties of actuator differently in
each data model which needs itand possibly others
Currently we do not have the cross domain experience about which is the
right decision (if it is only one because it could be several), so my
recommended course of action would be to create a directory in the
directory incubated where most of the coming data models are being
created and once you got something complete and you test it in real
case scenario, then it could be considered for official adoption.
If you agree we could create that directory. Bear in mind that the data
model for this element is also being developed by IUDX (the Smart city
association in India) and therefore some compatibility issues could be
raised. I'd need you to give me a github user for give your the right
permissions on the repo.
Best
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
fiware-tech-help mailing list
fiware-tech-help@lists.fiware.org
To unsubscribe from fiware-tech-help mailing list, go to the information page of the list at:
https://lists.fiware.org/listinfo/fiware-tech-help
This guy made the same request by mail and I've answered.
I'll paste the answer on JIRA as well.