Category: Smart Energy domain

No comments

New data models on Energy

  By ,

There are two data models coming for the Energy domain (ACMeasurement and InverterDevice). You can submit an issue on it if interested.

Once harmonized with the contributors and checking the interaction with other data models they will be incorporated into the Energy repository inside the domain of Smart Energy.

ACMeasurement

The Data Model intended to measure the electrical energies consumed by an electrical system which uses an Alternating Current (AC) for a three-phase (L1, L2, L3) or single-phase (L) and neutral (N). It integrates the initial version of the data Modem [THREEPHASEMEASUREMENT], extended to also perform single-phase measurements. it includes attributes for various electrical measurements such as power, frequency, current and voltage.

Additional Information about Attributes : For some attributes such as current and voltage the value is a structured value with properties for the Single-Phase (L) or three different phases (L1, L2 and L3). For some measurements such as the different power types (active, reactive and apparent power) there is an attribute for the total from all phases. The rules are defined as below : – Three Phase – Total = L1 + L2 + L3 – Single Phase – Total = L.

For most of the attributes, there are various ways they can be actually measured. For this purpose the measurementType Meta Data Attribute can be used. It can have the following values:

When using the values [average, rms, minimum, maximum], another metadata attribute called measurementInterval should be used to give the length of the measurement period in seconds. Also the Meta Data timestamp attribute should be the end time of the measurement period.

InverterDevice

The Data Model is intended to describe the mechanical, electrical characteristics of an Inverter according to DC – Direct Current Information supplied as input and AC – Alternating Current Information returned as output.

Additional Information about Data Model: This Data Model can be used directly as the main entity to describe the device [INVERTER] or as a sub-entity of the Data Model [DEVICE] using a reference by the refDevice attribute.

No comments

New harmonization repository

  By , , , , , , , , ,

In order to provide a more transparent and participative approach to the creation and maintenance of data models, here you can see the three stages for a usual data model to be part of the official list of data models.

1.- Pending is the ‘wild’ zone where developers share their thoughts and create their data models. When finished (ready) they can create a PR on the right Subject repository.

2.- Harmonization is the repository for those new accepted models while they are fine-tuned or completed

3.- Subject means the repository in which the data model is officially published. Once there they are versioned when necessary.

Pending Harmonization Subject
Control of contributions No Yes Yes
Scripts for checking No Yes (specific) Yes (only acceptance and on update)
Code inside json schema No Harmonizing Local standard

Global standard
Versioning No No Yes
Managed Each contributor Contributor + SDM control SDM control
In domain No No Yes
Accept issues Yes but not managed Yes Yes (Here the open ones)
First Access Anyone
  1. Anyone previous pending acceptance
  2. Members direct
 N/A

SDM: Smart Data Models initiative

No comments

Connection with European open data portal

  By , , , , , , , , ,

The European open data portal is possibly the biggest open data portal in the world with more than one million free datasets coming from 36 countries.

One of the mechanisms to access its data is the use of the standard of DCAT-AP standard 2.0 which defines its catalogue of resources.

Image

In the repository pending there are two data models, in progress to connect a dataset and a distribution as an additional resource by using NGSI. The idea is to create a script to map this resource into NGSI.

No comments

Updated the csv examples

  By , , , , , , , , ,

Every data model has a directory with examples of the payloads (json and jsonld) in key-values and normalized formats.

But it also includes examples of csv that it could help to connect the data models for other platforms.

Now, these examples are re-created automatically once a day.

The naming convention for these examples are the same name of the original payload plus a .csv suffix.

An example for the Battery data model examples.

Best.

No comments

Searchable descriptions of data models

  By , , , , , , , , ,

In the upper menu (option Search descriptions) there is a searchable database of the descriptions for all the properties across the different data models.
Try it out here.

This DDBB is updated daily.

No comments

Working with https and improvement in the issue form

  By , , , , , , , ,

1.- It is just a technical improvement but now you can access everything in this site with https://data-models.fiware.org.

2.- The issue form has also been improved with new options but simplified structure.

Check it out and please report any issue.

Best

No comments

New version of contributors file

  By , , , , , , , , ,

Every subject had a file named CONTRIBUTORS.md which compiles all contributors to the different data models in this subject. However, from the point of view of the management, it was not a structured format. Due to this, it is going to be replaced with a new file named CONTRIBUTORS.yaml with the same info but structured so we could manage properly and answer questions like:

  • How many contributors collaborate in this subject?
  • How many subjects are being contributed by this person?
  • What organisations are contributing to the initiative?

Now there is also a field for allocating comments.

The format is friendly enough to be simply edited but at the same time, it can be automatically processed.

Next week CONTRIBUTORS.md will be removed from the different repos.

No comments

Updated the attributes search data base

  By , , , , , , , ,

In order to create a new data model is always interesting what others have done in order copy and to maintain interoperability.

That’s why we have available a database with all attributes and enumerations across all data models.

Now it’s updated daily and the number of occurrences is also available.

No comments

What’s is your opinion of the new specification model?

  By , , , , , , , , ,

We are testing a potential new format for the specification that

1) makes easier for people to read the specification

2) provides additional utility to be connected with other platforms making NGSI more compatible

Could you check these two new specifications Building, BuildingOperation compared with the old two Building, BuildingOperation and gives us your opinion?

(once in, click on the name of the object for deploying all the content)

[cf7form cf7key=”new-specification-format”]

The actual new specs are here without viewer (building, building operation) what you see above is generated automatically from the yaml specs.

What’s the idea behind adopting yaml specifications? To allow multiple evolutions (automatic multilanguage spec, integration with other platforms, etc)